Remote lab submissions fail more often on missing paperwork than on math errors. After shepherding dozens of Canadian titles through GLI and BMM, we standardised a documentation pack operators can forward without translation layers.
Core artefacts every submission needs
- Signed par sheets with version hashes matching the submitted binary.
- RNG technical description plus recent statistical test output.
- Seed-change and deployment procedures with named approvers.
- Client build manifest listing JS bundles, assets and config flags.
Evidence operators forget to include
Screen recordings of autoplay interruption, reality-check flows, and max-bet enforcement are now routine requests. We capture them in a single MP4 per jurisdiction pack so labs do not re-film on different devices.
Version discipline saves retest fees
Any post-submission change — even a typo in help text — gets a change record with impact analysis: math, presentation, or compliance-only. Labs price retests by category; marking compliance-only updates correctly has saved our clients thousands in CAD on recent launches.
Submission calendar and lab liaison
Book lab slots before art lock when possible — peak seasons queue four to six weeks. Assign one internal owner who speaks both engineering and compliance so questions do not bounce between teams with contradictory answers. We keep a shared spreadsheet of open queries, evidence links, and due dates visible to the operator as well as the studio.