Oversee
Oversee a system of 20 to 40 schools, without being the last to know.
An Education Director carries 20 to 40 schools inside a system of 800 to 2,000. The role is the least-tooled relative to its accountability. Oversee is not a separate product: it is what emerges when the schools in a Director's portfolio already run Lead, Improve and Assure. Five signal blocks surface for the Director: a heat-map of the portfolio, single-school alerts, incident storm mode when three schools go red at once, a department roll-up across clusters, and a public trust audit of every school's community-facing record.
One dataset. Twenty-five schools. The signal the tier has never had.
Promise 1 of 3
Twenty-five schools. No tool. Three principals on the phone at once.
In a system of 800 to 2,000 schools, the Director that loses composure under a three-school storm is not the one the Department promotes. The friction cost is the load the role is currently carrying on memory: calls, meetings and reconstructed reporting from 20 to 40 Principals at the same time. The Director finds out about the problem after it becomes an incident. Portfolio posture is reconstructed from PDFs. System trends are visible only in hindsight, and only for the two or three schools loud enough to be heard.
Promise 2 of 3
Five signal blocks. Not features. The pane the tier has never had.
Oversee is not a separate product module. It is the view that emerges for a Director when the schools in the portfolio already run EthosGov. Each signal block below is composed from cross-pillar data (02-organisation-settings, 03-dashboard, 06-monitor-risk, 08-compliance, 14-assurance-logs, 16-trust-portal) so the Director reads what the site is already creating, instead of re-asking for it. The strategic block is the third: Incident Storm Mode. That is the moment the tier is most exposed, and the moment Oversee earns its keep.
Promise 3 of 3
Oversee is piloted at a Director portfolio in 60 days.
Week 1: Director scoping and threshold design per pillar.
Research anchor
Directors hold twenty-five sites in their head. The ones that go wrong were not invisible at the site. They were illegible upstream. Oversee makes upstream legible without asking any Principal for a new report.
What Oversee changes
Portfolio legibility, without a re-ask.
- Held on one Director's surface
- 25 sites
- Director sees the same data that runs the school
- Read-only
- From first call to a Director portfolio pilot
- 60 days
Heatmap, storm mode, roll-up. No phone calls to produce the view.
No duplicate reporting. No bi-weekly data request. Just the surface.
Five schools, one Director, live in EthosGov.
Twenty-five schools. No tool. Three principals on the phone at once.
In a system of 800 to 2,000 schools, the Director that loses composure under a three-school storm is not the one the Department promotes. The friction cost is the load the role is currently carrying on memory: calls, meetings and reconstructed reporting from 20 to 40 Principals at the same time. The Director finds out about the problem after it becomes an incident. Portfolio posture is reconstructed from PDFs. System trends are visible only in hindsight, and only for the two or three schools loud enough to be heard.
Oversee gives the Director live cross-site signal with drill-down to site context, the right alerts at the right time, and a triage pattern for the multi-site event, all composed from the data the schools are already creating in Lead, Improve and Assure.
- Director visibility depends on what each site reports manually.
- Escalation still happens by calls and inbox chains.
- Portfolio posture is reconstructed from individual reports.
- System trends are visible only after they become incidents.
The Shift
In a system of 800 to 2,000 schools, the Director that holds composure under a three-school storm is the one the Department promotes.
Five signal blocks. Not features. The pane the tier has never had.
Oversee is not a separate product module. It is the view that emerges for a Director when the schools in the portfolio already run EthosGov. Each signal block below is composed from cross-pillar data (02-organisation-settings, 03-dashboard, 06-monitor-risk, 08-compliance, 14-assurance-logs, 16-trust-portal) so the Director reads what the site is already creating, instead of re-asking for it. The strategic block is the third: Incident Storm Mode. That is the moment the tier is most exposed, and the moment Oversee earns its keep.
Director Heat-Map
Twenty-five schools × four signals. One pane. One click to the site context.
Treatment coverage, appetite position, compliance completion and incident pattern, aggregated across the Director's 20 to 40 schools. Each cell reads from the same data the Principal, Deputy and Business Manager already work with at the site. Green means holding; amber means attention; red means the next call belongs here. Drill-down is one click, straight to the site's own Lead, Improve or Assure view, not a re-keyed summary.
Signal
Source: 03-dashboard School Overview, 06-monitor-risk appetite bands, 08-compliance obligations. Eight of a typical 20 to 40 schools shown.
Single-School Alerts
What surfaces when one school in the portfolio goes amber or red.
Not all signal is a storm. Most days, a Director is reading one school at a time: one out-of-appetite risk, one critical log entry, one overdue compliance obligation, one policy that missed review. Oversee concentrates that signal into a single feed: owner, age, severity, next action visible without opening the school. The Director walks into the call already knowing what to ask about; the Principal spends the call solving the problem, not describing it.
| School | Signal | Severity | Owner | Age |
|---|---|---|---|---|
Dunvegan PS | Risk H2 out of appetite: staff wellbeing cluster.Third incident in 21 days. Treatment review overdue. | High | Principal | 2d |
Glenside HS | Critical incident: near-miss at pick-up crossing.Second near-miss in 14d. Safeguarding rail triggered. | Critical | Principal | 4h |
Glenside HS | Child Safe Standards §7 obligation: evidence missing.Auto-reminder twice. Needs acknowledgement. | High | Deputy | 11d |
Belmont HS | Policy review overdue: complaints and feedback.12 months since Council approval. | Medium | Principal | 4wk |
Elderslie HS | Risk matrix shift: Camp A treatment closing.Positive movement; Director check-in optional. | Low | Deputy | 7d |
Source: 06-monitor-risk out-of-appetite, 14-assurance-logs critical incidents, 08-compliance overdue obligations. The Director walks into the call already knowing what to ask about.
Incident Storm Mode
When three schools go red at once: triage, delegate, share the playbook, debrief across the portfolio.
A bereavement ripples across a cluster. A state-wide weather event closes seven sites in a morning. A safeguarding story breaks and four schools get the same parent question by 9am. In a system of 800 to 2,000 schools, the Director that loses composure under a three-school storm is not the one the Department promotes. Oversee concentrates Director attention: a triage queue ranked by severity and age, delegated acknowledgement so deputies and liaisons share the load, a shared playbook that drops each school into the same response shape, and a parallel debrief lane that turns the storm into learning for all 20 to 40 schools, not just the three in the storm.
| School | Event | Severity | Status | Playbook |
|---|---|---|---|---|
Glenside HS | Community bereavement: Yr 10 family.Parent comms live; staff brief at 0830. | Critical | Dep ack | BRV-01 |
Dunvegan PS | Ripple: siblings attend. Wellbeing cover needed.Shared response with Glenside HS. | High | Dep ack | BRV-01 |
Hazelwood PS | Ripple: shared bus route; Yr 6 transition.Liaison absorbs parent enquiries. | High | Liaison | BRV-01 |
Flinders PS | Watching list: pending parent enquiries.Pre-briefed playbook available if escalated. | Medium | Watching | BRV-01 |
Cluster A (3 schools) | Shared debrief → risk register, policy, training.Writes back across all 25 schools, not just the three in the storm. | Debrief | Director | BRV-01 → v2 |
Source: 06-monitor-risk, 14-assurance-logs history, 03-dashboard ownership scoreboard, 13-camps-excursions debrief pattern. The third signal block is the one the tier is most exposed on, and the one Oversee is built around.
Department Roll-Up
Policy pipeline, camps status and ownership scoreboard across every cluster.
One step up from the heat-map. When the Executive Director asks how the Directorate is tracking, the roll-up is already composed: percentage of schools at Child Safe Standards Stage 04, percentage of Council-approved SIPs in adoption, percentage of camp debriefs written back to the risk register. Filterable by cluster, region or cohort. Not reconstructed from PDFs. Composed from what the sites are already running.
Child Safe Standards. Obligations at Stage 04 (Adopted).
Federal CSS §3 and §7 across the Directorate.
Measure: Target 95% by Q3; escalate exceptions to cluster lead.
SIP adoption. Councils reading live pyramid, not planning-day PDF.
Priority × term × KR decomposition live across the portfolio.
Measure: 22 of 25 schools live; 3 in pilot onboarding.
Camp debriefs written back to risk register within 7 days.
Closes the learning loop across clusters, not just within schools.
Measure: Target 100% within 7d; current 82%.
Ownership scoreboard. Obligations with a named accountable leader.
The Department's hardest number: obligations that are not orphaned.
Measure: 100% of named-owner obligations; no gaps by EOY.
Source: 03-dashboard roll-up, 02-organisation-settings department / cluster folders. The Department reads what the site is already creating, not a second form the site has to fill.
Public Trust Audit
A Director can inspect any school's public story, without calling the school.
The community-facing record is part of the Department's posture, whether or not it is acknowledged as such. Oversee gives the Director a one-click read of any school's Trust Portal: what is approved, what is public, what is featured, whether the public version matches the internal record. The Director confirms the public story is aligned with the operating one, before a journalist, a regulator or a concerned parent raises the gap.
Draft
The artefact exists internally. Site owns it. Not visible to community.
Approved
Council or leadership approval captured. Ready for publication at site discretion.
Public
Published to Trust Portal. Parent, prospective family or journalist can read it.
Featured
Site has chosen to lead with this artefact. Director can confirm alignment with internal record.
Director audit
Director inspects any site's public record in one click. Drift from internal record flagged.
CurrentSource: 16-trust-portal. The Director confirms that the public story matches the internal one, before the gap is raised by someone else.
Why existing oversight tooling still fails the Director tier.
| Capability | Spreadsheets and Email | Department-Built Tools | Independent-School Product | BI / Power BI Dashboards |  |
|---|---|---|---|---|---|
| Live portfolio heat-map for Director | No | No | Not applicable | Possible, not live | Yes |
| Single-school alert feed with owner and age | Inbox-based | No | No | No | Yes |
| Incident storm mode: triage, delegate, playbook, debrief | No | No | No | No | Yes |
| Department roll-up composed from live site data | Manual | Partial | Not applicable | Reported | Native |
| Public trust audit: one click per school | No | No | No | No | Yes |
| Designed for the Director tier holding 20 to 40 schools | No | No | No | No | Yes |
BI is downstream of data. Oversee is where the data is created, at the site, in a single governance layer. A BI layer on top of Oversee is trivial. A BI layer on top of 25 disconnected tools is what the Department already has.
Frequently asked
Frequently asked questions
Oversee serves principals, directors and departments from one rail.
Who we help
Principals
Less re-explaining, more doing. The Director reads what you already know.
Deputy Principals
The oversight pane the role has been running from notebooks, now live and portable.
Governing Councils
The Director can support the Council, not surprise it. Same source, same signal.
Education Directors
The tool the role has never had: twenty-five schools, live, across Lead, Improve and Assure, with a storm mode for the day three schools go red at once.
Why EthosGov
TrustWhy the sector should trust Oversee.
Aligned to Australian public-school system governance: Department for Education (SA) Directorate structures, multi-site oversight frameworks, state and federal reporting rhythms.
Built on the Invisible Labour evidence base (SASSLA and Monash, 2024). The case that Director visibility, done properly, is load reduction for the Principal, not load addition.
ISO 27001 aligned, Australian hosted, WCAG 2.1 AA, procurement-ready with role-based access and permission scoping by design.
Frequently asked questions
What is public school oversight software?
It is a portfolio and system oversight layer that connects site operations (Lead, Improve and Assure) to director and department views, with a dedicated pattern for multi-site critical incidents.
Can this work with partial portfolio rollout?
Yes. Directors can begin with a pilot subset and still gain immediate cross-site visibility.
How does incident storm mode differ from a single-school alert?
Storm mode is for the day three or more schools go red at once: a cluster bereavement, a state-wide weather event, a safeguarding story. It switches the view to a triage queue, shares the playbook across schools and runs a parallel debrief lane so the storm becomes learning for the whole portfolio.
How does this support Go2Gov procurement?
Oversee is designed for procurement readiness with role-based controls, system-level reporting and partial coverage as a first-class case.
A Director dashboard sounds like more surveillance of the Principal.
It is not. The Director sees what the Principal sees. The intent is to stop the Director re-asking for what the site already knows. It is a load-reduction mechanism, evidenced in site pilots: less re-reporting, not more scrutiny.
Does every site have to be on EthosGov for a Director to use Oversee?
No. The portfolio view works with partial coverage. A Director can light up the schools that are on EthosGov and keep the rest on current process, then expand as more schools come online.
How is this different from a BI dashboard the Department could build?
BI is downstream of data. Oversee is where the data is created, at the site, in a single governance layer. A BI layer on top of Oversee is trivial. A BI layer on top of 25 disconnected tools is what the Department already has.
What about data sovereignty and privacy?
Australian hosting. Role-based access. Permission scoping per role. ISO 27001 aligned. See /trust for the full posture.
Inside Oversee
The Director's surface, visible.
The portfolio view Directors have not had before. Actual screens.
Heatmap across the portfolio 
Compare schools side by side 
Priorities rolled up 
Roles across the portfolio 
Board papers in one place
Go deeper
Read the thinking behind Oversee
- OverseeArticle
The portfolio view Directors have never had
What changes when the surface is real, not a spreadsheet from the Department.
Read more
- OverseeArticle
Routing critical incident escalation for Directors
Storm mode, triage queue, parallel debrief lane.
Read more
- OverseeArticle
Why the Department keeps building and retiring the same tool
The structural problem department-built tools cannot solve.
Read more
The wedge promise
Five schools, one Director, a live portfolio. Sixty days.
Start with five sites. Scale if it works.
Day
Day 1
Governance Review with Director and five Principals.
Day
Week 2-3
Sites configured. Roles assigned. Views scoped.
Day
Week 4-6
Storm mode drill. Roll-up patterns calibrated.
Day
Day 60
Director portfolio is live. First review runs in EthosGov.