Who it's for / Principals
The job has changed. The tools have not. Until now.
SASSLA and Monash named it Invisible Labour. The SASSLA and SASPA joint paper called for a redesign of the role. EthosGov is the first software product written from that evidence base. Not one more form. One governance rail the principal can actually lean on.
One dashboard. Council, compliance, strategic priorities and actions, visible in a glance.
Promise 1 of 3
Weekend work, returned.
The Sunday-night Council pack rebuilt from three systems stops being a Principal job. The rail composes it.
Promise 2 of 3
A Council that arrives ready.
Plain-English packs that survive a chair transition. Decisions and actions held by the tool, not by your memory.
Promise 3 of 3
A Director who already sees you.
Live register, live incidents, live council activity. The brief becomes a glance, not a 4th re-report.
Why a change is on the table
The role grew. The tools did not. The cost is sitting on you.
Principals are carrying compliance, council and director relationships in a stack of tools built for a job that no longer exists. The load is measurable, and the sector has named it.
Burden 1 of 3
Sunday, 10pm.
The Council pack rebuilt from three systems. The labour is invisible to anyone but you, and it leaves the school the day you do.
Burden 2 of 3
Tuesday, 9am.
A DfE directive lands. You add it to the list in your head. The compliance picture lives in your inbox and your Deputy's spreadsheet.
Burden 3 of 3
Friday, 6pm.
The Director called. You spent the call catching them up, not coaching with them. Your relationship is built on recall, not on shared evidence.
The role
What this role actually carries.
The Principal role is carrying more weight every year, and most of it is invisible to the tools the sector bought ten years ago. Three kinds of load sit on the role, all at once.
- 01
Compliance you cannot afford to miss.
SA DfE directives, ESB expectations, Act obligations, WHS, child safety, privacy. Tracked in your head or your Deputy's spreadsheet.
- 02
A Governing Council that depends on you.
Volunteer community members. Forty-page packs signed off on trust. A chair hoping you told them everything.
- 03
A Director who is only as close as their last visit.
Twenty-five schools competing for their time. You are alone with the register until something goes wrong.
Principals on EthosGov
What changes with EthosGov.
The Principal stops being the memory of the site. Three shifts land fast, usually inside the first council cycle.
Compliance becomes infrastructure.
Pre-loaded DfE calendar. Named owners. Evidence held by the tool, not your inbox. Audit prep stops being a weekend.
Voice
The Principal Voice.
These are not marketing quotes. They are drawn from published sector research into the modern public school principal role.
The job has changed beyond recognition. The tools principals are handed have not. Invisible labour is not a feeling, it is a measurable driver of principal harm.
South Australian principals report governance, compliance and reporting load as the single largest source of role dissatisfaction in the last five years.
Redesign of the role must begin with redesign of the system the role sits inside. Software alone is not the fix, but the current software is part of the problem.
Life inside the work
A day on EthosGov.
Seven small shifts across a single Wednesday. Each one a friction point removed, not a form added.
- 7:45am
Morning glance.
Open EthosGov in the car park. Three red cells on the site dashboard. One is already owned by the Deputy. The other two can wait until recess. You walk in with your day set.
- 9:10am
Deputy update.
No separate standup doc. You and the Deputy work through the live action pane together, clearing two items and re-scoping a third.
- 10:40am
Council pack prep.
Next week's pack is composing itself from live data. You change one headline and leave a note for the chair. Ten-minute read. No forty-page rebuild.
- 12:15pm
Director call.
The Director calls. You share a link, not a document. They see the same register you see. The call is about what happens next, not about catching up.
- 2:00pm
Incident review.
A yard incident from Tuesday is already captured with staff detail, parent contact and photo evidence. You add the follow-up plan and close the loop.
- 3:30pm
Policy acknowledgement.
The new behaviour policy needs teacher acknowledgement before Friday. Two reminders are already queued by the system. You do not have to chase.
- 5:45pm
Close the laptop.
The council pack is queued. The register is current. The Director has visibility. You leave without a backpack of unfinished work.
Talk track
How a Principal introduces EthosGov to their leadership team.
The words that make the shift legible to the people who will live it with you.
Principal
Opening
I have been carrying the pack in my head for too long. We are going to stop rebuilding it every cycle.
Principal
The shift
One layer. Five things we already do. Meetings, strategy, compliance, procedures, actions. No new reports.
Principal
What changes for you
You will see decisions land, actions move, and the Council read something in ten minutes. That is the whole trick.
Answers
Frequently asked questions
I already have a deputy who runs this. Why do I need another tool?
EthosGov is not another tool for the Deputy. It is where the Deputy's work becomes visible to you, your Council and your Director without them re-reporting it. The Deputy keeps owning the register. You stop being the consolidator.
Do I have to bring my Council onto the platform on day one?
No. The Principal view can be up inside a fortnight and the pack can compose from live data before the Council ever logs in. Council seats activate when the chair is ready.
Is this another login for my teaching staff?
Only where it has to be. Classroom staff interact through short workflows they already do, such as policy acknowledgement. They do not have to learn a new system.
How is this different from the compliance tool the Department already pays for?
Department tools tell you what is required. EthosGov is where your site does the work and evidences it. You stop being the bridge between what is asked and what you can prove.
Take the load self-assessment.
Ten minutes. Five questions calibrated to the Invisible Labour evidence base. A clear read-out of where the load sits in your week, with a fourteen-day plan for getting the biggest piece off the role.
Site clarity
One working view, not four.
Director visibility
They see it without asking.
System assurance
Evidence held by the tool.
Load reduction
Weekend work goes back where it belongs.