Tiered barring register
One register. Shared exactly as far as the ban goes.
The register is the base layer, and the scope is the whole point of it. A ban is held at venue level unless it has been approved to travel further, and the platform enforces that in row-level security rather than trusting an interface to hide it. Every record carries an expiry, so the register stays current instead of drifting into a list nobody will defend.
What it does
Five scopes
Venue, accord, local government area, state and national — each with its own approval requirement.
Ban currency
Every barring has an expiry date; lapsing records are surfaced before they expire and swept nightly.
Bulk onboarding
Import an existing accord register from CSV with per-row validation and a persistent batch history.
Full audit trail
Who lodged, who approved, who revoked, what changed and when — exportable.
What that gets you
- No silent expiry: a lapsed ban stops being enforced and says so
- Sharing is a deliberate, approved act with a name attached
- The register can be handed to a reviewer without a covering explanation