Running a school involves hundreds of operational details that sit behind teaching and learning.
Opening checks. Premises. Visitors. Repairs. Fire safety. Trips. Transport. Catering. Contractors. Incidents. Tasks. Evidence.
EdiWay brings those operational workflows into a connected, permission-aware school workspace so the right people can see what needs doing, who is responsible, what has been completed and what still needs attention.
EdiWay supports the classes and teaching groups that organise day-to-day learning.
Create and maintain appropriate classes.
Connect the correct learners to each group.
Assign appropriate teaching responsibility.
Connect classes to the relevant subject.
Maintain appropriate course or pathway context.
Keep teaching structures connected to the wider school organisation.
Use the class as part of scheduled teaching.
Connect lesson registers to the relevant group. The class becomes part of the connected school structure rather than another standalone list of learners.
Schools can maintain their curriculum organisation around subjects, courses, departments and teaching groups.
Create and manage the school’s subject structure.
Maintain appropriate courses and pathways.
Group relevant teaching activity.
Connect teaching groups to the appropriate subject or course.
Keep teaching responsibility connected.
Maintain the appropriate learner membership.
Use the same structure when scheduling lessons. This gives the timetable a meaningful academic context rather than treating it as a collection of unrelated calendar entries.
EdiWay supports school timetable creation around the people and spaces required for teaching. A timetable entry can connect:
Which teaching group is scheduled?
Who is teaching?
Which learners belong to the scheduled group?
What is being taught?
Where is the lesson taking place?
When does it happen?
Which recurring or rotating timetable context applies?
What additional scheduled resources are required where enabled? The same timetable structure can then feed staff, learner, classroom and registration workflows.
Individual staff timetables can show the appropriate scheduled teaching context.
See the teaching groups assigned to the member of staff.
Understand the day’s scheduled activity.
See where each lesson is due to take place.
Keep lesson periods clear.
Move from the lesson into the relevant attendance workflow.
See appropriate changes where cover has been assigned.
Keep relevant timetable context distinguishable where enabled. The staff timetable connects naturally into the Teacher and Classroom Workspace.
EdiWay can provide learner-specific timetable information based on current class membership and scheduled teaching.
See scheduled learning.
Understand the subject context.
Keep the relevant class clear.
Show appropriate lesson locations.
Display suitable teaching information.
Reflect authorised timetable updates.
Make appropriate timetable information available through the learner workspace. The learner timetable uses the connected learner record rather than requiring a separate schedule to be maintained manually.
Rooms can be allocated as part of the timetable.
Identify the teaching space.
Connect it to the scheduled group.
Maintain the teaching responsibility.
Keep occupancy linked to the correct period.
Identify overlapping room allocations.
Keep rooms and timetable records within the correct organisation. Room allocation helps coordinate school space. It does not independently determine that a room is safe, accessible or suitable for a particular activity. Relevant premises and operational records remain within School Operations.
Connected timetable data can identify known scheduling conflicts. EdiWay's current timetable foundations can check overlaps involving:
Avoid scheduling the same member of staff into conflicting lessons.
Identify overlapping class allocations.
Prevent known double-bookings.
Consider repeating timetable entries.
Consider specific scheduled entries.
Respect appropriate cycle-week context.
Reject inappropriate cross-school timetable relationships. Conflict checks are based on the information recorded in EdiWay. A timetable without a detected conflict does not guarantee that every practical staffing, room or operational constraint has been considered.
School timetables change. Staff may be absent. Rooms may become unavailable. Teaching groups may change. A one-off activity may affect the normal school day. When authorised changes are made, the connected structure can help keep relevant workflows aligned.
Update the appropriate teaching responsibility.
Keep the correct group attached.
Change the scheduled space.
Maintain the revised period.
Reflect the appropriate change.
Keep the current schedule visible.
Connect attendance to the correct lesson context.
Use the dedicated cover workflow when staff absence requires replacement.
EdiWay connects timetable and workforce cover information. When a member of staff is unavailable, authorised staff can understand the teaching responsibilities affected and coordinate an appropriate response.
Identify what needs covering.
Use the workforce record.
Consider relevant staff scheduling information.
Record the authorised cover arrangement.
Keep the replacement responsibility clear.
Allow the appropriate authorised member of staff to manage the lesson workflow. Cover remains a management decision. The timetable does not automatically decide who should cover an absent colleague.
The timetable provides important context for attendance. A scheduled teaching group can connect directly to the appropriate lesson register.
Use the current teaching group.
Use the appropriate class membership.
Connect attendance to the scheduled teaching period.
Allow the authorised member of staff to take the register.
Maintain the attendance record.
Keep subsequent authorised amendments auditable. This reduces the need to recreate learner lists every time a register is taken.
EdiWay supports multiple registration points, including:
Record morning attendance.
Record afternoon attendance.
Take attendance within individual lessons.
Use the appropriate tutor or registration group.
Support additional attendance points where configured. The detailed management of attendance codes, lateness, absence, parent notifications, persistent absence and attendance analysis belongs to the dedicated Attendance and Registration workflow.
Attendance depends on accurate group membership. EdiWay connects class membership and timetable context so registers can reflect the relevant learner group.
Use appropriate active class membership.
Keep the correct register context.
Connect the group to the scheduled lesson.
Keep register access appropriately scoped.
Return attendance to the connected learner journey.
Preserve appropriate attendance records even when future class membership changes. Changing a learner’s class should not silently rewrite their historical attendance.
Where enabled, EdiWay's developing curriculum pathway foundations can connect learner choices to teaching groups and timetable feasibility. That can include:
Organise appropriate curriculum choices.
Record supported learner or family selections.
Consider available places.
Apply configured required or incompatible choices.
Check relevant timetable clashes.
Generate appropriate option classes where supported.
Keep confirmed learner allocation visible.
Provide factual information about enrolment and capacity. These workflows remain subject to configuration and runtime assurance and should not be presented as autonomous curriculum decision-making.
The timetable is one part of the teacher's wider workflow. From the relevant class, authorised teachers can connect to areas such as:
See the learners they currently teach.
Record lesson attendance.
Use relevant teaching material.
Set appropriate work.
Record and review authorised academic evidence.
See appropriate learner support information according to permissions.
Keep learning evidence connected. The teacher should not need unrestricted access to the entire learner record simply because the learner appears on their timetable.
Teachers may need practical information to help a learner participate in lessons. Where authorised, the classroom context may surface information such as:
Approved classroom-useful support.
Relevant agreed educational adjustments.
Practical strategies for the lesson.
Minimum necessary safety information.
Appropriate information relevant to current teaching.
Relevant classroom support relationships. This does not give every teacher unrestricted access to full SEND, medical, wellbeing or safeguarding records.
Different users need different timetable information.
Access their classes and relevant teaching schedules.
See their appropriate timetable.
See suitable learner timetable information where enabled.
Manage authorised school timetable structures.
Access appropriate whole-school oversight.
Use relevant staffing and timetable context.
Access schedules relevant to their assigned responsibilities.
Timetabling and school operations intersect around rooms, events and temporary changes.
Use the school’s appropriate teaching spaces.
Known operational issues may affect room availability.
Off-site activities can affect the ordinary school day.
School activity can create timetable changes.
Staff absence can change teaching responsibility.
Keep premises and safety evidence within its own canonical workflow. The timetable coordinates teaching use of school space. It does not replace premises management.
Where enabled and appropriately assured, AI or automated assistance may help authorised users work with timetable information. That could include:
Help identify scheduling issues.
Assist with possible arrangements.
Organise factual class, staff or room information.
Help understand the impact of proposed changes.
Prepare working information for timetable managers. Any generated recommendation remains subject to human review.
Maintain subjects, courses and departments.
Connect learners to appropriate classes.
Keep teaching responsibility clear.
Schedule classes into appropriate periods.
Connect lessons to school spaces.
Identify known staff, class and room clashes.
Make appropriate staff and learner timetables available.
Use the class through the Teacher Workspace.
Connect attendance to the scheduled group.
Manage cover, room changes and authorised timetable updates without breaking the wider learner record.
Yes.
Class management and teaching-group capability are part of the current platform scope.
Yes.
Subject, course and department management are represented within the curriculum structure.
Yes.
Timetable creation is part of the current platform capability set.
Yes.
Individual staff timetables are supported.
Yes.
Learner timetable capability is represented.
Yes.
Room allocation forms part of timetable management.
Yes.
Current timetable foundations include staff, class and room overlap checking.
The platform supports timetable construction and conflict management.
The website should not promise fully autonomous optimisation or a guaranteed optimal timetable.
Current timetable integrity controls cover recurring, dated and rotating-week entries.
Yes.
Lesson attendance is supported alongside AM, PM, tutor and multiple daily registers.
No.
This page explains how attendance connects to classes and timetables.
Detailed attendance codes, lateness, absence management, persistent absence, notifications, reporting and interventions belong to Attendance and Registration.
Authorised timetable changes can remain connected to the relevant staff, class and learner schedule.
Yes.
Cover management is represented within timetable capability and connects to the dedicated workforce absence and cover workflow.
Current timetable foundations include room-overlap controls based on recorded timetable information.
No.
Premises suitability, maintenance, safety and accessibility remain operational responsibilities.
Yes.
The teacher’s authorised class context can connect to registers, resources, assignments and assessment workflows.
No.
Sensitive SEND, safeguarding, medical and wellbeing information remains subject to separate permission boundaries.
No.
Any AI or automated timetable assistance should remain subject to authorised human review.
Move from the scheduled class into day-to-day teaching.
Connect staff availability and authorised cover to teaching responsibilities.
Manage registers, attendance codes, absence, lateness, persistent absence and attendance support.
Connect suitable resources to classroom activity.
Keep academic evidence connected to the learner and class context.
Connect rooms, premises and operational changes without duplicating the timetable record.
EdiWay is undergoing active development and live testing.
Subject management, course management, teaching groups, departments, timetable creation, staff timetables, learner timetables, room allocation, resource allocation, cover management and timetable conflict handling are represented within the current platform capability set.
Current timetable integrity foundations validate school ownership and can identify overlapping staff, class and room allocations across recurring, dated and rotating-week timetable entries.
Attendance foundations include AM, PM, lesson and tutor registers, with the wider detailed attendance workflow available through Attendance and Registration.
Curriculum-option allocation, advanced timetable utilisation, protected-time handling and AI-assisted timetable workflows may require additional configuration, runtime assurance or controlled rollout.
EdiWay should therefore be positioned as a connected class, timetable and registration environment - with final curriculum, staffing, room and scheduling decisions remaining with authorised school staff.