Who it's for / Departments and Go2Gov
Governance infrastructure you do not have to build.
Departments of Education spend years building site-level governance tools that age out before they mature. EthosGov is the deployable alternative. Multi-state architecture. Australian hosting. ISO 27001 aligned. WCAG 2.1 AA. Go2Gov procurement ready. Deployed at the centre, owned at the site, reported through the Director tier.
Department posture composed from live site data across every Director portfolio.
Promise 1 of 3
Deployable, not buildable.
Stand up at the Department level, configure per state, roll to Director portfolios. Cadence in weeks, not in years.
Promise 2 of 3
Procurement-ready out of the box.
ISO 27001 alignment, Australian hosting, WCAG 2.1 AA, ISMS and DR documentation on request. Go2Gov pathway in place.
Promise 3 of 3
Evidence chain, directive to site.
Watch a directive move the portfolio in real time. Compliance reporting becomes inspection of a live chain, not reconstruction of a paper trail.
Why a change is on the table
Two decades of internal builds. The same shipping problem.
Departments of Education across Australia have been trying to build site-level governance tooling internally. The pattern is consistent. The cause is not effort. The procurement-to-deployment cycle is longer than the half-life of the policy environment the tool was built to serve.
Burden 1 of 3
Built and ageing.
Internal builds age out before they ship. Each new policy environment finds the tool a cycle behind, and another rebuild is on the agenda.
Burden 2 of 3
Wrong-shape commercial.
Enterprise GRC products were built for board-below-executive. They do not model school-below-Director-below-Department, so they sit unused or distort the role.
Burden 3 of 3
Twenty-five spreadsheets.
Governance tooling left to each site to solve individually. Twenty-five sites, twenty-five spreadsheets, all re-keyed into Departmental returns. No shared chain of evidence at the centre.
The role
Why Departments keep building.
Departments of Education across Australia have spent two decades trying to build site-level governance tooling internally. The pattern is consistent and the reason is not a lack of effort.
- 01
Department-built tools age out faster than they ship.
The procurement-to-deployment cycle is longer than the half-life of the policy environment the tool was built to serve.
- 02
Commercial GRC products do not model the site-to-Director-to-Department chain.
Enterprise risk and compliance products were built for a board-below-executive pattern, not a school-below-Director-below-Department one.
- 03
Governance tooling is left to each site to solve individually.
Twenty-five schools in one portfolio, twenty-five different spreadsheets, all re-keyed into Departmental returns. No shared chain of evidence.
Departments and Go2Gov on EthosGov
What changes with EthosGov.
Four shifts the Department sees when EthosGov is the shared governance rail underneath a Director portfolio.
Deployable, not buildable.
Stand up at the Department level. Configure per state. Roll to Director portfolios. Shipping cadence measured in weeks, not years.
Context
The Go2Gov pathway.
EthosGov is structured for the Go2Gov procurement route. That means eligibility documentation, a graduated deployment model that matches pilot-funding cadence, and a reporting posture compatible with Departmental sponsorship.
Three reference deployments are in scoping and delivery: the SA DfE five-school pilot through a Director portfolio, a Catholic Education SA governance extension and a federated deployment with Christian Education National. Procurement pack is available on request.
Voice
Framework alignment.
The frameworks and standards EthosGov aligns to. Each one carries a procurement artefact available in the Trust pack.
Aligned to ISO 27001 for information security. Audit-ready ISMS documentation available on request.
Aligned to ISO 31000 for risk management. Risk controls modelled directly in the Assurance layer.
Aligned to WCAG 2.1 AA for accessibility. Accessibility is a design-time constraint, not an afterthought.
Aligned to the Go2Gov procurement model. Australian hosting, Australian-registered corporate entity, sovereign data handling.
Life inside the work
What a Department sees.
Seven touchpoints across a typical reporting cycle, from directive issue to Executive posture.
- Week 1
Directive issues.
A central directive lands. The system routes it to every Director portfolio and every site, with owner and due date.
- Week 2
Coverage read.
Department sees live coverage of the directive across the system. Which portfolios have acknowledged. Which sites are evidencing.
- Week 4
Pattern emergence.
Repeated blockers surface. Department adjusts support rather than waiting for end-of-term report.
- Week 6
Portfolio roll-up.
Every Director portfolio composes into a Department view. The Executive Director reads live posture, not a rebuilt summary.
- Week 8
Cross-state comparison.
Where EthosGov operates in more than one jurisdiction, comparable posture is available by design.
- End of term
Departmental reporting.
Minister-ready reporting artefacts compose from the same live chain. No re-build. No reconciliation.
- Next cycle
Policy learning loop.
Patterns inform the next directive. The tool closes the loop between policy and practice.
Talk track
How EthosGov enters a Department conversation.
Departments have been buying tools and retiring them for fifteen years. This is the structural answer, not another product.
Department Buyer
Opening
We are not another vendor. We are the rail you have been trying to build and retire.
Department Buyer
Positioning
Policy authored centrally, adopted at the site, measurable up. One source of truth that survives a leadership change.
Department Buyer
What we need from you
A Directorate willing to pilot at five schools. We will do the rest.
Answers
Frequently asked questions
Is EthosGov on a panel or procurement pathway?
EthosGov is configured for the Go2Gov procurement pathway and holds the artefacts required to support Departmental pilot funding and graduated deployment. Panel status and pathway availability vary by jurisdiction and are confirmed during scoping.
Where is data hosted?
Australian hosting by default, on Australian-sovereign infrastructure. Data residency statements are included in the procurement pack.
What is the graduated deployment model?
A Department typically begins with a Director-portfolio pilot of four to five schools. Value lands within the first term. Portfolio coverage expands in waves aligned to natural Departmental cadence points.
How does EthosGov differ from commercial GRC products?
Commercial GRC products model a board-below-executive pattern. EthosGov models the school-below-Director-below-Department pattern the public school system actually operates in. That difference is architectural, not cosmetic.
Request the procurement pack.
ISMS documentation, DR playbook, penetration test summary, DPA template, ISO alignment statements, reference deployment list. Emailed on request, under NDA where needed.