Casino game certification-readiness checklist

What does certification-ready mean?

Certification-ready means the product scope, intended market, applicable requirements, build, evidence, and owners are sufficiently controlled for an external testing body to begin useful work. It does not mean that a developer can guarantee approval or that one report applies in every jurisdiction.

Start by naming the exact product, entity roles, intended distribution model, target jurisdiction, responsible authority, selected laboratory, and version to be evaluated. Record each unresolved point as an assumption with an owner and due date.

Is the product scope frozen enough to test?

A test candidate needs an identifiable boundary. List the client, server or RGS components, mathematics, configuration, integrations, third-party libraries, supported devices, languages, and operational dependencies included in the submission.

• Assign a unique version and immutable source-control reference.
• Record build instructions, dependencies, checksums, and deployment configuration.
• Separate test-only tools and data from the release candidate.
• Name the owner who can explain every included component.
• Document exclusions so an omitted dependency is not mistaken for a tested component.

Is the mathematics evidence reproducible?

The mathematics pack should let a qualified reviewer reproduce the intended game behavior. Include the rules, paytable, probability model, return calculations, prize distribution, feature logic, rounding behavior, limits, and simulation method that apply to the submitted configuration.

Do not treat a simulation result as a substitute for the underlying model. Record the code version, random seed policy, sample size, configuration, output, reviewer, and reconciliation between calculated and simulated results.

Can the team trace requirements to evidence?

A requirements matrix should map each applicable requirement to the implementation, verification method, evidence location, status, and owner. The applicable source may be a jurisdiction’s rules, a laboratory intake requirement, a referenced technical standard, or a contractual integration requirement.

Evidence area	Minimum useful record	Readiness warning
Requirements	Source, version, applicability decision, owner	A generic checklist with no jurisdiction
Build	Source reference, dependency lock, instructions, checksum	A binary that cannot be reproduced
Functional tests	Requirement, procedure, expected result, observed result	Screenshots without traceability
Defects	Severity, affected version, disposition, retest evidence	Informal fixes outside change control
Submission	Inventory, contacts, delivery record, accepted exceptions	Files sent through untracked channels

Are environments and integrations controlled?

Record how the test environment differs from production and who controls each interface. Include authentication, encryption, time handling, error behavior, interrupted sessions, recovery, logging, configuration, and test-data handling for every material boundary.

If the game connects to an RGS, aggregator, platform, wallet, identity service, or reporting system, agree which side produces each test result. The RGS, aggregator, platform, and operator explainer helps separate those responsibilities.

Is the change process ready for findings?

External testing usually creates questions and findings, so readiness includes the repair loop. Define defect severity, triage ownership, permitted changes, regression scope, evidence updates, rebuild rules, and how a corrected version returns to the laboratory.

For programs where Wizards may fit, review its certification and compliance support alongside independent laboratories and other qualified advisers. GEN’s relationship with Wizards is disclosed; the responsible authority or laboratory retains its own decision.

What should the readiness review produce?

The review should produce a signed scope, applicable-requirements register, evidence index, reproducible candidate, open-issue list, submission owner, and stop/go decision. If a critical jurisdiction, product boundary, mathematics artifact, or build-control question remains unknown, resolve it before paying for avoidable external test cycles.