Who it's for / Deputy Principals
The role that holds the register. The tool the register needs.
Deputies carry the governance weight of the site in practice. WHS logs, risk reviews, incident follow-up, compliance evidence, camp and excursion readiness. Usually all in spreadsheets that live on one drive, owned by one person. EthosGov is the backstop the role has been waiting for.
One register. One incident log. One evidence pane. Not three spreadsheets and a OneNote.
Promise 1 of 3
The register stops being you.
Risk, incidents and compliance evidence held by the tool. The chain survives a leave, a transition, an audit week.
Promise 2 of 3
One source, three audiences.
The Department, the Council and the parent community read the same record from where they sit. No re-keying.
Promise 3 of 3
The next Deputy is twenty minutes in.
Onboarding is reading the register, not rebuilding it. Institutional memory finally lives somewhere outside one head.
Why a change is on the table
Three libraries. One memory. A leave day away from collapse.
Most Deputies are running the governance spine of the school in spreadsheets, notebooks and inbox folders. The work is real. The risk is invisible until the day the role transitions.
Burden 1 of 3
The drawer.
The incident log lives in one notebook in one drawer. Searchable only by the person who wrote it. Impossible to evidence under audit.
Burden 2 of 3
The drive.
Compliance evidence scattered across three drives and four inboxes. Different folder for each domain. No chain that holds together.
Burden 3 of 3
The Friday.
When you go on leave, the site goes with you. The next Deputy is staring at columns they did not name and risks they did not score.
The role
What the role actually holds.
Most Deputies are running the governance spine of the school without a tool built for it. Four pieces of that spine sit on the desk right now.
- 01
The risk register nobody else reads.
Reviewed on a single day of the year. Forgotten the week after. Referenced only after an incident.
- 02
The incident log that lives in a notebook.
Captured in one person's handwriting. Locked in the top drawer. Impossible to search when the Department asks.
- 03
Compliance evidence scattered across drives and inboxes.
Different folder for each domain. Different owners for each folder. No single chain of evidence.
- 04
Camp and excursion paperwork that repeats every term.
Risk assessments re-typed from last year. Consent forms rebuilt from memory. Ratios recalculated every time.
Deputy Principals on EthosGov
What changes with EthosGov.
The Deputy stops being the spreadsheet. Four things move off the desk and into the operating layer.
Site register, structured and live.
ISO 31000 aligned. Owners, evidence, review cadence. Updated where the work happens, not a month later.
Context
How Principal and Deputy use EthosGov together.
Ownership stays where it belongs. The Deputy owns the site register, the incident archive and the compliance calendar. The Principal owns the site direction and the relationship with the Council, the Director and the Department.
What changes is the handoff. Instead of a weekly briefing rebuilt from memory, the Principal reads the same live view the Deputy is working in. Status, exceptions and follow-ups are visible in real time. The Deputy stops being a translator. The Principal stops being a re-reporter.
Voice
Why Deputies love it.
Three things we hear on every walkthrough with a Deputy who has been running the register in spreadsheets for five years.
No more did you get the email on a Monday. The register is where the evidence is. Anyone with permission can see it.
When I go on leave, the site does not go with me. The next Deputy can pick it up in twenty minutes.
The Director sees my work, not just my Principal's report of it. The register speaks for itself.
Life inside the work
A day on EthosGov.
A Deputy's Tuesday, re-shaped by having a single operating layer instead of six spreadsheets.
- 8:05am
Yard check.
One hazard noted on the way past the oval. Captured on the phone in twenty seconds, owner routed, photo attached.
- 9:30am
Risk review.
Weekly review pane. Three risks with elevated residual. One control expired. Two minutes to extend, update and move on.
- 10:50am
Incident follow-up.
Monday's behaviour incident is already in the archive with witness statements and parent contact. You attach the follow-up plan and the case closes itself.
- 12:30pm
Camp readiness.
Year 5 camp next month. Last year's plan clones forward. You update four risks, one medical note and move on to lunch.
- 2:15pm
Compliance moment.
A DfE directive has landed. Tool routes it to the right owner with a due date. You sign off on your piece and the evidence attaches automatically.
- 3:45pm
Principal handoff.
Five-minute walk past the office. Principal glances at the same register. No briefing meeting.
- 5:10pm
Home.
No backpack. No weekend list. The site is in the tool, not in your head.
Talk track
How the Deputy makes the rail their own.
The scaffolding you already carry, now held by the tool instead of your memory.
Deputy Principal
Before
I was the governance backstop. Four notebooks. One head. No second pair of eyes.
Deputy Principal
After
One action register. Every forum writes into it. Nothing walks out of the meeting without an owner.
Deputy Principal
What I tell my team
The tool reads what we decided last time. You do not have to brief me. Open the register.
Answers
Frequently asked questions
Does this replace our existing spreadsheets?
Yes, but not on day one. The tool can absorb your register, your incident log and your camp paperwork in sequence so the Deputy is never holding two versions of the same data at the same time.
Who owns the site register inside EthosGov?
You do. Roles and permissions are configurable, but the Deputy is the default register owner and the default workflow routes all risk updates through the role.
Can I still use a paper notebook for yard incidents?
You can, but the phone capture is faster and attaches evidence to the record straight away. Most Deputies switch inside the first fortnight because the evidence chain is cleaner.
See the site register in action.
Bring your current site risk register, your incident archive and your last camp pack. We show you what the same information looks like when it is held by the tool and not by the role.