EthosGov vs CompliSpace
Policy library vs execution layer. Why public schools do not need the policy library the Department already wrote, and what they need instead.
CompliSpace, now part of Ideagen, is the most established governance platform in the independent school sector in Australia.
It offers mature policy libraries, compliance documentation frameworks, risk templates, and audit trails. For independent schools, where the Board carries governance authority and the Business Manager holds the rail, CompliSpace is a credible choice.
Public schools are a different operating environment. The distinction matters, and it matters more than it first appears.
The Governance Model Is Different
An independent school is a sovereign entity. Its Board authors its policies. Its Business Manager operationalises them. Its assurance posture is constructed inside the school.
A public school is not sovereign in that sense. It sits inside a system of hundreds of schools, a Chief Executive, a chain of Education Directors, and a Department that writes the policies every school must execute.
Authorship is not the school's job. Execution is.
CompliSpace was designed for the authorship model. The product is organised around helping schools write, maintain, and demonstrate their own policy frameworks. That is the right product for an independent school.
In a public school, the school does not need to author the child safety policy, the WHS framework, or the incident response protocol. The Department has already done that. What the school needs is proof that the policies were executed.
A policy library cannot prove execution. Only an execution layer can.
Policy Library vs Execution Layer
CompliSpace is a policy library with compliance tooling around it. The library is its centre of gravity. Schools buy it because the library is thorough, professionally maintained, and trusted by regulators.
EthosGov is an execution layer with reporting tooling around it. The execution record is its centre of gravity. Schools adopt it because the evidence trail is live, structured, and composable into the three audiences that assurance in the public system has to serve.
These are different products. They are not direct competitors.
The comparison becomes real when a public school or a Department considers whether a policy library approach is sufficient for the public system. In most cases, the answer is no. The policy library problem has been solved by the Department at the central level. The execution problem has not.
The Verbs Tell the Story
EthosGov is organised around four verbs the public system already uses. Lead, Improve, Assure, Oversee.
CompliSpace does not frame itself around these verbs. Its framework is structured around governance, risk, and compliance in the traditional independent-school sense. The framework is coherent, but it does not map to the language a public Department, a public school Principal, or a public Education Director uses to describe their work.
Language is not cosmetic. A tool that asks the sector to adopt its vocabulary is adding friction. A tool that uses the sector's own vocabulary is reducing it.
Where CompliSpace Fits
For independent schools where policy authorship is a real and ongoing activity, CompliSpace fits. The product is mature. It has a long customer base. It has earned its reputation.
For public schools where policy is centrally authored, the policy library features of CompliSpace are largely redundant. The investment would pay for capability the school does not use.
Where EthosGov Fits
For public schools and public-system deployments, EthosGov is purpose-built.
The execution layer captures evidence as work happens. The compliance calendar is pre-loaded with state-specific obligations, maintained centrally, configured per site. The risk register uses ISO 31000 alignment. Post-incident review writes back to risk, policy and training, automatically. Council packs build from existing work. Education Directors see a live portfolio view across their schools.
None of these capabilities exist in a policy-library product. They are not a criticism of the policy-library model. They are a different category of product.
Capability Snapshot
| Capability | EthosGov | CompliSpace (Ideagen) |
|---|---|---|
| Policy authorship tools | Not centre of product | Yes, centre of product |
| Central policy library maintained by vendor | Not applicable (Department authored) | Yes |
| Pre-loaded state-specific compliance calendars (SA DfE, ESB) | Yes | Limited |
| Live execution record (evidence captured as work happens) | Yes | Limited |
| ISO 31000-aligned risk register with live treatments | Yes | Yes |
| Post-incident review feeding back into risk and training | Yes | Limited |
| Action register capturing decisions from every leadership forum | Yes | No |
| Council-ready pack auto-generated in plain language | Yes | No |
| Live Director portfolio view across 20-30 schools | Yes | No |
| Department roll-up from site-level data | Yes | No |
| Parent-facing trust portal | Yes | Rare |
| Designed for public-system governance model | Yes | No |
| Centre-deployed, site-configured, centre-reported | Yes | No |
The Line We Stand On
Public schools do not need a policy library. The Department already gave them the policies.
What public schools need is a way to show they actually did them. That is a different product. That is what EthosGov is.
Take the Next Step
If this article speaks to your situation, two routes from here.
Go deeper on the verb. Read the Assure cornerstone. It is the deep page that sits underneath every article in this category.
See it on your site. Book a Governance Review. 45 minutes. No deck. We measure what the friction is costing you and whether EthosGov reduces it measurably.
Part of the EthosGov resources library. Governance infrastructure for public school systems. Lead. Improve. Assure. Oversee.
Discover more about EthosGov
Continue exploring governance insight, product context, or speak with our team.