- Daily Checks
- Premises
- Maintenance
- Visitors
- Trips
- Transport
- Catering
- Safety
- Evidence
Daily Checklist
Maintain the school’s configured operational checks.
Staff Tasks
Assign appropriate work to responsible staff.
Completion
Record when configured tasks have been completed.
Outstanding Work
Keep unfinished activity visible.
Escalation
Surface missed or overdue checks where supported.
Evidence
Attach appropriate supporting information.
Photos
Maintain relevant inspection evidence where enabled.
Operational Overview
Give authorised leaders visibility of the current position. The purpose is not to create more administration. It is to make operational responsibility easier to see.
Premises
Check relevant areas before use.
Access
Record appropriate opening activity.
Playground
Maintain configured outdoor checks.
Cleaning
Record required inspection activity.
Catering Areas
Connect relevant kitchen checks.
Accessibility
Maintain appropriate accessibility-review records.
Water and Utilities
Record applicable school-held checks.
Outstanding Defects
Keep known issues visible. The school determines which checks apply, how frequently they are required and who is competent to complete or review them. EdiWay records the workflow. It does not determine the school’s legal obligations automatically.
Building Assets
Maintain an appropriate school asset register.
Rooms
Keep operational room information connected.
Maintenance
Track repairs and maintenance activity.
Planned Work
Record appropriate planned maintenance.
Contractors
Maintain relevant contractor relationships.
Asset History
Keep appropriate maintenance history.
Evidence
Connect inspection or repair evidence.
Operational Status
Make known issues easier to identify. The detailed estates record stays operational. School-level risk and compliance oversight can use that evidence without creating a second version of it.
Issue
Record the defect or maintenance requirement.
Location
Keep the problem connected to the relevant school area or asset.
Priority
Record the school’s reviewed operational priority.
Owner
Identify who is responsible for the next action.
Contractor
Connect an appropriate external contractor where required.
Evidence
Attach relevant information or photos.
Work
Track the appropriate repair activity.
Completion
Record the school-held outcome.
History
Preserve appropriate earlier activity. EdiWay helps track the record and response. It does not independently determine whether a building, room or asset is safe to use.
Fire Alarm Checks
Record testing activity.
Weekly Fire Tests
Maintain scheduled school-held records.
Fire Drills
Record drill activity and appropriate outcomes.
Evacuation Records
Maintain relevant evacuation evidence.
Fire Doors
Record inspections.
Fire Extinguishers
Maintain appropriate check information.
Emergency Lighting
Record relevant testing.
Fire Risk Assessments
Keep school-held assessments connected to the operational record. EdiWay helps organise the evidence. The responsible school and competent people remain accountable for determining whether checks, controls and assessments are sufficient.
Risk Assessments
Maintain school risk-assessment records.
Dynamic Risk Assessments
Record appropriate changing operational context.
Accidents
Maintain accident records.
Incident Investigation
Record authorised follow-up.
First Aid Register
Keep relevant first-aider information.
First Aid Incidents
Record appropriate school-held treatment information.
COSHH
Maintain relevant hazardous-substance records.
PPE
Keep applicable PPE records.
Safety Training
Connect appropriate workforce evidence.
Inspections
Maintain safety-inspection records. EdiWay supports recording, evidence and follow-up. It does not decide that an activity is safe or that a risk is legally acceptable.
- Legionella checks
- Water temperature logs
- PAT testing
- Gas safety
- Electrical inspections
- Playground checks
- Kitchen safety
- Cleaning audits
- Accessibility checks
- Daily opening checks
EdiWay can help schools connect those records to owners, dates and evidence. The school remains responsible for determining which requirements apply and what frequency, competence and external certification are required.
Visitor
Maintain the relevant visit record.
School
Keep the visit within the correct organisational scope.
Host
Identify the appropriate school contact.
Arrival
Record check-in information.
Departure
Record check-out.
Contractor
Connect appropriate contractor context.
Badge or Access Context
Maintain relevant operational information where supported.
Presence
Give authorised users appropriate visibility of current visitors.
History
Preserve suitable previous visit information. Visitor access is an operational workflow. It should not automatically expose learner, safeguarding, medical or other sensitive information. Advanced visitor identity, restricted-person and emergency-accountability workflows remain subject to additional assurance.
Trip
Maintain the authorised school trip record.
Learner Roster
Keep the correct learners connected to the visit.
Parent and Carer Decisions
Record appropriate trip permission where enabled.
Risk Assessment
Maintain the trip-specific school-held assessment.
Staff
Record appropriate trip staffing.
Transport
Connect relevant school vehicle and accessibility context where enabled.
Departure
Record appropriate trip departure.
Return
Maintain return information.
Emergency Information
Prepare controlled minimum-necessary information where supported.
Evidence
Keep relevant trip records connected. Trip decisions, risk assessments and departure approval remain human responsibilities.
Learner Roster
Are the expected learners recorded?
Consent
Is required family permission available?
Current Risk Assessment
Has the configured school review been completed?
Trip Lead
Is an appropriate member of staff assigned?
Staffing
Does the school’s configured supervision approach have the required people?
Vehicle Context
Is appropriate school-held vehicle information available where relevant?
Accessibility
Have explicit transport requirements been considered?
Expected Return
Is the trip schedule clear?
Emergency Information
Is the required controlled pack available where enabled? A readiness state reflects the configured operational evidence. It is not an independent certification that a trip is safe.
Routes
Maintain appropriate route information.
Vehicles
Keep school-held vehicle records.
Learner Assignments
Connect learners to appropriate transport arrangements.
Incidents
Maintain relevant transport incidents.
School Scope
Keep transport information within the correct organisation.
Trip Transport
Connect appropriate transport requirements to educational visits.Connect relevant school vehicle and accessibility context where enabled.
Accessibility
Record explicit operational requirements where supported. The wider transport lifecycle – including advanced manifests, provider integration, telematics and live tracking – should not currently be assumed to be fully available. EdiWay should not be presented as continuously tracking learners or vehicles.
Meal Registrations
Use recorded meal activity where enabled.
Allergen Alerts
Surface appropriate recorded information to authorised users.
Kitchen Safety
Maintain relevant inspection evidence.
Learner Context
Connect meal information to the correct learner where appropriate.
Operational Oversight
Use recorded activity without inferring unrecorded kitchen conditions. Broader catering operations – such as full menu planning, stock, production forecasting, waste management and end-to-end kitchen reconciliation – remain a developing capability area. A missing meal record should not automatically be interpreted as a nutrition, welfare or safeguarding concern.
Events Calendar
Maintain school events.
Parent Events
Connect suitable family activity.
Learner Context
Link appropriate school participation where supported.
Communication
Keep relevant event information available to the intended audience.
Trips
Use the dedicated trip workflow when an activity requires the additional operational controls of an educational visit.
Permissions
Keep access appropriate to the activity. Broader end-to-end club and co-curricular management – including enrolment, registers, payments and achievement history – remains an area being consolidated across existing events, trips and learner workflows.
- Medical conditions
- Allergies
- Medication requirements
- Care plans
- First aid information
- Appropriate practical alerts
Operational users should receive only the information required for their role.
School Operations
Owns the detailed operational records:
- Daily checks
- Fire safety activity
- Health and safety records
- Premises inspections
- Maintenance
- Contractor activity
- Relevant statutory checks
- Operational evidence
School Compliance, Risk and Evidence
Uses appropriate information for:
- Whole-school oversight
- Responsibilities
- Deadlines
- Risk-register context
- Evidence readiness
- Inspection preparation
- Controlled evidence sharing
The same operational check should not have to be recreated in two places.
Admissions
New learner applications and enrolment belong to Admissions and Learner Records.
Attendance
Registers and school attendance belong to Attendance and Registration.
Timetable
Teaching schedules belong to Classes, Timetable and Attendance.
Behaviour
Behaviour, rewards and pastoral activity remain within their dedicated workflow.
Medical
Sensitive learner care records belong to Medical and Care Records.
Compliance
School-level compliance and evidence readiness belong to School Compliance, Risk and Evidence.
Governance
Policies, governors and improvement activity belong to School Governance, Policies and Improvement. School Operations connects to these workflows without duplicating their records.
Operations Staff
Manage relevant premises and daily workflows.
Site and Estates Staff
Access appropriate building, asset and maintenance information.
School Leaders
Receive authorised operational oversight.
Trip Leads
Access the information required for their educational visit.
Catering Staff
Receive appropriate meal and allergen context.
Transport Staff
See relevant route, vehicle or learner-assignment information.
Medical Staff
Access appropriate care records through the medical workflow.
Teachers
Receive the operational information relevant to their teaching responsibilities.
Parents and Carers
See suitable events, trip requests and learner-specific information where enabled.
Current
Relevant information is available and current.
Attention
Recorded information requires follow-up.
Quiet
No recent relevant activity has been recorded.
Empty
The applicable record contains no items.
Unavailable
The required source or workflow is not available. This matters operationally. “No record available” is not the same as “no problem exists”.
Operational Summaries
Organise selected current information.
Outstanding Tasks
Prepare a working overview.
Inspection Preparation
Help organise permitted evidence.
Meeting Preparation
Summarise selected operational context.
Draft Communication
Prepare appropriate messages for human review.
Evidence Organisation
Help authorised staff locate relevant source information. Every output remains human-reviewed.
EdiWay AI does not:
- Decide whether premises are safe
- Approve a risk assessment
- Determine whether a fire check is legally sufficient
- Certify statutory compliance
- Decide whether a trip is safe to depart
- Determine a learner's medical requirements
- Infer safeguarding risk from ordinary operational data
- Automatically approve contractors
- Replace competent professional judgement
1. Configure the Operational Requirement
Define the school’s applicable check or workflow.
2. Assign Responsibility
Identify the appropriate staff member or team.
3. Complete the Work
Record the operational activity.
4. Add Evidence
Attach suitable supporting information where required.
5. Identify Exceptions
Keep incomplete or problematic activity visible.
6. Take Action
Record the appropriate response.
7. Escalate Where Needed
Bring unresolved operational issues to the appropriate person.
8. Preserve History
Keep earlier activity understandable.
9. Feed Compliance Oversight
Use relevant operational evidence without duplicating it.
10. Review
Keep the operational process current as school requirements change.
School Operations focuses on the practical workflows involved in running the school day, including daily checks, premises, maintenance, health and safety records, visitors, contractors, trips, transport and relevant meal or event activity.
Admissions now has its own dedicated Admissions and Learner Records workflow.
School Operations can connect to it without duplicating the admissions record.
School attendance and registration have their own dedicated workflow.
Operational activities such as trips or alternative settings can maintain their own relevant participation context.
Yes.
Daily operational checklists are represented within the current capability set.
Yes.
Staff task assignment and completion tracking are represented within daily operations.
Escalation alerts are represented within the operational capability set.
Yes.
Fire alarms, weekly tests, drills, evacuations, fire doors, extinguishers, emergency lighting and fire-risk-assessment records are represented.
Yes.
Risk assessments, accidents, incident investigation, first aid, COSHH, PPE, training and inspection records are represented.
No.
EdiWay helps maintain records, actions and evidence.
Schools remain responsible for competent assessment and their legal and operational obligations.
Yes.
Building assets, maintenance workflows, contractors, asset history and planned maintenance are represented.
Visitor-presence and contractor-sign-in foundations exist.
Some advanced visitor controls remain subject to additional runtime and security assurance.
Yes.
Trip management, consent, risk assessments and trip registers are represented, with more advanced staffing, transport and emergency-information controls undergoing continued assurance.
Parent and carer trip-permission workflows are represented where enabled.
No.
Trip safety, risk assessment and departure decisions remain with authorised staff and the school’s procedures.
Transport foundations include route, vehicle, learner-assignment and incident oversight.
Full manifests, provider integration, telematics and live tracking should not currently be assumed.
Not currently as a complete end-to-end kitchen platform.
Meal registrations, appropriate allergen context and operational safety evidence can be connected, while broader catering operations remain under development.
Events and activity foundations exist, but a fully consolidated co-curricular lifecycle covering enrolment, registers, payments and achievement remains a developing area.
Yes.
Detailed operational records can contribute to School Compliance, Risk and Evidence without being recreated there.
No.
AI may assist with permitted summaries and evidence organisation where enabled.
Safety, risk and compliance decisions remain human.
School Compliance, Risk and Evidence
Turn appropriate operational checks and evidence into whole-school oversight.
Medical and Care Records
Keep sensitive learner medical and care information within its dedicated permission boundary.
Attendance and Registration
Manage school attendance separately from trips and other operational activity.
Classes, Timetable and Attendance
Connect teaching schedules, rooms and staff to the wider operational context.
School Governance, Policies and Improvement
Connect operational evidence to appropriate leadership, policy and improvement oversight.
Permissions, Consent and Information Sharing
Control access to sensitive learner, staff and operational information.