A product ticket often begins with a link and the instruction “the regulator requires this”. That is too little information to review. The link may lead to an application guide, a code, a technical standard or a consultation. Each is useful, but they do different work. Before writing acceptance criteria, identify the kind of document and the proposition it actually supports.
This brief compares named passages from the Gambling Commission and the Malta Gaming Authority. It does not assign a legal status to every document from either authority. The practical workflow below is our editorial method, not a regulator-prescribed process.
Start with the document’s own classification
The Gambling Commission’s customer identity verification provision, 17.1.1, is presented as a licence condition. Its first paragraph connects verification to the point before a customer may gamble. The applicability statement also matters: it identifies the relevant remote licences and exceptions. A ticket that copies only the timing phrase loses that boundary.
In contrast, remote customer interaction provision 3.4.3 is a social responsibility code provision. The page explains the licence-condition status of compliance with such provisions. It contains a number of separate requirements and commencement notes. Calling it merely “advice” because its label includes “code” would be a serious reading error.
Now consider ordinary code provision 8.1.1. The Commission distinguishes ordinary codes from operator licence conditions and describes them as good practice. The same explanation also gives them relevance in legal proceedings and licensing review. Neither “identical to a licence condition” nor “safe to ignore” is a faithful summary. Record the distinction instead of flattening it into a single mandatory/optional switch.
A helpful explanation can point somewhere else
The Commission’s technical standards for gambling software page explains the relationship between software deployed in reliance on a Commission operating licence and its technical standards and testing requirements. That is a useful entry point. The page is not, on its own, a complete testing specification for every release.
For a reviewable engineering decision, keep two links: the explanation that helped you find the subject and the operative document or test requirement that supplies the actual criterion. If the second link has not been inspected, say so. “The overview mentions testing” cannot substantiate an assertion that a particular build has passed the applicable tests.
The MGA game providers and back-office application page describes the critical gaming supply context, including relevant software and regulatory records. Its role in this collection is an application and scope reference. It is not a certification of any supplier, and it does not make every product with a database subject to the same obligations.
A proposal belongs in a different column
The MGA’s 30 September 2022 consultation notice concerns proposed changes to the Player Protection Directive. It is historical evidence of a consultation, not a substitute for the resulting text. A proposal can explain what was being considered while remaining insufficient to establish what was adopted or when it began to apply.
This matters when a search result is easier to read than the instrument itself. A headline containing the desired phrase may appear authoritative because it sits on the regulator’s domain. The domain confirms the publisher, but the document’s function still needs inspection. A consultation response, an amendment announcement and an amended directive should remain separate records.
Build a claim that another reader can challenge
For each proposed requirement, write a short evidence statement with five parts: the document identifier, the exact locator, the relevant population or activity, the narrowly supported proposition and the unresolved boundary. The document matrix makes this distinction visible through separate requirement/context labels and source-verification fields.
Here is a synthetic review example. A team proposes: “Every account event must be retained for twelve months.” Its evidence is a customer-history provision. The reviewer should ask whether the cited text addresses access to account history, retention of all system events, or both. If the source establishes only one of those matters, the broader claim must not survive merely because the number sounds plausible. The unsupported part needs another source or an explicit editorial label.
A second synthetic example concerns a licence register. A record in a regulator’s register may help identify a particular authorisation. It does not automatically establish that a release, subsidiary, product or target market is covered. The researcher must connect the register entry to those facts instead of treating a recognised name as proof of all of them.
Keep interpretation visible
An editorial implementation suggestion can still be valuable. “Capture the version of the rule used in the decision” is a useful engineering recommendation. It should be labelled as our recommendation unless the specific obligation to capture it is established in a cited source. Separating these layers makes the publication more useful, because readers can change the implementation without silently changing the underlying claim.
Our comparison view therefore leaves gaps. A Great Britain provision beside an unverified Maltese document is not a legal equivalence. “No assessed source in this collection” describes the collection’s limit; it says nothing about the absence of a rule in the jurisdiction. That wording is deliberately less convenient than a green compliance score.
Before turning the note into a release condition
Ask the reviewer to identify the document type aloud, point to the supporting passage, state the scope and explain any date limitation. Then separate the legal question from the implementation test. A passing software test can demonstrate a chosen behaviour under defined conditions. It cannot establish the correctness of an unverified interpretation that supplied the test.
If applicability remains uncertain, retain the record as context or pending research. The useful output is a bounded decision trail: what was read, what follows from it, what is editorial analysis and what still needs qualified review. That is a stronger foundation than a confident sentence supported only by an official-looking link.
Source-backed statements and editorial examples serve different purposes. Verify applicability and the current text before using a source for a legal or release decision.
Source notes
Each note identifies the reading task and its limits. A source recheck does not establish a complete current legal position or change this brief’s original publication date.
GC-ID LCCP 17.1.1 — Customer identity verification
For licences within its stated scope, customer identity must be established before gambling; the provision lists exceptions.
Source recheck: . Outcome: verified within this task: 17.1.1 applicability and paragraph 1.
Excluded licence types matter. No universal identity, age-check or AML procedure is prescribed here.
Read the official sourceGC-INTERACT LCCP 3.4.3 — Remote customer interaction
In-scope licensees must monitor customer activity from account opening to identify harm or potential harm. Paragraph 4 is within the provisions in force from 12 September 2022.
Source recheck: . Outcome: verified within this task: 3.4.3 applicability, paragraph 4 and the listed commencement dates.
12 September 2022 applies to paragraph 4, not every part of 3.4.3. This is not a complete account of customer-interaction duties.
Read the official sourceGC-ORDINARY LCCP 8.1.1 — Ordinary code
The ordinary-code explanation distinguishes good practice from operator licence conditions, while explaining its evidential and licence-review relevance.
Source recheck: . Outcome: verified within this task: The ordinary-code legal-status explanation on the 8.1.1 page.
Used to distinguish document types, not to provide a notification workflow or individual legal assessment.
Read the official sourceGC-SOFTWARE Technical standards for gambling software
Software made available in reliance on a Commission operating licence must meet its RTS and relevant testing strategy. The page distinguishes overseas-only supply.
Source recheck: . Outcome: verified within this task: Deployment scope and distinction for overseas-only supply.
No build has been tested. The complete current testing strategy has not been audited; this page is a reading entry point.
Read the official sourceMGA-B2B Game Providers and Back Office
The application guidance describes B2B critical gaming supply, including material game elements and software processing essential regulatory records.
Source recheck: . Outcome: verified within this task: The application page’s description of critical gaming supply.
No specific integration is classified. Application guidance is not a complete legal instrument or proof of authorisation.
Read the official sourceMGA-CONSULT-2022 Closed consultation on player-protection amendments
This dated notice describes proposed changes and a consultation. It is historical evidence of a research stage, not proof that a proposal itself became a requirement.
Source recheck: . Outcome: verified within this task: Historical notice of a consultation on proposed changes.
The consultation is historical, not an open invitation or an operative requirement. Its original closing date was later extended.
Read the official source