Saturday · 5 PM–8 PM
Day-out permission
A short outing with a defined departure and expected return time.
Platform / Student Movement
Connect leave, day-out and late-night permissions with approvals, gate records and return follow-up.
- Configured approvals
- Recorded exit & return
- Evening reporting
Different plans. The right permission.
A day out. Time away. A later return.
Friday evening → Sunday evening
Leave permission
Time away from campus, with departure and return dates recorded.
Expected back · 10:30 PM
Late-night permission
A request to return later than the university’s usual reporting time.
Illustrative timings. Your university defines the available permissions and their rules.
One permission. Connected responsibilities.
From the request. To the recorded return.
Sending day-out request…
01Student requests
Dates, timing and the reason reach the university’s configured approval route.
University decision · Approved
02University decides
Parent consent via WhatsApp, when required.
Student update: day-out approved.Return by 8 PM · sample notification
Main-gate exit · 5 PM
03Departure recorded
Security checks the approved permission. The main-gate exit is recorded in this example.
Hostel reporting · 7:42 PM
04Return recorded
Campus return and hostel reporting are separate events, where your university records both.
Parent consent is included only when required. The university defines the approval order and decision-makers.
Illustrative journey · sample timesThe evening reporting picture
Permission gives context. Follow-up gets focus.
Approved leave and approved late entry remain separate from unexplained absence. Wardens can focus on the students whose reporting or return needs checking.
9:30 PM · sample evening reportHostel A · 1,200 residents · sample snapshot
Hostel reporting recorded1,080Hostel reporting recorded
Approved leave80Away under approved leave
Approved late entry25Permission covers a later return
Needs follow-up15Reporting or return needs checking
In the university’s view
Who returned. Who needs a check.
Permissions & movement recordsIllustrative product view · Saturday evening
| Student / hostel | Permission | Departed | Expected return | Hostel reporting | Status |
|---|---|---|---|---|---|
| Ananya S. · A-201 | Day-out | Sat · 5 PM | Sat · 8 PM | Sat · 7:42 PM | Returned |
| Rohan M. · B-104 | Weekend leave | Fri · 6 PM | Sun · 8 PM | — | Approved leave |
| Meera P. · A-305 | Late entry | Sat · 7 PM | Sat · 10:30 PM | — | Approved late entry |
| Arjun K. · B-202 | Day-out | Sat · 4 PM | Sat · 9 PM | Not recorded | Needs follow-up |
Who acts on a missing return?
Assigned warden reviews permission and reporting records → gate team checks the recorded return → responsible campus team follows up with the student under university procedure.
Illustrative staff response: establish the student's status, then complete the follow-up under your campus process.University-controlled setting
Before your campus connects. Three practical answers.
Who approves a request?
Your university defines the responsible approvers, permission types, timings and follow-up ownership.
Is parent consent mandatory?
Only when your university requires it. WhatsApp parent consent supports the configured university decision process.
Can existing gates connect?
Your IT team and FretBox review device compatibility and interfaces before rollout. Campus entry and hostel reporting follow your configured setup.
Connect the whole permission journey.
Explore the student experience, the connected teams and your university’s rules.