The Gambling Commission website uses cookies to make the site work better for you. Some of these cookies are essential to how the site functions and others are optional. Optional cookies help us remember your settings, measure your use of the site and personalise how we communicate with you. Any data collected is anonymised and we do not set optional cookies unless you consent.

Set cookie preferences

You've accepted all cookies. You can change your cookie settings at any time.

Skip to main content


Testing strategy for compliance with remote gambling and software technical standards

Requirements for the timing and procedures for the testing of remote gambling products.

4 - Annual games testing

View and download the annual games testing audit template.

4.1 The requirement for an annual games testing audit applies to those licensees that hold a gambling software licence and a remote bingo operating, remote bingo (game host), remote casino, remote casino (game host), remote general betting (standard) (virtual events) or remote betting host (virtual events) Generally this will include those licensees that have assumed responsibility for games testing (for example, from a software supplier or content developer).The audit must be carried out by a Commission approved test house and will:

  • check a randomly selected sample of major and minor updates (to confirm that they did or did not require external testing). Section 3 and Annex A provide further detail of major/minor updates
  • confirm that licence holders have adhered to required change controls (applicable elements as contained in Section 6 of the testing strategy)
  • confirm the list of games made available to consumers served in reliance of a Commission licence
  • confirm licensees have in place effective live RTP monitoring processes.

4.2 The previous requirements set the minimum scope of the audit. The Commission may broaden the scope in certain cases to address specific concerns, for example, evidence of non-compliance with other aspects of the RTS and LCCP.

4.3 Where issues are identified by the audit these may be corrected by licensees, however the identified and corrected issues must still be included in the final audit report to the Commission.

4.4 The results of the audit must be counter-signed by the relevant PML holder or specified person and submitted to the Commission directly or via the approved test house that conducted the audit. It remains the responsibility of the licence holder to ensure that the audit report is submitted to the Commission. The final audit should be submitted by using eServices (opens in new tab).

4.5 The audit submission dates will be staggered in order to avoid all audits being performed within a similar period and therefore putting pressure on test houses. Licensees will be assigned to a submission pool, as illustrated in Table 2 as follows. The Commission may be able to accommodate certain requests from licensees to be assigned to a specific pool, though this cannot be guaranteed if the allocation of the preferred audit submission pool is oversubscribed.

4.6 The Commission expects those licensees that are exempt from the annual audit requirement to seek assurance that games and updates have been tested in accordance with the testing strategy prior to release.

Table 2: Annual games testing audit submission pools

Submission pools Audit period
(previous 12 months)
Deadline for submission of annual audit to Commission
Pool 1 1 July – 30 June following year Four weeks after audit period end date
Pool 2 1 October – 30 September following year Four weeks after audit period end date
Pool 3 1 January – 31 December full calendar year Four weeks after audit period end date
Pool 4 1 April – 31 March following year Four weeks after audit period end date
Previous section
3 - Procedure for testing
Next section
5 - Live RTP monitoring
Is this page useful?
Back to top