Where it works

Everything SteadCalm covers, on one page.

The platform spans a lot of ground — the door, the roster, the appeal, the compliance pack, the neighbourhood and the case file. Rather than make you read the whole site, here is the index: pick the setting, the capability or the kind of organisation you are, and read only that.

Where it is used

The settings SteadCalm is built for, and what the platform does in each of them.

Licensed venues

Hotels, pubs, RSLs, clubs, casinos and bottle shops

A licensed venue carries the liability for every refusal, every barring and every person working the door. SteadCalm sits underneath those decisions: the check that produced them is recorded, the person refused has a way to contest it, and the paperwork a licensing inspector asks for is generated from what the venue actually did rather than retyped at the end of the quarter.

Venues, accords & door teams

Coordinated barring across the venues in a precinct

An accord only works if every venue trusts the register and the process behind it. SteadCalm gives coordinators a shared register with explicit scopes, an approval step before anything is shared beyond the originating venue, and an appeal path that is independent of the venue that lodged the ban — which is the part that keeps accord-wide barring defensible.

Neighbourhoods & community safety

Community reporting, registered assets and local coordination

Community Shield is the council-side module. Residents and businesses register property and vehicles, report incidents into a structured intake, and nominate cameras they are willing to have contacted

Police, investigators & enforcement

Evidence that survives contact with a court

Where an agency is involved, the question is never whether a match was made — it is whether the record of it holds up. SteadCalm keeps the frames, the confidence score, the reviewer's decision and the chain of custody for every check, and packages a case as a numbered fact ledger with each written paragraph mapped back to the fact it came from.

What it does

The working parts of the platform. Each one can be read on its own page.

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

Photo door-check & entry register

The check, and the record that it happened

Point the tablet at a patron and the check runs against the registers that venue is entitled to see. Face embeddings and SHA-256 ID hashes are matched — raw licence numbers are never stored — and anything below the configured threshold goes to a reviewer with full context rather than producing an automatic refusal

Workforce currency

The roster becomes the evidence that everyone working was licensed to be there

This is the module most venues and security operators switch on first, because the exposure is immediate and the current control is usually a folder of photocopies. Credentials are held per person with expiry dates, flagged sixty days out, verified as attested register checks, and stamped at every shift sign-on — so the question 'was that person licensed on the night' has a one-click answer.

Appeals & due process

Anyone can put a person on a list; few can show how they contest it

A barring notice issues with a tokenised appeal link — no account, no app. The grounds are routed to a reviewer who is not the person who lodged the ban, and the reviewer can uphold, vary, withdraw or reject with written reasons

Compliance packs

Generated from real activity, not retyped the week before an inspection

Compliance paperwork usually exists twice: once as what the venue did, and once as what somebody wrote down afterwards. SteadCalm generates the pack from the first one

NSW FRT Code compliance

Everything the NSW Code of Practice expects a venue to hold — tracked and evidenced

Hotels and clubs operating facial recognition in NSW now answer to the Liquor & Gaming NSW Code of Practice. SteadCalm's FRT workspace holds the lot in one place: a clause-by-clause tracker, the Attachment A provider declaration, a separated exclusion-data store, weekly and monthly usage reports with FNIR/FPIR and downtime, and the change, maintenance, complaint, breach and authorised-user registers the Code requires — ready to hand to Liquor & Gaming NSW on request.

Live monitoring

Turns the door check into a continuous one

Your existing entrance, gaming-floor and car-park cameras stream into the console. Subjects are tracked frame to frame with a coloured box and an ID that persists across cameras, and a match against an active barring raises an alert before the person reaches the door

Community Shield

The council-side module for neighbourhood safety

Community Shield is a council product. It brings community reporting, registered property and vehicles, voluntarily nominated cameras, case threads and role-routed early warnings into one place, so a local government area can review recurring incident patterns and prioritise patrol effort against a record rather than a rumour.

Investigation & records

Court-ready records, chain of custody and audit packets

Every check, match, note and export is timestamped and packaged. Cases assemble into a numbered fact ledger, generated narrative must cite the specific facts it drew on, and the export contains both a readable PDF and a JSON manifest of the exact snapshot used — so a record produced today can be reconstructed a year from now.

Who buys it

How the platform is licensed and scoped for each kind of organisation.

Group operator

Multi-site hospitality groups with central oversight

A group runs one standard across many doors. Licensing is banded by number of sites under a single agreement and one invoice, with group-wide registers and reporting on top of each venue's own record set.

Council / community safety

Community Shield for a local government area

Licensed to the council rather than to venues. Property, vehicle and camera registers, community reporting intake, recurring-incident review and patrol prioritisation for the whole local government area, under the council's own governance and retention settings.

Security operator

Contract security and crowd control, with currency at the centre

For operators staffing multiple licensed venues, the commercial problem is proving that every guard on every shift was licensed and current. Workforce currency runs across the whole guard roster, and per-shift sign-on evidence is shared with the venues you staff.

Police / agency

Governance, retention and evidentiary controls

Agency deployments with the controls procurement asks for: retention windows per record class, chain of custody on every artefact, audit packets with a JSON manifest, and a security assessment pack for the approval process.

Still not sure where you fit?

Tell us how many doors or stores you run and who signs off, and we will point you at the right starting point.

See pricing Request access