Leave of Absence
Parent and warden approvals, with a live out-of-campus list.
One sentence a boarding school has to be able to answer at any moment, without ringing anybody: who is off campus, who said they could be, and when are they due back.
Students and parents file on their own emailed links — no accounts to issue. Each kind of leave carries its own rules (notice, duration, blackout dates, an allowance, a return time) and its own approval chain, because a day pass and a weekend exeat are signed off by different people.
The gate board shows a guard three lists in the order they matter at a boom: not back, out now, going out. Overdue is worked out from the clock, so it stops being true the moment the pupil walks back in.
HOW IT CONNECTS
A shared institutional foundation.
This module works within the same institution and student register as the rest of CampusOS. Staff access is controlled by their role and module permissions.
KEY CAPABILITIES
What changes in the workflow
Leave types with your own rules and your own approval chains
Filing by students and parents on one-time links, no logins to issue
Parent consent recorded with the wording as it stood that day
A gate board built for the person on the gate
Extensions that are kept as extensions, never an edit of the original
Where a child is staying, encrypted and behind its own permission
YOUR WORKFLOW IN CAMPUSOS
Show us how your institution works.
We’ll focus on this workflow in the live product and show you how it connects to the rest of the institution.