Databus Logo
Blog Login →
NCPCR + CBSE Circular 24/2023 + POCSO + JJ Act + DPDP compliant

Hostel Management System for Indian Boarding Schools

It's 9:47 PM. Headcount: 479 of 480. Paper register has no answers about the missing boarder.

Residential operations layer for Indian boarding schools. Digital Gate Pass with OTP parental consent + biometric nightly headcount with 90-second missing-student alert + RMO-integrated infirmary + pastoral care safeguarding.

Built around NCPCR Regulatory Guidelines for Hostels + CBSE Circular 24/2023 + POCSO Act 2012 + JJ Act 2015 Sections 41-42 + DPDP Act 2023. Used by 500+ Indian schools.

90 sec
Missing-student alert
CBSE 2023
Circular 24 compliant
NCPCR
Hostel guidelines ready
POCSO
Safeguarding workflow

Four high-liability gaps in paper-based hostel operations

Where In Loco Parentis breaks down in Indian boarding schools.

📝

Forged paper out-pass

Senior boarder copies the warden's signature from last weekend's pass. Gate guard sees a paper slip, opens the gate. No verifiable parental consent. Student is off campus. School has no legal defence if anything happens — and no record of who let them out.

🌙

The 47-minute headcount

9:45 PM roll call across 6 dormitory wings. Warden walks each wing with the register. By the time the count reaches 479 of 480 — at roughly 10:34 PM — 47 minutes of head-start window has elapsed before anyone realises a boarder is missing. The search starts cold.

💊

2 AM medical mystery

Boarder wakes at 2 AM with abdominal pain. RMO arrives. No accessible medical history — the file is locked in the admin office. Parent unreachable. Allergies unknown. The decision to medicate or refer to hospital is made under guesswork instead of data.

🍽️

Friday-night food waste

Long weekend approaches. 87 boarders going home; 393 staying. Head Chef cooks for 480 because nobody told them. Friday dinner: 87 untouched plates. Saturday lunch: another 87. Annual food waste from this single pattern alone: substantial — and invisible to the Director until the audit.

Six regulatory frameworks · One operational layer

The compliance frameworks Indian boarding schools must operate under.

The original CBSE 2017 directive made it explicit: "the onus for safety and security of children in school campus shall solely lie upon the school authorities." SchoolDeck builds the operational layer that makes compliance with these frameworks actually achievable.

Primary hostel framework

NCPCR Regulatory Guidelines for Hostels of Educational Institutions for Children

National Commission for Protection of Child Rights — formal regulatory framework specifically governing hostel operations in Indian educational institutions. Covers allocation, headcount, medical, pastoral, visitor management.

CBSE-specific

CBSE Circular 24/2023 dated 01.09.2023

Guidelines for Residential Schools and Schools with Hostel Facilities — RMO presence on campus + qualified hospital staff backup, robust visitor management system, quarterly water tank purity checks, fire extinguishers + smoke alarms, Type 1 + Type 2 safety drills, washrooms within campus buildings.

Child safeguarding

POCSO Act 2012

Protection of Children from Sexual Offences Act — applies to all child-care institutions including residential schools. Compliant safeguarding incident reporting workflow with restricted visibility (Safeguarding Officer + Principal only) and immediate timestamped audit trail.

Child care institution

JJ Act 2015 Sections 41-42

Juvenile Justice (Care and Protection of Children) Act 2015 — Child Care Institution registration framework. Residential schools serving as CCIs must maintain documented registration. Records retention + child protection officer designation supported in the platform.

Disaster management

NDMA School Safety Policy 2016

National Disaster Management Authority — emergency protocol activation workflows for fire, earthquake, flood, lockdown, medical emergency. Pre-defined escalation chains with role-specific notifications.

Data protection

DPDP Act 2023

Digital Personal Data Protection Act — children under 18 require verifiable parental consent for personal data processing. OTP-based consent workflow for outings, medical disclosures, and Local Guardian registrations. Full Phase III readiness for May 13, 2027.

References: NCPCR Regulatory Guidelines for Hostels (ncpcr.gov.in). CBSE Circular 24/2023 dated 01.09.2023 (saras.cbse.gov.in). NCPCR Manual on Safety and Security of Children in Schools 2021 distributed via CBSE Circular 01/2022 dated 05.01.2022. NDMA Guidelines on School Safety Policy 2016. POCSO Act 2012 (Ministry of Women and Child Development). Juvenile Justice (Care and Protection of Children) Act 2015. Digital Personal Data Protection Act 2023.

"I am the Chief Warden and Director of Residential Life at a fully-residential CBSE school in Coorg — 480 boarders, no day scholars, a hill-station campus with three dormitory blocks and patchy 4G between buildings. My job is the same job that has existed at boarding schools for 200 years: keep 480 other people's children safe through the night. The headcount used to be the moment I dreaded each day. Forty-seven minutes across three buildings, hand-tallied. If a boarder was missing, that's 47 minutes of head-start before I even knew to start looking. With SchoolDeck's Warden App and the dormitory biometric terminals, the count completes in under 4 minutes — and the system tells me where the missing boarder's last gate scan and last meal RFID tap were. The first time it surfaced a missing senior who had simply gone to the library after dinner, we found him in 90 seconds instead of 90 minutes. The Digital Gate Pass replaced a paper system I had stopped trusting years ago — too many forged signatures, too many parents claiming they never approved something the boarder said they did. Now every outing has the parent's SMS OTP timestamp in the audit log. When a parent disputed an outing last term, I showed them the OTP they had sent themselves, from their own phone, at 14:22 on the Friday. The dispute ended in 3 minutes. And the offline mode is not a marketing line for us — the Coorg-Mysuru highway loses 4G regularly, which means our boarders' Saturday outings happen partially offline. The Warden App caches everything and syncs when we're back online. That's the line between a system that works in Bangalore and a system that works in Coorg."
A
Mr. Anand Krishnamurthy
Chief Warden & Director of Residential Life · Fully-Residential CBSE School, Coorg, Karnataka · 480 boarders · 3 dormitory blocks · Migrated July 2024

Hostel management = residential layer that takes over from 3 PM onwards

Regular school ERP modules — fees, attendance, exams — handle the 8 AM-3 PM day-school workflow. Hostel management handles everything else: nights, weekends, full residential calendar, school holidays when boarders remain on campus.

The legal stakes are different. The doctrine of In Loco Parentis — the school acting "in the place of a parent" — places total legal and moral responsibility on the school for the boarding student's safety, well-being, nutrition, and medical care 24/7. The 2017 CBSE directive made this explicit: "the onus for safety and security of children in school campus shall solely lie upon the school authorities."

Paper registers and verbal permissions cannot meet that standard. SchoolDeck's hostel module is built specifically around the verified Indian regulatory framework — NCPCR Regulatory Guidelines for Hostels of Educational Institutions for Children, CBSE Circular 24/2023, POCSO Act 2012, JJ Act 2015 Sections 41-42, NDMA School Safety Policy 2016, and DPDP Act 2023.

Digital Gate Pass with OTP parental consent — the four-step verifiable workflow

The traditional paper "Out-Pass" is the single most exploited security gap in Indian boarding schools. Forged signatures, backdated slips, students copying last weekend's pass — the gate guard sees a paper, opens the gate, no audit trail.

The digital workflow has four mandatory steps:

  1. Request: Student submits outing request via the Student App or campus kiosk — destination, accompanying person (parent or pre-verified Local Guardian), planned exit time, planned return time.
  2. OTP parental consent: System sends push notification to parent through the Parent App. Parent approves with a 6-digit SMS OTP — meeting DPDP Act 2023 standard for verifiable parental consent before processing child personal data.
  3. Warden authorization: Chief Warden or duty Housemaster reviews the parent-approved request against hostel rules (academic standing, prior demerits, curfew limits) and authorizes or denies.
  4. QR-based gate execution: On authorization, system generates a secure QR code valid only for the approved time window. Security personnel scan the QR at gate exit and return — exact timestamps logged, parent notified of both events.

Late-return alert escalation: If the student does not return by the planned time plus a configurable grace period (typically 30 minutes), the system automatically triggers: Warden notification → Chief Warden after 15 minutes → Campus Security + Parent + Local Guardian after 30 minutes. No student goes "unaccounted for" silently.

Biometric nightly headcount — from 47 minutes to under 4

The nightly 9:45 PM roll call across multiple dormitory wings is the operational moment with the highest residential-school liability. A manual headcount across three wings typically takes 45-90 minutes — meaning if a boarder is missing, the search starts with that much of a head-start window already gone.

Two supported modes:

  • Mobile App mode: Warden walks through the dormitory wing with a tablet running the Warden App, checks off students by name, students confirm presence via fingerprint touch or face capture on the Warden's device. Offline mode caches all check-ins locally if connectivity drops, syncs automatically on reconnect.
  • Biometric Terminal mode: Wall-mounted biometric devices at dormitory entry points; students present finger or face within the configured headcount window.

Cross-referenced missing-student alert: System cross-references all roll-call modes. If a student is missing across all methods, alert escalates within 90 seconds to Chief Warden's phone + Campus Security + Resident Medical Officer (in case the student is unwell in another wing). Last known location is surfaced automatically — last gate scan timestamp, last meal RFID tap, last app activity, last dormitory biometric — to assist the search. The first 90 seconds of a missing-student incident become productive search time instead of compilation time.

Room and bed allocation — constraint-based matching

Manual room allocation at the start of the academic year is notoriously chaotic. The visual dashboard maps the entire residential infrastructure — every building, floor, room, bed — with real-time occupancy.

Allocation constraint rules:

  • Age/grade separation: Junior boarders not placed in senior dormitories without explicit warden approval.
  • Medical needs floor placement: Students with mobility issues, asthma triggers (no top floor), or specific medical needs automatically routed to appropriate floor.
  • Roommate compatibility: System suggests roommate matches based on age, grade, and parent-disclosed preferences (e.g., sleep schedule, religious practice considerations). Reduces mid-year reallocation requests.
  • Asset mapping to student: Specific room furniture (Bed No. 4, Study Desk B) mapped directly to student ID. When a boarder breaks a study lamp, the cost flows to that student's fee ledger automatically without dispute.
  • Mid-term conversion: When a day-scholar converts to boarder mid-term, the system automatically calculates prorated boarding fees and generates the new invoice — no manual reconciliation by the accountant.

Mess management — operationally distinct from the day-school canteen

Mess vs Canteen — distinct workflows. The day-school canteen module handles snacks, lunch, and tuck shop for day scholars with individual transactions, FSSAI HFSS compliance, and Green/Yellow/Red color-coded menu. The residential mess (this section) handles three compulsory daily meals + full board nutrition + meal forecasting from out-pass data — different operational reality.

The hostel mess is a large-scale operation. Cooking for 480 boarders when 87 have gone home for a long weekend results in significant food waste — and the operational reality is that the kitchen often doesn't know who is on campus until 30 minutes before serving.

Mess attendance forecasting: Because the system tracks every approved out-pass through the Digital Gate Pass workflow, the Head Chef sees the exact on-campus count for the next meal. "Saturday dinner head count: 393. Forty-seven boarders are pre-approved out till Sunday evening. Forty more have applied for day-trip leave pending warden approval." The kitchen can plan precisely.

Pay-Per-Meal model: RFID taps at the dining hall entry record exact meal attendance per student. Schools can transition from a flat term fee to a Pay-Per-Meal consumption model with exact billing — a particularly useful option for schools where boarders frequently skip meals for off-campus weekend stays.

Allergen alerts at the POS: The mess module integrates with each student's medical profile. If a student with a documented nut allergy taps their card for a dessert containing peanuts, the POS terminal flashes a red warning to the serving staff before the meal is plated — preventing a medical emergency before it begins.

Infirmary module — RMO workflow per CBSE Circular 24/2023

CBSE Circular 24/2023 requires Resident Medical Officer (RMO) presence on campus with qualified hospital staff backup for emergencies (Clause xiv-xv). The Infirmary module digitizes the campus clinic and makes the RMO workflow operationally consistent.

Complete medical profile per boarding student — established at admission, updated by the RMO:

  • Blood group, allergies (food / drug / environmental), chronic conditions, ongoing medication.
  • Vaccination history with reminder triggers for boosters.
  • Prior hospitalizations and known reactions to specific medications.
  • Family doctor contact and preferred hospital for referrals.
  • Parent + Local Guardian + Trust Treasurer contacts for medical decisions.

Dispensed medication log: Every paracetamol or other medication dispensed by the RMO or nurse is logged against the student — complete medication history available if the student needs external hospital referral.

Quarantine workflow: If a student needs isolation (suspected contagious illness), the system blocks the dormitory return and routes the student to a designated quarantine room. Parents notified immediately. Emergency hospital referral: for cases requiring external hospital visit, parent + Local Guardian + Trust Treasurer (for hospital billing authorization) all notified simultaneously through the Parent App + SMS + voice call escalation.

Pastoral care + POCSO Act safeguarding — two systems, deliberately separate

Residential schools shape character alongside academics. The pastoral care framework operates two deliberately separate workflows:

(1) Safeguarding incident reporting (POCSO Act 2012 compliant): Visible only to the designated Safeguarding Officer and Principal — not to general Wardens or Housemasters. Any student, staff member, or parent can submit a safeguarding concern through the app. Reports are immediately timestamped, encrypted, and routed to the Safeguarding Officer who follows the school's POCSO-compliant response protocol. The restricted visibility is the design — most safeguarding incidents involve trusted adults.

(2) Discipline Record + Pastoral Tracking: Visible to Housemasters, Chief Warden, and the school counsellor. Housemasters log positive reinforcements (helped junior with homework, won inter-house event) and demerits (missed study hour, attitude issue, curfew breach). The system flags behavioral patterns to the school counsellor — a normally cheerful boarder who suddenly accumulates multiple demerits + missed classes + reduced mess attendance triggers a counsellor notification. Identifies potential mental health struggle before it escalates.

The deliberately separate visibility levels are critical — safeguarding workflows must never be visible to the general staff cohort, while pastoral observations need to flow to the counsellor for proactive intervention.

Cashless Campus + laundry tracking

Digital Pocket Money Wallet: Parents transfer funds via UPI to the student's wallet (subject to the school's per-student monthly spending cap, configurable by the Trust). Student uses RFID card or biometric for tuck shop, laundry add-ons, extra meals. Every transaction logged with timestamp + terminal + amount — parent sees spending history in their app. Eliminates physical cash on campus (a safety vector) and gives parents financial visibility. Wallet refunds at year-end or withdrawal processed back to parent UPI through Fee Management standard refund workflow.

Laundry Tracking: Each student gets a unique laundry ID. Weekly laundry collection logged piece-by-piece; return from vendor verified against the digital log. Eliminates "missing uniform" disputes — every garment accounted for.

Native integration with other SchoolDeck modules

The hostel module is not a standalone app. It's wired into the broader SchoolDeck ERP — eliminating the duplicate data entry that plagues schools running separate boarding software:

  • Fee Management — room damages, mess Pay-Per-Meal charges, mid-term boarder conversion prorated invoicing all flow to the student's fee ledger automatically. No manual reconciliation.
  • Canteen Management — distinct workflow for day-school canteen, but shared student database and dietary profile. Cross-cluster, not duplicated.
  • Communication Tool — Parent App OTP consent, WhatsApp Business API notifications (TRAI DLT compliant), SMS escalation for emergencies. The hostel module triggers messages; communication-tool delivers them.
  • Visitor Management — when shipped, will handle visitor entry (parents visiting boarders, vendor entry) which is the opposite direction of gate traffic from outings. Different workflow, shared gate device.
  • Inventory Management — when shipped, will handle infirmary medicine stock + hostel furniture inventory + cleaning supplies. The hostel module owns medical-record workflow; inventory module will own stock-tracking workflow.

Paper registers vs SchoolDeck Hostel Management

Operational area Paper registers SchoolDeck Hostel ERP
Student outings Paper out-pass; forgeable signatures Digital QR + OTP parent consent + Warden auth
Nightly headcount 45-90 minutes across wings Under 4 min + 90-sec missing alert
Missing student response Cold search after ~1 hr delay Last gate scan + RFID + app activity surfaced
Mess attendance Cook for 480 when 87 are away Live count from out-pass + meal RSVP
Allergen safety Verbal warning if mess staff remember Red POS alert at the serving station
Medical history access File in admin office, locked at 2 AM Instant RMO access from anywhere
POCSO safeguarding Verbal reports lost or mishandled Restricted-visibility encrypted reporting
Behavioral pattern detection Counsellor sees only escalated cases Pattern flagging before escalation
Local Guardian verification Gate guard relies on memory Photo + ID on gate guard device
Cash on campus Physical cash = safety vector Cashless Wallet (UPI top-up + RFID spend)
Offline operation Connectivity loss = chaos Offline mode for safety-critical workflows

Frequently asked questions

What Chief Wardens and Directors of Residential Life ask first.

What is a hostel management system and how is it different from a regular school ERP?

+

A hostel management system is the residential operations layer — it takes over from 3 PM (when the day-school day ends) and runs through the night, weekend, and full residential calendar. Regular school ERP handles 8 AM-3 PM (attendance, fees, exams). Hostel management handles: room and bed allocation across dormitory wings, daily mess attendance and meal forecasting, Digital Gate Pass workflow for outings with OTP parental consent, nightly biometric headcount with missing-student alert escalation, campus Infirmary with RMO workflow, pastoral care and POCSO-compliant safeguarding logs, laundry tracking, Cashless Campus pocket money. Two layers share a unified student database — day-scholar converting to boarder mid-term requires no re-entry. Compliant with NCPCR Regulatory Guidelines for Hostels, CBSE Circular 24/2023, and JJ Act 2015 Sections 41-42 Child Care Institution framework.

How does SchoolDeck comply with NCPCR and CBSE 2023 boarding school guidelines?

+

Built around the verified regulatory framework for Indian residential schools. NCPCR Regulatory Guidelines for Hostels of Educational Institutions for Children — implemented across allocation, headcount, medical, pastoral, visitor workflows. CBSE Circular 24/2023 dated 01.09.2023 — robust visitor management requirement (via cross-link to /visitor-management/), RMO presence + qualified hospital staff backup (Infirmary module), quarterly water tank purity checks (maintenance log), fire extinguishers + smoke alarms (infrastructure register), Type 1 evacuation + Type 2 terror attack safety drills (drill scheduler). POCSO Act 2012 — restricted-visibility safeguarding workflow. JJ Act 2015 Sections 41-42 — Child Care Institution registration documentation. DPDP Act 2023 — OTP-based verifiable parental consent for child data. NDMA School Safety Policy 2016 — emergency protocol activation.

How does the Digital Gate Pass with OTP parental consent work?

+

Four-step verifiable workflow replacing forgeable paper slips. (1) Student request: outing request via Student App or kiosk — destination, accompanying person, planned exit + return times. (2) OTP parental consent: parent receives push notification on Parent App, approves with 6-digit SMS OTP — meets DPDP Act 2023 verifiable parental consent standard. (3) Warden authorization: Chief Warden reviews against academic standing, demerits, curfew — authorizes or denies. (4) QR gate execution: secure QR valid only for approved window. Security scans at exit + return, exact timestamps logged, parent notified of both. Late-return alert escalation: Warden → Chief Warden after 15 min → Campus Security + Parent + Local Guardian after 30 min. No paper. No silent unaccounted-for students.

How is hostel mess management different from the day-school canteen module?

+

Operationally distinct. /canteen-management/ (day-school canteen) = snacks + lunch + tuck shop with individual transactions, FSSAI HFSS compliance, Green/Yellow/Red color-coded healthy menu. Hostel mess (this page) = three compulsory daily meals + full board nutrition + meal forecasting from out-pass data. The hostel mess specifically owns: mess attendance forecasting (Head Chef sees exact on-campus count for next meal based on out-pass approvals), Pay-Per-Meal model with RFID taps (vs flat term fee), allergen alerts at mess POS for dietary-restricted students, special meal handling for fasting / religious requirements, rotational menu planning with nutritionist sign-off. Linked through unified student database but operate as distinct modules with own workflows.

How does the nightly biometric headcount and missing-student escalation work?

+

Two supported modes. Mobile App: Warden walks dormitory wing with tablet running Warden App, checks off students by name, students confirm presence via fingerprint or face capture. Offline mode caches data locally if connectivity drops, syncs on reconnect. Biometric terminal: wall-mounted devices at dormitory entry; students present finger or face within headcount window. System cross-references modes — if missing across all methods, alert escalates within 90 seconds to Chief Warden + Campus Security + Resident Medical Officer (in case student is unwell in another wing). Last known location surfaced automatically — last gate scan, last meal RFID tap, last app activity — to assist search. Manual 9 PM roll call historically took 45-90 minutes across multiple wings.

How does the campus Infirmary with Resident Medical Officer (RMO) workflow operate?

+

CBSE Circular 24/2023 requires RMO presence on campus + qualified hospital staff backup. The Infirmary module digitizes the campus clinic. Every boarder has a complete medical profile maintained at admission and updated by RMO: blood group, allergies (food/drug/environmental), chronic conditions, ongoing medication, vaccination history, prior hospitalizations, family doctor contact, preferred hospital. Nurses and RMO log every consultation — symptoms, diagnosis, prescribed medication, vital signs. Every paracetamol or other medication dispensed is logged against the student — complete history available if external hospital referral needed. Quarantine: system blocks dormitory return, notifies parents. Emergency referral: parent + Local Guardian + Trust Treasurer all notified simultaneously.

How does pastoral care work with POCSO Act safeguarding requirements?

+

Two deliberately separate workflows. Safeguarding incident reporting (POCSO 2012): visible ONLY to designated Safeguarding Officer + Principal — not general Wardens or Housemasters. Any student, staff, or parent can submit a safeguarding concern through the app. Reports timestamped, encrypted, routed to Safeguarding Officer following POCSO-compliant response protocol. The restricted visibility is the design — most safeguarding incidents involve trusted adults. Discipline Record + Pastoral Tracking: visible to Housemasters + Chief Warden + counsellor. Routine positive reinforcements + demerits. System flags behavioral patterns to counsellor — a normally cheerful boarder accumulating multiple demerits + missed classes + reduced mess attendance triggers counsellor notification before escalation.

What happens if the internet goes down during headcount or gate operations?

+

Offline mode built into every safety-critical workflow. Warden App: downloads roster at start of shift, full headcount completion offline, caches biometric/check-off data locally, syncs when connectivity returns. Gate scanner: caches QR validity for next 12 hours of pre-approved outings — guards validate against cached approval list, log timestamps locally, sync on reconnect. Critical alert escalation falls back to SMS over GSM if data unavailable. RMO emergency protocol works fully offline. Periodic offline-mode testing during deployment + standard handover checklist. For low-connectivity areas (hill stations, rural campuses) — Coorg, Kodaikanal, Mussoorie regularly operate offline for headcount.

How does the system handle authorised Local Guardians for outings?

+

At admission, parents register up to 3 Local Guardians per student — typically close relatives in same city as school. For each: full name, relationship, photo, government photo ID (Aadhaar masked except last 4 digits per DPDP Act), contact, address. All guardians verified by admission office before activation. When student requests outing accompanied by Local Guardian, parent selects from registered list during OTP approval. At gate exit: security guard sees guardian's photo + ID on device, verifies physical person picking up matches photo, only then opens gate. If person doesn't match any registered guardian or parent, gate guard cannot release student — must call Chief Warden for exception process requiring additional verbal verification with parent.

Can parents pre-load pocket money for students to use on campus?

+

Yes — Cashless Campus bundled with hostel module. Parents transfer funds via UPI to student's Digital Pocket Money Wallet (subject to school's per-student monthly spending cap, configurable by Trust). Student uses RFID card or biometric for tuck shop, laundry add-ons, extra meals. Every transaction logged with timestamp, terminal location, amount — parent sees spending history in app. Eliminates physical cash on campus (a safety vector) and gives parents financial visibility. Wallet refunds at year-end or withdrawal processed back to parent UPI account through Fee Management standard refund workflow.

What does deployment look like for a residential school?

+

21-28 working days for fully-residential school (longer than day-school 7-10 days because of additional residential modules + biometric hardware integration). Includes: dormitory layout digitization (every building, floor, room, bed); existing student-to-room allocation migration; Local Guardian database upload; medical profile data entry by RMO; staff RBAC setup (Chief Warden / Housemaster / RMO / Mess Manager / Safeguarding Officer); biometric terminal installation at dormitory entry (typically 1 per wing); gate guard device provisioning; Mess POS RFID terminal setup at dining hall entry; parent app onboarding before first outing cycle; offline-mode testing across safety-critical workflows; first month parallel run with existing paper systems before full cutover. Pricing: bundled within standard SchoolDeck plan at ₹30 per student per month. One-time setup fee for biometric + POS hardware procurement and installation.

Connected modules

Hostel module integrates with — not duplicates — these SchoolDeck modules.

For Indian Chief Wardens, Directors of Residential Life & Boarding School Trustees

Close the 47-minute headcount window. Replace forgeable paper out-passes. Sleep at night.

NCPCR + CBSE Circular 24/2023 + POCSO Act + JJ Act + DPDP Act compliant. Digital Gate Pass + biometric headcount + RMO infirmary + pastoral care safeguarding. Offline mode for low-connectivity campuses.

From ₹30/student/month · 500+ Indian schools · Residential deployment 21-28 days