Complete Platform White Paper

A connected operating system for school, family, learner and authorised professional workflows

September 2026

https://ediway.co.uk

Publication note and scope

This white paper brings together EdiWay’s established public platform narrative and the later 2026 platform architecture, governance and statutory-workflow developments. It is intended to be an in-depth description of the connected platform and the processes it supports, not a feature-count catalogue and not a website-production tracker.

EdiWay is presented here as a native, all-in-one education platform. Core records, workflows, communications, documents, reporting, safeguarding collaboration, attendance, entitlements and operational processes are designed to run on EdiWay-owned services and canonical EdiWay data. External connections are controlled boundaries for migration, authorised exchange, payment processing or specifically approved interoperability; they are not intended to become hidden runtime dependencies for core EdiWay workflows.

Explore EdiWay: School Platform  |  Families & Learning Pathways  |  Trust & Governance

1. Executive summary

Schools and the wider education system increasingly manage the same learner across many separate tools: records, attendance, SEND, safeguarding, assessments, resources, parent communication, workforce, recruitment, payments and emerging AI services. Fragmentation creates duplicate records, repeated data entry, inconsistent evidence, disconnected workflows and additional security boundaries.

EdiWay is designed to address that fragmentation by organising work around one governed learner journey. The platform combines school management, family participation, learner support, assessment, curriculum, workforce, operations, commerce, reporting and governed AI within a shared permission-aware architecture.

The platform’s newer architecture moves beyond a single-school record. A learner can move between mainstream school, alternative provision, independent or online provision, part-time further education, home education, flexi-schooling, temporary arrangements and other authorised pathways while retaining one coherent identity and a time-aware history of education status, responsible organisations, evidence and access decisions.

This does not mean every participant sees everything. EdiWay is explicitly designed so that school staff, families, local-authority roles, providers and professionals see only the information and actions they are authorised to use. Sensitive records can require role, organisation, learner, relationship, case, purpose and field-level checks before access is allowed.

The result is a platform that can support day-to-day school operation while also providing the foundations for continuity across home education, EOTAS, alternative provision, transition, multi-agency collaboration and emerging statutory processes.

Explore EdiWay: School Platform  |  Core Features  |  Families & Learning Pathways

2. Why EdiWay exists

2.1 Fragmented systems create fragmented journeys

• The same learner is duplicated across MIS, attendance, SEND, safeguarding, assessment, communication, HR and payment tools.
• Evidence is repeatedly exported, copied or re-keyed.
• Families and professionals can be asked to repeat information already held elsewhere.
• Leaders can lack one operational view of learning, support, workforce and school services.
• Sensitive information can move into uncontrolled spreadsheets, inboxes or downloads.

EdiWay’s response is not simply to place many menus in one interface. The underlying principle is to connect records and workflows so that a lawful, authorised action in one area can use the same canonical learner, organisation, evidence and audit foundations as another area.

2.2 SEND, safeguarding and evidence pressure

SEND and safeguarding work depend on chronology, evidence quality, timely review and clear ownership. EdiWay therefore treats plans, interventions, evidence, outcomes, referrals, meetings and reviews as structured processes rather than isolated documents. The platform is designed to retain source history, decision rationale and review state while keeping human professionals responsible for conclusions.

2.3 Workforce and administrative burden

Administrative work becomes particularly expensive when the same information must be recreated for attendance follow-up, support plans, reports, staffing, parent communications, recruitment and compliance evidence. EdiWay is intended to reduce that repetition by reusing governed records and by giving each role a workspace appropriate to its responsibilities.

2.4 Changing education pathways

A learner’s education may no longer fit one continuous full-time school enrolment. Home education, hybrid arrangements, EOTAS, alternative provision, part-time FE and temporary placements introduce questions about who is responsible, where education is expected to take place and which evidence supports that position. EdiWay’s education-status model is designed to make those questions explicit and historically traceable.

Explore EdiWay: Home Education  |  EOTAS  |  Professional Collaboration

3. Platform operating model

3.1 Native-first architecture

EdiWay is intended to own the core experience end to end. School, learner, family, support, workflow, document, reporting and communication processes should operate on EdiWay’s own canonical data and shared services. External connections should be explicit boundaries for purposes such as migration, statutory exchange, payment processing or approved interoperability.

3.2 Shared platform foundations

3.3 Human accountability

EdiWay is designed to automate administration and support information work, not to automate statutory judgement. Teachers, school leaders, SENCOs, DSLs, local-authority officers and other authorised professionals remain responsible for professional and statutory decisions.

Explore EdiWay: Data Security & Governance  |  Permissions, Consent & Information Sharing  |  Implementation & Product Assurance

4. Identity, learner continuity and education status

4.1 Persistent learner identity

The central architectural shift is from a record tied only to one school enrolment toward a persistent learner identity. The learner remains the same person when their provider, education mode, family relationship, responsible organisation or access context changes.

• Learner identifiers can be reconciled without making one external identifier the master key.
• Previous names, relationships and education arrangements can remain historically queryable.
• School transitions can preserve approved, governed snapshots rather than requiring uncontrolled exports.
• Home education, EOTAS and other pathways reference the same learner instead of creating unrelated identities.

4.2 Effective-dated education status

EdiWay’s education-status foundation is designed to answer a practical question at any point in time: where is this learner expected to receive education, who is responsible for knowing that, and what evidence supports the status?

4.3 Transition and learner continuity

Transition packs and learner continuity are designed around approved, purpose-bound information sharing. A transfer can use an immutable snapshot, recipient scope, purpose or lawful basis, expiry, revocation and access history instead of treating a downloadable document as unrestricted permission to reuse the whole learner record.

Explore EdiWay: Admissions & Learner Records  |  Transition Packs & Learner Continuity  |  Adult Learner Record

5. Permissions, relationships and information sharing

5.1 Beyond ordinary role-based access

A role such as teacher, SENCO, DSL, parent, provider or local-authority officer is not sufficient by itself to decide access. EdiWay is designed to combine role-based access with organisation membership, learner relationship, case membership, purpose of use, sensitivity and explicit restrictions.

5.2 Family and professional relationships

The platform distinguishes a general account from the legal or operational relationship that account has with the learner. Parent, parental responsibility, kinship care, foster care, family network, emergency contact, authorised representative and professional relationships can have different rights, dates and evidence.

5.3 Information-sharing ledger

Significant disclosures should be attributable: what was shared, by whom, to which recipient, for what purpose, under which lawful basis where recorded, and at what time. This allows EdiWay to support controlled collaboration without treating every participant as a full-record user.

5.4 Child and family voice

Learner and family contributions can be recorded as structured evidence with controlled visibility. The interface should not promise absolute confidentiality where safeguarding or legal obligations may require disclosure, and sensitive child voice should be protected from broad access.

Explore EdiWay: Permissions, Consent & Information Sharing  |  Privacy & Data Protection  |  Professional Collaboration

6. School onboarding, setup and leadership

6.1 From organisation creation to operating school

1. Create or select the school/organisation and define the appropriate education sectors, years, settings and active services.
2. Assign authorised staff and leadership roles with school and domain scope.
3. Configure term dates, timetables, classes, subjects, attendance, behaviour, communications and operational settings.
4. Adopt relevant policies, entitlements and product modules.
5. Load or migrate learner, staff and supporting data through governed import or migration workflows.
6. Run validation and reconciliation before relying on imported or newly configured operational data.

6.2 Leadership view

School leaders require visibility across operational demand rather than raw database access. EdiWay’s leadership model brings together role-scoped measures, work queues, scheduled actions, evidence readiness and exceptions from connected domains.

6.3 School governance and improvement

Governors, policies, improvement targets, actions, evidence and review can be managed as governed records. The principle is that improvement evidence should link to canonical source records rather than requiring leaders to build a separate evidence repository.

Explore EdiWay: School Setup & Leadership  |  School Governance, Policies & Improvement  |  Reporting & Administration

7. Admissions, enrolment and learner lifecycle

7.1 Admissions process

1. Receive an enquiry or application and capture applicant information through the authorised process.
2. Review required forms, evidence and admissions criteria within the school’s configured workflow.
3. Record decisions, offers, waiting-list or next-stage outcomes with an auditable status history.
4. Where an offer is accepted, reconcile or create the canonical learner identity rather than creating an unnecessary duplicate.
5. Create the enrolment/provider relationship and activate the correct education status.
6. Provision role-appropriate parent/learner access and connect the learner to classes, timetable, attendance, support and communication workflows.

7.2 Learner profile

The learner profile is a connected workspace rather than a single data-entry form. Depending on role and permissions, it can connect personal and family information, attendance, behaviour, assessments, SEND, interventions, medical/care information, resources, evidence, plans, transition and pathway information.

7.3 Corrections and history

Material lifecycle changes should preserve original dates, sources and correction history. Imported-at time should not be confused with occurred-at time, and high-risk historic data should not be silently converted into a current statutory or safeguarding state.

Explore EdiWay: Admissions & Learner Records  |  Parent & Learner Experience  |  Classes, Timetable & Attendance

8. Classes, timetable, attendance and classroom operation

8.1 Class and timetable model

Classes connect learners, teaching staff, subjects, rooms/timetable periods, curriculum context and classroom activity. The teacher workspace is designed to place attendance, behaviour, resources, assessment, support context and communication within the same role-scoped operating view.

8.2 Attendance process

1. Resolve the learner’s current education status and attendance expectation.
2. Open the authorised class/session register with the expected learner set.
3. Record marks using configured codes and permissions.
4. Surface missing, late or exception states for follow-up.
5. Route follow-up actions and communications according to school policy and role.
6. Retain corrections and material changes through audit/evidence rather than overwriting history without trace.

8.3 Behaviour, rewards and pastoral support

Behaviour and pastoral work can connect incidents, positive recognition, interventions, support actions and review. The platform should distinguish descriptive evidence from prediction and should avoid representing aggregate indicators as autonomous risk determinations.

Explore EdiWay: Attendance & Registration  |  Teacher & Classroom Workspace  |  Behaviour, Rewards & Pastoral Support  |  Communication & Family Engagement

9. Curriculum, assessment, results and learner evidence

9.1 Curriculum and lesson planning

EdiWay’s curriculum foundation connects curriculum plans, sequenced units, prerequisites, class options/pathways, timetable feasibility, lesson plans, resources and evidence. Approved curriculum versions can provide controlled context for lesson planning without allowing AI or a teacher draft to rewrite approved curriculum history.

9.2 Assessment and progress

Assessment can include academic/formative records, targets, progress measures and wider educational screening/support profiles. The platform separates non-diagnostic educational screening from clinical diagnosis and keeps the teacher or professional responsible for interpretation.

9.3 Qualifications, results and destinations

Where configured, results and destination records can follow the learner beyond ordinary classroom assessment, supporting GCSE, A-level or vocational outcome records and post-16 destination context without turning local records into claims of official awarding-body integration.

9.4 Homework, assignments and evidence

1. Teacher selects or creates an authorised learning resource or task.
2. The task is assigned to the appropriate class/learner context.
3. Learner evidence or completion information is submitted through the governed workspace.
4. Teacher reviews the work, adds feedback and records the appropriate outcome.
5. Evidence remains connected to the learner, resource, assignment and review rather than becoming an isolated upload.

Explore EdiWay: Assessment & Progress  |  Academic Assessment & Progress Tracking  |  Qualifications, Results & Destinations  |  Homework, Assignments & Learner Evidence

10. SEND, safeguarding, wellbeing and medical support

10.1 Connected support model

EdiWay brings SEND, wellbeing, safeguarding, medical/care and educational support into one learner-centred architecture while preserving different permissions and decision boundaries. A shared learner identity does not imply a shared visibility level.

10.2 SEND / APDR support process

1. Identify a support need, concern or referral and record the evidence source.
2. Assess need through school-held evidence, learner/family voice, educational screening and professional information where authorised.
3. Create or update support planning, outcomes, adjustments and provision.
4. Deliver interventions or provision and record sessions, evidence and relevant cost/delivery data.
5. Review impact using recorded evidence, human judgement and next-review dates.
6. Where appropriate, feed reviewed outcomes into IEP, EHC Section E or support-plan text through permission-checked, auditable write-back.

10.3 EHC evidence and annual review

The platform can organise school-held EHC information, outcomes, evidence, professional recommendations and annual-review material. It does not issue EHC plans or replace local-authority statutory decision-making.

10.4 Safeguarding workflow

1. Authorised staff record a concern against the authoritative learner or staff subject.
2. The concern is scoped to the correct school/object and receives an immutable version history.
3. DSL or authorised safeguarding roles triage, acknowledge, assign and manage actions/referrals.
4. Chronology, evidence and outcomes remain source-linked and permission-preserving.
5. Archive, retention and legal-hold controls govern lifecycle rather than ordinary deletion.
6. Broad AI/search access to safeguarding records is denied by default; any future AI assistance must use a separately governed purpose-specific workflow.

10.5 Medical and care records

Medical/care functionality can include conditions, allergies, medication, care plans, incidents, first aid and operational alerts. Health data should remain purpose-limited, permission-restricted and visibly distinct by source. NHS interoperability is not claimed unless a separately governed identity, terminology, API and assurance programme is completed.

Explore EdiWay: SEND, Safeguarding & Wellbeing  |  Provision & Support Planning  |  Intervention Support & Impact Review  |  EHC Evidence & Annual Reviews  |  Safeguarding Records & Chronology  |  Medical & Care Records

11. Families, home education, hybrid learning and transition

11.1 Families and learning pathways

Family participation is a core part of the platform. A family pathway can connect goals, barriers, interventions, actions, outcomes, child voice, family voice, providers, evidence and review schedules while still restricting each participant to the data they are entitled to use.

11.2 Home education

Home education is treated as part of the learner’s wider history rather than a disconnected account. Parents can use home-learning plans, routines, resources and evidence while the platform keeps school-origin, home-origin and professional-origin records distinct.

11.3 Hybrid and flexible education

Hybrid/flexible pathways require source-aware continuity. School attendance, home learning and commissioned provision should not be blended into a misleading single measure. EdiWay’s model is designed to preserve the origin and responsibility of each activity while maintaining a coherent learner view.

11.4 Parent and learner workspace

Parents can manage linked children, receive communications, contribute evidence, interact with authorised support processes and access the parts of the learner journey that their relationship permits. Learner self-service can be scoped by age, configuration and sensitivity.

11.5 Transition and adulthood

Transition packs support controlled continuity between organisations. The adult learner record direction is designed so that continuity can increasingly become learner-controlled as the person moves beyond compulsory schooling, subject to product scope and legal configuration.

Explore EdiWay: Families & Learning Pathways  |  Home Education  |  Hybrid Learning & Flexible Pathways  |  Parent & Learner Experience  |  Transition Packs & Learner Continuity  |  Adult Learner Record

12. Alternative provision, EOTAS and multi-agency casework

12.1 Professional collaboration

EdiWay’s professional model is case- and learner-scoped. A professional can be verified, linked to an organisation and invited to a specific learner/case purpose without receiving broad access to unrelated learner records.

12.2 Alternative provision

Alternative provision can be represented through provider relationships, placement dates, attendance/engagement, evidence, reviews and reintegration activity. The school or responsible organisation can maintain oversight without treating the provider as a second master learner record.

12.3 EOTAS

EOTAS is represented separately from ordinary school attendance and enrolment. The platform can connect responsible-school context, commissioned providers, delivery evidence and case status while preserving the legal and operational distinction between EOTAS and school-based provision.

12.4 Multi-agency casework

1. Create or link the canonical learner/case and identify the responsible organisation.
2. Verify each participant organisation and professional relationship.
3. Apply case membership, purpose and sensitivity scope before exposing information.
4. Record meetings, requested evidence, actions, decisions, timelines and follow-up tasks.
5. Share only the minimum authorised material and retain disclosure/access evidence.
6. Close or transition the case without deleting the learner’s underlying source history.

Explore EdiWay: Multi-Agency / Specialist Pathways  |  EOTAS  |  Alternative Provision & Provider Management  |  Multi-Agency Casework, Meetings & Evidence  |  Professional Collaboration

13. Children’s Wellbeing and Schools Act 2026 readiness

13.1 Product interpretation

The Children’s Wellbeing and Schools Act 2026 is an important architectural signal for EdiWay because it increases the importance of learner identity, education status, local-authority processes, multi-agency information sharing and accountable statutory workflows. EdiWay’s approach is to extend shared foundations rather than build a disconnected “Act module”.

The Act received Royal Assent on 29 April 2026. Detailed operation of individual provisions may depend on commencement regulations, delegated regulations and statutory guidance. EdiWay therefore treats legal rules as versioned configuration with jurisdiction, effective dates and legal-review status rather than assuming every duty became operational on Royal Assent.

13.2 Vulnerable learner withdrawal / home education

Where a legally approved and active policy requires local-authority involvement before a vulnerable learner can be removed from roll for home education, EdiWay’s bounded workflow is designed to prevent premature completion, capture the relevant assessment/evidence, route the authority decision and update education status only after the configured conditions are satisfied.

13.3 Children Not in School register

The CNIS foundation uses an authority-owned register aggregate linked to the canonical learner, education status, responsible authority, case, workflow, evidence, notifications, timeline and audit. It supports parent/provider information returns, reviews, support offers, controlled corrections and recipient-bound information requests/disclosures without granting a provider full case access.

13.4 No automated statutory determination

CNIS suitability, safeguarding, statutory consent and attendance-order decisions must remain human decisions. The platform may structure evidence, enforce workflow gates and record decisions, but it must not make the legal judgement autonomously.

13.5 What remains deliberately qualified

• EdiWay does not claim that the platform itself makes a school, authority or provider compliant with the Act.
• Rules remain fail-closed where legal configuration, commencement or required policy settings are not approved.
• Complaints/appeals, attendance-order lifecycle and some safeguarding-partner extensions remain areas requiring further implementation or assurance.
• Any public wording must distinguish “supports this workflow” from “guarantees compliance”.

Explore EdiWay: Children’s Wellbeing & Schools Act 2026 Readiness  |  Home Education  |  Permissions & Information Sharing  |  Implementation & Product Assurance

14. Trusts, organisations and governance

14.1 Organisation graph

EdiWay’s organisation model can represent trusts, school groups, local authorities, providers and shared services through effective-dated relationships. This supports historical membership and delegated operation while avoiding the dangerous assumption that belonging to a trust automatically grants learner-level access.

14.2 Delegated roles and policies

Executive, finance, safeguarding, SEND, organisation-admin and shared-service roles can be scoped to their permitted domains. Policies can be inherited, advisory or override-controlled according to configuration, with audit on material changes.

14.3 Trust comparison and executive analytics

Cross-school reporting should use defined measures, denominator rules, domain permission filtering and small-cohort suppression. Aggregate comparison is not a route to unrestricted learner records.

14.4 Governance evidence

Governance work can link policies, meetings, actions, improvement priorities and source evidence. This helps trusts and school leaders work from governed records rather than creating a second uncontrolled reporting layer.

Explore EdiWay: Trust & Governance  |  Data Security & Governance  |  School Governance & Improvement

15. Workforce, recruitment and protected time

15.1 Recruitment to staff record

1. Publish or manage a vacancy within the authorised school/organisation context.
2. Receive and progress applications through configured assessment, task, interview and offer stages.
3. Record the hiring outcome with evidence and role permissions.
4. Convert the successful applicant into the canonical staff identity through a retry-safe staff-linking workflow rather than recreating the person manually.
5. Complete onboarding, qualifications, checks and workforce records.

15.2 HR and workforce

Workforce records can cover staff profiles, contracts/employment context, qualifications, documents, leave, absence, cover, CPD, performance, onboarding, induction, time/shift information and compliance evidence, subject to configured product scope.

15.3 PPA and protected-time foundation

The protected-time model is designed around effective-dated workforce policy, timetabled teaching time, entitlement calculation, protected allocations, disruption, recovery, disputes and leadership oversight. It is intentionally framed as entitlement and workload governance rather than staff surveillance.

Jurisdiction and employment policy matter: a rule applicable to maintained schools in England should not be silently applied to every academy, independent school, college or UK nation.

Explore EdiWay: Recruitment & HR  |  Careers & Recruitment  |  HR & Workforce  |  Staff Records, Onboarding & SCR  |  Absence, Leave, Cover & TOIL  |  Performance, CPD & Induction

16. Operations, compliance, trips, assets and services

16.1 School operations as a connected service layer

Operational services include visitors, clubs, trips, transport-related readiness, premises/compliance evidence, assets, checks, defects and other school-service workflows. Smaller services can remain connected under School Operations while deeper domains mature into dedicated product areas.

16.2 Trips and accountability

Trip readiness can connect participant lists, consent history, risk assessment versions, staff assignment, driver/vehicle readiness, accessibility capacity and minimum-necessary emergency packs. Sensitive medical data should be separately permissioned rather than automatically included in every trip document.

16.3 Compliance, risk and evidence

School compliance can connect recurring checks, evidence, defects, responsible staff, escalation and reporting. The aim is to make evidence traceable to the task or source record, not to present a checklist as proof of legal compliance.

16.4 Assets, QR and utility monitoring

The Operations foundation includes school/location/asset-scoped utility meters, append-only readings, revocable opaque QR credentials and immutable scan events. QR tokens are designed not to expose learner or security details. Mismatches can create reviewable defects instead of silently completing checks.

16.5 Service boundaries

Advanced energy analytics, native/offline scanning, some transport-provider integrations, catering depth and wider residential/Student Life operations remain areas where public product claims should follow demonstrated implementation and assurance.

Explore EdiWay: School Operations  |  School Compliance, Risk & Evidence  |  Data Security & Governance

17. Resources, library, homework and evidence

17.1 Teaching resource library

The Teaching Resource Library supports structured learning resources, classification, search, assignment and connection to classroom/homework workflows. This is distinct from physical library circulation.

17.2 Physical library operations

A separate school library circulation foundation covers catalogue titles/copies, loans, renewals, returns, holds, stocktake and reconciliation. Because this is operationally different from teaching resources, the white paper distinguishes the two even when the public website groups them under broader resource or operations navigation.

17.3 Evidence chain

Learner evidence can be linked to the originating task, resource, plan, intervention or professional process. This allows the platform to show not only that a file exists, but why it exists, who supplied it, what it supports and how it was reviewed.

Explore EdiWay: Resources, Homework & Evidence  |  Teaching Resource Library  |  Homework, Assignments & Learner Evidence

18. Marketplace, payments and commerce

18.1 School storefronts and purchasing

EdiWay Marketplace allows schools to operate storefronts and manage products, orders and parent purchasing within a linked-school context. Public browsing and parent-linked purchasing can be separated so that the relationship to a school is respected where required.

18.2 Stripe Connect and seller workflows

Marketplace payment architecture uses Stripe Connect for seller onboarding and payment boundaries. EdiWay retains platform-side order, commission, reconciliation and audit evidence while avoiding claims that local recorded tax information is itself tax advice or a statutory VAT return.

18.3 Recorded tax evidence

The platform has a bounded recorded-tax evidence layer for snapshots and adjustments, but merchant-of-record policy, tax determination, accounting integration and professional review remain separate concerns. Historic transaction evidence should remain immutable even if a seller’s later tax status changes.

Explore EdiWay: School Marketplace & Payments  |  Marketplace Buyer Terms  |  Marketplace Seller Terms

19. EdiWay AI and governed automation

19.1 AI as a governed assistance layer

EdiWay AI is designed to work inside the same school, learner, role and entitlement boundaries as the rest of the platform. Its primary role is to draft, summarise, explain and create practical resources from authorised context, with human review before consequential use.

19.2 Typical supported uses

• Resource and lesson drafting from approved context.
• Communication drafts.
• Report and learner-support drafts.
• Literacy/dyslexia and Preparation for Adulthood draft support where configured.
• Evidence-aware summaries that identify missing source information rather than inventing it.
• Usage/credit controls and BYOK provider configuration where supported.

19.3 Governance controls

• Source snapshots and provenance should be retained for consequential drafts.
• AI cannot approve its own output.
• Sensitive data is accessible only when the actor could access the underlying source for the permitted purpose.
• Safeguarding records are excluded from broad AI search/retrieval by default.
• AI must not diagnose, issue EHC plans, make safeguarding findings, determine EOTAS eligibility or make statutory decisions.

19.4 Education AI safety

DfE generative-AI product safety standards emphasise clear purpose, evidence-based claims, filtering, security, privacy, safe design/testing and accountable governance. EdiWay’s AI positioning is intentionally consistent with those principles: bounded purpose, permission control, human review and no exaggerated autonomous-decision claims.

Explore EdiWay: EdiWay AI  |  AI Governance  |  Safeguarding Boundaries

20. Reporting, analytics and evidence assurance

20.1 Reporting from canonical sources

Reports should use the authoritative source records for the question being answered and retain school/organisation/learner permission boundaries. CSV, document and dashboard outputs are presentation layers, not replacement systems of record.

20.2 Intervention impact

Intervention impact reporting is designed to use recorded delivery, reviews, outcomes and evidence. It can flag missing evidence, overdue review or low dosage deterministically, but predictive scoring is a separate future governance question and should not be implied by factual impact reporting.

20.3 Trust and leadership analytics

Leadership projections can combine bounded measures from attendance, SEND, behaviour, safeguarding, workforce, operations and other domains. Cross-school comparison must respect domain restrictions, definitions, minimum-cohort suppression and source freshness.

20.4 FE statutory data foundation

The platform includes a code-integrated FE ILR/EAS/FIS/funding-assurance suite intended for an appropriately configured FE-capable provider. Annual schemas, rules, reference data, official Submit Learner Data outputs and official funding reports remain authoritative. EdiWay should not claim DfE certification, direct submission or official funding accuracy without the corresponding annual assurance and supported interface.

Explore EdiWay: Reporting & Administration  |  Implementation & Product Assurance

21. Implementation, migration and product assurance

21.1 Implementation sequence

EdiWay’s engineering approach is consolidation-first: audit → map → reuse → reconcile → harden → extend → build → verify. Existing identity, organisation, case, workflow, work-item, notification, audit, policy, timeline, evidence and event primitives should be extended before parallel architectures are introduced.

21.2 Customer migration process

1. Discover the source systems, exports, data owners and required historical scope.
2. Map source identities and fields to canonical EdiWay owners.
3. Classify sensitive and high-risk records and decide what requires human review.
4. Run staged/dry-run imports with counts, warnings and rejected rows.
5. Migrate in bounded, resumable batches while retaining source identifiers and original timestamps.
6. Reconcile totals, duplicates, attachments, statuses and exceptions.
7. Verify role, cross-school, reporting and workflow behaviour before cutover.
8. Retain a signed/controlled completion and exception record.

21.3 Security and denial testing

Production assurance requires more than positive workflows. Sensitive areas need explicit denied-user, cross-school, cross-organisation, direct-post/tamper, stale-write and concurrency tests as well as independent security assurance, accessibility checks, provider failure-path evidence and operational recovery procedures.

21.4 Release-state language

Explore EdiWay: Implementation, Migration & Product Assurance  |  Data Security & Governance  |  Accessibility

22. End-to-end process maps

22.1 Learner joins a school

Application/enquiry → admissions decision → identity reconciliation → enrolment/provider relationship → education status → family access → class/timetable → attendance → assessment/support/evidence → transition or exit.

22.2 SEND support cycle

Concern/referral → evidence and screening → support plan/APDR → provision/intervention → delivery evidence → review and outcomes → reviewed write-back / annual review → continue, adapt or close.

22.3 Safeguarding concern

Concern recorded → authoritative scope and immutable version → DSL triage → actions/referrals → chronology/evidence → review/closure → retention/legal hold → controlled disclosure/transfer where authorised.

22.4 Home education / vulnerable withdrawal

Parent request → current status and policy check → vulnerability/consent workflow where applicable → LA task/decision where legally configured → school completion gate → effective-dated education status → home-education/CNIS pathway as required.

22.5 CNIS provider information request

Authority-owned CNIS entry → policy-approved request → recipient-bound provider access → minimum requested fields → governed evidence upload → certified immutable return → reconciliation to authority work item → review/correction/support/closure.

22.6 Alternative provision / EOTAS

Case/commission → provider relationship → learner education status → delivery/attendance evidence → review and outcome → responsible-school/authority oversight → transition/reintegration/cessation.

22.7 Recruitment to employment

Vacancy → application → assessment/interview → offer → hire → applicant-to-staff conversion → onboarding/SCR/qualifications → timetable/workforce → absence/cover/CPD/performance.

22.8 Learning resource to evidence

Approved resource/lesson → assignment → learner completion/evidence → teacher review/feedback → assessment/support context → reporting and pathway evidence.

22.9 Marketplace purchase

School product → buyer context → checkout/payment provider → EdiWay order snapshot → school/seller commission/reconciliation → refund/adjustment where required → auditable reporting.

23. Supported claims and important boundaries

23.1 Claims this paper supports

• EdiWay connects school management, families, learner records, attendance, SEND, assessment, resources, workforce, recruitment, commerce, reporting and governed AI within a shared platform architecture.
• EdiWay supports continuity across school, home education, hybrid/flexible arrangements, EOTAS, alternative provision and transition without treating those pathways as unrelated learner identities.
• Parent/carer and professional participation can be scoped to the learner, relationship, case and purpose.
• Safeguarding, medical and other sensitive domains use stronger access boundaries than ordinary school records.
• EdiWay AI is designed as a permission-aware, human-reviewed assistance layer rather than an autonomous statutory decision-maker.
• EdiWay includes organisation/trust governance and effective-dated education-status foundations that can support multi-organisation workflows.

23.2 Claims that must remain qualified

• Official Ofsted, NHS, CAMHS, Local Authority or government-system integration unless the exact interface is separately implemented and assured.
• Compliance certification or a claim that EdiWay alone makes a customer compliant with legislation.
• DfE certification, direct statutory submission or official funding accuracy for FE returns without annual official assurance.
• Clinical or diagnostic conclusions from educational screening, sensory, literacy, demand-support or wellbeing tools.
• AI-generated safeguarding, EHC, EOTAS, attendance-order, CNIS suitability or other statutory decisions.
• Native/offline mobile operation, unrestricted learner data caching or a full mobile app where those capabilities are not proven.
• Complete Student Life/residential, NHS interoperability, advanced energy, full accounting/finance or other gated programmes where assurance is incomplete.

24. Platform website reference directory

The white paper links to product pages throughout. The directory below groups the same pages by user journey so readers can move from the architecture/process description into detailed product material. It intentionally lists pages rather than their publication status.

School platform

• School Platform
• Core Features
• School Setup & Leadership
• School Operations
• Classes, Timetable & Attendance
• Admissions & Learner Records
• Attendance & Registration
• Teacher & Classroom Workspace
• Behaviour, Rewards & Pastoral Support
• Communication & Family Engagement
• Assessment & Progress
• Academic Assessment & Progress Tracking
• Qualifications, Results & Destinations
• Educational Screening & Learner Support Profiles
• SEND, Safeguarding & Wellbeing
• Provision & Support Planning
• Intervention Support & Impact Review
• EHC Plan Evidence & Annual Reviews
• Learner Wellbeing & SEMH Support
• Safeguarding Records & Chronology
• Medical & Care Records
• Resources, Homework & Evidence
• Teaching Resource Library
• Homework, Assignments & Learner Evidence
• EdiWay AI
• HR & Workforce
• School Marketplace & Payments
• Reporting & Administration
• School Compliance, Risk & Evidence
• School Governance, Policies & Improvement
• Pricing

Families and learning pathways

• Families & Learning Pathways
• Home Education
• Parent & Learner Experience
• Professional Collaboration
• Transition Packs & Learner Continuity
• Adult Learner Record
• Hybrid Learning & Flexible Education Pathways

Trust and governance

• Trust & Governance
• Data Security & Governance
• Permissions, Consent & Information Sharing
• AI Governance
• Safeguarding Boundaries
• Privacy & Data Protection
• Accessibility Statement
• Data Retention & Subject Rights
• Implementation, Migration & Product Assurance
• Children’s Wellbeing & Schools Act 2026 Readiness

Recruitment and HR

• Recruitment & HR
• Careers & Recruitment
• HR & Workforce
• Staff Records, Onboarding & SCR
• Absence, Leave, Cover & TOIL
• Performance, CPD & Induction

Multi-agency and specialist pathways

• Multi-Agency / Specialist Pathways
• EOTAS
• Professional Collaboration
• Alternative Provision & Provider Management
• Multi-Agency Casework, Meetings & Evidence

25. References and source basis

This paper is grounded primarily in the EdiWay working white paper supplied for this review, the August 2026 platform integration audit, the Children’s Wellbeing & Schools Act 2026 platform blueprint, and the supplied website architecture list. The public-policy references below provide external context and should not be read as endorsements of EdiWay.

• EdiWay website
• Children’s Wellbeing and Schools Act 2026 – policy summary (DfE)
• Children’s Wellbeing and Schools Act 2026 – legislation
• Keeping children safe in education 2026
• DfE generative AI product safety standards
• DfE data protection in schools
• DfE school workforce statistics
• House of Commons Library SEND briefing