Resources

AN OPERATOR’S GUIDE

State Lottery Modernisation RFP: Technical and Operating Requirements

A state or institutional lottery modernisation programme needs more than a catalogue of software features. Procurement must connect the existing operating estate to a deliverable future service, with continuity, accountability and acceptance evidence.

Use this framework to prepare that technical and operating brief. The lottery provider evaluation checklist covers general supplier due diligence; this article focuses on institutional delivery boundaries. The authority’s procurement and regulatory advisers should define the applicable formal requirements separately.

Begin with outcomes and the current estate

Write the programme outcomes in terms that can be accepted: replace an unsupported component, connect channels, improve reporting access or introduce a defined product capability. Identify who accepts each outcome and which current services cannot be interrupted.

  • Inventory player and retailer systems, terminals, draw operations and reporting tools.
  • Identify existing contracts, interfaces, data sources and operational dependencies.
  • Record service windows, draw schedules and periods when changes are restricted.
  • Distinguish first-release requirements from optional future phases.

Describe the target operating architecture

Separate platform supply, hosting, operator processes and third-party services. Specify where the authority retains approval, configuration or data control, and which tasks a supplier is expected to perform.

Use the platform scope overview as a starting point for a module discussion, not as a substitute for a project-specific capability matrix. Require suppliers to identify what is standard, configured, customised, externally provided or excluded.

RequirementEvidence to request
Retail and digital channelsA channel map with sales, validation, payout and support ownership.
Draw and product operationsDefined result sources, cut-offs, settlement and exception handling.
Data and reportingField-level exports, access controls, report definitions and delivery timing.
Service managementNamed escalation, change approvals and handover responsibilities.

Specify interfaces as deliverables

For each interface, identify producer, consumer, data owner, identifiers, frequency, security boundary and exception process. Include terminal or retailer systems, payments, identity checks, finance, support and result distribution where applicable.

The lottery API integration guide helps structure these questions. Require an agreed test environment and sample data. An interface is not accepted merely because an endpoint exists; it must support the agreed business flow and failure cases.

Define continuity and recovery around lottery operations

State the service measures, exclusions, monitoring responsibility and escalation process that matter to your operation. Specify recovery targets and acceptable data loss for each critical service, with a method of demonstrating recovery.

NIST’s contingency-planning guidance provides a reference for prioritising information-system recovery. It is not a lottery certification or a claim about a supplier. Use the security, uptime and SLA checklist to request project-specific controls and evidence.

  • What happens to sales and open tickets during a service interruption?
  • Who authorises a pause, restart or change around a scheduled draw?
  • How are results, balances and outstanding claims checked after recovery?
  • What recovery exercise and operational record form part of acceptance?

Plan transition without treating data as a file copy

Document the data scope, source quality, reconciliation, access permissions and cutover sequence. Include outstanding tickets, balances, retailer records and unresolved cases where relevant. State who signs off the transition and what happens if a checkpoint fails.

The lottery platform migration guide covers the detailed transition workstream. In the institutional RFP, make that workstream a priced and accountable deliverable, including retention or decommissioning decisions owned by the authority.

Use evidence-based acceptance and handover

Request a responsibility schedule covering the authority, supplier and each third party. Price integration, support, change and exit work explicitly. Record dependencies and exclusions so that different bids can be compared on the same scope.

  1. Give each requirement an identifier, priority, responsible owner and acceptance method.
  2. Separate mandatory pass/fail gates from scored comparisons and optional enhancements.
  3. Demonstrate complete operational journeys, including an exception and recovery, with retained evidence.
  4. Agree issue severity, remedial responsibility and the conditions for accepting unresolved items.
  5. Require documentation, training, access handover and an agreed service transition before final acceptance.

Ask suppliers for a scoped response

A useful response includes the architecture, requirement-by-requirement matrix, evidence links, delivery plan, dependencies and named delivery roles. Ask which requirements are not supported today and what would be required to deliver them. Keep institutional suitability separate from unverified claims about customers, awards or certifications.

Compare full replacement with phased module deployment

An institutional lottery can evaluate a complete platform replacement or introduce selected modules alongside its legacy core. The procurement brief should ask bidders to explain both the final architecture and the temporary operating architecture. A phased route is not automatically simpler: it creates a period in which old and new components must agree on identities, transactions and responsibility. A replacement route concentrates more change into the transition. Compare the work and dependencies, not only the proposed launch date.

Use the platform module overview to define a phase with a demonstrable operating outcome. State what enters service, what remains in the legacy core and which interfaces become temporary. For retail phases, use the POS integration guide to identify the affected terminal journeys. Require each temporary connection to have an owner and an exit condition; otherwise it can become an unpriced permanent dependency.

Assign one system of record during coexistence

For each data domain, nominate the authoritative record and permitted writer at every phase. A copied customer profile, ticket or balance must not become an independent source merely because a new module displays it. Specify whether the new component reads, proposes a change or owns the final update. Keep this boundary explicit in the data control and export requirements.

Separate authority over new activity from responsibility for earlier records. A new draw service may handle future draws while historical tickets still require the legacy result reference. The draw and results integration guide helps identify the references that must remain connected through that split.

Phase-boundary decisions and evidence before transferring authority
Data domainTemporary ownership decisionPhase-exit evidence
Customer identityWhich system approves status and profile changes?The same customer remains traceable and only the authorised writer applies changes.
Accepted saleWhich system commits the ticket and purchase reference?Both views explain one accepted transaction without duplicate participation.
Draw and settlementWho owns open tickets before and after the boundary?Outstanding tickets retain their draw, result and settlement references.
Retailer accountWhich journal records channel obligations?Opening, movement and closing records reconcile across the agreed period.
Reporting and exceptionsWhich record governs a disputed difference?Differences have explanations, owners and an accepted treatment before the phase closes.

Make parallel reconciliation a phase-exit gate

Define what a parallel run means: processing a controlled copy, comparing reports or operating separate channels with a shared reconciliation. Do not let a comparison run issue a second live ticket or update the customer balance twice. Agree the same transaction population, business-day boundary and late-event treatment for both sides. Record differences at transaction level, assign resolution ownership and document which unresolved items prevent exit.

Connect the migration workstream to a phase-specific UAT acceptance gate. Retain proof that the new writer is active, the old writer is disabled where required and historical queries still work. Retirement needs its own evidence: open obligations have an owner, temporary interfaces can stop, and retained records remain accessible through the agreed operating process. Completing a module installation does not establish any of those outcomes.

Bring your proposed phases and legacy boundaries to WhiteLotto. CONTACT to discuss the platform scope and acceptance questions for institutional modernisation.

Technical reference

Discuss institutional platform requirements

Share your current estate, channel scope, continuity priorities and procurement stage. WhiteLotto can discuss the relevant platform scope and technical questions for an institutional project.

CONTACT

Wojciech Lysak is the Managing Director of WhiteLotto.com. LinkedIn