Blocks, rooms and residents, with visitor rules, leave approval and meal plans, so the answer to "who is here" is not a headcount.
Book a demoA parent rings the warden at nine in the evening to ask whether their daughter signed back in. The register is a book in the office, the office is locked, and the answer involves walking the corridor.
Meanwhile room allocation is a wall chart, hostel fees are on a separate list from tuition, and a resident who moved room in October is still billed for the old one.
When residency is part of the student record, both questions answer themselves from wherever the warden is standing.
Grouped by the job it does rather than listed as one long set of features.
Room types with capacity and per-room charges, so allocation respects what a room actually is.
Allocating, shifting and vacating a resident, with the fee following the room rather than being edited separately.
Who is in the building, checkable from a phone at nine in the evening rather than from a book in a locked office.
Check-in against approved relatives and your own visiting rules, which is a safeguarding requirement rather than a convenience.
Requested, approved and recorded, so a resident who is away legitimately is not counted missing.
Plan assignment per resident and the numbers the kitchen needs, without a separate list.
Charged through the same fee structure as tuition, so a family gets one bill.
Items issued to a resident and returned on vacating, so losses are attributable.
Which rooms are full, which beds are free and what the block is costing.
The nine o'clock phone call. A parent asks whether their child signed back in. If the register is a book in an office, the honest answer is "let me go and look", which is not the answer a worried parent needs.
The resident who changed room. Moved in October, still billed for the old room, because the wall chart and the fee list are different documents.
The visitor nobody checked. Somebody signs in as an uncle. Without a record of approved relatives, there is no way to know whether that is true.
The approved outing counted as missing. A resident away with permission appears absent at the evening check, so the warden chases somebody who did the right thing.
These are the cases worth testing in a demo. Bring the messiest one you have.
The same records, presented differently depending on the job.
Allocates rooms, runs the evening check, approves leave and controls visitors, from wherever they are.
See their child's room and leave status, and request an outing rather than phoning.
Sees hostel charges as part of the family balance rather than as a separate list.
A visitor and residency record that can be produced when it is actually needed.
A resident is a student, so residency attaches to the record admissions created. A withdrawal vacates the room and closes the hostel charge without anybody remembering to.
Hostel fees bill through the same structure as tuition. Hostel attendance sits alongside daily attendance rather than in a separate book. Approved leave is the same leave the rest of the institution can see.
That is why the evening check and the fee ledger cannot disagree.
The parts of the institution this touches most.
The check, the visitor rules, the outing approvals. Those are what a warden judges a hostel module on.
Book a demo