Lottery Operator KPI Framework: Definitions, Formulas & Dashboard
A useful lottery operator KPI framework connects commercial performance to ticket, wallet and settlement records. Start with agreed definitions and reliable reconciliation, then build acquisition, retention and service measures around them. A dashboard should explain what happened, who needs to act and whether the underlying data is complete. This framework is for operators evaluating or […]
A useful lottery operator KPI framework connects commercial performance to ticket, wallet and settlement records. Start with agreed definitions and reliable reconciliation, then build acquisition, retention and service measures around them. A dashboard should explain what happened, who needs to act and whether the underlying data is complete.
This framework is for operators evaluating or improving a lottery operation. It does not prescribe industry benchmarks or present WhiteLotto customer results. Use the operator readiness library to connect measurement to your operating model.
Create a metric dictionary before choosing targets
Every KPI needs a business owner, source, formula, reporting currency, time window and inclusion policy. Define whether the period follows purchase time, draw time or settlement time. Keep test accounts, cancelled tickets, void transactions, bonuses and refunded amounts explicit. Changing a definition should produce a versioned change, not an unexplained improvement on the dashboard.
| Measure | Working definition | Important boundary |
|---|---|---|
| Ticket sales | Sum of accepted ticket stakes, with cancellations and refunds reported separately. | Not deposits, wallet balance or profit. |
| Settlement completeness | Tickets with completed settlement ÷ tickets due for settlement. | Use a draw cohort whose results are final. |
| Payment completion | Completed funding operations ÷ eligible initiated operations. | Deduplicate retries; separate pending and declined outcomes. |
| Verification completion | Applicants completing the required journey ÷ applicants starting that journey. | Show pending cases and time to decision separately. |
| Returning-player rate | Players active in the current period from a defined previous-period cohort ÷ eligible players in that cohort. | Use consistent activity and eligibility definitions. |
| Acquisition cost | Attributed acquisition expenditure ÷ newly acquired players meeting a defined activation event. | Specify attribution window and whether agency/affiliate costs are included. |
| Unreconciled value | Value of unresolved differences across matched payment, wallet, ticket and settlement records. | Report age and direction; netting can hide problems. |
| Support resolution time | Elapsed time from case creation to agreed resolution, segmented by case type. | Distinguish waiting time, reopenings and unresolved cases. |
Separate sales, contribution and cash
Do not label ticket sales as revenue without confirming the contractual and accounting treatment. Draw ownership, jackpot resale and other models can produce different economic boundaries. Agree those definitions with finance before comparing products or providers.
A management contribution model can be expressed as recognised operating revenue minus directly attributable supplier, prize-risk, payment, bonus and variable service costs. Keep accounting recognition and actual cash settlement distinct. The pricing and TCO guide helps expose costs that are absent from a headline revenue-share percentage.
A synthetic dashboard example
Suppose a closed-draw test cohort contains 200 accepted tickets, with 198 fully settled and two unresolved. Settlement completeness is 99%, but the two exceptions still need amounts, reasons and an owner. A headline percentage is not permission to discard them. If a separate retention test cohort has 120 eligible players and 30 return, the returning-player rate is 25%. These are illustrative calculations, not performance targets or observed platform results.
Use three linked views rather than one score
- Commercial: acquisition, activation, repeat activity and product contribution by consistent cohorts.
- Operational: pending tickets, settlement gaps, payment exceptions, verification queues and support ageing.
- Technical: request volume, errors, latency and resource saturation, linked to affected business journeys.
Google’s SRE monitoring guidance explains the four technical signals of traffic, errors, latency and saturation. Those signals complement lottery business measures; healthy infrastructure alone does not prove that tickets and funds reconcile.
Segment by product, channel, locale and provider when the volume supports a meaningful comparison. Use aggregate or appropriately controlled data rather than exposing names, emails or identity documents on a general management dashboard.
Give each exception a response
Define which owner investigates a deteriorating measure, what evidence they inspect and when they escalate. Reconciliation breaks, suspected duplicate financial effects and delayed settlement need operational handling, not just a red chart. Align these responses with the SLA and support requirements.
During UAT and go-live acceptance, use known synthetic transactions to verify the numerator, denominator and underlying export. Include the KPI dictionary and reporting access in your provider evaluation checklist.
Lottery KPI FAQ
Should every operator use the same benchmark?
No. Product mix, market, cohort, channel and cost boundaries differ. Establish a trustworthy baseline before setting a target for your operation.
Can deposits measure lottery sales?
No. Funding an account and purchasing an accepted ticket are different events. Reconcile both and report them separately.
What should we bring to a reporting discussion?
A metric dictionary, an anonymised sample layout and the required decision owners. Do not send player exports or credentials.
Review the platform overview and bring your reporting requirements to WhiteLotto. CONTACT.