EdiWay – Complete Platform White Paper

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

EdiWay’s latest architecture adds a further operating principle: connected information should help authorised people close improvement loops, not merely produce more reports. A recurring pattern across the platform is signal or requirement → readiness → gap → responsible person → approved resource/training/action → delivery → evidence → human review → outcome → next action or recognition.

This model can support teaching and curriculum improvement, attendance barriers, behaviour and reintegration, SEND provision, safeguarding readiness, medical support, workforce capability, transition, trips, governance and school improvement while keeping high-impact judgement with authorised people.

↑ Back to contents

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

2.5 From recording activity to closing improvement loops #

Schools do not only need systems that record what happened. They need a dependable way to identify what requires attention, route the next action, connect approved guidance or resources, preserve delivery evidence and review whether the response improved the intended outcome.

EdiWay therefore extends the connected learner journey into a wider quality model. The system can surface factual readiness, missing prerequisites, overdue review, delivery variance or learning opportunity while leaving professional interpretation and high-impact decisions with the authorised human.

↑ Back to contents

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

3.4 Core MIS plus connected platform #

EdiWay now has a clearer two-layer product definition.

Core MIS qualification layer

The core is intended to provide the information-management functions schools need from a modern MIS:

• school and organisation setup;
• user identity, roles and permissions;
• learner identity and records;
• pupil relationship mapping;
• admissions and transfers;
• classes, groups and timetable;
• attendance management;
• behaviour and pastoral;
• assessment and progress;
• mandatory SEND and looked-after-child reporting data where applicable;
• reporting and data quality;
• School Census and transfer-data readiness;
• APIs, bulk export and migration;
• audit, security and service controls.

Connected EdiWay platform

Around that core, schools and other authorised users can use optional connected domains including:

• EdiWay Learning;
• family and learner workspaces;
• Home Education and hybrid learning;
• SEND/APDR/EHC evidence;
• safeguarding;
• wellbeing, medical and care;
• professional collaboration;
• alternative provision and EOTAS;
• workforce and recruitment;
• governance and improvement;
• operations, trips, activities, catering and assets;
• payments and marketplace workflows;
• governed AI.

This distinction matters commercially and architecturally. A school can evaluate a recognisable MIS core while the wider EdiWay platform reduces fragmentation where additional modules are useful.

3.5 Shared identity does not mean shared visibility #

The canonical learner identity is a continuity mechanism, not a universally visible file.

School records, family/Home Education records, professional evidence, provider delivery, learner-owned evidence and local-authority case records may all refer to the same learner while retaining different:

• controllers or source owners;
• permitted audiences;
• purposes;
• sensitivity classifications;
• effective periods;
• export/disclosure rights.

The platform therefore aims to connect the journey without collapsing all data into one audience.

3.6 Quality and readiness as a shared platform foundation #

Quality and readiness are cross-platform projections over canonical records rather than replacement systems of record. The same pattern can connect a curriculum objective to teaching evidence, an APDR plan to provision delivery, a medical plan to staff readiness, a role requirement to verified CPD, or a school-improvement goal to reviewed outcomes.

Measured ≠ judged. Correlated ≠ caused. Acknowledged ≠ competent. Recorded ≠ proven. AI assisted ≠ AI decided.

↑ Back to contents

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

↑ Back to contents

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.

Deny-first principle

If the platform cannot establish the actor, organisation, learner or record scope required for a sensitive action, the action should fail closed rather than infer permission.

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

5.5 Data sovereignty and organisational isolation #

EdiWay’s connected architecture must not become a hierarchy-driven surveillance model.

The following are deliberately separate:

Organisation membership ≠ school membership ≠ learner authority ≠ case authority ≠ export authority.

A trust, local authority, sponsor, operator or platform administrator does not gain unrestricted learner access merely because it is structurally above, funds, creates or administers one or more schools.

LA / multi-school example

An LA might fund, provision or administer 100 schools. Its authorised organisation team may legitimately see:

• the schools in its portfolio;
• contract or subscription allocation;
• implementation status;
• approved capacity or organisation-level metrics;
• aggregate information authorised for the oversight purpose.

That relationship alone must not expose:

• every pupil profile;
• safeguarding chronology;
• medical history;
• SEND case notes;
• family/Home Education evidence;
• behaviour narratives;
• learner work;
• unrelated professional casework.

Where an LA practitioner genuinely needs identifiable information, a separate authority route applies:

named learner/case + purpose + permitted fields + effective dates + sensitivity rules + restrictions

An LA user’s school-operator workspace and statutory/case workspace should remain distinct even if one account holds both responsibilities.

5.6 View, export, disclosure and AI context are different permissions #

The ability to view a record does not automatically permit:

• CSV/PDF download;
• bulk export;
• API disclosure;
• onward sharing;
• attachment download;
• use as AI context.

Export and disclosure need their own authorisation and audit.

5.7 Aggregate-first oversight #

Where a trust, LA or organisation can fulfil its purpose using aggregates, it should not receive identifiable detail by default.

Multi-school analytics should use:

• defined measures;
• source and date definitions;
• approved projections;
• minimum-cohort/suppression rules where appropriate;
• permission filtering;
• source freshness and unknown-state indicators.

A dashboard must not become a side door into restricted learner or family records.

5.8 Platform administration is not customer-data authority #

Technical/platform administrators need powers to operate releases, subscriptions, catalogue configuration, tenant lifecycle and supported onboarding.

Those technical responsibilities do not create automatic unrestricted access to pupil records, safeguarding, HR, school money or family evidence. Sensitive production support needs an explicit governed support/break-glass model rather than an assumed superuser right.

↑ Back to contents

6. School onboarding, setup and leadership #

6.1 From organisation creation to operating school #

Create or select the school/organisation and define the appropriate education sectors, years, settings and active services.

Assign authorised staff and leadership roles with school and domain scope.

Configure term dates, timetables, classes, subjects, attendance, behaviour, communications and operational settings.

Adopt relevant policies, entitlements and product modules.

Load or migrate learner, staff and supporting data through governed import or migration workflows.

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

6.4 Quality, readiness and continuous improvement #

EdiWay’s improvement model is designed around a reusable closed loop:

This framework is intended to improve the quality of learning, learner support, professional practice, school operations and governance without collapsing those dimensions into one score.

6.5 Improvement without automated judgement #

EdiWay can calculate due dates, completeness, readiness, delivery variance, source freshness and defined metrics. It should not autonomously decide that a teacher, learner or school is “good” or “bad”, assign an inspection judgement, diagnose a condition, substantiate safeguarding or make another high-impact professional conclusion.

Where interpretation matters, the platform supplies evidence and structured context; the authorised human records the judgement and rationale.

↑ Back to contents

7. Admissions, enrolment and learner lifecycle #

7.1 Admissions process #

Receive an enquiry or application and capture applicant information through the authorised process.

Review required forms, evidence and admissions criteria within the school’s configured workflow.

Record decisions, offers, waiting-list or next-stage outcomes with an auditable status history.

Where an offer is accepted, reconcile or create the canonical learner identity rather than creating an unnecessary duplicate.

Create the enrolment/provider relationship and activate the correct education status.

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

↑ Back to contents

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 #

Resolve the learner’s current education status and attendance expectation.

Open the authorised class/session register with the expected learner set.

Record marks using configured codes and permissions.

Surface missing, late or exception states for follow-up.

Route follow-up actions and communications according to school policy and role.

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

8.4 Attendance barriers, support and review #

Attendance patterns can create a review signal, but a pattern is not itself a safeguarding finding or a judgement about a family. Where authorised, staff can connect repeated absence or lateness to human-reviewed barriers, learner/family voice, agreed support, responsible actions and later attendance evidence.

The intended loop is: pattern → contact/voice → barrier evidence → agreed support → owner → review date → later attendance evidence → human review.

8.5 Behaviour, support and reintegration readiness #

Behaviour records can connect context, immediate response, restorative work, reasonable adjustments, learner/family voice and later review. Repeated incidents can create a human-review signal without automatically inferring SEND, diagnosis, safeguarding or deliberate intent.

For suspension, managed move or return, a readiness view can check whether the learner/family voice, support plan, timetable, named staff, learning catch-up, relevant adjustments and review date are in place while keeping the legal or disciplinary decision with authorised leaders.

↑ Back to contents

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 #

Teacher selects or creates an authorised learning resource or task.

The task is assigned to the appropriate class/learner context.

Learner evidence or completion information is submitted through the governed workspace.

Teacher reviews the work, adds feedback and records the appropriate outcome.

Evidence remains connected to the learner, resource, assignment and review rather than becoming an isolated upload.

9.5 Unified learner assessment and evidence architecture #

EdiWay’s assessment direction is broader than a collection of isolated score tables. The target is a shared, schema-driven evidence architecture that can support different assessment/profile definitions while retaining version, source, respondent and review context.

This is especially important where evidence is gathered from several settings or contributors. A school observation, parent contribution and professional report should not overwrite one another merely because they relate to the same topic.

The architecture can support:

• versioned assessment/profile definitions;
• repeatable sessions and review cycles;
• multiple respondents;
• source-specific evidence;
• longitudinal comparison;
• age/phase applicability;
• consent and visibility rules;
• review and moderation;
• links to support plans, outcomes and transition evidence.

9.6 Communication, literacy and preparation-for-adulthood profiles #

The current platform direction includes detailed non-diagnostic educational profile families such as:

Speech, Language and Communication / SLCN profile

A structured communication profile can cover areas such as receptive and expressive language, social communication, interaction, functional communication and the communication impact of sensory or environmental context. The purpose is educational support and evidence, not clinical diagnosis.

Literacy and dyslexia support profile

The literacy profile can organise evidence across reading, spelling, writing, phonological processing, fluency, working-memory demands, rapid naming and related classroom observations. Indicator bands and professional interpretation should be preferred to an invented diagnostic score.

Life Skills and Preparation for Adulthood

PfA evidence can span independent living, community participation, employment readiness, health, relationships, travel, communication and other stage-appropriate independence goals. The platform should distinguish performance in one environment from evidence that a skill generalises across settings.

9.7 Learner Evidence Portfolio #

The Learner Evidence Portfolio provides a governed way to connect material to the reason it exists.

Evidence may include:

• documents;
• photographs;
• audio/video where permitted;
• structured observations;
• learner voice;
• family voice;
• professional evidence;
• work-experience/supervisor evidence;
• intervention evidence;
• assessment evidence.

Sensitive media or observations can require stronger permissions, purpose restrictions and audience redaction.

Multi-respondent requests should allow a parent, learner or external professional to contribute their own perspective without silently amending the school’s assessment.

9.8 Transition and work-experience evidence #

The wider learner record can connect:

• work-experience placement;
• hours/attendance;
• reasonable adjustments;
• safeguarding/readiness checks;
• supervisor feedback;
• learner reflection;
• destination context;
• transition-pack evidence.

This supports post-16 planning without turning readiness evidence into a deterministic prediction of future success.

9.9 Academic and statutory assessment coverage #

EdiWay’s assessment model is intended to accommodate school-held data for a broad range of phases and assessment types, including where configured:

• Reception Baseline context;
• EYFS Profile;
• phonics screening;
• Multiplication Tables Check;
• KS1/KS2 assessment and teacher assessment;
• spelling, punctuation and grammar evidence;
• GCSE/Key Stage 4;
• Progress 8 / Attainment 8 data where relevant;
• A-level and vocational outcomes;
• internal/formative assessment;
• data drops;
• attitudes-to-learning grades;
• targets;
• destination records.

Official assessment services, awarding bodies and statutory-return specifications remain authoritative. A local EdiWay record does not itself prove official integration or submission.

9.10 School, governance and compliance assessment surfaces #

Not every assessment in EdiWay is a pupil assessment.

School-level or workforce evidence can include self-evaluation, curriculum review, risk, safeguarding assurance, health and safety, fire/premises evidence, probation or other configured review processes.

These records must remain distinct from learner attainment and from official inspection judgements.

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

9.11 Learning recovery, extension and recognition #

EdiWay’s learning model can support both recovery and excellence. Curriculum or assessment evidence may show that a learner needs reteaching, additional practice, an intervention or an extension opportunity. The platform can connect that need to a reviewed resource, assignment or activity and then to later evidence and teacher review.

Recognition should reflect demonstrated knowledge or contribution rather than attendance alone. Depending on the programme, evidence can include quizzes, scenarios, written/oral work, projects, supervised activities, teacher review, community contribution or an independently verified external credential.

Approved recognition can become part of the learner evidence portfolio, personal-development record, enrichment history, careers evidence or transition material without being misrepresented as a regulated qualification.

↑ Back to contents

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 #

Identify a support need, concern or referral and record the evidence source.

Assess need through school-held evidence, learner/family voice, educational screening and professional information where authorised.

Create or update support planning, outcomes, adjustments and provision.

Deliver interventions or provision and record sessions, evidence and relevant cost/delivery data.

Review impact using recorded evidence, human judgement and next-review dates.

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 #

Authorised staff record a concern against the authoritative learner or staff subject.

The concern is scoped to the correct school/object and receives an immutable version history.

DSL or authorised safeguarding roles triage, acknowledge, assign and manage actions/referrals.

Chronology, evidence and outcomes remain source-linked and permission-preserving.

Archive, retention and legal-hold controls govern lifecycle rather than ordinary deletion.

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.

10.6 Medical readiness and staff competency #

Medical support is more than storing a condition. Where implemented and configured, EdiWay can connect an active Individual Healthcare Plan or medical requirement to relevant staff training, verified competency, current-plan acknowledgement, medication/equipment readiness and the operational context in which support is required.

A readiness projection can evaluate ordinary lessons, PE, clubs, trips, examinations, cover or other supported contexts and return a factual state such as READY, ACTION REQUIRED, NOT READY, UNKNOWN or NOT APPLICABLE.

Course completion, plan acknowledgement, practical competency and authority to administer care remain separate concepts. A completed awareness course must never by itself authorise medication or clinical action.

10.7 Health Awareness & Community Resilience #

EdiWay Learning can support generic, age-appropriate health-awareness education through tutor time, assemblies, Health Education/PSHE, enrichment, independent learning or school-defined courses. This education is deliberately separated from named learner medical records.

Initial awareness pathways can include seizures and epilepsy, allergy/anaphylaxis, asthma, diabetes, first aid, hidden/chronic health conditions, dignity, privacy and knowing when to seek adult or emergency help.

A learner’s private medical condition may create staff-support requirements; it must not automatically identify that learner to classmates. Whole-school awareness content remains generic unless a separate, lawful and human-authorised disclosure process applies.

10.8 Health-awareness learning and learner recognition #

Health-awareness learning can use the same resource, assignment, attempt, evidence and review engine used elsewhere in EdiWay. Recognition is evidence-based and can progress through configured levels such as Awareness, Foundation, Extended Knowledge, Advanced Awareness and a broader Community Health Champion pathway.

An EdiWay certificate represents educational recognition of demonstrated knowledge. It must not be presented as a clinical, professional or regulated medical qualification unless a genuine external awarding arrangement separately supports that claim.

10.9 Sensory support profile #

The sensory-support workflow can organise parent, school, learner and professional observations around patterns such as seeking, avoiding, sensitivity and registration, while retaining contextual description rather than treating a profile as diagnosis.

Evidence can include:

• structured caregiver responses;
• strengths and barriers;
• triggers or environmental context;
• observed response;
• what helped;
• goals and adjustments;
• school/family calendar observations;
• consent, audience and revocation state;
• links to support planning after human review.

10.10 Demand avoidance and autonomy support #

EdiWay’s demand-support direction is needs-led rather than diagnosis-led.

The platform can record:

• demand/barrier context;
• autonomy and communication needs;
• agreed adjustments;
• capacity/check-in evidence;
• strategy use and helpfulness;
• family, school and professional contributions;
• links to sensory, SEND, observation and intervention records.

The platform must not diagnose PDA or generate an unsupported PDA score.

10.11 Domain separation #

The learner may simultaneously have SEND, safeguarding, medical, behaviour and wellbeing records, but these domains do not share the same visibility rules.

Examples:

• a teacher may need an adjustment without the underlying safeguarding narrative;
• catering staff may need an allergy instruction without the full medical record;
• an operations user may need a minimum-detail exception without a diagnosis;
• SEND access does not automatically confer safeguarding access.

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

↑ Back to contents

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.

11.6 Home Education is a first-class context #

A Home Education learner must not require a dummy or fake school enrolment in order to use EdiWay.

The family/Home Education context can hold its own:

• learning plan;
• routines;
• resources;
• attempts and evidence;
• family observations;
• learner voice;
• authorised professional contributions;
• progress/review history.

School-origin, family-origin and professional-origin records retain their provenance.

A school-created resource may be deliberately shared with an eligible Home Education learner without sharing the source school’s pupil community, learner records or private assignment data.

If the learner later joins a school, the new school does not automatically own or inherit all family-created history. Relevant evidence can be selectively disclosed through an authorised transition process.

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

11.6 Transition readiness and first-review continuity #

A receiving setting can prepare for the learner without inheriting the whole historic record. A transition-readiness view can connect placement confirmation, current timetable, accessibility/adjustments, authorised SEND and medical preparation, transport where relevant, learner/family orientation and receipt of approved transfer material.

A configurable post-transition review can then connect attendance, learner/family voice, support delivery, learning engagement and unresolved actions so continuity is reviewed rather than assumed.

↑ Back to contents

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 #

Create or link the canonical learner/case and identify the responsible organisation.

Verify each participant organisation and professional relationship.

Apply case membership, purpose and sensitivity scope before exposing information.

Record meetings, requested evidence, actions, decisions, timelines and follow-up tasks.

Share only the minimum authorised material and retain disclosure/access evidence.

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

↑ Back to contents

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

↑ Back to contents

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.

14.5 Multi-school operator responsibilities #

EdiWay separates the responsibilities that are often incorrectly combined under the label “owner”.

A multi-school customer may have different actors for:

• workspace provisioning;
• legal/operating responsibility;
• contracting;
• subscription payment;
• school financial payee;
• staff administration;
• governance;
• statutory/case responsibility.

Paying for a school grants no general learner or case access.

Creating a school workspace grants no continuing operational authority after a governed handover unless a separate mandate exists.

14.6 Local-authority operating modes #

An LA can appear in EdiWay in different capacities:

Provisioning on behalf of schools

Create or allocate a school workspace and invite authorised school leadership. Continuing pupil/operational access requires a separate effective mandate.

Subscription sponsor

Fund agreed schools and manage allocation. Billing authority does not confer safeguarding, HR, finance, medical or statutory case authority.

Authorised operator/administrator

Administer specified institutions under a verified mandate. Scope, actions, dates, purpose and sensitive-domain permissions remain explicit.

Professional/statutory case role

Work with named learners/cases under the applicable authority. This does not create a broad learner-search permission.

These contexts can exist on one account while remaining separate authorisation contexts.

14.7 Aggregate organisation analytics #

Trust/LA analytics are intended to answer organisation-level questions without turning organisation membership into learner browsing.

Reports should use approved measures and drill-through only where the user independently holds the underlying record authority.

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

↑ Back to contents

15. Workforce, recruitment and protected time #

15.1 Recruitment to staff record #

Publish or manage a vacancy within the authorised school/organisation context.

Receive and progress applications through configured assessment, task, interview and offer stages.

Record the hiring outcome with evidence and role permissions.

Convert the successful applicant into the canonical staff identity through a retry-safe staff-linking workflow rather than recreating the person manually.

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

15.4 Role readiness and professional development #

Workforce quality can be supported through a role-readiness projection that connects required qualifications, training, competency, policy acknowledgements, renewal/expiry, induction and assigned responsibilities to the current staff role.

The development loop is: development need → objective → approved course/coaching/resource → completion → evidence → verification where required → practical application → reflection/review → next objective.

Course progress, verified training evidence, qualification proof, statutory clearance and demonstrated impact remain separate. EdiWay should not infer staff suitability or performance from course completion alone.

↑ Back to contents

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

16.6 Operational readiness and exception management #

The readiness model can be applied to trips, rooms, assets, vehicles where supported, medical equipment, estates checks and other operational prerequisites. A factual readiness state can identify missing approval, training, consent, inspection, equipment, accessibility, medical or emergency preparation without declaring the overall activity legally safe.

Critical defects or expired prerequisites can block a new use where configured, while preserving the original finding, corrective action and verification history. Human owners remain responsible for the operational decision.

↑ Back to contents

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.

17.4 EdiWay Learning #

EdiWay Learning is the umbrella learning architecture.

A resource is a learning object first. “Homework” is one delivery context.

The same resource/attempt/evidence foundation can support:

• school classwork;
• formal homework;
• independent practice;
• family-assisted learning;
• Home Education;
• hybrid learning;
• AP/EOTAS activity;
• professional assignments.

17.5 Resource origin and audience #

A resource can originate from:

• the EdiWay platform;
• a school;
• an authorised professional;
• a family/Home Education context.

Origin, ownership and audience are separate.

A school-created resource may be offered outside the school only through deliberate approved sharing. Sharing the resource does not share learner-identifiable examples, school records or community membership.

17.6 Structured response experiences #

The learning engine is designed for more than generic quizzes. Response types can include:

• multiple choice;
• short answer;
• extended writing;
• reading comprehension;
• problem solving;
• calculation practice;
• times-table practice;
• phonics practice;
• practical tasks;
• project-based work;
• oral discussion;
• self-reflection.

Each response style should have an appropriate learner and review experience rather than being forced into one generic text field.

17.7 Assignment, attempt and review chain #

A learning activity should preserve:

• resource/version;
• assignment;
• class/learner or other authorised audience;
• release/due window;
• learner attempt;
• autosave/resume;
• answers or private evidence;
• support/adaptation used;
• contributor attribution;
• final submission;
• review method/rubric;
• human feedback;
• correction/moderation history.

Engagement, completion and attainment remain separate concepts.

17.8 AI Resource Studio #

AI may help authorised staff create draft lesson plans, explanations, examples, worksheets, differentiated activities or question sets using approved curriculum/guideline context.

Publication remains a human decision. The reviewer remains responsible for accuracy, suitability, safety, bias, copyright and answer-key quality.

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

17.9 Courses, awareness pathways and evidence-backed awards #

The resource engine can support structured courses and pathways without creating another learning system. A course can freeze reviewed resource versions, required activities, scenarios, assessment rules, extension options and award criteria.

This enables EdiWay to support health awareness, community resilience, leadership, volunteering, digital citizenship, careers/employability, sustainability, mentoring and other personal-development learning where the school chooses to use them.

Learning creates evidence. Deeper learning can create stronger evidence. Recognition reflects demonstrated knowledge or contribution, not merely attendance.

↑ Back to contents

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.

18.4 Connected school payments and learner finance #

The current School Payments & Commerce integration extends beyond a public shop. A school can manage private, school-scoped products such as uniform and supplies, while the operational School Management domains remain authoritative for trips, clubs, activities, events, admissions, catering and learner services. Marketplace provides the shared financial boundary for obligations, payment attempts, verified allocations, credits, refunds, Finance Exceptions and reconciliation without converting every operational record into a product or order.

The integrated payment model currently includes:

• hosted Stripe Checkout for parent learner-wallet top-ups, with a £5 minimum, school destination evidence and signed-webhook-only wallet crediting;
• school-scoped product orders with collection or school-arranged delivery, manual tracking evidence and parent-linked fulfilment views;
• trip and club charge plans supporting a single charge, deposit/balance or finite instalments, with deliberate learner issue, immutable source identities and payer-scope checks;
• event bookings that separate RSVP, consent, capacity, booking, payment and attendance, with holds and late-settlement exceptions;
• admissions offers, deposits and admission-fee obligations separated from parent acceptance and learner enrolment;
• withdrawn-admission deposits governed by frozen refundable terms, original-destination refund requests, independent finance approval and durable retention/refund evidence;
• finite tuition, nursery and wraparound-fee agreements with frozen terms, governed adjustments, adjustment retirement and approved leaver/proration amendments;
• learner finance projections combining obligations, verified allocations, wallet liability and fee agreements without taking ownership away from the source domains; and
• original-destination refund rules: card-funded activity refunds return through the provider, wallet-funded reversals return to the same learner wallet, and unsupported offline cases remain governed finance reviews.

Operational availability is intentionally separate from online payment readiness. Schools may create trips, clubs, events, admissions records and other operational work when Stripe is not ready; online collection is disabled or routed to an approved offline workflow until the required school payment capability is active. A browser redirect never proves settlement, consent, enrolment, attendance or fulfilment.

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

↑ Back to contents

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.

Platform-managed provider configuration, subscription/usage controls and governed credit allocation 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.

19.5 Current AI operating model #

EdiWay uses a platform-managed provider configuration and governed subscription/credit model rather than making customer-supplied API keys the core operating model.

AI requests should record enough provenance to reconstruct the consequential draft context, including actor/scope, purpose, source IDs or revisions, model/prompt release, permitted fields, provider result state and review state.

Learner records are not training data by default. Prompt examples, configuration or any provider fine-tuning must remain separately governed and should never be described as “training on learner data” unless that exact processing genuinely occurs and has been approved.

19.6 Learner-facing AI safety #

DfE’s January 2026 generative-AI product safety update added explicit expectations around cognitive development, emotional/social development, mental health and manipulation.

Accordingly, learner-facing EdiWay AI should include controls such as:

• clear intended educational purpose;
• age/SEND-aware safety settings;
• effective filtering and moderation;
• task-bounded interaction;
• no cultivation of emotional dependency;
• no statements designed to isolate the learner from real-world support;
• no manipulative persuasion, guilt, pressure or dark patterns;
• no design intended primarily to prolong engagement;
• appropriate session/break controls where required;
• clear escalation and complaints routes;
• accountable human governance.

Explore EdiWay: EdiWay AI | AI Governance | Safeguarding Boundaries

↑ Back to contents

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.

20.5 Report access is not source-record access #

A permission to view a report or dashboard should not silently grant the underlying source permissions.

Where a fixed report can be calculated from approved aggregates, the output should exclude unnecessary narrative/person rows.

20.6 View and export are separate capabilities #

A user may legitimately be authorised to see a dashboard but not to export the underlying data.

Exports should be:

• separately authorised;
• actor-audited;
• scope-bound;
• formula-safe for CSV;
• protected against cross-school leakage;
• explicit about generation time and reporting period.

Explore EdiWay: Reporting & Administration | Implementation & Product Assurance

20.7 DfE MIS framework readiness #

The Department for Education is developing an open Management Information Systems framework for England, expected to launch on 1 September 2027. The framework is intended to support standard MIS modules, optional modules and additional services such as training/support; supplier comparison; cyber-security and data-protection requirements; transparent pricing; and more reliable data transfer between systems. Academy trusts must use the framework once live and should plan to move as soon as practicable after launch in line with current contract expiry. Local-authority maintained schools and groups are expected to use it, and further-education providers can use it.

The framework is intended to support:

• standard MIS modules;
• optional modules;
• additional services such as training/support;
• clearer supplier comparison;
• cyber-security and data-protection qualification;
• transparent pricing and accountability;
• reliable data transfer between systems.

Academy trusts must use the framework once live. Local-authority maintained schools and groups are expected to use it. Further-education providers can use it.

For EdiWay this creates a specific qualification programme, not merely a marketing opportunity.

The platform should be described as:

preparing its core MIS, security, interoperability, migration and commercial controls for the Department for Education’s planned MIS framework.

It must not be described as DfE approved, framework compliant or awarded until the relevant official evidence exists.

20.8 DfE MIS Core Principles #

DfE’s 2026 MIS Core Principles materially affect EdiWay’s technical and commercial architecture. They cover areas including recognised cyber-security assurance or a transition path toward it; transparent pricing for core provision, optional modules and integrations; fair contract/renewal terms; school-data ownership and controller/processor boundaries; restrictions on reuse of School Data; continued access and exit support; machine-readable data transfer; API/download access; and supplier cooperation with migration. The current published guidance should be treated as the source of truth because framework terms may continue to evolve before launch.

Key requirements include:

• Cyber Essentials Plus and/or ISO 27001 accreditation, or the published transition path toward accreditation;
• transparent pricing for core provision, optional modules and third-party integrations;
• fair contract terms and controlled automatic renewal;
• clear school-data ownership and controller/processor boundaries;
• appropriate UK/EEA processing or safeguarded transfers;
• no repurposing of School Data outside the contracted service, law or specific authority;
• continued school access to its data;
• bulk transfer availability;
• download/API access;
• migration-ready machine-readable formats;
• API-enabled sharing with third parties including other schools, EdTech suppliers and DfE;
• supplier cooperation with entry and exit migration.

This reinforces EdiWay’s core/optional-module distinction and makes portability a first-class requirement rather than a future integration feature.

20.9 Interoperability, APIs and portability #

Every external interface should define:

• purpose;
• authority;
• source;
• recipient;
• field set;
• direction;
• version;
• credential scope;
• effective period;
• retries/replay;
• failure handling;
• audit.

The target is controlled interoperability, not broad credentials that bypass EdiWay’s internal permissions.

Schools should be able to obtain migration-ready data in machine-readable formats with provenance and scope intact.

20.10 Migration as a supported journey #

Migration should follow:

Discover → Map → Classify → Dry run → Bounded/resumable import → Reconcile → Verify → Complete/Exception

Imported data must retain source and timestamps where applicable.

Importing a record must not silently increase its authority, audience or sensitivity classification.

Exit migration should be treated with the same seriousness as onboarding.

20.11 DfE data-spine compatibility without unrestricted central access #

DfE’s 2026 Every Child Achieving and Thriving white paper states an intention to develop a secure, privacy-respecting education “data spine” connecting information such as pupil records, attendance, progress and assessment across systems.

EdiWay can support approved national interfaces without making the DfE—or any other external organisation—a universal EdiWay reader.

A DfE interface should therefore be implemented as a versioned projection that defines:

• the legal/operational purpose;
• authority;
• population;
• exact fields;
• frequency;
• receiving service;
• correction process;
• audit/receipt evidence;
• retention expectations.

For example:

attendance interface ≠ safeguarding + medical + family + homework access

and:

statutory-return interface ≠ unrestricted access to family Home Education history or unrelated professional casework.

EdiWay cannot promise that future legislation will never require new disclosure. It can avoid creating a standing technically unrestricted route. A new disclosure purpose should require an explicit versioned implementation and authority decision rather than silently widening an existing credential.

20.12 Quality, readiness and continuous-improvement reporting #

Cross-domain quality reporting should prefer actionable, source-defined measures over decorative scores. Examples include review actions due, planned provision delivered, curriculum objectives evidenced, competencies current, transition receipts outstanding, policies due and operational readiness gaps.

Every material metric should define its source, numerator/denominator where applicable, date basis, exclusions, unknown handling, sensitivity and permitted audience. Unknown must not be converted to zero.

20.13 No default teacher, learner or school quality score #

EdiWay should not create a single composite teacher-quality, learner-risk or school-quality score by default. Composite scores can hide definitions, context and uncertainty and may be mistaken for professional or inspection judgements.

If a future composite index is ever proposed, it requires an explicit purpose, governed weighting, bias/impact review, explainability, human-use restrictions and appropriate assurance.

↑ Back to contents

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 #

Discover the source systems, exports, data owners and required historical scope.

Map source identities and fields to canonical EdiWay owners.

Classify sensitive and high-risk records and decide what requires human review.

Run staged/dry-run imports with counts, warnings and rejected rows.

Migrate in bounded, resumable batches while retaining source identifiers and original timestamps.

Reconcile totals, duplicates, attachments, statuses and exceptions.

Verify role, cross-school, reporting and workflow behaviour before cutover.

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

21.5 Current implementation status and evidence discipline #

This public white paper intentionally does not publish a single platform-wide implementation percentage.

The September percentages became stale as platform development advanced, and a percentage can incorrectly merge several different questions:

• is the capability documented?
• is native code present?
• is the canonical writer/reader actually used?
• are server-side permissions enforced?
• has migration been proven?
• has hosted MariaDB/HTTP acceptance passed?
• has accessibility/security/provider assurance passed?
• is the public claim safe?

Current implementation truth therefore belongs in the authoritative build specification, requirement records, release evidence and acceptance tests.

The public paper should describe product direction and verified capability boundaries without turning an old checkpoint into a permanent headline.

↑ Back to contents

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.

22.10 LA funds or administers multiple schools #

LA organisation relationship → authorised school portfolio/provisioning → contract/allocation/aggregate oversight → no automatic pupil search → separate named learner/case mandate where required → purpose/field/effective-period controls → expiry/revocation.

22.11 DfE or third-party data exchange #

Approved interface → versioned purpose/authority → exact field projection → authenticated transfer → receipt/failure/retry evidence → correction/reconciliation → no automatic expansion into unrelated domains.

22.12 Home Education resource journey #

Family chooses authorised learner → Home Education context → platform/family/approved shared resource → learner attempt/evidence → family or authorised professional review → selective disclosure if needed → transition without automatic school ownership.

22.13 Learning assignment #

Reviewed resource/version → eligible class/learner → frozen assignment context → save/resume attempt → evidence/answers → submission → teacher/human review → feedback/outcome → authorised learner/family projection.

22.14 Medical readiness and specialist evidence #

Condition/IHP → approved actions → staff training/competency → acknowledgement → timetable/activity context → readiness state → minimum-necessary alert → incident/educational-impact evidence → family/learner evidence where authorised → specialist evidence pack → professional review → revised support/IHP where appropriate.

Other pupils receive no learner-specific medical information through this flow. Generic health-awareness education is a separate learning pathway.

22.15 School quality and continuous improvement #

Goal/requirement → baseline/source evidence → readiness or gap → accountable owner → approved action/resource/training → delivery → evidence → human review → improved/partial/no-change/inconclusive outcome → next action → later review.

The process links to canonical source records; it does not copy all evidence into a second improvement database.

22.16 Learner extension and recognition #

Demonstrated understanding/strength → extension opportunity → reviewed advanced resource/project → learner attempt/evidence → assessment or human review → recognition → evidence portfolio → optional next pathway.

This gives the learner journey a positive-development route as well as intervention and remediation.

↑ Back to contents

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.

EdiWay’s target architecture also supports a cross-platform quality/readiness model that links factual signals and requirements to accountable actions, evidence and human-reviewed outcomes without creating an autonomous inspection or staff-scoring engine.

EdiWay Learning can support generic health-awareness and community-resilience courses, evidence-backed extension learning and internal recognition while keeping named learner medical records private.

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.

Claims that a readiness state guarantees safety, statutory compliance or professional competence beyond the underlying verified evidence.

Claims that an EdiWay awareness award or certificate is an externally accredited or regulated medical/first-aid qualification unless a genuine awarding arrangement supports it.

Claims that a cross-domain metric proves teaching quality, staff performance, learner risk, school quality or causal impact.

23.3 Current strategic claims #

Within the relevant evidence boundary, EdiWay can be positioned as:

• a modern interoperable MIS and connected education platform in active development;
• built around one learner identity and permission-aware access;
• designed so organisational hierarchy does not automatically become learner-data access;
• designed around scoped APIs, portability and migration;
• preparing for the planned DfE MIS framework;
• able to support school, family, Home Education, hybrid, professional, AP/EOTAS and transition contexts within separate authority boundaries;
• designed around human-reviewed AI rather than autonomous high-impact decision-making.

Do not claim without current evidence:

• DfE approval or framework award;
• Cyber Essentials Plus or ISO 27001 certification unless achieved;
• automatic UK GDPR/KCSIE/Ofsted compliance;
• direct government/NHS/LA integration unless the exact interface is live and assured;
• guaranteed savings;
• full production readiness of every optional module.

Within the relevant implementation boundary, EdiWay can also be described as designed to connect readiness, accountable action, evidence and human review across school and learner workflows, and to support evidence-backed learner recognition and extension.

23.4 Audience value #

23.5 DfE / ministerial / partner briefing summary #

For a Department for Education, local authority, trust, potential pilot partner or funder, EdiWay can be summarised as follows:

EdiWay is a modern interoperable MIS and connected education platform designed around one learner identity, while keeping visibility purpose-specific and permission-aware.

The platform aims to:

• reduce software and data fragmentation;
• reduce repeated school administration;
• provide a credible core MIS;
• connect learning, SEND, safeguarding, families, Home Education and authorised professional collaboration;
• improve data portability and migration;
• enable controlled APIs rather than broad data access;
• help schools use AI within stronger education-specific safety and governance;
• support multi-school/LA oversight without blanket learner access;
• preserve evidence provenance across transitions.

The core strategic message is:

Connect the learner journey without making the learner universally visible.

The latest architecture adds a further message for public-sector and school partners: EdiWay is intended not only to connect data, but to help authorised people turn evidence into accountable improvement loops while preserving professional judgement and data boundaries.

Connect the learner journey. Make readiness visible. Close improvement loops. Keep judgement human.

↑ Back to contents

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

↑ Back to contents

25. References and source basis #

This paper is grounded primarily in the EdiWay complete-platform working paper and architecture materials, including the 1 November 2026 Medical Readiness, Health Awareness & Learner Recognition integration specification and the 1 November 2026 Quality, Readiness & Continuous Improvement framework. The public-policy references below provide external context and should not be read as endorsements of EdiWay.

25.1 Current public-policy sources #

• DfE — Choosing a school management information system (MIS).
• DfE Get Help Buying for Schools — Core Principles for school MIS procurement.
• DfE Get Help Buying for Schools — About the Management Information Systems framework.
• DfE — Academy Trust Handbook 2026.
• DfE — Supporting pupils with medical conditions at school.
• DfE — Allergy safety in schools (published 6 July 2026).
• DfE — Proposal on support for pupils with medical conditions at school: consultation outcome.
• DfE — Relationships Education, RSE and Health Education statutory guidance.
• DfE — Generative AI: product safety standards (updated 19 January 2026).
• Keeping children safe in education 2026; DfE data-protection guidance; statutory assessment/return specifications and other domain guidance where referenced by the relevant workflow.

25.2 EdiWay architecture source basis #

• Complete Platform White Paper and detailed 2026 platform narrative.
• Full Build Integration architecture and current implementation evidence.
• Medical Readiness, Health Awareness & Learner Recognition Integration Build Specification — 1 November 2026.
• Quality, Readiness & Continuous Improvement Framework Integration Build Specification — 1 November 2026.
• Platform Overview & Role-Based Value Proposition — updated 1 November 2026.

25.3 Final note #

EdiWay is broad by design, but breadth should not be confused with an unconditional claim that every possible workflow is production-assured in every jurisdiction or customer configuration. Its central value is the connected architecture: one learner identity, clear process ownership, controlled collaboration, portable data, visible readiness, accountable action and evidence that remains traceable to its source — without making every record visible to every connected organisation or delegating professional judgement to an algorithm.

↑ Back to contents