SkieWhat should a hostel warden or admin check every day and every week?
Each evening check the geofence and breach alerts and that night mode is on; each morning check which devices went quiet overnight and which are low on charge. Weekly, read the patterns for each block and the audit log. Keep it short and have a deputy for nights and weekends.
A hostel differs from a school: the devices sit with students around the clock, rules change at night, and the warden cares about who is where. The routine follows that shape.
Evening: before curfew, open the breach centre for the hostel group and the geofence page. Check that devices are inside the compound and that none is silent. Night mode switches to a smaller set of allowed apps overnight, with calls still allowed, so confirm the schedule has taken effect by looking at on latest policy. Windows may run overnight, and the first matching window wins, so check that no other window is overriding it.
Morning: look at which devices went quiet overnight and why. Low battery tells you who did not charge. A device that was out of its zone after curfew is a conversation, not a verdict, since an alert tells you a device moved and not why. Sync and resolve what has recovered, and follow up the rest.
Weekly: read Insights patterns for each block, starting with higher-confidence ones, and compare blocks with each other. Review the silent share if Wi-Fi is the only network, in case a corridor is weak. Look at the audit log for changes to schedules and geofences. Hostel Wi-Fi can be locked after setup so it is the only network; see create a Wi-Fi profile.
Let students and parents know what is tracked and who sees it. See hostel device management and night mode. Practical tip: write the steps for a missing student device, including who is called and when lost mode is used, and keep them where the night staff can find them.