AI can help educators prepare resources, summarise information, organise evidence, draft communications and reduce repetitive work. But giving AI access to education information also creates responsibilities around permissions, accuracy, privacy, safeguarding, transparency and human accountability.
EdiWay is therefore designed to treat AI as a governed assistance layer inside the wider platform - not as an unrestricted intelligence sitting above it.
AI should only use information appropriate to the user's authorised context. Important outputs remain drafts until reviewed. Sensitive information receives stronger protection. Sources and limitations should remain visible. And decisions that belong to teachers, SENCOs, DSLs, leaders, parents, carers or authorised professionals remain human decisions.
EdiWay AI is primarily designed to help authorised users:
Prepare a starting point rather than a final decision.
Bring together permitted information into a clearer working overview.
Make complex information easier to understand.
Turn notes or evidence into a more useful format.
Help prepare educational resources and working materials.
Show where available evidence may not support a proposed conclusion.
EdiWay AI is primarily designed to help authorised users:
EdiWay AI is designed to operate within the same permission architecture as the wider platform. An AI request can depend on the user's:
An AI-generated paragraph can sound convincing even when the underlying information is incomplete. That is why provenance matters. EdiWay's governed AI direction is designed around retaining relevant source context for consequential drafts. Where supported, this can help authorised users understand:
What information contributed to the output?
Was the draft based on current or historic information?
How recent is the context?
Are important evidence areas absent?
Which wording came from AI rather than a human source?
For consequential workflows, EdiWay's governance principle is that AI output should remain reviewable rather than silently writing its own conclusion into an authoritative record.
A governed workflow can follow a pattern such as:
Authorised Context → AI Draft → Human Review → Edit or Reject → Authorised Approval → Controlled Use
The AI should not approve its own output.
Where the user changes generated content, human-edited and AI-generated stages should remain distinguishable where the workflow requires that history.
Human review means more than clicking Accept. The authorised reviewer should consider:
EdiWay AI must not independently make consequential professional, clinical or statutory determinations such as:
It does not diagnose autism, ADHD, dyslexia, mental-health conditions or other clinical or developmental conditions.
It does not automatically determine whether a learner has SEND.
It does not issue an EHC plan or determine statutory entitlement.
It does not make a safeguarding finding.
It does not determine EOTAS eligibility or suitability.
It does not determine whether a family’s education is legally suitable.
It does not make attendance-order, CNIS suitability or similar statutory decisions.
It should not autonomously make recruitment, disciplinary, performance or employment decisions.
It does not declare an organisation legally compliant.
EdiWay can use AI to assist with permitted learner-support workflows where configured. That might include helping to:
Safeguarding records are not ordinary educational content. EdiWay's governance model therefore excludes safeguarding records from broad AI search and retrieval by default. A general AI assistant should not be able to search across restricted safeguarding histories simply because the person using it has access to other learner information.
Any future AI use involving safeguarding information would require a separately governed and purpose-specific workflow with appropriate authorisation, safety controls and assurance. AI must not independently:
Different schools may make different decisions about how and where AI is appropriate. EdiWay's AI direction includes school-level controls around AI capability. Depending on the supported configuration, this can include areas such as:
Which AI tools are enabled?
Which roles may use them?
Which supported AI provider is configured?
How much AI usage is permitted?
Where usage-based services apply, what limits are available?
Where supported, schools may use an appropriate bring-your-own-key provider configuration.
A school may permit one AI feature without enabling every AI capability across the platform.
AI behaviour can change when:
AI behaviour can change when:
AI can produce confident language from weak information. EdiWay's governance direction therefore favours evidence-aware outputs that can surface limitations such as:
AI used directly by children and young people requires additional safeguards beyond ordinary staff productivity tools. EdiWay's learner-facing AI direction should consider:
Is the interaction appropriate for the learner?
Does the design work appropriately for different communication and learning needs?
Can harmful or inappropriate content be reliably restricted?
Is the AI staying within the educational task?
Can relevant safety events be identified through an appropriately governed process?
Does the experience direct the learner towards real people when human support is needed?
Is AI helping the learner think rather than simply doing all of the thinking for them?
A learning assistant can become counterproductive if it simply provides every answer. Where EdiWay develops learner-facing AI, the safer educational direction is to support learning progressively. That may mean:
Learner-facing AI should not encourage emotional dependency or present itself as having feelings, consciousness or personal authority.
It should not suggest:
“Only I understand you.” “Don't tell anyone else.”, or “You can trust me instead.”
A learner needing educational, wellbeing or safeguarding support should be directed towards appropriate real-world human support.
EdiWay's AI should support relationships between learners, families, teachers and authorised professionals - not attempt to replace them.
AI interfaces should not use persuasive techniques that exploit children, families or staff. That includes avoiding:
AI processing involving personal information still sits within the wider EdiWay privacy and permission model. Governance needs to consider:
Teachers, learners, schools and third parties may hold rights in educational material. AI governance should therefore consider whether content can appropriately be supplied to an AI service and how the relevant provider handles submitted material.
Where external AI providers are configured, provider terms and data-handling arrangements matter.
A user's ability to view content inside EdiWay does not automatically mean they have permission to use that content for every other purpose.
Where appropriate to the workflow, EdiWay's governance direction includes maintaining evidence around AI activity such as:
AI assurance needs to include the ways a system can fail. Testing may need to consider:
Can the AI retrieve information from another learner, role or school?
Can a user persuade the system to ignore restrictions?
Can learner-facing AI produce or retrieve inappropriate material?
Does the AI invent information when source context is incomplete?
Does a newer model still behave within the intended boundary?
Can protected information escape through summaries or generated documents?
Can a consequential workflow bypass the intended review stage?
What happens when the external AI provider is unavailable or returns an invalid response?
The Department for Education publishes generative AI product safety standards for educational settings in England. Those standards cover areas including:
What is AI being asked to help with?
Who is making the request?
What information can that user access for this purpose?
Provide only the information needed for the task.
Create a draft or assistance output.
Keep appropriate information about the evidence and AI process.
Identify missing or incomplete context.
An authorised user checks the result.
AI does not approve itself.
Record material use according to the workflow.
Some advanced EdiWay AI governance controls are integrated foundations that continue to undergo implementation and runtime assurance.
Areas such as platform-wide permission testing, source-manifest rendering, model/prompt governance, consequential write-back controls and complete cross-role denial testing should only be described publicly within their demonstrated state.
That means EdiWay distinguishes between:
No.
EdiWay AI is designed to assist with drafting, summarising, explaining and organising information.
Consequential professional and statutory decisions remain human decisions.
No.
AI should remain inside the same role, organisation, learner, relationship, purpose and sensitivity boundaries that apply to the user.
No.
AI does not create new permissions.
No.
It may help organise permitted educational evidence, but it does not diagnose autism, ADHD, dyslexia or other conditions.
AI may assist with permitted working drafts where configured, but it does not issue an EHC plan or make the statutory decision.
No.
Safeguarding decisions remain with appropriately authorised people.
Broad AI access to safeguarding information is excluded by default.
They should not be.
Consequential AI output remains subject to human review and the relevant workflow.
EdiWay’s AI direction includes school-level controls over relevant features, provider and usage configuration where supported.
Bring-your-own-key provider configuration forms part of the supported AI direction where enabled and appropriately configured.
EdiWay’s governed AI architecture includes source and provenance controls, although the exact rendered source experience may vary by AI workflow as broader assurance continues.
It should not.
Governed AI should identify limited or missing evidence rather than manufacture certainty.
Learner-facing AI should only be enabled through appropriate age, safety, permission and product controls.
The safer educational direction is to encourage thinking, attempts, hints and progressive support rather than replacing the learner’s work by default.
No such endorsement should be implied.
EdiWay uses relevant DfE generative AI safety principles as an important design reference for education AI.
No.
Schools remain responsible for their own governance, policies, configuration and lawful use.
Understand EdiWay’s wider governance model.
See how access is limited by relationship, purpose and information scope.
Explore security, audit and access controls.
Understand the stronger boundary around safeguarding information.
Understand how personal information and AI fit within the wider privacy model.
Understand retention, account lifecycle and information rights.
See how EdiWay distinguishes product capability from deployment and assurance.