Bring admissions, enrolment, learner information, family relationships, school history, documents and education pathways into one permission-aware learner record.
EdiWay helps schools create a clearer foundation for everything that follows - from classes and attendance to assessment, SEND, communication and transition - without repeatedly recreating the same learner information across separate systems.
A learner appears across almost every part of school life.
When each area creates its own version of the learner, information can become duplicated, inconsistent or difficult to follow.
EdiWay is designed around a central learner record that gives each connected workflow the context it needs while preserving the boundaries around sensitive information.
Maintain the core information needed to identify and support the learner.
Connect the learner to the correct school, year group, education mode and current status.
Link parents, carers and other approved family relationships.
Connect classes, subjects, timetable, resources and assessment information.
Link permitted SEND, intervention, wellbeing and support information.
Connect attendance, behaviour, school services and relevant administrative activity.
Preserve appropriate previous-school, transition and learner-history information.
It is to ensure that authorised workflows refer to the correct learner and that users see only the information relevant to their responsibilities.
Admissions information should not disappear into a separate system once a learner joins the school. EdiWay is designed to help schools move relevant information from enquiry or application through admission and into the learner’s school record where the applicable workflow is enabled.
Record appropriate initial interest or school enquiries.
Maintain applicant information through an enabled admissions workflow.
Collect relevant learner, family and school information.
Make the current stage of an application visible to authorised admissions users.
Collect appropriate documents where required.
Record the authorised outcome of the school’s admissions process.
Manage relevant offer information and acceptance status where enabled.
Maintain appropriate applicant status where the school operates a waiting-list process.
Move approved information into the learner’s active school context without unnecessary re-entry. EdiWay helps schools organise admissions information.
The school remains responsible for its admission arrangements, eligibility decisions, statutory duties and applicable admissions processes.
When an applicant becomes a learner, the relevant information should move into the school context in a controlled way.
Check the core learner information before activation.
Connect the learner to the correct school and education context.
Review the parents, carers and contacts associated with the learner.
Record when the learner’s active school relationship begins.
Connect the learner to the appropriate year group, cohort or starting structure.
Identify which admissions documents need to remain available after enrolment.
Enable appropriate learner or family access where required.
Ensure school staff can access only the information needed for their responsibilities.
Preserve appropriate application and admission context rather than silently rewriting the learner’s history.
The joining process should create continuity while keeping applicant information, school records and sensitive information appropriately governed.
The core learner profile provides the identity and school context used across connected workflows.
Maintain the learner’s name and relevant identifying information.
Record appropriate preferred names and other configured identity information.
Maintain authorised learner contact information where relevant.
Record the information required by the school’s configured workflows.
Make clear whether the learner is prospective, current, former or otherwise represented in an enabled pathway.
Connect the learner to the appropriate educational stage.
Distinguish school-enrolled, home-educated, hybrid or other enabled education contexts.
Preserve when school relationships begin and end.
Connect approved learner documents to the correct record.
Retain appropriate historical information when important identity or school-context information changes.
Core profile information should provide context to connected workflows without making every related record universally visible.
Family access should depend on a recognised relationship with the learner. EdiWay allows schools to organise parent, carer and family relationships around the learner record rather than assuming every family account has the same authority.
Link recognised parent relationships to the appropriate learner.
Maintain relevant carer relationships and contact information.
Support learners who have more than one recognised parent or carer relationship.
Allow an authorised family user to move between linked children while keeping each learner record separate.
Maintain the appropriate contact information for each relationship.
Keep relevant emergency-contact information available to authorised staff.
Support approved additional family relationships where that workflow is enabled.
Make clear whether a family relationship is current, historical or otherwise restricted.
Use relationship and permission information when deciding which records, messages and actions can be accessed.
A family relationship does not automatically provide access to every part of the learner record.
Outdated relationship information can create communication and access problems. EdiWay helps schools keep the learner’s relationship context visible.
Identify the parents, carers and other users currently connected to the learner.
Maintain relevant telephone, email and address information.
Record the recognised nature of the relationship.
Use appropriate relationship information when selecting recipients.
Keep portal access separate from the simple existence of a contact record.
Retain relevant relationship history without treating it as continuing authority.
Apply appropriate sharing or access restrictions through governed workflows.
Update relationships when family circumstances, responsibilities or school information change. A former or historical relationship should not automatically continue to grant current platform access.
The same learner may move between different educational contexts over time. EdiWay keeps that context visible so records are interpreted correctly.
Connect the learner to classes, timetable, school attendance and relevant school workflows.
Keep parent-led routines, resources and evidence distinct from school registration and attendance.
Preserve the source of school and home evidence rather than merging them into one undifferentiated record.
Keep provision, sessions and case information separate from ordinary school attendance where that pathway is enabled.
Maintain appropriate placement context and responsible-school relationships.
Connect relevant learning, qualification and destination context.
Preserve selected evidence when the learner moves between settings or phases.
Support movement towards an adult-controlled record where that pathway is enabled. Education mode gives meaning to the record.
A home-learning routine is not a school register, and a previous school relationship should not be treated as a current enrolment.
Learner records change as people join, move through and leave a school. EdiWay helps keep those lifecycle stages clear.
Maintain an applicant or enquiry context before active enrolment.
Prepare the information and relationships needed for the learner’s start.
Use the active school relationship across everyday workflows.
Prepare the appropriate movement between settings or pathways.
Close the active school relationship while retaining appropriate historical information.
Preserve the relevant school history without treating the learner as currently enrolled.
Review existing history before creating new or duplicate records.
Where enabled, support the change from child-linked access towards appropriate adult control. Lifecycle status should affect what users can do with a record and which school workflows include the learner.
The joiner process can bring together the information needed before a learner begins everyday school activity.
Review personal and school information.
Check recognised parents, carers and emergency contacts.
Connect the learner to the correct academic context.
Prepare appropriate class or teaching-group membership.
Ensure relevant authorised staff receive the educational context they require.
Make appropriate medical and care information available only to authorised users.
Prepare approved family and learner communication routes.
Identify required and missing information.
Make outstanding setup actions visible before everyday workflows depend on the record. The aim is to reduce repeated setup while ensuring sensitive information still follows its own access rules.
A learner leaving the school should not result in their information disappearing or their current access continuing indefinitely.
Record when the active school relationship ends.
Maintain appropriate destination information where known and required.
Remove the learner from current class and timetable contexts at the appropriate point.
Preserve historical attendance while ending future school-registration expectations.
Review which school-specific family services should remain available.
Remove or review relationships that no longer have a current purpose.
Identify records, resources or support reviews requiring completion.
Prepare selected evidence where authorised.
Retain the appropriate school history in accordance with applicable retention and governance requirements. A leaver record should preserve history without creating the impression that the school relationship remains active.
Duplicate learner records can fragment evidence and make it harder to understand the learner’s history. EdiWay is designed around a single connected learner identity within the appropriate platform context.
Check whether the learner already exists in the relevant school or platform context.
Compare appropriate identifying information before a new record is created.
Check whether the learner is already linked to an existing family account.
Avoid creating a new learner simply because the learner changes year group, class or education pathway.
Keep previous-school and current-school contexts distinct without treating the learner as two unrelated people.
Allow authorised users to review potential data-quality problems.
Resolve duplicate or incorrect information through an authorised process. Record matching should support data quality. It should not automatically merge sensitive records without appropriate review.
The learner profile can connect to many parts of EdiWay. That does not mean every user sees all of them.
Connect current teaching groups and schedule context.
Link authorised attendance history and registration information.
Connect relevant behaviour activity, achievements and pastoral follow-up.
Link academic assessment, evidence, targets and progress.
Connect authorised support records, provision and interventions.
Maintain relevant school-held EHC-plan context.
Connect permitted pastoral and wellbeing information.
Maintain sensitive health, medication and care context separately.
Connect assigned learning and learner evidence.
Use the correct learner and relationship context when communicating.
Prepare selected evidence for a new setting or pathway. The learner record is the connecting point. Permissions determine which connected areas an individual user can access.
Learner records may include information that is necessary for safe school support but too sensitive for unrestricted access.
Maintain relevant school-held medical context.
Record appropriate information needed for school support.
Make authorised allergy information available where required.
Connect relevant medication requirements and records.
Surface important information to appropriately authorised staff.
Maintain relevant individual healthcare or care information.
Record relevant dietary requirements.
Give authorised users the information they need for an appropriate school response. Medical information should be available according to responsibility and purpose, not simply because someone can view the learner’s general profile.
A learner record may reference many different kinds of documents. EdiWay helps schools keep those documents connected to the correct learner and information area.
Maintain relevant application or onboarding information.
Store appropriate learner-related school records.
Preserve documents contributed by a parent or carer as family-origin evidence.
Connect documents to relevant assessment workflows.
Link authorised records to support planning or review.
Preserve reports and contributions from external professionals with their source.
Select appropriate records for an authorised transition pack.
Retain relevant material according to applicable retention requirements.
Limit sensitive documents according to the information area and user responsibility. A document attached to the learner should not automatically become visible to everyone who can access the basic learner profile.
A connected learner journey may contain information created by different people. The source of that information matters.
Information created and maintained through authorised school workflows.
Evidence or observations provided by parents and carers.
Views, reflections or evidence submitted by the learner.
Information created by authorised external practitioners.
Records deliberately shared for an approved purpose.
Documents or decisions originating from the relevant statutory organisation.
Data brought from an earlier system or source.
Records created in an earlier school or education context. Connecting these records should not silently change who created them or what authority they carry.
Learner notes can be valuable, but free-text information needs a clear purpose and appropriate audience.
Capture relevant educational observations.
Record information supporting teaching or progress review.
Keep relevant pastoral context within the appropriate workflow.
Record permitted information provided through approved communication.
Connect authorised professional observations through their proper relationship.
Preserve when an observation was created and by whom.
Make clear why the information was recorded.
Keep SEND, medical, HR and safeguarding information in their controlled domains rather than copying sensitive content into general notes. A general learner note should never become a shortcut around sensitive-information permissions.
Learner information changes over time. Schools still need to understand what happened previously without treating old information as automatically current.
Maintain appropriate earlier education-setting context.
Preserve historical academic context.
Keep relevant previous class relationships.
Retain assessment evidence within its original period and framework.
Preserve historical attendance without mixing it with current registration.
Maintain relevant learner achievements over time.
Retain appropriate previous intervention and SEND evidence.
Record when the learner moved between settings or education pathways.
Keep authorised historical records according to retention requirements.
Understand how family and professional relationships changed over time. Historical information provides context. It should not automatically create current permissions, current support status or current school relationships.
A learner changing school, phase or pathway may need relevant information to follow them. EdiWay is designed to support controlled continuity rather than unrestricted record transfer.
Prepare relevant evidence for an authorised receiving setting.
Support appropriate continuity between phases.
Connect selected learning, support and transition evidence.
Carry reviewed strategies, provision context and relevant evidence where appropriate.
Maintain source separation when a learner moves between school and parent-led education.
Keep responsible-school and provision context explicit.
Select the information required for the approved purpose.
Allow an authorised person to check the material and audience.
Keep author, source, date and purpose visible.
Apply appropriate controls to transition access where the workflow supports them.
Parents and carers should not need to understand the school’s internal system to participate in the learner journey. EdiWay provides role-specific family experiences linked to approved children.
View information approved for the family relationship.
Move between linked learners without mixing their records.
Access relevant timetable, resources and homework.
View approved assessment and progress information.
Preserve historical attendance without mixing it with current registration.
Contribute appropriate family evidence where requested.
Participate in selected SEND, sensory or review workflows.
Access approved reports and information.
See requests, forms or tasks requiring a family response. Families do not automatically receive internal staff notes, restricted safeguarding information or every school-owned record.
The learner experience should reflect what the learner is expected and authorised to do.
Access relevant personal and school information.
See the learning schedule appropriate to the current education mode.
Access assigned learning.
Complete relevant learner activity.
Contribute work or evidence where enabled.
View approved feedback and assessment information.
Receive age-appropriate communication.
Contribute views through suitable workflows.
Participate in appropriate future-planning activity. Learner access may become more independent as age, setting and family configuration allow.
A connected learner record should help staff work efficiently without exposing unrelated information.
Access assigned learners, classes and appropriate teaching context.
Use permitted SEND and support information.
Access relevant pastoral and wellbeing context.
Work within separately controlled safeguarding areas.
Access only the health or operational information required for their work.
Receive appropriate school-wide oversight according to their responsibility.
Maintain relevant learner, admissions and school information.
Support platform operation without automatically receiving authority over confidential case content. Access should follow school, role, learner, relationship, information area and permitted action.
Some learners receive support from professionals outside the school. EdiWay uses purposeful learner relationships rather than treating an external practitioner as another ordinary staff user.
Connect the relationship to the relevant learner.
Record why the professional is involved.
Identify the relevant approved professional organisation where applicable.
Control which information areas can be used.
Allow appropriate evidence or actions without opening unrelated records.
Keep external involvement time-aware.
Allow access to end when its approved purpose ends.
Remove access when the relationship is no longer appropriate.
Retain appropriate visibility of authorised professional participation. A professional relationship does not create unrestricted access to the learner’s complete history.
EdiWay can use several layers of context to determine what an authorised person can see or do.
Which organisation is the user working within?
What responsibilities have they been given?
Which learners are relevant to those responsibilities?
Which teaching groups have been assigned?
Is there a recognised family or professional relationship?
Does the user have access to assessment, SEND, medical, safeguarding or another controlled area?
Can the user view, create, update, approve, share or administer the information?
Is the relationship or permission still current? Being able to view the learner’s basic profile should not automatically provide access to every connected domain.
A reliable learner record depends on understanding where information is missing, outdated or inconsistent.
Identify important fields that have not yet been completed.
Surface learners without required family or school relationships.
Flag potential duplicate learner information for authorised review.
Identify inconsistent start, leaving or relationship dates.
Show when required implementation or admission records remain outstanding.
Distinguish current, prospective, former and archived learner contexts.
Identify learners without an appropriate year group, education mode or school status.
Make it possible to review information that may no longer reflect the current situation.
Retain appropriate context when important records are updated. A blank value should remain a missing value – not silently become “no”, “none” or another conclusion.
Schools moving from another system may need to bring existing learner information into EdiWay. Import should be treated as a controlled implementation process.
Record where the information originated.
Confirm how existing information relates to the EdiWay learner model.
Reduce the risk of duplicate learner identities.
Review parent, carer and contact relationships.
Keep relevant admission, enrolment, support and historical dates.
Identify information that does not fit the expected structure.
Apply additional care to SEND, safeguarding and medical data.
Compare totals and representative learner records against the original source.
Make import problems visible rather than silently dropping data.
Require appropriate review before imported information is relied upon operationally. Import availability and supported formats may depend on the school’s implementation arrangement and current platform capabilities.
Authorised staff may need to understand who is applying, joining, currently enrolled or leaving.
Review relevant application information where admissions workflows are enabled.
Distinguish active learners from applicants and former pupils.
Identify learners due to join.
Review relevant leaving information and outstanding actions.
Understand the current learner population by educational stage.
Keep school, home, hybrid and specialist pathways explicit.
Identify incomplete learner or relationship records.
Surface information requiring administrative review.
Review relevant learners preparing to move to another setting or phase.
Ensure reports reflect only the school and learner populations the user is authorised to oversee. A learner total is only useful when the population included in that number is clearly defined.
Where enabled, EdiWay AI can help authorised users prepare drafts from learner information they are already permitted to access.
Prepare a working summary from selected visible records.
Help organise selected evidence before human review.
Prepare family or learner communication using permitted context.
Summarise selected information for an authorised meeting or workflow.
Highlight information that may need to be checked.
Keep the underlying record context available for human review. AI does not gain broader access than the user invoking it. AI outputs remain drafts. EdiWay AI does not autonomously change learner identity, admissions status, SEND status, safeguarding records or statutory information.
Create the appropriate prospective learner and family context where admissions workflows are enabled.
Check information, documents and application status.
Record the authorised school decision.
Activate the learner within the correct school and education context.
Link family relationships, year groups, classes and appropriate services.
Use the learner record across attendance, learning, assessment and communication.
Connect authorised SEND, wellbeing, medical and professional evidence.
Maintain accurate relationships, status and historical information.
Prepare selected, governed evidence for the learner’s next setting or pathway.
Keep the appropriate history while access and responsibilities change.
When learner information sits across separate systems and spreadsheets, staff may need to repeatedly check:
EdiWay connects the learner identity to wider school workflows so that information can be reused responsibly rather than repeatedly recreated. The result should be a clearer learner journey – not unrestricted access to every record.
The learner record is the central identity and school context used to connect authorised information such as family relationships, classes, attendance, assessment, SEND, documents, resources and transition activity.
Different information areas retain their own permissions.
EdiWay includes learner-record functionality for maintaining pupil information, family relationships, school context, documents and history.
The learner record also connects to wider operational, assessment, SEND, learning and family workflows.
EdiWay is designed to support school enquiry and admissions workflows, including relevant applicant information and movement into an active learner record where enabled.
The school remains responsible for its admissions policy and decisions.
Relevant approved information can be carried into the learner’s school context rather than being re-entered unnecessarily.
Admissions records and school-held learner records should still retain the appropriate source and history.
A parent or carer can be linked to multiple learners where the appropriate relationships exist.
Each child retains a separate learner record.
Yes.
The learner record can represent multiple relevant family relationships while preserving the context and permissions associated with each one.
No.
Family access should depend on the recognised relationship, relevant permissions, the school’s configuration and the information being shared.
No.
Teacher access can be limited to assigned classes, learners and permitted information areas.
No.
Safeguarding is a separately controlled information domain.
Access to the basic learner profile does not automatically provide access to safeguarding chronology or case information.
Yes.
Medical and care information should be available only to users with an appropriate responsibility and permission.
Appropriate previous-school and historical learner information can be retained as part of the learner journey.
Historical relationships should remain distinguishable from current ones.
EdiWay supports learner lifecycle and transition workflows.
Selected evidence can be prepared for an approved receiving setting without exposing the complete unrestricted learner record.
The learner journey should preserve continuity as year groups, classes and academic periods change rather than creating unrelated learner identities each year.
EdiWay can support data-quality and record-matching workflows, but potential matches should be reviewed carefully before records are combined.
Sensitive information should never be automatically merged without appropriate controls.
Import and migration may be supported depending on the data source and implementation arrangement.
Imported information should be mapped, validated and reconciled before operational use.
Approved professionals can participate through defined learner-specific relationships where enabled.
They should receive only the information required for the approved purpose – not unrestricted access to the full record.
AI assistance should remain permission-aware and human-reviewed.
EdiWay AI does not independently change admissions decisions, learner identity, SEND status, safeguarding findings or statutory records.
The active school relationship can be closed while relevant historical information is retained according to the school’s responsibilities and applicable retention rules.
Current access, family services and professional relationships should also be reviewed.
Selected information can be prepared through controlled transition workflows.
Sharing should have a defined recipient, purpose and information scope rather than automatically transferring the complete learner history.
No.
EdiWay connects the learner journey, but assessment, SEND, safeguarding, medical, family and professional information can retain different permissions, ownership and visibility.
Configure the school, year groups, subjects, roles and permissions that give learner records their organisational context.
Connect current learners to teaching groups, schedules and school registration.
Use current family relationships and learner context when sending approved school communication.
Connect assessment evidence, targets and review information to the correct learner.
Connect authorised support evidence while keeping sensitive information areas separately controlled.
Understand assessment permissions, contribution boundaries, edit history and retention.
EdiWay is undergoing active development and live testing.
Participating schools can explore available learner-record, admissions, relationship and lifecycle workflows and provide practical feedback on how information connects across everyday school activity.
Some admissions stages, imports, migrations, reporting, external sharing and specialised lifecycle workflows may require additional configuration, remain under development or be available through controlled rollout.