Skip to main content
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.

Multi-level school approval chain — HOD, Vice Principal, and Principal steps with statuses

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.

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.

See your approval chain in CampusTrack

A 20-minute walkthrough with your real chain — HOD, VP, Principal — on leave, regularization, and policies.