Prove the procedure is followed.
Written steps, named and dated sign-offs, and a log of every change, ready when an auditor asks.
What you can show
The record, kept as the work happens.
Everything here is in the product today, on every plan unless it says Team plan. Evidence you can show an auditor; whether you meet a standard is for you and your auditor to decide.
The procedure, written out
Each process can carry a written procedure: every step in order, who does it, in which system and roughly how long, then the actions as a numbered list. The AI drafts it from the map or you write it, and it prints from your browser.
Named, dated sign-offs
The people who do the work confirm their own steps, from a phone page or a QR code on the wall. Each step shows who confirmed it and the date.
“Changed since it was confirmed”
Edit a step and its sign-off drops: the step says “Changed since it was confirmed”, names who confirmed the earlier version, and waits for someone to confirm it again. Put the text back exactly and the sign-off returns.
A log of who did what
Edits, sign-offs, versions, locks, adopted changes and access changes are logged with the person and the time. The log comes out as activity.csv in the one-file export of everything, on every plan.
Versions, lock and restore
Name a version, compare it with today or bring it back; a version is kept before every AI edit. An admin can lock an approved process so nobody edits it until an admin lifts the lock, and notes and sign-offs still work.
Who can see and change what
Five access levels, from people who only look to admins. Limit anyone to chosen departments or processes. Only the people you choose see pay rates.
Reports for the board
The CFO report shows every figure with its working and how sure it is. On the Team plan, the board pack adds a one-page print, a spreadsheet and a whole-organisation report.
An outside reviewer, for one process
Invite an auditor or adviser as a free guest to one process: they read it, leave notes, answer questions and confirm steps, nothing else. Team plan.
Where it helps
For the reviews you already face.
Quality and safety systems (ISO 9001, ISO 45001)
The auditor asks for the procedure and proof it's followed. Show the written steps, who confirmed each and when, and every change since.
Construction sites
The site induction and the permit to work. Show each routine as written, who signs each step on site, and when it last changed.
NDIS providers (practice standards)
Each support routine, described by role. Show how it runs, who confirmed each step, and the log of changes between reviews.
Freight and logistics (Chain of Responsibility)
The pre-trip check drivers sign, and the load-restraint check. Show both as written, who does each step, and a dated record of every change.
Accounting practices (APES 320)
The engagement and review procedures. Show who signed off each step, and the history of changes to them.
Property managers (trust-account audits)
The trust-account reconciliation and the routine inspection. Show each step, who confirmed it, and every change.
Aged care providers (Aged Care Quality Standards)
Non-clinical routines, described by role: rostering, cleaning, a new staff member's induction. Show who confirmed each step, and every change.
Food manufacturers (HACCP, SQF, BRCGS)
The allergen clean-down and the critical control point checks. Show each as written, who signs each step, and when it last changed.
Independent schools (registration reviews)
The enrolment and duty-of-care routines. Show them step by step, who confirmed each, and every change since the last review.
Answering to another standard? If it asks for written procedures and proof they're followed, this is the record.
Behind the record
Where the record lives.
Your workspace and backups in Sydney. Encrypted backups every 6 hours, restore-tested, most recently on 23 October 2026. On Starter and above, people can sign in with their Microsoft or Google account.
Security answers for your reviewerHow the mapping worksThe export format and integrations
Questions
Audit evidence questions.
How does this help with an ISO 9001 or ISO 45001 audit?
It gives you evidence to show: each procedure as written, who confirmed each step and when, what changed since, and the activity log. Your auditor decides whether you meet the standard; Entrilla keeps the record.
What happens to a sign-off when someone changes a step?
The step is marked “Changed since it was confirmed”, names who confirmed the earlier version, and waits for someone to confirm it again. If the text is put back exactly as it was, the sign-off comes back on its own.
Can we give an auditor the log?
Yes. The activity log comes out as activity.csv in the one-file export of everything, which the people who can see pay rates download on every plan. Each line says who did what, on which process, and when, in UTC.
Can we stop an approved procedure being changed?
Yes. An admin can lock a process so nobody edits it until an admin lifts the lock; notes and sign-offs still work. Both go in the activity log.
Can an outside reviewer see just one process?
On the Team plan, invite them as a free guest to that one process. They read it, leave notes, answer questions and confirm steps, nothing else.
Does the AI change our procedures?
The AI never changes a live workflow on its own. It edits one only when a person in your organisation asks it to, saving a version first so the change can be put back, and its recommendations change nothing until someone accepts them.
Does this help with aged care, food safety or school registration reviews?
It keeps the same record: each routine as written, who confirmed each step and when, and every change. Describe care routines by role, never by resident. Your auditor decides whether you meet the standard; Entrilla keeps the record.