Compliance that blocks the mistake instead of reporting it
A worker's police check expired three weeks ago and they've worked eleven shifts since. Nobody noticed, because the expiry date lives in a spreadsheet nobody opens.
Track the checks, tickets and documents each person must hold, with expiry dates and evidence — or a policy statement they read and acknowledge, recorded with what they saw and when. An item can apply only where it fits, such as a working-with-children check for staff aged 18 or over, and anyone it can't be checked for is flagged, not assumed compliant. Status works itself out: current, expiring, overdue or missing, with a page listing exactly who needs to act on which item. Where staff upload their own evidence you can require an administrator to approve it. Then set rostering to warn — or to refuse outright — when someone isn't compliant on the date of the shift.
You stop chasing paperwork and start reading a list, and the failure that would have cost you your registration can't reach the roster.
Controlling who sees what
Most systems give you three or four fixed roles, none of which match how you actually work. So everyone becomes an administrator and the receptionist can see payroll.
Build your own access levels, granting or denying each area of the system independently. Start from four sensible roles and create as many of your own as you need. Where you run multiple sites, permissions can be limited to one of them.
People see what their job requires and nothing else, without bending your structure to fit someone else's idea of roles.
Privacy you can evidence
Australian privacy law gives people rights over their information, and "we're careful with it" isn't an answer an auditor or an insurer accepts.
Consent is recorded with the exact wording the person agreed to, its version and time, and any withdrawal. Every document and form is marked shared with the client or withheld. Completed forms and notes are locked against later edits, and significant actions go to an audit log of who did what, and when.
A real answer when a client, an auditor or an insurer asks how their information is governed.
Australian data, including in-app AI
Anyone with an IT function will ask where the data lives, and a vague answer costs you the conversation.
Your database runs in Azure Australia East (Sydney), the app itself runs in Azure in Melbourne, and documents are stored in AWS Sydney. Our in-app AI features run on AWS Bedrock on Australia-only infrastructure in Sydney and Melbourne — prompts and uploaded documents are processed in-region and never sent overseas, and are not retained or used for training. The optional AI phone and website assistant runs through a voice partner in the United States. Two-factor authentication and trusted-device recognition are available.
The security conversation is short, and every answer is specific.
