Casino content release: match the game version to its evidence

Content release evidence matrix

Complete the applicable regulator, test-house and contractual checks for the intended release. This matrix supports those decisions and does not replace them.

Create one manifest for the proposed release

Record the studio, title identifier, software build, maths or paytable version, offered RTP configurations, currencies, languages, device scope and dependent services. Attach the intended distribution route and market scope. The manifest should describe what will actually be deployed, not every option mentioned in a sales deck. Ask the studio and aggregator to identify which fields each controls. If the operator selects a configuration later, retain that selection as part of the final release record instead of relying on a generic title-level entry.

Locate the applicable testing responsibility

The Gambling Commission’s testing strategy sets out its approach to technical testing, including testing procedures, annual work, live RTP monitoring and in-house development, testing and release practices. Buyers should identify the applicable licence role and responsibilities before deciding what evidence to request. The strategy is specific to its regulatory context; it is not a universal checklist for every market. Use the current primary guidance and qualified compliance input to determine who must obtain, submit, maintain or act on the relevant evidence.

Gambling Commission — Testing strategy

Assess a change by its effect on fairness

The Commission’s Annex A distinguishes major updates that may affect fairness from minor updates that do not. It identifies random-number generation, scaling or mapping, and rules including software processing as fairness-related elements, with major updates requiring external retesting. Classification depends on the change and relevant judgement, not the size of the version-number increment. Ask for a documented assessment of each changed component and its affected games. A shared backend change can deserve attention even when the visible game artwork is unchanged.

Gambling Commission — Annex A: major and minor updates

Check the report and the testing scope

The Commission states that approved test houses have different testing scopes and that licensees must verify the selected house is approved for the work required. For the proposed release, obtain the relevant report reference and identify the tested components, version, assumptions and exclusions. Match those to the manifest. Our recommendation is to record unknown matches as unresolved rather than treating a supplier logo or an unrelated certificate as proof. Do not infer approval of an entire operator, distribution chain or territory from one game report.

Gambling Commission — Approved test-house scope

Test the integration that surrounds the game

A game report does not replace your acceptance of the integration boundary. Propose controlled tests for launch identity, supported currency and configuration, wallet debits and credits, reconnect, duplicate callbacks and an interrupted round. Define the expected customer and ledger outcome with the relevant owners. Save the manifest reference with every observation. When a game launches successfully but the wrong configuration is selected, the smoke test has found a failure; it has not established that the intended commercial product is ready.

Design withdrawal and rollback around existing rounds

Rehearse how the distribution chain stops new launches while keeping already accepted obligations identifiable. Ask who can disable a title or configuration, how the instruction propagates and who resolves an open round when the usual service is unavailable. A rollback should name the authorised destination version and how outstanding references remain interpretable. Record any dependency that prevents a clean reversal. Test with synthetic rounds and the approved sandbox procedure; do not attempt an improvised production rollback to prove a procurement claim.

Release with a small, explicit decision record

Use the manifest, applicable test evidence, integration observations and unresolved exception list as the basis for approval. Name the responsible decision owner, exact approved scope and any conditions. Reopen the assessment when a material version, configuration, distribution or market assumption changes. For ongoing operations, agree who receives anomalies and source updates and who can pause distribution. The supplier worksheet can hold these questions across candidates, while the manifest remains the authoritative record for one concrete release.