Operational value
The important outcome is not another leave register; it is earlier visibility of the timetable impact.
Workflow journey
Leave to substitute coverage
Connect staff leave requests to timetable context so coordinators can arrange substitute coverage before a class is uncovered. See the workflow, ownership, rollout sequence, and boundaries before choosing a school management platform.
One operating picture for academic, administrative, and family teams.
At a glance
A useful page should answer the next operational question
Connect staff leave requests to timetable context so coordinators can arrange substitute coverage before a class is uncovered.
Who this is for
- Teachers
- Line managers
- Timetable coordinators
Start with the evidence
Use the linked product and documentation pages to validate the workflow against your school’s data, roles, policies, and deployment.
Read the supporting materialHow it works
Follow the handoffs, not just the feature list
A clear sequence makes ownership, exceptions, and the next system action visible.
- 01
Request
A staff member submits dates, leave type, and reason through the role-scoped workspace.
- 02
Check
Approvers review entitlement, balance, calendar conflicts, and teaching responsibility.
- 03
Approve
The manager records the decision with a visible leave history.
- 04
Cover
The timetable team assigns a substitute and shares the class context and materials.
Product truth
What to verify before rollout
Good school software copy should answer who owns the work, what the handoff produces, and which parts still depend on deployment decisions.
Validate for your rollout
Capability status
This page describes the supported workflow boundary. Confirm configuration, integrations, data, and policy requirements in a representative pilot before committing to production.
Teams in the workflow
- Teachers
- Line managers
- Timetable coordinators
Deep dive
Decisions, handoffs, and boundaries
Use these details to turn a product page into an implementation conversation.
Deployment note
Agree who owns approval and substitute assignment because schools vary between HR, department heads, and academic offices.
What to rehearse
Test a short absence, an overlapping request, an approver decision, and a timetable change so the cover owner knows which record is authoritative.
Evidence layer
Read the supporting product and implementation material before making a capability claim.
Questions, answered
Straightforward answers for visitors evaluating the product.
Does approval automatically assign a substitute?+
The workflow surfaces the conflict and coverage need; schools should confirm the exact assignment policy during setup.
Assign a workflow owner and test it with a representative staff account before the busy part of the term. Verify that approvals, coverage details, and sensitive fields remain within the intended role.
Are student and staff leave the same process?+
They are related but distinct workflows with different approvers and records.
Assign a workflow owner and test it with a representative staff account before the busy part of the term. Verify that approvals, coverage details, and sensitive fields remain within the intended role.
Does the system replace the school leave policy?+
No. It records the configured request and decision flow; entitlement rules, emergency cover, and attendance policy remain school responsibilities.
Treat that boundary as an explicit procurement or deployment decision. Document the responsible owner and any supporting process before rollout.
Continue exploring
Related planning and product pages
Follow the next link based on the question your team needs to answer.
Turn the page into a rollout conversation
We can walk through the workflow with your school’s roles, calendar, data, and first-term priorities.
Already using Schoolyi? Sign in