Build a record you can explain

Connect a customer event to its source, decision and version. Keep access-to-history rules separate from retention policy.

Independent editorial analysisPublished · Source review 6 min

Design the question before the log

A useful record lets a reviewer reconstruct an event without guessing which system, policy or configuration produced it. Collecting more events is not automatically better evidence. A record without a stable identifier, time basis or explanation can become expensive data that still fails to answer the question asked during a review.

Start with questions such as “what did the customer see?”, “which decision was applied?” and “which version produced that outcome?” Then identify the smallest set of records needed to answer them. The following design suggestions are editorial recommendations; they are not a universal legal logging specification.

Customer history is not a retention schedule

UKGC RTS 1B specifies self-service access to at least three months of account and gambling history, with at least twelve months available on request, within the standard’s stated scope. Subscription lotteries are excluded from RTS 1’s applicability statement.

This is an access-to-history requirement. It does not, by itself, establish how long every event, security log, identity document or backup should be retained. A retention decision needs its own purpose, applicable obligations, owner and deletion process. Do not turn a customer-history window into a blanket rule for all data stores.

An event envelope worth reviewing

Field Editorial purpose Common failure
Event ID Distinguish an event from its retries Counting a retry as a new action
Occurred / received time Explain processing delay Treating arrival order as event order
Actor reference Join evidence without unnecessary identity detail Copying raw identity data into logs
Decision and reason Explain the chosen action Keeping only a success flag
Policy / build version Reproduce the historical logic Applying today’s rules to yesterday’s event
Correlation reference Follow a request across boundaries Losing the link at a vendor handoff

The table describes an example envelope. It is not a production schema. Its fields need a privacy, security and operational review for the system where they will be used. A correlation reference can itself be sensitive if it enables records to be joined.

Follow one event through a failure

Synthetic example. A history service receives the same settlement message twice after a network timeout. A naïve consumer appends two rows. A reviewer later sees a mismatch between the balance and history view.

In an example design, the consumer first checks the stable event ID, records that a duplicate delivery occurred, and avoids applying the business change twice. The review evidence shows both transport attempts and one accepted business event. A test should cover a duplicate arriving after a restart, not only two deliveries in the same process.

Next, introduce an out-of-order event. Confirm that the displayed history communicates event time consistently and that any correction leaves a trace. A successful retry is not evidence that an earlier incorrect view was never shown. Preserve enough context to explain what changed without indefinitely retaining all raw payloads.

Define a retrieval path

Evidence that exists only in an inaccessible archive may be difficult to use. Specify who can request a record, how the request is authenticated, which format is returned and how completeness is checked. Treat the customer-facing retrieval path and the internal investigation path as separate use cases.

For each, test a date boundary, a migrated account, a timezone change, a corrected transaction and an unavailable dependency. The acceptance criteria should describe observable results. “Logging works” is not a reproducible test; “the exported history contains one accepted settlement linked to its correction” is.

The MGA B2B application guidance also identifies software that processes essential regulatory records within its description of critical gaming supply. That is useful context for deciding which supplier relationships to investigate. It is not a retention period or an approval of the example design above.

Keep the record of the decision

Maintain an evidence map alongside the implementation: source, scope, interpretation, test, system owner and review trigger. A source update can then be traced to the affected test rather than becoming an unstructured announcement. Record unknowns explicitly, including a source’s effective date when it has not been established.

For the dates and provenance behind the limited requirement discussed here, open RL-001 in the document matrix. The methodology explains how we distinguish the source text from our implementation suggestions. The vendor brief addresses evidence crossing an organisational boundary.

Reading boundary

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-RTS1 RTS 1 — Customer account information

In-scope customers need self-service access to at least three months of history and at least twelve months on request. This is not a universal retention period.

Gambling Commission · technical standard · Locator: RTS requirement 1B

Source recheck: . Outcome: verified within this task: RTS 1 applicability and requirement 1B; access to history only.

Not a universal retention schedule. Commencement of this wording has not been established.

Read the official source
MGA-B2B Game Providers and Back Office

The application guidance describes B2B critical gaming supply, including material game elements and software processing essential regulatory records.

Malta Gaming Authority · application guidance · Locator: Game Providers and Back Office

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 source