- AM & PM Registers
- Lesson Attendance
- Absence Management
- Family Communication
- Attendance Review
School Sessions
Record attendance against the appropriate school day or session.
Classes and Lessons
Connect lesson attendance to the correct class and timetable.
Learner Context
Make sure each attendance record belongs to the correct learner and school relationship.
Absence Context
Record relevant absence information and reasons.
Lateness
Capture late arrival and appropriate supporting information.
Follow-Up
Identify records or actions requiring authorised staff attention.
Family Communication
Connect relevant attendance communication to the correct learner and family relationship.
Reporting
Give authorised staff a clearer view of attendance information without losing the underlying record context.
Morning Register
Record the learner’s attendance for the relevant morning session.
Afternoon Register
Complete the appropriate afternoon registration.
Current Learners
Include learners who belong in the relevant school population rather than applicants, leavers or unrelated records.
Expected Learners
Use the learner’s active school and timetable context to understand who should appear.
Attendance Marks
Record the appropriate attendance status through the school’s configured workflow.
Missing Marks
Make incomplete register information visible rather than assuming a learner was present or absent.
Register Status
Show whether the relevant register remains incomplete or has been submitted.
Authorised Corrections
Allow permitted changes through appropriate attendance workflows. A missing mark should remain visibly unresolved until it is reviewed. It should not silently become an attendance conclusion.
Class Context
Open the register from the correct teaching group.
Lesson Context
Connect attendance to the appropriate scheduled period.
Learner List
Use current class membership rather than a separate attendance list.
Teacher Responsibility
Give the assigned teacher or authorised staff member access to the register they need.
Lesson Attendance
Record learner attendance at the relevant teaching session.
Late Arrival
Capture a learner arriving after the expected lesson start where appropriate.
Missing Learner Context
Help authorised staff investigate an unexpected absence from a lesson.
Register Completion
Make outstanding lesson registers visible for follow-up. Lesson-level attendance should complement the school’s wider attendance record without creating unrelated versions of the same learner.
Tutor Groups
Complete registration for the relevant tutor or form group.
Year Groups
Work with appropriately configured year structures.
Teaching Groups
Use class-based registration where this reflects the school day.
Multiple Attendance Points
Support more than one relevant registration point where the school requires it.
Staff Assignment
Keep register access connected to the appropriate staff responsibility.
Learner Membership
Use current group relationships to determine who belongs in the register.
Changes Over Time
Preserve historical attendance when class or group membership changes. A learner moving classes should not rewrite the context of registers completed earlier in the year.
Attendance Codes
Use the relevant configured coding structure.
Absence Reasons
Record supporting information explaining the attendance event where appropriate.
Authorised Absence
Maintain the school’s authorised absence record through the relevant workflow.
Unauthorised Absence
Record unauthorised absence according to the school’s approved process.
Lateness
Distinguish late arrival from ordinary absence.
School Activity
Preserve appropriate context where the learner is participating in an authorised activity.
Supporting Notes
Allow proportionate additional information where required.
Current Guidance
Schools remain responsible for ensuring that attendance codes and practices reflect the current requirements that apply to them. EdiWay can support the configured workflow but should not present a code as valid merely because it exists in the platform.
Initial Absence
Record that the learner is not present at the expected attendance point.
Reason
Add relevant absence information when it becomes available.
Family Contact
Record or connect appropriate communication with the learner’s parent or carer.
Supporting Information
Maintain relevant evidence through the appropriate workflow where required.
Authorisation
Record the authorised school decision about the absence where applicable.
Follow-Up
Assign an appropriate next action where more information is needed.
Review
Allow authorised staff to update the record when verified information becomes available.
History
Preserve appropriate context when an attendance record is corrected.
The system should distinguish:
We do not yet know why the learner is absent
from:
The school has reviewed the information and classified the absence.
Arrival Time
Record the relevant late-arrival information where required.
Attendance Session
Connect the late record to the appropriate session or lesson.
Reason
Record a relevant reason where supplied or required.
Staff Entry
Retain appropriate information about who recorded the event.
Family Information
Connect relevant parent or carer communication.
Repeated Lateness
Allow authorised staff to review recorded patterns over an appropriate period.
Follow-Up
Record agreed school actions where further review is required.
Correction
Allow authorised adjustment when the original information was incorrect. Repeated lateness can prompt a human review. It should not generate an automatic conclusion about the learner, family circumstances or safeguarding risk.
Missing Registers
Identify expected registers that have not yet been completed.
Incomplete Marks
Highlight learners whose attendance status remains unresolved.
Unsubmitted Activity
Show relevant registration workflows that remain open.
Responsible Staff
Make clear who is expected to complete or review the register.
Follow-Up
Allow appropriate actions or reminders to be coordinated.
Corrections
Identify attendance records that have been returned for review.
Data Readiness
Make incomplete attendance information visible before it is relied upon in wider reporting.
Leadership Oversight
Allow authorised leaders to understand where registration processes remain incomplete. A completed-looking dashboard should not hide unfinished registers underneath it.
Daily Attendance
Review relevant morning and afternoon information.
Lesson Attendance
See lesson-level history where the school uses that workflow.
Absence History
Review recorded absences and their relevant classification.
Lateness History
Understand recorded late-arrival information over time.
Corrections
Preserve appropriate information about supported changes.
Academic Periods
Review attendance within the relevant term, year or defined reporting period.
School History
Keep attendance connected to the school relationship in which it occurred.
Current Versus Historical
Distinguish current attendance concerns from older school records. Historical attendance provides useful context. It should not automatically determine the action required today.
Attendance Level
Review the learner’s recorded attendance within a defined period.
Absence Frequency
Understand how often absence has been recorded.
Lateness
Review relevant late-arrival information.
Changes Over Time
Compare appropriate periods where the underlying data supports it.
Registration Completeness
Check whether missing marks limit the interpretation.
Learner Context
Allow authorised users to consider relevant school information where they have permission.
Family Contact
See whether appropriate communication or follow-up has taken place.
Outstanding Actions
Identify meetings, information requests or reviews still requiring attention. EdiWay can help staff identify information that deserves review. It does not automatically determine the cause of absence or the correct intervention.
Defined Period
Make clear which attendance period is being considered.
Recorded Attendance
Use sufficiently complete registration data.
Absence Context
Review the information recorded against relevant absences.
Missing Information
Identify unresolved absence or register records.
Previous Follow-Up
See relevant attendance actions already completed.
Family Engagement
Review approved communication and contributions.
Support Context
Consider permitted pastoral, SEND or wellbeing information where it is relevant.
Next Action
Allow an appropriately authorised person to decide what should happen next. Schools remain responsible for applying current attendance guidance and thresholds. EdiWay should not use an unexplained algorithm to label a learner as an attendance risk.
Family Conversation
Record relevant contact and agreed next steps.
Learner Voice
Include an appropriate learner perspective where useful.
Meeting
Organise an attendance-focused meeting and its follow-up.
Actions
Assign tasks to the appropriate person.
Support Strategies
Record agreed approaches through the relevant school workflow.
Review Date
Make clear when attendance or support should be reconsidered.
Outcome
Record what happened following the action.
Escalation
Allow authorised staff to move information into another relevant process where required. Attendance support remains a human-led process. The platform helps organise the information and agreed actions around that work.
Restrictions
Respect relevant relationship, contact and information-sharing restrictions.
Absence Notifications
Send appropriate information to linked parents or carers where enabled.
Information Requests
Ask for relevant absence information through the appropriate communication route.
Late Notifications
Share permitted lateness information where the school’s process requires it.
Meeting Requests
Arrange attendance conversations and reviews.
Follow-Up Messages
Communicate agreed actions or next steps.
Positive Updates
Recognise meaningful improvement where appropriate.
Multiple Family Relationships
Use the correct approved recipient rather than assuming every linked adult has identical communication rights.
Communication History
Retain appropriate attendance-related communication where the workflow supports it.
Attendance Overview
View approved school attendance information.
Absence Information
See relevant absence details made available by the school.
Information Requests
Respond when the school needs additional context.
Communication
Receive appropriate attendance messages.
Meetings and Actions
See relevant agreed next steps.
Multiple Children
Move between linked learners without mixing attendance records.
Relationship-Based Access
Receive information according to the approved relationship with the learner.
Historical Context
Access only the attendance information the school has made available for the appropriate period. Families do not automatically receive internal attendance notes, information about other learners or restricted safeguarding records.
Attendance Record
Shows school participation and relevant registration information.
Behaviour Record
Describes recorded behaviour events, achievements or pastoral responses.
Combined Review
Authorised staff may consider both where there is a legitimate educational purpose.
Separate Ownership
A behaviour event should not automatically change an attendance record.
Separate Conclusions
Absence does not prove a behaviour concern.
Pastoral Support
Relevant evidence can inform an appropriate human-led support discussion.
Safeguarding Boundary
Neither attendance nor behaviour automatically establishes a safeguarding finding.
Appropriate Adjustments
Review permitted information about agreed support where relevant.
Learner Voice
Understand appropriate learner experience and barriers.
Family Evidence
Consider relevant parent or carer context.
Support Plans
Connect approved attendance-related actions to the appropriate support workflow.
Intervention Context
Consider relevant support that has been delivered.
Review
Allow the SENCO or other authorised person to participate where needed.
Information Boundaries
Keep detailed SEND evidence restricted to users with an appropriate role. Attendance patterns do not diagnose SEND or establish the cause of absence.
Attendance Change
Identify recorded changes that may warrant conversation.
Pastoral Information
Review permitted relevant context.
Learner Check-In
Use appropriate learner voice where enabled.
Family Context
Consider approved family information.
Support Actions
Connect attendance to suitable pastoral follow-up.
Review
Record what authorised staff decided to do next.
Information Separation
Keep sensitive wellbeing records out of general attendance views unless access is appropriate. A change in attendance is a signal to review the context. It is not a mental-health diagnosis.
Preserve Attendance
Keep the original attendance record in its proper context.
Raise a Concern
Allow authorised staff to follow the school’s safeguarding process where necessary.
DSL Review
Keep safeguarding review within the restricted safeguarding domain.
Information Boundaries
Do not make safeguarding chronology visible to ordinary attendance users.
Human Decision
Allow trained staff to determine whether further safeguarding action is required.
Record the Outcome
Keep safeguarding decisions and follow-up inside the correct controlled workflow. EdiWay does not automa ically infer neglect, abuse or safeguarding risk from attendance data.
Provider Context
Identify the relevant provision or education provider.
Session Information
Record appropriate participation or delivery information.
Responsible Organisation
Keep the school or authority context visible where applicable.
Learner Status
Distinguish alternative provision from ordinary on-site school attendance.
Provider Evidence
Preserve the source of relevant attendance information.
Follow-Up
Identify missing or incomplete provider information.
Review
Use appropriate provision and progress workflows rather than assuming school registration alone explains participation.
Reintegration
Maintain relevant historical context where a learner returns to a school timetable.
Authorised Editing
Limit attendance corrections to users with the appropriate responsibility.
Previous Information
Retain suitable historical context for supported changes.
Reason for Change
Record an explanation for material corrections where the workflow requires it.
Actor
Keep appropriate information about who made the change.
Date and Time
Preserve when the correction occurred.
Updated Status
Make the current attendance record clear.
Related Evidence
Connect relevant supporting information where appropriate.
Record the Outcome
Allow unusual or significant changes to be reviewed by an authorised user. Corrections should improve the record without silently erasing important history.
Incomplete Registers
Identify attendance points that remain unfinished.
Missing Learner Marks
Show unresolved records.
Unexpected Learners
Highlight inappropriate or inconsistent register membership for review.
Duplicate Information
Identify potential duplicated attendance records.
Invalid Context
Make attendance linked to the wrong period or school context visible for correction.
Leavers
Prevent former learners from continuing to distort current attendance populations.
New Starters
Make the effective start of the school relationship clear.
Timetable Changes
Preserve the correct context when classes or teaching arrangements change.
Corrections
Make authorised updates visible to appropriate reviewers.
Reporting Readiness
Indicate when missing information materially limits a report. Attendance reporting should expose important data gaps rather than hiding them inside a percentage.
Individual Learner
Review attendance history for an authorised learner and defined period.
Class
Understand attendance within an appropriate class context.
Year Group
Review relevant information for a defined cohort.
School
Provide authorised leadership oversight of the current learner population.
Time Period
Make the dates or academic period explicit.
Attendance Measure
Explain what is included in the calculation.
Missing Data
Show when incomplete registers affect interpretation.
Absence Context
Allow authorised users to understand appropriate recorded reasons.
Group Review
Compare permitted populations carefully.
Follow-Up
Move from a report to the learners or actions requiring authorised attention. A percentage is only meaningful when its population, dates and underlying data are understood.
Register Completion
Which relevant registers remain incomplete?
Current Attendance
What does the recorded school attendance picture show?
Missing Information
Which attendance records remain unresolved?
Lateness
Are there repeated late-arrival patterns requiring review?
Attendance Concerns
Which learners meet the school’s defined criteria for further attention?
Family Contact
Has relevant follow-up been recorded?
Support Actions
Are attendance-related actions complete or overdue?
Data Quality
Is incomplete information limiting the school-level picture?
Trends
How has recorded attendance changed across appropriate periods? Leadership information should point towards the next human action rather than simply create more statistics.
Teachers
Complete relevant class, lesson, tutor or session registers and review learners within their assigned scope.
Attendance Staff
Review absence information, lateness, incomplete records and relevant follow-up.
Pastoral Teams
Use appropriate attendance context when coordinating learner support.
SENCOs
Consider attendance alongside permitted SEND information where relevant.
Safeguarding Leads
Review attendance information where it forms part of an authorised safeguarding process.
School Leaders
Access appropriate school-level attendance oversight and reporting.
Administrative Staff
Maintain relevant learner, registration and attendance information.
Parents and Carers
Access attendance information approved for their linked child.
Learners
See age-appropriate attendance information where enabled.
School Scope
Attendance belongs to the relevant school context.
Learner Scope
Users access attendance only for appropriate learners.
Class Scope
Teachers can be limited to assigned teaching groups.
Role Scope
Different attendance actions can be available to different staff.
Attendance Concerns
Viewing a register does not necessarily permit historical correction.
Reporting Scope
School-level reporting should be limited to authorised roles.
Family Scope
Parents and carers access only the information approved for their learner relationship.
SEND Scope
Sensitive support information remains separately permissioned.
Safeguarding Scope
Safeguarding chronology remains separately controlled.
Draft Attendance Summaries
Prepare a concise summary of selected recorded information.
Family Communication Drafts
Help prepare appropriate attendance messages for human review.
Meeting Preparation
Organise relevant permitted attendance information before a review.
Follow-Up Summaries
Draft an overview of actions already recorded.
Missing Information
Highlight unresolved fields or incomplete context.
Reporting Explanation
Help authorised users understand the information shown in a selected attendance report. Every AI output remains a draft requiring human review.
EdiWay AI does not:
- Predict that a learner will become persistently absent
- Determine why a learner is absent
- Diagnose a medical, SEND or mental-health condition
- Infer neglect or safeguarding risk from attendance alone
- Decide whether an absence should be authorised
- Make legal or enforcement decisions
- Automatically decide which intervention a learner requires
- Replace current attendance guidance or school policy
1. Establish the Context
Identify the school, date, session, lesson, class and expected learners.
2. Take the Register
Record the relevant attendance information.
3. Identify Missing Information
Keep unresolved marks and incomplete registers visible.
4. Add Context
Record appropriate absence or lateness information.
5. Communicate
Contact the correct family member where required and enabled.
6. Review
Allow authorised attendance or pastoral staff to consider repeated or significant concerns.
7. Support
Connect appropriate actions, meetings or wider support where necessary.
8. Escalate Carefully
Move relevant information into SEND, wellbeing or safeguarding workflows only through an authorised human decision.
9. Report
Use sufficiently complete attendance information for individual, cohort or leadership review.
10. Preserve History
Retain appropriate context when attendance records are corrected or the learner changes setting.
- Whether the register was completed
- Whether a learner was absent or simply unmarked
- Why the learner was absent
- Whether the parent or carer was contacted
- Whether lateness has become repeated
- Whether a meeting was arranged
- Whether support was agreed
- Whether the record was later corrected
- Whether incomplete data is affecting reports
- Whether school attendance is being confused with EOTAS, home or alternative provision activity
EdiWay connects the attendance record to the wider learner and school context while keeping the interpretation and response with authorised people.
EdiWay supports core school-registration workflows including morning, afternoon and lesson attendance, with tutor, group or additional attendance points available according to school configuration.
Yes.
Lesson registers can be connected to the relevant class, timetable and assigned learners.
EdiWay supports recording lateness and associated context such as an appropriate reason where required.
Attendance workflows can support relevant absence classification according to the school’s configured processes.
Schools remain responsible for applying current attendance requirements and determining the appropriate classification.
EdiWay supports configured attendance coding and reason structures.
Schools remain responsible for ensuring their configuration reflects the current requirements applying to their setting.
Attendance reporting can help authorised users identify learners meeting configured or current review criteria.
The underlying attendance data should be sufficiently complete, and the school remains responsible for applying current guidance and deciding what action is appropriate.
The public product should not be positioned as automatically predicting which learners will become absent.
Attendance information can support human-led review of recorded patterns and circumstances.
Attendance communication can be sent to linked parents or carers where the relevant communication workflow is enabled.
Recipient selection should respect current family relationships and information-sharing controls.
Family responses or information requests may be supported through enabled communication workflows.
The school remains responsible for reviewing the information and updating the attendance record appropriately.
Relevant attendance context can be considered within an authorised SEND review.
Attendance does not diagnose SEND or automatically reveal the learner’s complete SEND record to attendance users.
No.
An authorised person may decide that attendance information requires safeguarding review, but attendance does not automatically establish neglect, abuse or other safeguarding findings.
Authorised safeguarding users may use relevant attendance information where it forms part of their responsibilities.
Ordinary attendance access does not provide access to the safeguarding record.
AI should not automatically label a learner as vulnerable or predict safeguarding risk from attendance.
Where enabled, AI can assist with drafting, summarising and preparation from permitted information.
Home education should not be represented as ordinary school attendance.
Parent-led routines and learning records belong within the home-education pathway.
EOTAS participation or provision records should remain separate from ordinary school registration.
The exact workflow depends on the enabled education pathway and responsibility model.
Authorised corrections can be supported, with appropriate context around material changes where enabled.
Authorised leaders can review appropriate school-level attendance information according to their role, data readiness and reporting configuration.
EdiWay should not be assumed to provide a live official government submission connection unless that specific workflow has been implemented, tested and documented.
The school remains responsible for its official reporting and statutory responsibilities.
No software automatically creates organisational compliance.
Schools remain responsible for their policies, attendance practice, current guidance, staff decisions and statutory duties.
Schools can begin with relevant available registration and attendance workflows and connect communication, pastoral support, reporting and other areas as implementation develops.
Feature availability may depend on configuration, permissions, subscription and controlled rollout.
Learner Records
Use the active learner, school and family context that underpins attendance.
Classes and Timetables
Connect registers to the correct teaching groups, learners and school day.
Communication and Family Engagement
Contact linked families and coordinate appropriate attendance follow-up.
Behaviour, Rewards and Pastoral Support
Consider permitted behaviour and pastoral context without treating attendance as a behavioural conclusion.
SEND, Safeguarding and Wellbeing
Connect relevant attendance evidence to controlled support workflows when an authorised person decides it is appropriate.
Reporting and Administration
Review attendance, missing registers, data quality and school-level information.