The approver is teaching
A head of department is in front of a class for most of the day and cannot action a request between periods. Approvals that assume desk access queue until after school, which is why same-day requests fail.
Workflows · Schools & Campuses
Approval Workflows That Match How Schools Decide
Leave, attendance regularization, and policy sign-offs routed the way schools actually work — HOD → Vice Principal → Principal — with every decision timestamped, auditable, and approvable from a phone.
Multi-level chains · Mobile approvals · Full audit trail · Growth plan
Corporate HR tools stop at 'manager approves'
Generic HR software assumes one manager approves everything. Schools don't work that way: a teacher's leave passes through the head of department, then the vice principal, and sometimes the principal — with different chains for teaching and non-teaching staff, and different rules during exam weeks. CampusTrack models those chains natively. Requests route to the right person at each level, reminders chase the pending step, and the full decision history stays on the record — so nothing lives in WhatsApp threads or gets signed on paper and lost.
Illustrative interface — a leave request moving through the HOD → VP → Principal chain.
Multi-level chains (HOD → VP → Principal)
Define approval chains per campus and per staff group. Teaching, admin, and support staff can each follow their own route.
Leave approvals
Leave requests carry balances, team-calendar context, and the academic calendar — approvers see exam-week clashes before they say yes.
Attendance regularization
Missed check-ins and corrections go through manager approval instead of silent edits — the register stays trustworthy.
Policy Read & Sign
Publish school policies with versioning, e-signature, and acknowledgement tracking — see exactly who has signed and who is pending.
Approve from a phone
Approvers act from the mobile app with push notifications — decisions do not wait for someone to reach a desktop.
Every decision on the record
Who requested, who approved, when, and at which level — a complete audit trail, inspection-ready without any assembly.
Where school approvals actually stall
Approval chains fail for organisational reasons rather than technical ones. These are the specific failure modes a school hits.
Nobody defined the deputy
When the approver is on leave, requests stop. A delegation rule that activates automatically is the difference between a chain that survives half-term and one that silently blocks for a week.
The chain differs by request, not by person
A day of leave and an unpaid sabbatical do not need the same signatures. Systems with one chain per employee force schools to either over-approve routine requests or under-approve serious ones.
Group and campus levels both exist
A branch principal approves within their school; a group HR director sits above all of them. A chain that only understands one level cannot express that, so it gets handled by email instead.
Verbal approval happened first
The teacher already asked in the corridor and was told yes. The system request is a formality afterwards, which means it needs to be fast and low-friction rather than a second decision point.
The trail matters more than the click
When a request is later disputed, what matters is who approved it, when, and what they saw at the time. An approval with no record is indistinguishable from one that never happened.
Questions
Frequently asked questions
Which plan includes multi-level approval workflows?
The Growth plan. Starter includes basic one-level leave approval; Growth adds the full HOD → VP → Principal chains, attendance regularization approvals, and policy Read & Sign with e-signature.
Can different campuses have different approval chains?
Yes. Chains are configured per campus and per staff group, so a nursery, a school, and a university campus in the same group can each route approvals their own way.
What happens when an approver is on leave?
Pending requests are visible to HR with reminders chasing the open step, so a request never disappears into an absent approver’s queue unnoticed.
Is the approval history available for audits?
Yes — every request carries its full decision trail (requester, levels, approvers, timestamps, comments) and exports with your attendance and leave records.
What happens to a request if the approver leaves the school?
Pending requests reassign to the delegate or the next level in the chain rather than sitting against a deactivated account. Requests stranded on a departed approver are one of the most common causes of a leave balance that never reconciles.
Can a request be withdrawn after submission?
Yes, up to the point it is actioned. A teacher whose circumstances change should not need an approver to reject something they no longer want, which is otherwise a rejection on their record for no reason.
Explore further
Interactive Onboarding ChecklistThe rollout checklist that walks a school through setup, from geofences to approval chains.Campus staff attendanceThe attendance layer these workflows sit on.Performance & observationQuality workflows with sign-offs — Full HRMS plan.PricingStarter free up to 50 staff · Growth AED 949/mo · Full HRMS custom.
See your approval chain in CampusTrack
A 20-minute walkthrough with your real chain — HOD, VP, Principal — on leave, regularization, and policies.