Gaming Incident Register Software The 2024 Standard for NSW Venues
Since July 2024, NSW gaming venues must operate a Digital Incident Register (DIR) meeting the L&GNSW prescribed standard. Paper registers are no longer compliant. Spreadsheets do not meet the standard. The venue needs purpose-built software. Here is what the DIR has to do, what to look for in a software product, and how the DIR sits alongside AUSTRAC AML/CTF compliance.
The DIR Standard What L&GNSW Requires
The Digital Incident Register is the structured electronic record of incidents at a NSW gaming venue. The L&GNSW standard introduced in July 2024 specifies the categories of incident that must be recorded and the form of the record. Required incident categories include:
- Patron refusals and removals.
- Self-exclusion actions and breaches.
- Responsible-gambling interactions and interventions.
- Gaming machine malfunctions and large payouts.
- Disturbances, altercations, or violence.
- Minors attempting to access gaming areas.
- Police or regulator attendance.
- Any incident the venue considers significant.
Each entry must include a timestamp, the staff member who recorded it, the patron details where applicable, the description of the incident, and the disposition. The DIR must be tamper-evident, retain editing history, and produce defensible records on inspection.
Why Paper and Spreadsheets Fail the Standard
Paper
Paper records cannot demonstrate they have not been altered. Pages can be rewritten, removed, or misplaced. The standard requires tamper evidence; paper provides none.
Spreadsheets
Spreadsheet records are silently editable. Any cell can be changed without leaving an audit trail. A spreadsheet incident register may have the right fields and the right entries, but it cannot demonstrate integrity. L&GNSW treats spreadsheet-only DIRs as equivalent to no DIR.
Generic incident-management products
Some generic compliance management products include incident management, but they are typically not configured for the specific L&GNSW DIR requirements (category set, field structure, retention rules). Adopting a generic product without configuration can produce a DIR that misses the standard despite meeting general best practice.
What Gaming Incident Register Software Must Do
Categories aligned to L&GNSW requirements
The product’s incident categories should match the L&GNSW standard, with category-specific fields where the standard requires them. Configurable categories alone are insufficient if the configuration leaves gaps.
Tamper-evident records
Every entry is timestamped at creation. Edits are logged with user, time, and the change made. Deletion is logical, not physical — the record remains visible with deletion-flagged status. Inspectors can see the full history.
Mobile-friendly capture
Incidents happen on the gaming floor, not at a desk. The product should support quick capture from a tablet or phone in the gaming area. Long, complicated entry forms produce incomplete records.
Multi-venue support
Group operators need a single register that captures incidents across all venues with the appropriate access controls. Each venue’s local staff sees their venue; group compliance officers see the whole estate.
Reporting and search
Inspectors need to be able to extract specific incidents on request. The product should support search by date, category, patron, staff member, machine, and other dimensions. Reporting outputs in formats the regulator can read directly.
Integration with the rest of compliance
Incidents do not exist in isolation. A self-exclusion breach in the DIR is also a self-exclusion enforcement record. A harm-minimisation intervention is also a training-relevance signal. The DIR should connect to the broader compliance platform rather than sit as a standalone tool.
The AUSTRAC Layer
The DIR is a state harm-minimisation record. AUSTRAC AML/CTF records are federal financial-crime records. The two are distinct but operationally connected:
- A self-excluded patron attempting circumvention may be an AML/CTF indicator.
- A large unusual payout flagged in the DIR is also a record AUSTRAC may ask about.
- Patron-interaction records that cross both regimes should be available to both regulators in their respective formats.
A platform that handles the DIR, AUSTRAC AML/CTF records, and the rest of the venue’s compliance posture in one integrated view eliminates the gaps that arise when the regimes are run in parallel. A DIR that satisfies L&GNSW but does not connect to the AML/CTF program is a partial answer to a layered question.
How to Evaluate Vendors
Five questions for any DIR vendor:
- Does the product specifically meet the L&GNSW July 2024 standard? Ask for documentation. Generic claims are not evidence.
- How is tamper evidence implemented? Walk through the audit log of an edited record. The audit trail should be visible, complete, and not editable by venue staff.
- Can the product handle multi-venue operations if applicable? Group rollups, venue-specific access, group compliance reporting.
- Does the product integrate with the rest of compliance? Self-exclusion register, AUSTRAC AML/CTF program, training records. Standalone DIRs create the gaps the integration is designed to close.
- What reporting outputs are produced? The DIR should produce L&GNSW-format reports, custom-period reports, and patron-specific extracts on demand.
Frequently Asked Questions
What if our paper-based register has been working for us so far?
Since July 2024, paper-based registers are not compliant. “Working for us” is the venue’s perception; the inspection finding is the regulator’s perspective. Transition is required, not optional.
Can we use a basic incident-management module from a hospitality platform?
Possibly, depending on configuration. The basic module is unlikely to meet the L&GNSW standard out of the box. Configuration to match the prescribed categories and tamper-evidence requirements is the work; if the platform supports it, the basic module can be made compliant.
Do we need a separate DIR if our AML/CTF platform handles incidents?
If the AML/CTF platform’s incident management handles the DIR’s specific requirements (categories, tamper evidence, retention, reporting), no one platform serves both. If it does not, yes the DIR has specific state-regulator requirements the AML platform may not meet.
How long must DIR records be retained?
L&GNSW retention requirements apply, typically aligned with related state retention frameworks. AUSTRAC’s seven-year retention applies to records that intersect with AML/CTF purposes. The longer of the two is the practical retention.
What does an L&GNSW inspector check in the DIR?
Currency are entries from the past month present and detailed. Specificity do entries describe the incident substantively. Tamper evidence can the inspector see the full audit log including edits. Coverage are the prescribed categories all populated where appropriate.
DIR + AUSTRAC + Self-Exclusion in One Platform
ComplyIQ delivers the L&GNSW Digital Incident Register alongside the AUSTRAC AML/CTF program, self-exclusion register enforcement, RCG and AML/CTF training tracking, and the rest of the venue’s compliance posture in a single platform built for NSW pubs and clubs.
References
- Gaming Machines Act 2001 (NSW) legislation.nsw.gov.au
- Liquor & Gaming NSW, Digital Incident Register liquorandgaming.nsw.gov.au
- Liquor & Gaming NSW liquorandgaming.nsw.gov.au