Decide with context
Review leave, day-out and late-night requests through your university’s approval route.
See permissions & movement
For Warden / Hostel Teams
Review leave requests, follow up on assigned repairs and check which residents have returned or need a follow-up.
Built around your responsibility
Review leave, day-out and late-night requests through your university’s approval route.
See permissions & movementFollow student complaints, responsible service teams and recorded progress.
Follow a concern to its teamSeparate recorded returns, approved absences and residents needing follow-up.
Explore gate & return recordsYour role in action · illustrative example
LEAVE-01 · parent approved where required
Review the request and record the warden’s decision.
Decision recorded → student and gate informedRoom 214 · leaking tap · maintenance assigned
Check progress with the service team and keep the resident updated.
Repair update → resident receives contextNight review · sample 9:30 PM
Check permission and movement records with security.
Return recorded → night review updatedIllustrative workload and sample counts. Optional parent approval follows university rules. A permission does not itself record an exit or return.
The people behind the operation

Students or staff submit visitor details in the app before arrival.
Security records details and asks whom to meet. The student or staff host gets an app alert to approve or deny entry.
The gate team follows the host’s action and the university’s visitor process.
A university-controlled setting
Apply campus-defined permission rules and optional parent involvement.
Use your university’s timings and movement records to guide follow-up.
Keep hostel staff, maintenance and security responsible for their own actions.
Mr. Ramveer Singh
Warden
The people around your role
From your priorities to your campus
A personalised 30-minute walkthrough with your team.