Create your trust
Add a trust in the platform administration portal.
Connect linked schools’ evidence and website oversight. Share content proposals while each school retains approval of its own published pages.
Shared visibility. School-level context.
The trust overview combines current assessed readiness, source coverage, critical findings, outstanding work, training and staff-duty summaries. Expand school rows to inspect the underlying categories.
Review safeguarding evidence and agree accountable next steps. The school view explains the context behind the trust totals.
Example figures, not customer results or an inspection judgement.
Add a trust in the platform administration portal.
Select the trust on each school record. Deleted schools are excluded from the active overview.
Create a Trust administrator account bound to that trust. Access follows its current linked schools.
Use the combined overview and prepare school governor reports. Trust policy management is available through the existing trust workspace.
Readiness averages schools with current assessed scores. Source coverage is shown separately; it is not whole-school evidence completeness. Training completion uses assigned staff/module pairs.
An empty or unassessed school does not receive a fabricated score. Unavailable sources remain visible for follow-up.
Review linked schools’ website status and prepare central content proposals. A school officer reviews and applies each proposal to a versioned draft; another authorised officer approves the page before publication. Trust administrators cannot directly publish school pages through this workflow.
Schools can use CMS themes and their own Design Studio Brand Kit. Later central template changes do not overwrite accepted school content.
Explore CMS & Design Studio ↗AI-assisted policy review, evidence retrieval and website improvement help your team turn information into practical next steps.
Explore private AI ↗IGNX combines school-scoped retrieval with configured AI services. AWS deployments can process document evidence using managed models through Amazon Bedrock.
Model provider, processing region, storage and data residency are agreed before rollout. Local deployments can use a self-hosted model.
Retrieval brings relevant evidence into AI-assisted analysis. Review outputs against the source documents and current guidance.
School records are scoped through account permissions. Authorised trust users can review their linked schools; platform administrators have broader access.
Agree model hosting, storage, retention and access before rollout. Access segregation does not mean every school has a separate database or server.
AI processing follows the configured provider and data boundary. Website crawling, vulnerability checks and email may contact external services when enabled.