Approvals with context
Keep the request, dates and approval status connected for the responsible teams.
Student Movement
A permission is a decision.A return completes the journey.
Connect leave, day-out and late-night requests with parent and warden approvals, gate records and the hostel’s nightly follow-up.
A personalised 30-minute campus walkthrough.
A connected campus workflow
- 01
Request permission
The student applies for leave, day-out or late entry.
- 02
Review the request
Parents and wardens act through the configured approval route.
- 03
Follow the movement
Gate records and hostel reporting give teams the context for follow-up.
Your university defines the rules and responsibilities.
Connected roles
- Students & parents
- Wardens
- Hostel & main-gate security
- Student welfare
What this connects
The work. The people. The complete picture.
Departure & return
Follow movement through the configured gate and hostel processes.
A meaningful night check
At 9:30 pm, approved leave and approved late entry stay separate from unexplained absence.
Explore the workflow · Interactive examples with sample data
Want to see the full leave journey end-to-end?
From student request to parent notification — 6 steps, 30 seconds.
Complete leave journey
Two tracks. One complete record.
The approval track and the movement track run in parallel. Approval enables departure — the connection is shown below. Choose a return scenario to animate the full journey.
Approval track
Student → ApproversStudent submits leave request
Resident App
Parent approves on WhatsApp
WhatsApp
Warden approves leave
Admin App
Leave approved — gate notified
System
Approval unlocks gate exit — movement track begins here
Movement track
Returns as expectedStudent exits at gate
Gate · QR scan
Student away — on leave
Movement record
Student returns — re-entry recorded
Gate · QR scan
Leave closed — record complete
System
Returns as expected
Student exits, stays away, returns on time. Gate records re-entry. Leave closed.
Notifications by role
What each person sees in this scenario
The same leave event surfaces different information to the student, warden, and security team. Switch scenarios above to see how each view changes.
Student
Resident App
Leave approved. Gate pass active. Return recorded.
Warden
Admin App
Priya S. — on approved leave. Expected return: Sunday 8 PM. ✓ Returned.
Security
Gate App
Priya S. — approved leave. QR scan at exit and return. No action needed.
Parent involvement
Parents receive a WhatsApp notification at the configured approval stage — no app download required. They approve or decline directly in the chat. If the student's return is overdue, parents are notified automatically alongside the warden.
Configured for your campus
Start with your university’s rules.
Agree the scope with the people who own the work. Fretbox supports configuration, role-specific training and adoption.
See implementation & supportBring these to the discussion
- Permission types, approval routes and parent involvement
- Hostel reporting times and late-entry rules
- Gate devices, return records and follow-up owners
Are approved leave and late entry counted as unexplained absence?
No. Approved leave, approved late entry and students who have not reported are separate statuses. This gives wardens and security a clearer basis for follow-up.
The next connection
Continue across the campus operation.
From an example to your campus
Let’s walk through your student movement.
Bring the workflow, the teams involved and your existing systems.