For business managers, deputies and risk officers
Incident reporting that holds up when someone asks to see the record
Log critical incidents and ongoing assurance records as the work happens, in flexible tables you can shape to your school. The logs are auditable and non-fungible, so no one can quietly rewrite history. When an assessor or your board asks what happened, the evidence is already there.
Part of Prove it's handled — Risk, compliance, review and assurance as live, owned routines
Explore Governance OperationsCaptured as it happens
Injuries, WHS events, near-misses and incidents go in while the detail is fresh, not weeks later from a half-remembered email.
Non-fungible by design
Every entry carries a timestamp and history. The log is a governance object, not a spreadsheet row anyone can edit.
Evidence on demand
When the board, an assessor or a regulator asks, the record is already complete. Nothing to scramble for.
You know this story
The incident happens on a Tuesday
A student trips on the oval. A contractor reports a near-miss in the kitchen. A parent emails about something that happened on the bus. Each one gets handled, by good people, the way it has always been handled. A note here. An email there. A line in a spreadsheet on the deputy's laptop.
Then, months later, someone asks to see the record
A regulator. An insurer. The board, after an incident that should have been a pattern someone spotted earlier. And the honest answer is that the log was a spreadsheet nobody really kept up. One entry was edited and nobody can say when, or by whom, or what it said before. The work was done. Proving it was done is now a project.
With EthosOne, the answer is just there
Every critical incident and every assurance record sits in one auditable log, captured as the work happened, with a history no one can quietly overwrite. As one school put it: the evidence is just there when I need it, I'm not scrambling to reconstruct what happened.
Log it. Lock it. Surface it.
One auditable foundation handles the one-off critical incident and the ongoing assurance record your school keeps term after term.
- Step 1
Log it
Capture the incident or assurance record in a flexible, interactive table built for your school: date, time, location, people involved, what happened, the classification, the immediate action taken and who owns the follow-up. Structured enough to be useful, fast enough that staff actually use it.
- Step 2
Lock it
Every entry is timestamped and tracked. The log is non-fungible: edits are recorded, history is kept, and the record can be trusted as evidence rather than treated as a draft. This is the difference between a log and a spreadsheet.
- Step 3
Surface it
Recurring log items don't just sit there. Patterns in your assurance records surface a new risk for your risk register, so an incident logged today informs the controls you set tomorrow. Logging connects to risk, it does not live beside it.
See it in motion
From logging an incident to surfacing the pattern as a risk.
Log it — incident entry
EthosOne product UI, light theme, navy #2F3C56 + gold #EDC499 + blue #0089D4, white cards, rounded corners, Inter font, Australian English. A 'Critical incidents' log table: rows with Date/Time, Location, People, Classification chips (Injury, Near-miss, WHS, Child-safety), Immediate action, Owner avatar plus name, a status pill, and a timestamped History column on the right. 16:10.
Lock it — entry history
EthosOne product UI, light theme, navy/gold/blue palette, white cards, Inter font. An audit-history panel for one incident: a vertical timeline of edits, each with author avatar, timestamp and 'field changed from X to Y', plus a small 'Non-fungible record' lock badge. 16:10.
Surface it — risk link
EthosOne product UI, light theme, navy/gold/blue palette, white cards, Inter font. A recurring near-miss log row highlighted with an arrow or flyout to a 'New risk' card showing an ISO 31000 residual-risk matrix (red/amber/green cells) and current versus target scores. 16:10.
What you can log
EthosOne treats logging as a first-class governance object. Every log is a flexible table you can shape to your school's language, sitting on one auditable, non-fungible foundation.
| Log type | What it captures | Who tends to own it |
|---|---|---|
| Critical incidents | Serious injuries, trauma, illness, child-safety events and emergencies requiring escalation or notification | Deputy / principal / business manager |
| WHS events | Workplace injuries, hazards realised, contractor and site incidents | Business manager / WHS lead |
| Near-misses | The things that almost happened, captured so the pattern is visible before the next one isn't a near-miss | Operations / front-line staff |
| Ongoing assurance records | Routine checks, observations and evidence that controls are actually operating | Risk & governance officer |
| Injuries register | Student and staff injuries, with follow-up ownership and outcomes | Business manager / first-aid lead |
Where it fits in Prove it's handled
Governance operations
Critical incidents and assurance logs are one workspace in the Pillar 2 operational governance layer.
See the Prove it's handled hub →Risk management
Recurring log items surface in your risk register, so logging feeds prevention rather than sitting beside it.
Explore risk management →Compliance & routines
Incident and assurance records sit alongside your compliance obligations, in one cadence, not five tools.
Explore compliance →Regulatory review
Auditable logs are exactly the evidence assessors look for during registration and review.
Explore registration & review →
Questions schools ask about incident and assurance logs
What is an assurance log?
An assurance log is a maintained record that demonstrates your school's controls and obligations are actually being met, not just written down. It captures the ongoing evidence, the checks, observations, incidents and how they were handled, that proves the work happened. In EthosOne an assurance log is auditable and non-fungible, so it stands up as evidence when a board, assessor or regulator asks to see it.
What is a critical incident register?
A critical incident register is the single record of serious incidents at your school: injuries, trauma, illness, child-safety events and emergencies, along with what happened, the immediate actions taken and who owns the follow-up. EthosOne keeps the register as a timestamped, governed log rather than an editable spreadsheet, so nothing serious is lost across inboxes and folders.
Is a spreadsheet enough for incident records?
A spreadsheet can hold the data, but it cannot prove the data. Anyone can edit a cell, and nothing shows what changed, when, or who changed it, which is exactly what an assessor or insurer wants to know. EthosOne logs are non-fungible and timestamped, so the record is defensible, not just present.
How long should a school keep incident records?
It depends on the record and your jurisdiction, and some child-related incident records carry long retention obligations. The practical point is that records need to survive staff changes and the years between an incident and the day someone asks about it. EthosOne keeps logs in one durable, Australian-hosted system rather than on an individual's laptop.
Does logging connect to our risk register?
Yes. Recurring log items surface as a new risk for your risk register, so a pattern logged today informs the controls you set tomorrow. A risk assessment plans the control before an activity; the assurance log evidences that it worked, and EthosOne connects both.
Does EthosOne replace CompliSpace Assurance?
EthosOne logs critical incidents and assurance records today. The mobile Forms and Front-line Capture App that completes a like-for-like swap with CompliSpace Assurance is on the roadmap for around August 2026. We would rather tell you exactly where the line is than oversell it.
Start free. Then prove it.
Begin with a free, private read of where your governance sits today, then map the gaps with our team and put your incident and assurance records on an auditable footing.
Step 1
Get your Exposure ScoreFree, under 5 minutes.
Step 2
Book a Governance ReviewMap your gaps with our team.
Step 3
Board-ready in 30 daysPer-school licence on enrolment.
Prefer to start with the artefact? Download the Assurance log template
Why independent schools choose EthosOne
Governance clarity
Consistent, board-ready insight from one portal.
Assurance confidence
Named ownership keeps risk and actions visible.
Compliance control
State-aligned obligations managed in one cadence.
Risk transparency
ISO-aligned risk is governed, not just documented.
