Skip to content
2,183 standards indexed across 19 jurisdictions View the Atlas
Daily news + multi-week series Browse all insights
8 tools live Roadmap
AGLC · Standards Explainer 7 min read Oct 27, 2026

AGLC Game Certification and Change Control: How Approval Works

Alberta has no game-by-game approval queue. See how ATF certification, change categories and the five-day emergency fix rule decide your AGLC go-live.

Matt Denney

By

Founder, gamingcompliance.io · 15 yrs in iGaming compliance

Published Oct 27, 2026 7 min read Filed Technical Standards

AGLC does not run a game-by-game approval queue for iGaming content. Under the Standards and Requirements for Internet Gaming (SRIG, issued 14 January 2026, version dated 17 March 2026), the gate is certification by an AGLC-registered Accredited Testing Facility (ATF) before any game, random number generator or bet-processing component is deployed in Alberta. The rules apply to Registered Operators and to registered Goods or Services Suppliers that run critical gaming systems.

This article is based on a reading of the SRIG and the AGLC Internet Gaming Go-Live Compliance Guide (January 2026). Market launch was set for 13 July 2026, and the requirements below are stated as of those document versions.

What does “product approval” mean in Alberta?

Alberta does not use the label “product approval” in the SRIG. The operative requirement sits in the SRIG’s certification by Accredited Testing Facilities provisions (Section 4.12), which require certification for all games, random number generators and components of iGaming systems that accept, process, determine the outcome of, display and log player bets. The SRIG states that this includes, but is not limited to, slot games, table games, Sport and Event Betting, poker and other card games.

For live dealer games, certification extends to physical random number generators with electronic elements. The SRIG names physical roulette wheels, physical dice tables and card shufflers with electronic components.

The commercial gate is separate. The Go-Live Compliance Guide states that AGLC registration and completion of its requirements “do not authorize gaming operations”, and that authority lies with Alberta iGaming Corporation (AiGC), which holds the operating agreements. A supplier can hold a clean certificate and still have no route to market until the operator’s AiGC agreement is signed. Our earlier analysis of the AGLC SRIG framework covers the dual-authority structure.

Source: AGLC, Standards and Requirements for Internet Gaming, Section 4 (Certification by Accredited Testing Facilities), issued 14 January 2026, AGLC Internet Gaming Go-Live Compliance Guide, January 2026.

What must an ATF certificate contain?

The SRIG limits who may certify and what the certificate may say. Certifications must be issued only by ATFs registered by AGLC, must be in place before deployment in the Alberta market, and must not contain a limitation on AGLC’s use of the certification or purport to disclaim AGLC’s use of it. An ATF may not issue a certification that is contingent on future changes to the technology. It may issue one that specifies features that must be turned off or disabled for the technology to comply.

The certification instrument must carry four items according to the Go-Live Compliance Guide: the legal name of the AGLC-registered ATF, the legal name of the operator or supplier requesting certification, the date of issuance, and a unique identifier for AGLC tracking and follow-up.

Certification is needed only against the Standards relevant to games, random number generators, remote gaming servers, and sport and event betting systems under test. AGLC states that final determination of applicable Standards occurs after review of the specific technology. ATFs must add the SRIG to their ISO accreditation scope within one year of registration as a supplier in Alberta, and must suspend certifications and notify the affected supplier when they identify issues that materially affect a certification.

How are post-launch changes classified?

The SRIG and the Go-Live Compliance Guide define three modification categories. Re-certification is required when a modification, or a later discovery of an undetected issue, affects critical gaming system integrity, fairness or security, or compliance with the Standards.

AGLC modification categories (SRIG and Go-Live Compliance Guide, as of 17 March 2026 SRIG version)
Category Description Deployment ATF action
Non-Regulatory Cosmetic or minor changes unrelated to the Standards, such as bug fixes and language updates No recertification, confirm the change is non-regulatory None
Regulatory Changes affecting compliance or addressing regulatory concerns without urgency Certify before deployment Full certification
Regulatory Fix (Emergency) Urgent fixes for live issues affecting integrity or the Standards Deploy immediately Submit within 5 business days of release

The submitting party must keep records of testing and ATF certification and produce them to AGLC on request. The classification call sits with the registrant’s own change process. The SRIG requires Registered Operators to have policies and procedures in place to effectively mitigate risks and threats, and requires registered Goods or Services Suppliers to make known any material threat or risk to the security or integrity of the gaming systems they supply.

Registered Operators and suppliers running critical gaming systems must also give AGLC an annual Technology Compliance Confirmation. For operators the scope covers the whole technology solution deployed for Alberta, including the integration of third-party systems, though not the internals of third-party suppliers’ technology, which their own confirmations cover. The Go-Live Compliance Guide also asks registrants to describe the mechanisms that ensure installed software is ATF certified and that the integrity of deployed software is verified.

Can Ontario certifications be reused?

According to a published summary of AGLC’s transition guidance, AGLC said it would accept AGCO game certifications where they correspond to what was approved and implemented in Ontario and the issuing ATF is fully registered in Alberta. The same summary states that all game certifications must be Alberta-certified and filed with iGaming Compliance 90 days after Alberta market launch. Counted from 13 July 2026, that window closed on about 11 October 2026 by our calculation.

Suppliers still relying on Ontario paperwork after that date should confirm their position directly with AGLC iGaming Compliance. AGLC and AGCO also maintain separate notification logic. The Alberta notification matrix is framed as a standards-based judgment tool, while Ontario’s reads as a more granular versioned control artifact, and the two need separate routing, review and owner logic even where themes overlap. The AGCO and AGLC comparison sets out the wider differences.

What slows go-live and release timelines?

AGLC does not publish a rejection checklist. The following delay triggers are an analytical reading of the SRIG and Go-Live Compliance Guide text, not an AGLC list.

A certificate from an ATF that is not registered with AGLC does not satisfy the SRIG, whatever its standing in another province. A certificate that is conditional on future modifications, or that disclaims AGLC’s reliance, fails the SRIG wording directly. An instrument missing the ATF name, requesting party, issue date or unique identifier cannot be tracked by AGLC.

Scope gaps also create delay. A platform submission that omits the random number generator, the remote gaming server or the electronic components of a live dealer table leaves part of the bet-processing chain uncertified. Where a certificate depends on features being disabled, the production configuration should evidence that they are switched off, which is analysis rather than an AGLC requirement.

Release classification carries the main post-launch exposure. Treating a Regulatory change as Non-Regulatory deploys uncertified technology. An Emergency fix must be submitted to an ATF within five business days of release, and a missed deadline breaches that SRIG requirement. Game behaviour changes must also respect the SRIG rule that terms governing play must not change during a game session unless the player is made aware before placing any wagers, and the rule that outcome probability must stay constant and independent of game history or player unless explained in the terms governing play.

“Terms governing play must not be changed during a game session unless the player is made aware of the change before the player places any wagers in the game.” (AGLC SRIG, Game Management)

Suppliers and operators should consult qualified Alberta counsel on how AGLC applies these categories to a specific release, and should raise unclear classifications with AGLC iGaming Compliance (iGamingCompliance@aglc.ca) before deployment. Incident notifications and regulatory submissions go to that branch, AML and financial reporting go to AiGC, and ownership or key employee changes go to the AGLC Due Diligence Unit.

Timeline: As of the 17 March 2026 SRIG version, emergency fixes may be deployed before certification but must reach an ATF for Alberta certification within five business days of release. Non-urgent regulatory changes must be certified first.

Key Resources

AGLC, Standards and Requirements for Internet Gaming (SRIG), Sections 2, 4 and 4.12, version dated 17 March 2026.

AGLC, Internet Gaming Go-Live Compliance Guide, January 2026, including the Accredited Testing Facility Certification section.

AGLC, Application Guide for iGaming Registration, and the AGLC Notification Matrix, available from aglc.ca.

Matt Denney

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.

Related coverage · also tagged Technical Standards

Browse all →

Technical Standards

Provably Fair vs RNG Certified: What UKGC, MGA and GSC Actually Accept

Nov 16 · 13 min read

Technical Standards

Gambling VAT and GST: Classifying Taxable Supplies in Your Platform

Oct 18 · 6 min read

Technical Standards

Reality Checks, Session Limits and Time-Outs: UKGC, MGA and AGCO Rules

Oct 17 · 11 min read