Campus Operations

Hostel Management

Manage hostel buildings, blocks, rooms, beds, student allotments, checkouts, cancellations, history, and hostel reports.

Audience: Hostel wardens, admins, and permitted office staff
Last reviewed: September 2, 2026

Overview

Manage hostel buildings, blocks, rooms, beds, student allotments, checkouts, cancellations, history, and hostel reports.

Before you start

Hostel permissions assigned
Students active in the current school/session
Hostel, room, and bed setup completed before allotment

Main screens

Hostel Dashboard Hostels Blocks Rooms Beds Student Allotments Hostel Reports

Step-by-step workflows

Prepare hostel setup

Create hostel records.
Add blocks if your school uses blocks.
Create rooms under the correct hostel/block.
Create beds and define monthly fee only at the bed setup level when applicable.

Allot a student

Open Student Allotments.
Select the student, hostel, room, and available bed.
Confirm effective dates and status.
Save the allotment.
Use checkout or cancel actions only when the student leaves or the allotment was created incorrectly.

Operational detail

Permission requirements

Hostel setup, rooms, beds, allotments, checkout, cancellation, and reports are permission controlled.
Student allotment uses active student records and available bed status from the authenticated school.
Hostel fee information follows the approved boundary and does not directly alter fee module tables.

Hostel and block

Create the main hostel first. Use blocks only when the building structure needs another grouping level.

Room

Rooms belong to a hostel and optional block. Room capacity should match the number of beds configured.

Bed

Beds carry availability status and optional monthly fee. Monthly fee should not be repeated unnecessarily during allotment.

Allotment date

Use the effective start date for the student stay. Checkout or cancellation should record the real lifecycle change.

Student selection

Allot only active students from the school, and avoid duplicate active allotments for the same student.

Reports

Use occupancy, vacancy, and allotment history reports to review hostel utilization.

Validation and system feedback

Beds must be active and available before allotment.
A student should not have overlapping active hostel allotments.
Room, bed, hostel, and student relationships are validated on save.
Checkout and cancellation must use the allowed lifecycle action for the current allotment state.

Common mistakes to avoid

Repeating monthly fee entry in allotment instead of maintaining it on the bed.
Creating more beds than room capacity without reviewing setup.
Cancelling a valid past stay instead of checking it out.
Allotting inactive or wrong-session student records.

Safe use

Keep documentation and support privacy-safe

These guides explain normal user workflows only. Do not share passwords, OTPs, tokens, cookies, private student identifiers, payment details, raw internal IDs, provider configuration, or stack traces in support messages or screenshots.

Repeating monthly fee entry in allotment instead of maintaining it on the bed.
Creating more beds than room capacity without reviewing setup.
Cancelling a valid past stay instead of checking it out.
Allotting inactive or wrong-session student records.