Every bed, branch and invoice — one system.

• Lead capture, CRM follow-ups and a visit / appointment calendar
• Applications with city & branch preference, move-in date, accommodation category, academic or professional details, guardian and emergency contacts
• KYC and identity documents with a verification workflow; nationality-aware document requirements
• Policy acknowledgement captured with audit evidence
• Cross-branch blacklist and person alerts with reason and history — alerts are lifted, never silently deleted
• Permanent resident identity across branches and re-admissions
• Full lifecycle: apply → decide → waitlist and/or bed offer → reservation → check-in → stay → transfer / notice to vacate → checkout clearance

• Interest vs qualified waitlist, with preferences for branch, room category, bed type, AC, budget and move-in window
• Contact logging, priority, expiry, and withdraw / fulfil reasons
• Refundable waitlist deposits — held deposits refund or apply toward admission; no ‘forfeited’ status abuse
• Official bed offers act as soft-holds, with at most one active official hold per bed
• Matching suggestions surface candidates; management makes the decision

The waitlist never auto-reserves a bed.

• Reservations with payment gates and real-time bed revalidation
• Check-in checklist: KYC verified, payment verified, rules acknowledged, asset handover with damage notes, photos and signature
• Physical occupancy periods with overlap protection — no double occupancy of the same bed
• Bed blocks and maintenance holds that feed availability
• Transfers, including cross-branch, with approval and price-change rules
• Temporary bed release windows (weekend / seasonal) with handover and early return
• Short-stay bookings inside release windows; seat-retention billing vs continue-rent modes
• Resident revenue sharing / release incentives from eligible short-stay income (configurable %)
• Checkout clearance — keys, dues, deposits and assets — before a resident is ‘cleared’

Physical presence and gate movement are not occupancy.

• Price rules vs pricing agreements — the agreed price is snapshotted at acceptance
• Invoices become immutable once posted; balances are derived from allocations, not an editable field
• Payments with multi-invoice allocation
• Security deposits: hold → settle; refunds blocked while dues are outstanding unless an authorised override is recorded
• Late fees, waivers and adjustments with reason and approval
• Petty cash and branch expense categorisation
• Seat-retention charges, short-stay accommodation charges, release incentives and financial adjustments
• Cash books and voucher discipline (CRV-style receipts where configured)
• Optional sync to external accounting / GL through an idempotent integration queue

Posted invoices can be adjusted with a trail — never quietly rewritten.

• Branch base rates, occupancy rules and room overrides — precedence: override → room rule → branch rule → base
• Meter readings, billing periods and resident allocation by occupancy days
• Vacant beds receive no allocation
• Appliance permission fees and standard units, separate from communal pool rules
• Negative communal pool exception workflow
• Branch utilities: meters, solar, generator and outages tracked as facility consumption

• Maintenance tickets, activities, inspections, preventive maintenance and vendor work
• Cluster store inventory on a stock ledger — quantity is the sum of movements, not a fragile cached number
• Requisitions → issues → branch receipt; purchase order and GRN flows
• Asset register with assignment history (branch / room / bed), warranty and condition
• Physical key custody for room, wardrobe and facility keys and property masters
• Keys issue at check-in and return at checkout; open key issuances block a ‘cleared’ checkout

• Gate IN / OUT movement events that never change a bed’s sellable state
• Leave requests, late entries and guest visits
• Configurable curfew and branch policy
• Incidents and conduct outcomes tied to resident status, with reasons

A resident walking out of the gate does not free their bed.

• Employees linked to login accounts
• Roles and permissions — Super Admin, City / Cluster / Branch managers, Warden, Finance, Front Desk, Technical, Auditor
• Management assignments by organisational scope (city / cluster / branch) with effective dates
• Shifts, tasks, checklists and performance hooks as configured

Branch staff cannot act outside the branches they are assigned to.

• Branch kitchens and cluster kitchens serving nearby hostels
• Mess enrolment linked to residents
• Menus and production planning surfaces for kitchen staff
• Cost ownership remains branch-specific even when the kitchen is shared

• Institutions, routes and trips
• Resident transport enrolment
• Trip operations for branch staff

• Landlord and lease records kept separate from branch operations
• Compliance tracking per property
• Effective-dated branch ↔ property assignment history

• Digital notices with acknowledgement tracking
• In-app notifications for staff actions
• Triggered operational messages along admissions, finance, maintenance and security paths
• Architecture ready for multi-channel delivery via email and WhatsApp-class providers

• Central configuration rules — waitlist days, offer expiry, notice periods, KYC rules — instead of hard-coded exceptions
• Approval matrix, requests and decisions
• Document and file metadata with secure object storage
• SOPs, policies, digital forms and policy acknowledgements
• Human-readable number sequences and business IDs, separate from system UUIDs
• Insert-only audit trail: who did what, in which session and module, with redacted payload
• Role-based access control, privacy and backup / continuity practices for enterprise buyers

• Branch dashboard for day-to-day operations
• Cluster, city and portfolio rollups for managers
• KPIs: occupancy, admissions funnel, receivables, maintenance, security, kitchen and transport as available
• Audit and session history screens for compliance reviewers

• Staff Admin (web) — the full operational console, mobile-responsive for staff on the floor
• Applicant Portal — apply, upload documents, track waitlist and respond to offers
• Resident Portal — stay details, invoices and dues, leave and guests (as enabled), notices, release requests
• Offline-friendly queue patterns for field operations where designed

• External integration registry and idempotent transaction queue
• External references stored alongside records — provider IDs never replace internal UUIDs
• Optional accounting, messaging and utility / monitoring connectors