Hostel Outpass Management Web App with Warden Approval and Parent Notification

The Hostel Outpass Management Web App replaces the paper outpass registers still used in most college hostels with a digital request-and-approval workflow. In the paper system a student writes an entry in the warden's register and the warden signs it — parents hear about the trip only if the student calls home, and nobody can see at a glance who is currently outside campus. That causes three real problems: wardens cannot count who is out or overdue, late returns go unnoticed until someone scans pages of entries, and disputes arise over claimed verbal permission. This web app routes every request through a logged state machine instead: the student applies online, the warden approves or rejects with one click, an SMS goes to the registered parent number on the decision, and a QR gate pass is generated only for approved trips so security can verify identity and log exit and entry at the gate.

The system moves an outpass through a fixed state machine — PENDING → APPROVED or REJECTED → ISSUED → RETURNED — with a parent SMS fired on every transition out of PENDING and the QR gate pass minted only at ISSUED. A builder note from the actual demo build shaped this: instead of editable status fields, each request keeps an append-only event log, so a warden's decision, the SMS receipt and the gate scans all accumulate as permanent history that cannot be rewritten. The demo front-end exposes four working views — the student request form, the warden approval dashboard, the parent SMS inbox with a notification log, and the outpass history with QR gate passes — and ships with 9 realistic seeded outpass requests across three hostel blocks, so every screen and state is explorable end to end. The end-to-end loop runs like this.

1. The student logs in and fills the outpass form — name, roll number, block and room, departure and expected return time, reason with details, and the parent/guardian mobile number.
2. The request enters PENDING and appears on the warden dashboard with the student's details and their past outpass record.
3. The warden clicks Approve, or Reject with a mandatory recorded reason.
4. The notification engine fires a templated SMS to the parent's registered number — both the approve and reject paths send — and logs the delivery receipt.
5. An approved request moves to ISSUED: a QR gate pass is generated with the request ID, student details and the valid out-to-return window.
6. Security scans the QR at the gate to log the exit; on return, a second scan marks the student RETURNED.
7. Requests past their return time with no check-in are flagged OVERDUE on the dashboard for warden follow-up.

Tech stack:

• PHP 8 · MySQL (backend and database)
• HTML5 · CSS3 · JavaScript (responsive front-end)
• Session-based role authentication (student · warden · security)
• QR code generation (server-side library)
• SMS gateway API (Twilio/MSG91, configurable)
• Apache shared hosting
• Mobile-first responsive UI
• Git (version control)

The three capabilities that carry this project are the warden approval dashboard (a live pending queue with per-student outpass history and one-click approve/reject), automatic parent SMS notification (a templated message fired on every decision, both approve and reject paths), and the QR digital gate pass (minted only for approved trips, scanned by security at the gate to log exit and return). Around them sit overdue auto-flagging, role-based access for students, wardens and the security desk, an append-only audit trail, and a searchable outpass history that replaces the paper register. A builder note from the actual demo build: the approval flow is implemented as an append-only event log — PENDING → APPROVED or REJECTED → ISSUED → RETURNED — where the QR gate pass is generated only at ISSUED and a parent SMS fires on every transition out of PENDING; statuses are never edited in place, so the audit trail cannot be rewritten after the fact.

• [Warden approval dashboard] A live queue of pending requests with each student's details and past outpass record; the warden approves or rejects with one click, and a rejection requires a recorded reason that the student and parent can see.
• [Parent SMS notification] A templated SMS is sent automatically to the registered guardian number on every decision — approvals and rejections both send — with per-message delivery receipts tracked in a notification log.
• [QR digital gate pass] Approved outpasses mint a QR pass carrying the request ID, student details and valid window; security scans it at the gate, logging the exit, and a second scan on return marks the student checked in.
• [Overdue auto-flagging] Students who have not checked in by their stated return time are flagged OVERDUE on the warden dashboard automatically, so late returns surface without manual register-scanning.
• [Role-based access] Separate student, warden and security-desk views behind session login; students see and manage only their own requests, and every role gets a distinct dashboard.
• [Append-only audit trail] Each request carries an event log — requested, decided, issued, returned — with timestamps; statuses are never edited in place, so the full history is tamper-evident for disputes.
• [Outpass history and register export] Searchable history by student, date or block, plus a printable weekly register export that replaces the paper book the warden currently maintains.

Implemented as listed above. Configurable: SMS gateway provider, warden review-SLA threshold, outpass categories and reason lists. Future scope (not included): mobile app, biometric gate check, integration with hostel fee records.

• Complete full-stack source code (PHP backend, MySQL schema, responsive front-end)
• Working single-file HTML demo prototype (the build shown in the screenshots)
• MySQL schema and seed-data script
• Project report PDF (background, methodology, architecture, screenshots)
• PPT presentation for final review
• Viva Q&A preparation document
• Deployment guide (shared hosting setup and SMS gateway configuration)