What a live-dealer studio audit can establish

A clear camera view is not an audit report

A live casino stream shows a selected view of a game. It does not show the full set of controls that make a studio independently auditable. For gambling covered by Great Britain's remote technical standards, RTS 17 deals with those operational controls: equipment, staff procedures, supervision, access and records. Its subject is broader than the quality of the picture reaching a player's device.

That distinction gives the reader a practical task. When a service says a live game is audited, identify the object of the audit, the standard it covers and the evidence supporting the claim. A statement about security, a game's software or studio operation may answer different questions. Treating all three as one approval removes the scope that makes an audit meaningful.

This article reviews the Gambling Commission's published documents. It does not inspect a studio, reproduce a confidential report or certify an operator. The comparison below is an evidence-reading method for online live-dealer customers. It leaves game rules and strategy to the game-specific publications and does not attempt to measure video delay.

Sources: Remote gambling and software technical standards (RTS) - RTS 17 – Live dealer studios; Testing strategy for compliance with remote gambling and software technical standards - Summary.

Follow the five operational areas in RTS 17

RTS 17's requirement is that live-dealer operations be fair and independently auditable. Its implementation guidance then names concrete things that can be examined. Equipment should be appropriate for casino use and monitored for integrity. Dealers should be trained against documented procedures, with training records retained. Supervision and sufficiently detailed surveillance should support checking whether the procedures were followed.

The guidance also addresses access controls for secure areas, equipment and consumables, and the maintenance of game logs and analysable event statistics. These areas concern the operation behind the broadcast. A player may see a dealer handling cards but cannot infer the training record, access history or integrity checks from that view alone.

For a document review, translate each area into an evidence question: what was inspected, over what period, and what record supports the finding? This is our analytical method, not an additional regulatory checklist imposed on customers. We do not mark an operator non-compliant because its public page lacks internal documents. The absence of public detail limits what this article can verify; it does not establish what records exist inside the studio.

Sources: Remote gambling and software technical standards (RTS) - RTS 17 – Live dealer studios.

Compare three different uses of the word audit

The Commission's testing-strategy summary separates live-dealer compliance inspections from security audits. It says applicable remote licensees need an annual independent security audit. Its live-studio passage instead addresses whether a relevant audit sufficiently covers RTS 17, including the possibility of relying on an audit performed for another jurisdiction. That passage does not itself impose a universal annual physical visit by the Commission to every studio.

The Commission also has a separate page for games-testing annual audit reports. It describes review by an approved test house, countersignature and annual submission within four weeks of the audit period's end. That administrative timetable should not be relabelled as the date of a studio surveillance inspection.

| Evidence category | Question it is positioned to address | Inference to avoid | | --- | --- | --- | | Live-studio compliance audit covering RTS 17 | Are the relevant studio operations independently auditable and covered? | Every individual round has a public approval | | Annual security audit | Are applicable security requirements assessed? | All dealing procedures were inspected in person | | Games-testing annual audit report | Was the relevant games-testing process reviewed? | A live studio was visited on the submission date |

This is a comparison of the published categories, not a claim that a particular business has supplied any of these reports to us.

Sources: Testing strategy for compliance with remote gambling and software technical standards - Summary; Games testing annual audit reports.

An overseas audit needs matching coverage

The testing-strategy summary says that a studio audit undertaken for another jurisdiction can avoid duplication where it sufficiently covers RTS 17. If there has been no relevant audit, one is required for the Commission's compliance purposes. The important qualification is coverage; the existence of a foreign document is not enough by itself.

Imagine a hypothetical report that addresses building security but says nothing about dealing procedures or game logs. Its overseas origin is not the issue. Its stated scope would leave obvious questions against the operational areas in RTS 17. Conversely, a sufficiently scoped report cannot be dismissed simply because another jurisdiction commissioned it.

This hypothetical comparison does not decide whether an actual report is acceptable. We have no report to assess and do not substitute our judgement for the regulator's. It explains how to read a claim such as internationally audited: request the relevant standard, studio scope and coverage, then keep any unanswered fields visible. A logo, country name or broad assurance phrase cannot do that comparison on its own. Nor does the regulator's recognition of suitable existing work prove that every overseas studio has been accepted.

Sources: Testing strategy for compliance with remote gambling and software technical standards - Summary.

Public disclosure has a documented limit

A useful primary example is the Commission's published response to a request dated 31 July 2023 about Evolution Gaming live-casino studios. The requester asked about physical inspections and inspection reports. The response confirms that the Commission holds information within scope, but withholds the requested detail under section 31 of the Freedom of Information Act, explaining concerns about regulatory assessment methods.

That is a dated disclosure decision, not a current inspection register. It supports neither the assertion that no studio was inspected nor a claim that a named studio passed a specific inspection on a particular date. We cannot turn information held into a description of information we have not seen.

For readers, the distinction matters because a missing public report can be interpreted in opposite, equally unsupported ways. One person may treat it as proof that there was no oversight; another may treat the regulator's involvement as proof of a clean bill of health. The response establishes the limit of public disclosure in that case. Our evidence table therefore records the response, its request date and its scope, while leaving unseen findings unknown.

Sources: Evolution Gaming live casino studios.

Work a hypothetical assurance claim through the records

Suppose a fictional live-game page says its studio is audited and links to a security certificate. The first step is to read the certificate's subject. If it covers information security, record that scope accurately. Do not expand it to include dealer training, surveillance coverage or physical consumables unless the document actually covers them.

Next, imagine the operator supplies a report summary naming a studio and RTS 17 but omitting the period reviewed. That adds useful scope information but leaves the time boundary unresolved. Finally, imagine a dated summary identifies the relevant operation and explains its coverage. That is stronger evidence for the particular assurance claim, but it still is not proof that every future round will be error-free.

Our original figure shows these as separate evidence boxes rather than a single green approval badge. Each box asks what the document covers and what remains unknown. No fictional certificate, assessor or score is presented as real. The exercise is designed so a reader can apply the same questions to public documentation without inventing a test result or confusing an audit's existence with its contents.

Sources: Remote gambling and software technical standards (RTS) - RTS 17 – Live dealer studios; Testing strategy for compliance with remote gambling and software technical standards - Summary; Games testing annual audit reports.

Preserve a round concern without diagnosing the studio

A troubling video moment is an observation to preserve, not a studio-wide conclusion. Record the product, table identifier if shown, round reference, time and exact visible behaviour. Keep the distinction between a missing frame on your device and an action you can actually see. Do not fill a gap in a recording with an imagined dealing event.

RTS 17's references to surveillance, logs and game-event statistics explain why a round may have evidence beyond the customer's stream. They do not promise that every customer can obtain every internal recording. Our practical suggestion is to ask the operator which records it used to explain the identified event, and to retain its response alongside the original observation.

This article cannot establish what happened in an individual reader's round. It also cannot infer deliberate manipulation from a brief anomaly, or certify fairness because an explanation sounds plausible. Those claims need evidence specific to the event. The value of a precise record is that another person can investigate the same occurrence without relying on a vague description such as the table looked strange.

Sources: Remote gambling and software technical standards (RTS) - RTS 17 – Live dealer studios; Evolution Gaming live casino studios.

Make the conclusion as narrow as the evidence

A defensible document review ends with a statement of scope: we read this published standard; this policy describes the relevant assurance route; this public response limits what inspection information is available. It should not end with an invented pass mark for a studio whose reports were never inspected.

To repeat our method, list the claim, the type of document offered, the covered operation, the applicable standard and the period addressed. Then list the missing fields. Compare the categories before comparing dates. An annual security cycle, a games-testing submission deadline and a studio compliance inspection are not interchangeable events just because each can involve an auditor.

The result is useful even when some answers remain unavailable. It prevents an online live-dealer reader from confusing a stream with surveillance evidence, an audit logo with a disclosed finding, or a regulatory standard with proof of individual compliance. In this research, the standards and published disclosure response were verified. Actual studio audit contents, assessor findings and the compliance status of any named table were not, and remain outside the conclusion.

Sources: Remote gambling and software technical standards (RTS) - RTS 17 – Live dealer studios; Testing strategy for compliance with remote gambling and software technical standards - Summary; Evolution Gaming live casino studios.