GLI Certification Renewal: CMP, Annual Review and Re-Certification
GLI certification has no fixed renewal date. See how the CMP, annual full certification and Level 1 to 3 changes keep GLI-19 and GLI-33 approvals valid.
GLI certification does not lapse on a fixed renewal date. Under the GLI Change Management Program Guide v1.0 (published 6 May 2020, the version reviewed for this article in November 2026), a product operating under a Change Management Program (CMP) must be fully certified at least once a year, with a classified notification route for each change in between, unless the regulatory body specifies otherwise. Licensed operators and technology suppliers running a platform in more than one market must meet that cycle against every jurisdiction’s own rules, because each regulator sets its own standard and decides whether GLI’s default timings apply.
This explainer is for compliance and technical leads who already hold GLI-19 or GLI-33 certificates. Jurisdiction-specific application requires advice from qualified legal counsel. To understand how these standards apply across different regulatory frameworks, review the GLI-19 versus GLI-33 analysis for guidance tailored to your operating markets.
What maintenance consists of after initial certification
GLI-19 v3.0 (revision date 17 July 2020) at B.8.1 and GLI-33 v1.1 at B.8 both state that a change management policy is selected by the regulatory body for handling updates to the system and its components, based on the propensity for frequent system upgrades. GLI-33 adds that a risk-based programme typically categorises proposed changes by regulatory impact and attaches a certification procedure to each category. The independent test laboratory evaluates future modifications under whichever policy the regulator has chosen.
The CMP Guide supplies the baseline. Section 2.2 provides that, unless the regulatory body specifies otherwise, each product operating under a CMP must be fully certified at least once annually to the rules of every jurisdiction in which it operates, with formal certification documentation from an independent test laboratory with knowledge of the product. A hardship extension can be sought, and granting it is at the sole discretion of the regulatory body.
Section 2.3 provides that, unless the regulator says otherwise, the CMP policies and procedures must be approved by the regulatory body before the CMP is deployed and are then subject to audit. The notification routes below presuppose that approval.
How changes are classified and handled
Section 4 of the CMP Guide requires the technology supplier to classify every platform component against four criteria (confidentiality, integrity, availability and accountability) using a relevance code of 1 to 3. All components are recorded in a Critical Asset Register (CAR). Each change record then identifies the component by its CAR identifier and version, the person authorising the change, the person carrying it out, the anticipated release date and the level assigned. GLI-19 B.8 adds the date and reason for the change, a rollback strategy tested before release, an emergency change policy, named sign-off authorities and segregation of duties in the release process.
Section 5.1 sorts changes into three levels. The table below reflects CMP Guide v1.0 as reviewed in November 2026 and applies only where the regulatory body has not set different rules.
| Level | Definition (CMP Guide 5.1) | Examples given | Handling |
|---|---|---|---|
| Level 1, No Impact | No impact to regulated components | Backup software, adding or removing users, OS security patches, background images | Recorded in the change log with its level, no advance notice requirement in the text reviewed |
| Level 2, Low Impact | Low impact on platform integrity | Firewall rule changes, any change or addition of physical hardware, relocation of primary backup data | 3 business days’ notice to the regulator and certifying laboratory, passive approval if no testing request follows |
| Level 3, High Impact | High impact on regulated components or reporting | See CMP Guide 5.1.3 for the full list | Same 3 business day notice, regulator or delegated laboratory may require testing and certification before release |
Under section 6.1, the regulator, or the laboratory if delegated, can request testing and potentially certification of a Level 2 or Level 3 update before implementation. Where regulatory policy sets no additional rules and no testing requirement is notified within three business days, passive approval is conveyed. Where certification is not required before deployment, section 6.2 requires laboratory testing of the change within 90 days of its introduction to production. The licensee can keep releasing changes while that testing runs, and findings are reported through structures agreed with each regulator.
Section 6.3 allows Level 2 and Level 3 changes to be made immediately, without prior consent, in emergencies involving open threats or liabilities. Notice must reach the regulator as soon as possible and state why the emergency rule was used and all details then known. The regulator keeps the right to analyse each emergency change.
What triggers full re-certification rather than a CMP notification
A product needs full certification at the annual cycle, and before deployment whenever the regulator or its delegated laboratory requires certification of a Level 2 or Level 3 change. Changes to a game’s theoretical return to player percentage are a further flag, because GLI-19 treats the game as new for reporting purposes.
The annual cycle applies whatever the volume of notified changes in between. Section 2.2 of the CMP Guide ties it to each product operating under a CMP, so notified changes do not substitute for it.
Regulator-directed testing is the second trigger. Section 6.1 lets the regulator or delegated laboratory require certification before deployment of any Level 2 or Level 3 update. A change touching game outcome, reporting or other regulated components should be planned on the assumption that this will happen, since the Guide defines Level 3 by impact on regulated components or reporting. That is analysis, not a stated rule.
The third trigger is a change to the certified game’s mathematics. GLI-19 v3.0 does not itself prescribe re-certification for these changes, but the effect on records is explicit.
GLI-19 v3.0, A.6.1(b): “Each change to a game’s theoretical RTP percentage, including adding and/or changing progressive jackpot or incrementing jackpot increments, shall result in that game being treated as new for all reports and records.”
GLI-19 section 1.5.2 separately requires the configuration to be used in production to be communicated to the laboratory so a functionally equivalent test environment can be created. A production configuration that departs from the tested one falls outside what the laboratory evaluated.
Where a regulator has not adopted a CMP, the CMP Guide’s timings have no force and modifications follow that jurisdiction’s own submission rules. Written confirmation of the applicable route should be obtained from the regulator or the laboratory.
When a jurisdiction updates its standards
GLI-19 states that it can be adopted in whole or in part by any regulatory body, and GLI’s standards page confirms that each jurisdiction has authority to set its own standards, with many using GLI’s as a starting point. GLI-19 also records GLI’s policy of updating the document as often as warranted to reflect changes in technology and testing methods. Adoption of a new version therefore happens market by market, on each regulator’s timetable.
The sources reviewed set no universal transition rule for a platform certified against an earlier version. Because the CMP Guide frames the annual certification against “the rules and regulations of all jurisdictions operating therein”, the annual certification is the natural point at which a platform is tested against a newly adopted requirement. That is analysis, not a stated rule. Where a regulator publishes transition provisions, those control.
GLI lists “transfers of approval for existing iGaming certifications” among its digital testing services. Whether a transferred approval is accepted is a decision for the receiving regulator. The scope differences between the two main platform standards are covered in the GLI-19 versus GLI-33 analysis.
Regulators can also impose change management duties of their own on top of certification. As of November 2026, the AGLC Standards and Requirements for Internet Gaming (version dated 17 March 2026) require registered operators to have change management procedures reflecting industry best practices. All gaming system changes must be reviewed, risk assessed, tested, approved and verified with evidence linked to the change record, and emergency changes require a documented post-implementation review within two business days. The differences between the Ontario and Alberta frameworks are set out in the AGCO and AGLC comparison.
Key Resources
Source: Gaming Laboratories International, GLI-CMP Change Management Program Guide for Systems within the Gambling Industry, Version 1.0, published 6 May 2020, sections 2, 4, 5 and 6.
Gaming Laboratories International, GLI-19 Standards for Interactive Gaming Systems, Version 3.0 (17 July 2020), sections 1.5.2, A.6.1 and B.8.
Gaming Laboratories International, GLI-33 Standards for Event Wagering Systems, Version 1.1, Appendix B, section B.8 Change Management.
Alberta Gaming, Liquor and Cannabis, Standards and Requirements for Internet Gaming, 17 March 2026 edition.
Matt Denney
Editorial · gamingcompliance.io
Reads the primary source so you don't have to. Fifteen years inside iGaming compliance: operator, supplier, and crown-corporation lottery.