Live by January. Sure by the first board meeting.
Twelve weeks in Term 4, beside your team, with a gate every fortnight that says what is now true. Most schools land on Stage 2 with a risk register the committee reads from.
EthosOne implementation comes in two shapes.
A focused uplift takes a school through Foundation and Calendar and one further module (most often Risk and Compliance or Regulatory Readiness), configured with the school's own registers, calendar and owners in Term 4 and live in January.
What we keep hearing
It is a Friday in Term 4. The login for the last system arrived by email that morning with a manual attached, and the configuration has fallen to whoever is free after assembly. The register built that afternoon never quite matched the school, so nobody trusted it and nobody opened it again. What business managers ask for this time is the same: fewer places to look, and someone beside them while it is set up.
Somewhere in Term 4 the platform still has to be built, and this is the term we spend beside you.
A focused uplift lands on Stage 2. A full transformation keeps climbing, one stage a fortnight, in the order the school can absorb.
Foundation
Everything the school runs today is inventoried, mapped and loaded once. Staff sign in with the account they already have and every named owner has a role.
You cannot go back when the incumbent is read-only, every owner has signed in and the access matrix is signed.
Calendar
Core and Regulatory Readiness. The strategic plan is on the dashboard with owners, the calendar carries the jurisdiction's dates, and the next submission is assembled with evidence linked per standard.
You cannot go back when an executive meeting is run from the dashboard and the next submission is assembled in EthosOne.
- This engagement lands here
Risk
Risk and Compliance and Personnel. Appetite is set once and approved by the board, the register is real, assurance logs run for a full term, and the first expiry is caught by the system before the date.
You cannot go back when the first Risk and Audit Committee pack is produced from EthosOne and calendar tasks are closed on time.
Board
PolicyAI and Board Engagement. The policy review cycle runs through PolicyAI, the first legislative change is actioned, and the board pack is generated from the record for two consecutive meetings with directors logging in directly.
You cannot go back when two board packs in a row have come from EthosOne and resolutions and actions are tracked in the system.
Group
Group Management over every module. Each entity closes its own calendar, the group board pack is produced from the roll-up, and the group lead reads the portfolio view weekly.
You cannot go back when the group board pack comes from the roll-up and every entity is closing its own calendar.
The same twelve weeks for every school, with a gate every fortnight. A gate is what must be true to pass; if it is not true we stay until it is.
- Week 0
Kickoff and discovery
The data map: one page per school naming every register, calendar, policy set and list, where it lives, who owns it and which module it feeds. The Readiness Review can run here, before anything is signed.
- Week 2
Access live
Every named owner signed in with the account they already have. Permissions matrix signed. Tenant profile built from public sources before day one.
Gate. Every owner in, the matrix signed, the profile complete.
- Week 4
Calendar
Migration reconciled and the incumbent read-only. Compliance calendar live with owners. Strategic plan on the dashboard.
Gate. The school is operating from EthosOne alone for the calendar.
- Week 6
Risk
Register populated with appetite approved by the board. First Risk and Audit Committee pack from EthosOne. Staff register with expiry alerts firing.
Gate. The committee reads its first pack from the record.
- Week 10
Board
Policy gap report issued. First board meeting run from an EthosOne pack.
Gate. Directors read the pack the executive runs on.
- Week 12
Handover
Recurring calendar loaded, adoption baseline captured, the Source of Truth Statement in the principal's hands: these registers now live in EthosOne, these systems are retired.
- +30, +60, +90 days
Adoption
Logins by role, calendar close rate, packs generated, milestones hit or missed. Any miss is a call from us, not a ticket from you.
Four decisions only the school can make. We are in the room for each.
- The strategic plan's pillars, goals and owners, so every action has a parent.
- One appetite statement per risk category, owned by the board.
- The top risks and who owns each, populated in the workshop rather than emailed afterwards.
- The critical incident protocol: roles, escalation, communications, tested once.
The end of the planning day, the plan signed, the wall of notes behind them.
What you leave with
A committee that reads from the record
The first Risk and Audit Committee pack comes from EthosOne at week six, with appetite approved, owners named and controls tested. The second one assembles itself.
A calendar that closes on time
Every obligation with an owner and a date, evidence linked where it already lives, and a termly health check that clears what is overdue or unowned.
A team that ran the build
Admin and end-user sessions recorded and kept in the vault, so the people who run the platform in February are the people who built it in November.
The platform carries it after week twelve. The register, the calendar, the plan and the packs keep running with owners, due dates and a history of who changed what, and the recurring calendar brings us back for the appetite refresh and the readiness review on the dates the school set. Core · Risk and Compliance.
The two options
Focused uplift. Where most start.
Foundation, Calendar and one further module, hand-configured with your categories, appetite and scoring scale, the register populated with the risks already on the table, and the state-specific compliance calendar built around the dates you carry. Configured together in Term 4, live in January, and handed over at week twelve.
Full transformation, scoped.
Every module you adopt, climbing the same ladder in the order the school can absorb: Board Engagement, PolicyAI, Personnel and Group Management brought across as part of the work, not left as homework. We scope it on the modules chosen and the terms you have, and we write the sequence down so the executive can see what lands when.
- Stored in AustraliaAWS Sydney and Melbourne, one database per school
- AI stays in the country tooAmazon Bedrock; never trained on your content
- Published, not describedTrust Centre · ISMS policy · How we handle your data
“It meets all of the real frustrations of business directors in one place.”
Nick MillerDirector of Business, Blackfriars Priory SchoolThe six we are asked every time.
Still weighing something up? Thirty minutes with us, on your own registers, answers the rest.
Book your school a demo01What is included in a focused uplift?
One module configured with your own categories, appetite, scoring scale, registers, calendar and owners; the people who will run it trained in your environment; evidence linked; the first reports run; and support through the first term. All of it is included in the scope we write down with you, and there are no per-user fees.
02Can we add modules later?
Yes. Most schools begin with Risk and Compliance or Regulatory Readiness and add Board Engagement, HR Compliance or PolicyAI as the next need arrives. Whatever you add over the years, the licence is published in full on the pricing page.
03Do we migrate documents?
No. Evidence stays where it is, in your drive or your document system, and is linked to the obligation, risk or control it supports. Nothing is rebuilt twice and nothing is lost in a copy.
04How long does it take?
Blackfriars went from demo to live in under a month. A focused uplift configured in Term 4 is live for the start of the school year, with the licence running from January 2027. A full transformation is sequenced module by module at a pace the school can absorb.
05How long until we are live?
Board-ready in 30 days, or you do not pay until you are. Engagements run through Term 4 and the licence starts in January.
We begin with what you already have: the registers, the calendar, the policies and the people who own them, however they are currently kept. The work is done alongside your team rather than in a back room, so the people who run the platform in February are the people who built it in November.
It finishes with a handover the school keeps, with the evidence linked where it lives and the reports coming from live data rather than from us.
06Implementation: focused uplift or full transformation, in full: what does it cover?
A full transformation walks every module the school adopts up the same ladder in the order it can absorb, and is scoped on the modules chosen. Both run on one twelve-week arc with five gates, are delivered with the school's team rather than to it, and end with a handover and a Source of Truth Statement the principal can table.
What are the AI paragraphs you are currently missing from your policies? Watch how we do it.
Free, under ten minutes, and yours to keep whether or not you talk to us.
“It meets all of the real frustrations of business directors in one place.”
“School governance and risk is a complex area without a clear solution.”
Tell us the module and the term you have,and we would be glad to write the sequence down before anything is
Implementation service: a focused uplift with one module, or a full transformation matched to the modules adopted.