THE PLATFORM

Less scattered work.
More connected evidence.

One connected workspace for school compliance, website publishing and creative communications.

THE WORKFLOW
  1. Understand the finding
  2. Agree an accountable action
  3. Record the work
  4. Review the evidence
01 / CAPABILITIES

Find the tools for your next step.

Search the available workflows below. Some capabilities depend on school features, integrations and service configuration.

12 capabilities

Website / CMS

School website CMS

Build pages, manage navigation and media, import WordPress content and prepare your domain launch. Independent school approval keeps publication tied to the reviewed version.

Explore CMS ↗
Website / STUDIO

Design Studio

Create school artwork with editable templates and a Brand Kit. Review AI proposals, approve designs, export PNG, JPEG or PDF, and add approved graphics to CMS drafts.

Explore Design Studio ↗
Website / 01

Website improvement

Run a website audit, review prioritised findings, record notes and completion, and retest individual findings. Crawl coverage and manual-review findings stay visible.

Policies / 02

Policy requirements & manager

Review setting-specific requirements, manage policy versions and acknowledgements, assess policy content, and record evidence verification.

People / 03

Staff training & pathways

Assign categories or individual modules. Record quiz outcomes and completion; role pathways separately track acknowledgements and certificate expiry.

Leadership / 04

Action tracker

Create and update actions with owners, priorities, deadlines, progress notes and completion evidence. Filter overdue work and export the current view.

Leadership / 05

Governor report

Prepare a dated whole-school briefing covering evidence readiness, coverage, critical findings, training and recorded actions. Add meeting commentary, print to PDF or download a snapshot.

Leadership / 06

Ofsted preparation

Review inspection-report analysis and action priorities. Use evidence packs and inspector-question tools to support preparation. AI functions need configured model and retrieval services.

Trusts / 07

Trust oversight

Link schools to a trust and compare readiness, source coverage, risks, actions and staff training. Trust accounts are limited to their assigned trust.

Cyber / 08

Cyber readiness

Assess controls, manage evidence and actions, and run domain checks. WordPress vulnerability checks require WPScan availability and a configured token.

Leadership / 09

Governance & wider evidence

Maintain governor records and declarations, attendance snapshots and enrichment activities as supporting leadership evidence.

Leadership / 10

Access & audit

Use school roles, scoped portal roles and trust accounts. Two-factor authentication is available; audit records support accountability for tracked changes.

CMS + DESIGN STUDIO

From a finding to a better school website.

Create school content and artwork, review the exact version, then publish with confidence in what changed.

01

A CMS built around school publishing

Edit structured pages, navigation and media with six website themes. Review WordPress content imports before creating drafts. Another authorised school officer approves the exact page revision before publication, public verification and a compliance rescan.

↗
02

Design Studio for everyday school communications

Start with 27 editable templates for banners, posters, newsletters, prospectuses and more. Use your school Brand Kit, arrange text and images, and export independently approved designs as PNG, JPEG or PDF. Insert approved banner and image exports into CMS drafts for a separate page review.

↗
03

Plan the move to your school domain

Review domain ownership, redirects and launch checks, and manage website contact submissions in a school inbox. Hosting, DNS and TLS setup are agreed during onboarding. WordPress imports bring supported content into reviewable drafts; layouts, plugins and forms need separate review.

↗

AI suggestions remain proposals for independent review. Media usage permissions are checked before approved artwork can be published; later draft edits do not change the live version.

02 / FOLLOW-THROUGH

An action needs more than a tick.

01

Owner & deadline

Record a named owner, priority and due date. Overdue actions are calculated from current dates.

↗
02

Notes & evidence

Capture progress and evidence before marking an action done. Reopen an action when further work is needed.

↗
03

Review & export

Filter the tracker and export shown actions as CSV. Website and cyber plans retain their own finding verification.

↗
03 / GOVERNANCE

A briefing the board can question.

The governor report is built from current school records, with unknowns and unavailable sources clearly shown.

GOVERNOR BRIEFING / SAMPLE STRUCTURE

Evidence, risks & next steps.

School & preparation date

Readiness & source coverage

Evidence and risks by area

Assigned training & overdue actions

Leadership context & questions for the board

PRIVATE AI / SCHOOL CONTEXT / HUMAN REVIEW

Intelligence for your school.
Control over your data.

AI-assisted policy review, evidence retrieval and website improvement help your team turn information into practical next steps.

Explore private AI ↗
CONTROLLED AI PROCESSING

Managed models.
Your school context.

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.

01 / UNDERSTAND

Answers with school context

Retrieval brings relevant evidence into AI-assisted analysis. Review outputs against the source documents and current guidance.

02 / SEPARATE

School-scoped access

School records are scoped through account permissions. Authorised trust users can review their linked schools; platform administrators have broader access.

03 / CONTROL

Choose your data boundary

Agree model hosting, storage, retention and access before rollout. Access segregation does not mean every school has a separate database or server.

See how private AI fits the workflow +
  1. School evidenceDocuments and records within the configured school scope.
  2. Retrieval & modelRelevant context processed in the agreed AI environment.
  3. Your team reviewsCheck the evidence, decide the action and record progress.

AI processing follows the configured provider and data boundary. Website crawling, vulnerability checks and email may contact external services when enabled.

Your next step

Bring the right evidence
to the next conversation.

Show me how IGNX works ↗