Operator Console

Run the whole operation from one console.

One console. The actual job. Setup, competitions, draws, players, prizes, money and rules, in one operating environment rather than a collection of disconnected screens and plugins.

The useful dashboard is the one that lets you finish the job.

Operator Console
  • Setup
  • Competitions
  • Draw room
  • Players
  • Fulfilment
  • Finance
  • Compliance
  • Campaigns
  • Settings

Launch readiness

  • Brand applied
  • Legal pages published
  • Compliance controls set
  • First competition scheduled

Not ready to go live. One required step is still open.

Competition lifecycle

  1. Draft
  2. Scheduled
  3. Live
  4. Closed
  5. Drawn
  6. Fulfilled

Illustration of the console structure. Real screenshots will replace it.

Onboarding

From signup to live, without a server project.

Live Self service signup and guided setup. The operator environment is provisioned by the platform: storefront, legal pages, mail sender and an isolated runtime.

  1. Create operator

    Self service signup.

  2. Add brand

    Colour, accent, logo, font, corner radius.

  3. Complete setup

    Legal pages, controls, first competition.

  4. Pass readiness

    Missing requirements block launch.

  5. Go live

    Only when the checks pass.

Because finding out after launch is a rubbish onboarding strategy.

Readiness gate

Know when you are ready.

Beaver's readiness checks stop a competition site going live while required setup is still missing. The console shows what is outstanding, rather than letting you find out from a customer.

Live Readiness checking and gated go live.

Boab with a magnifying glass and a launch ready checklist.

Inside the console

Everything the job actually involves.

  • Builder

    Build competitions

    Set the prize, price, ticket pool, purchase caps, schedule, imagery and competition details.

  • Lifecycle

    Move them through their life

    From draft to fulfilled, in one place. Draft competitions stay out of the public storefront until they are ready.

  • Draw room

    Run the draw

    Commit the entries, execute the draw, publish the result and make it verifiable. Draw processing runs every minute.

  • Players

    Manage players

    Account information, entries, spending history and relevant account activity, including protection state.

  • Fulfilment

    Track the prize

    Record what is owed, age checks, dispatch, delivery evidence and fulfilment timing.

  • Finance

    See the money

    Revenue, VAT, margin and platform billing in the same operating environment.

  • Compliance

    Control the rules

    Spend caps, breaks, exclusion and suppression, with locked floors from Compliance Packs explained in the console.

  • Campaigns

    Talk to customers

    Build and send campaigns to real audiences, inside marketing and protection rules.

  • Settings

    Change things on the record

    Settings are managed centrally. Sensitive changes record actor, reason, before and after.

Draw room

Draws run on schedule. Proof comes with them.

Entries are committed before selection. The draw waits for the named public randomness, selects the winner and publishes the values needed to check it. A postal free entrant with no account can still be selected and contacted.

Draw roomChecked every minute
CompetitionEntriesStage
Example competition ACommittedAwaiting randomness
Example competition BCommittedDrawn, verifiable
Example competition COpenScheduled

Illustration of draw stages with example competitions.

Locked controls

Some settings should not be loosened.

Compliance Packs can impose minimum control levels that an operator cannot loosen. The console explains which pack imposed a locked floor, and why.

The control has a source. The source should be traceable.

Control settings

Player monthly spend limit

Locked floor. A Compliance Pack sets a minimum here. You can make it stricter, not looser. The console says which pack set it, and why.

Illustration of a locked control. Not the product interface.

Settings and audit

Who changed what, when and why.

Live Sensitive writes touching money, entries or marketing record the actor, the reason, and the value before and after.

And when you want the whole operating record out, the console exports players, orders, entries, draws and audit logs.

State tells you what was true. Audit tells you how it changed.

Export operating data
  • PlayersExport
  • OrdersExport
  • EntriesExport
  • DrawsExport
  • Audit logExport

Your data. Your file. Taken from the console, not requested from a supplier.

Illustration of the export list. The five data sets shown are the ones the console exports today.

Live walkthrough

See the console on the real product.

No theatre. No mystery demo environment.