- Designed for UK Education
- Permission-Aware Access
- Source-Aware Evidence
- Human-Reviewed AI
- A teacher may need one part of the learner journey.
- A SENCO may need another.
- A DSL may work with highly restricted safeguarding information.
- A parent or carer sees information appropriate to their relationship.
- An authorised professional may have access for one defined purpose.
- A school leader may see operational measures without automatically seeing every sensitive learner record.
One learner can have one connected journey without every user seeing the whole journey.
Role
What is this person authorised to do?
Organisation
Which school, trust, provider or organisation are they acting for?
Learner Relationship
Why does this person have a relationship with this learner?
Case or Workflow
Are they involved in the specific work being accessed?
Purpose
Why is the information needed?
Sensitivity
Does the information require stronger protection?
Explicit Restrictions
Are there additional controls that should prevent access?
This creates a more purposeful model than assuming everyone with the same job title should automatically have the same access everywhere.
- Safeguarding
- SEND
- Medical and care information
- Professional casework
- Family information
- Sensitive learner voice
- Cross-organisation sharing
- Statutory processes
Uncertainty should not become permission.
- Parent or carer
- Parental responsibility
- Foster or kinship relationship
- Emergency contact
- School staff relationship
- Tutor relationship
- Authorised professional
- Provider relationship
- Case involvement
- Organisational responsibility
- Start dates
- End dates
- Evidence
- Purpose
- Information scope
- Review points
- Revocation
This helps EdiWay reflect how education actually works: access comes from responsibility and purpose, not simply from knowing who the learner is.
School Information
Remains attributable to the school or authorised staff source.
Learner Evidence
Remains attributable to the learner.
Family Contributions
Remain attributable to parents and carers.
Professional Reports
Retain professional authorship.
Imported Information
Should retain relevant source and historical context.
AI-Assisted Drafts
- Remain distinguishable from underlying source evidence.
- Connecting information does not silently turn one source into another.
- A parent observation does not become a school finding.
- A screening result does not become a diagnosis.
- An AI summary does not replace the evidence behind it.
Source matters because meaning depends on where information came from.
- A learning activity
- Assessment
- Resource
- Support plan
- Intervention
- Meeting
- Review
- Professional process
- Transition
- Decision workflow
- Who supplied it?
- What does it support?
- What process produced it?
- Has it been reviewed?
- What happened next?
Better governance depends on evidence remaining meaningful – not becoming another uncontrolled document archive.
- Teachers
- School leaders
- SENCOs
- DSLs
- Governors
- Parents and carers
- Local-authority roles
- Qualified professionals
- Other authorised decision-makers
The platform may help structure the evidence. The responsible person remains accountable for the conclusion.
Safeguarding
Restricted to appropriately authorised safeguarding workflows and roles.
Medical and Care Information
Purpose-limited and separately permissioned.
SEND and Support
Available according to relevant role, relationship and workflow.
Learner Voice
Can require controlled visibility depending on sensitivity and context.
Professional Information
Limited according to the authorised relationship and purpose.
Family Information
Not automatically available to every person working with the learner.
A connected platform should reduce fragmentation without flattening important confidentiality boundaries.
Recipient
Who is receiving the information?
Learner
Who does it concern?
Purpose
Why is it being shared?
Scope
What information is actually needed?
Authority
What permission or lawful basis supports the disclosure where applicable?
Duration
Is access temporary or continuing?
Revocation
Can the relationship or access be ended?
Evidence
Can the disclosure itself be traced?
This supports collaboration while keeping the difference between sharing selected information and opening the learner record clear.
- Approved information
- Recipient scope
- Purpose
- Snapshot
- Access history
- Expiry
- Revocation
- Provenance
A learner can therefore maintain continuity without every future organisation inheriting unrestricted access to the entire historical record.
- Access
- Denied access
- Record changes
- Workflow transitions
- Information sharing
- Lifecycle changes
- Relevant administrative activity
- Who did this?
- When?
- In which organisation?
- Against which learner or workflow?
- What changed?
- Was access permitted?
Audit does not replace good policy or professional accountability. It helps make those responsibilities more visible.
- Draft
- Summarise
- Explain
- Structure information
- Prepare resources
- Organise evidence
- Prepare working reports
But AI should only work with information the user is permitted to use for the relevant purpose. Sensitive data does not become available simply because an AI feature is being used. Consequential AI output remains subject to human review.
And EdiWay AI must not independently:
- Diagnose a learner
- Issue an EHC plan
- Make safeguarding findings
- Determine SEND status
- Decide EOTAS eligibility
- Make statutory decisions
- Approve its own consequential output
AI can assist the work. It does not inherit the professional’s authority.
- Purposeful access
- Permissions
- Relationship scope
- Source attribution
- Controlled sharing
- Sensitive information
- Auditability
- Retention
- Subject rights
- Account lifecycle
However, software alone does not make an organisation compliant. Schools and other responsible organisations still need appropriate policies, lawful bases, notices, staff practice, retention decisions and governance processes.
- Information type
- Record owner
- Learner age
- Education status
- Legal requirements
- Organisational responsibilities
- Account lifecycle
- Safeguarding requirements
- Holds or restrictions
- Subject rights
The wider EdiWay learner-continuity model does not remove an organisation’s own responsibility to apply appropriate retention rules.
- Navigation
- Forms
- Content
- Workflows
- Learner interfaces
- Parent and carer interfaces
- Professional workspaces
- Documents
- Notifications
- AI-assisted content
Accessibility assurance is an ongoing product responsibility rather than a one-time design claim.
- Domain permissions
- Defined measures
- Organisational scope
- Source freshness
- Appropriate aggregation
- Small-cohort protections where relevant
Organisational visibility is not a shortcut around learner-level permissions.
Detailed school governance, policy and improvement workflows remain within the dedicated School Governance area.
Supported / Available
A capability that can be described within its documented boundaries.
Integrated Foundation
The core capability exists, but deployment, migration, role, provider, accessibility, legal or other assurance work may still be required.
Controlled / Policy-Dependent
A workflow is deliberately unavailable until the required configuration, permission, entitlement or policy is active.
Future / Not Claimed
A direction or capability that should not yet be marketed as available.
This distinction helps keep public product claims aligned with actual product assurance.
Discover
Understand source systems and responsible data owners.
Map
Identify where information belongs in the EdiWay model.
Classify
Recognise sensitive or high-risk records.
Test
Use staged or dry-run migration where appropriate.
Migrate
Move information through controlled processes.
Reconcile
Check counts, duplicates, attachments and exceptions.
Verify
Test roles, permissions and workflow behaviour.
Record
Keep appropriate completion and exception evidence.
Historic information should not silently become a current statutory, safeguarding or professional conclusion simply because it was imported.
- Denied users
- Cross-school access
- Cross-organisation access
- Direct request tampering
- Stale updates
- Concurrency
- Provider failure
- Recovery
- Accessibility
- Other negative-path scenarios
EdiWay’s assurance approach recognises that preventing the wrong action is as important as enabling the right one. Detailed technical and operational controls belong on the Data Security and Governance page.
- DfE endorsement
- Ofsted endorsement
- Local-authority endorsement
- NHS integration unless specifically implemented and assured
- Automatic statutory compliance
- Automatic legal decisions
- Universal compliance simply because a school uses EdiWay
EdiWay supports governed education workflows.
Responsible organisations and authorised professionals remain responsible for the decisions that belong to them.
- A safeguarding finding
- A diagnosis
- SEND status
- EHC plan entitlement
- A clinical conclusion
- EOTAS eligibility
- Statutory consent
- Home Education suitability
- A legal compliance conclusion
- A disciplinary outcome
- An employment decision
The platform can structure workflows, preserve evidence, enforce permissions and help people prepare information.
Human decision-makers remain accountable.
Connect. Control. Evidence. Review.
Who is acting?
2. Establish the Organisation
In which authorised context are they working?
3. Resolve the Relationship
Why do they have access to this learner or workflow?
4. Check the Purpose
What are they trying to do?
5. Evaluate Sensitivity
Does the information need stronger controls?
6. Allow or Deny
Apply the relevant permissions and restrictions.
7. Preserve the Source
Keep clear where information came from.
8. Record Important Actions
Retain appropriate audit and workflow evidence.
9. Keep Humans Accountable
Ensure consequential decisions remain with the responsible person.
10. Review the Relationship
Change or end access when responsibility changes.Let college become the next stage – not a reset.
This is how a connected education platform can remain connected without becoming indiscriminate.
No.
EdiWay is designed so access can depend on role, organisation, learner relationship, case, purpose, sensitivity and other restrictions.
No.
A job title alone should not determine access to every learner or information area.
Sensitive actions are designed to fail closed rather than infer access.
No.
Family access remains dependent on the relationship, information type, permissions and applicable workflow.
No.
Professional access is designed to remain learner-specific and purpose-limited.
No.
Organisation membership does not automatically create learner-level access.
The platform is designed to preserve source and provenance so school, family, learner, professional and imported information can remain distinguishable.
No.
AI should operate within the same underlying access and purpose boundaries as the authorised user.
No.
Consequential professional and statutory decisions remain human decisions.
No.
Safeguarding information is excluded from broad AI retrieval by default.
No.
EdiWay can support governed workflows and evidence, but organisational compliance depends on law, policy, configuration, implementation and human practice.
EdiWay should not claim DfE or Ofsted endorsement unless a specific formal approval exists and can be evidenced.
The platform foundation is designed to record material actions, access, denials and lifecycle changes.
No.
Some capabilities may be supported, controlled, configuration-dependent, in assurance or part of a later product stage.
Data Security and Governance
Explore platform access, security, audit and operational data controls.
Permissions, Consent and Information Sharing
Understand how relationships, purpose and information scope govern sharing.
AI Governance
See how EdiWay keeps AI permission-aware and human-reviewed.
Safeguarding Boundaries
Understand why safeguarding information requires separate, stronger controls.
Privacy and Data Protection
Read how privacy and organisational data responsibilities fit around the platform.
Data Retention and Subject Rights
Understand retention, account lifecycle and information rights.
Implementation, Migration and Product Assurance
See how EdiWay approaches migration, deployment and capability assurance.
- One learner journey.
- Clear relationships.
- Permission-aware access.
- Sensitive-data boundaries.
- Source-aware evidence.
- Controlled information sharing.
- Traceable actions.
- Human-reviewed AI.
- Human accountability.
- And product claims that stay within the boundaries the platform can support.