More project photos (3)
The problem
Hostel gate discipline is a daily operational problem. Students leave for the city, for home, for medical visits; wardens must know who is out, when they are expected back, and whether parents have consented to overnight stays. The paper-slip system fails on all three: slips get lost, signatures are forged or skipped, parents are never in the loop, and the gate guard keeps no reliable record of exits and entries. Late returns are noticed only when someone complains. This project builds GatePass, a hostel gate-pass management web app. A student files a request with pass type (day outing or overnight), dates, destination and reason. Day outings for students in good standing auto-approve per policy; overnight requests need parent confirmation via an SMS link before the warden can approve. Approval issues a QR-coded pass; the gate scans exits and entries; late returns trigger warnings and repeated violations block new passes until the warden clears them.
Submits outing requests and carries the QR pass to the gate.
Follow the working sequence
How it works
- The hostel office configures policy: gate hours, auto-approval rules, warning thresholds and the approval chain (floor in-charge, warden).
- A student submits a request with pass type, outing dates, expected return, destination and reason; the app checks standing and policy.
- Day outings for students in good standing auto-approve; overnight requests send the parent an SMS confirmation link first.
- Once the parent confirms, the request enters the warden's approval queue showing consent status; approval issues a QR-coded pass.
- At the gate, the guard scans the pass QR on exit and again on entry; the movement log records time, direction and gate per scan.
- Late returns trigger warning SMS to the student and parent automatically; repeated warnings block new pass requests until the warden clears them.
- The warden's dashboard shows pending approvals, approvals/rejections today, and the live count of students currently out.
Tech stack:
- HTML5 · CSS3 · vanilla JavaScript (ES6)
- Single-file front-end app (no build step)
- browser localStorage persistence
- QR-code rendering (client-side)
- Timeline/progress UI components
- Responsive CSS Grid/Flexbox layout
| Parameter | Value |
|---|---|
| App format | Single-file web app, runs offline after download (design) |
| Data storage | Browser localStorage; no server or install required for the demo |
| Seeded dataset | Approximately 20 passes, 14 pending approvals, gate log entries in the demo |
| Pass types | Day outing (auto-approved per policy), overnight (parent consent required) |
| Gate hours | 6 AM – 10 PM in the demo (configurable) |
| Warning rule | 3 warnings in a semester block new passes (configurable) |
| Multi-user | Single-user demo; roles shown as views; shared backend listed as extension |
Project features
- [Student request portal] Students file day-outing or overnight requests with dates, expected return time, destination and reason, with the parent contact on record shown for overnight consent.
- [Policy-driven auto-approval] Day outings for students in good standing auto-approve per configurable policy; overnight passes hold at parent confirmation before reaching the warden.
- [Parent consent via SMS link] Overnight requests send the parent an SMS confirmation link; the warden's approval unlocks only after the parent confirms — the consent chain is enforced, not assumed.
- [Warden approval queue] The warden sees pending requests oldest-first with student, type, outing window, reason and parent-consent status, with approve/reject decisions and mandatory rejection reasons.
- [QR-coded passes] Every approval generates a QR-coded pass the student carries; the gate scans it on exit and entry instead of trusting a paper slip.
- [Gate movement log] Exits and entries are logged by scan with time, pass number, direction and gate, giving the hostel a live count of students out and expected back.
- [Late-return enforcement] Late returns auto-trigger warning SMS to student and parent; three warnings in a semester block new passes until the warden clears them.
What is included
- Complete GatePass web app source code (single-file HTML/CSS/JS)
- Seeded demo dataset (students, passes, approval queue, gate log)
- Project report PDF (background, approval workflow, policy model, methodology, screenshots)
- PPT presentation for final review
- Viva Q&A preparation document
- User manual (student, warden and gate roles)
- Installation/deployment guide
Limitations & prerequisites
- The demo models the SMS and QR scan flows in-app; real SMS delivery needs a configured SMS gateway service, and real gate scanning needs a scanner or phone.
- Auto-approval policies and warning thresholds are demo configuration — the buying hostel sets its own rules.
- The demo runs single-user with browser storage; a live hostel deployment needs a shared backend (future scope).
- Parent phone numbers are demo data; real deployment must handle consent and data-privacy norms for student records.
- The system records what is scanned — it cannot physically stop a student who walks past the gate without scanning.
Frequently Asked Questions
How does the parent consent step work?
Overnight requests cannot reach the warden until the parent confirms. The app models this as an SMS confirmation link sent to the parent contact on record; the request shows an awaiting state, and the warden's approve action unlocks only after confirmation is recorded. Day outings skip this step per policy.
What stops a student from reusing an old pass?
Each approved pass carries a unique pass number and outing window; the gate log records every scan with timestamp and direction. A pass outside its window or already closed shows as invalid at scan time, so yesterday's slip does not work today.
How are late returns handled?
Return times are compared against the expected return on the pass. A late entry triggers a warning SMS to the student and the parent automatically, and the warning count is tracked per semester. At three warnings, new pass requests are blocked until the warden clears the record.
Why two approver levels — floor in-charge and warden?
It mirrors how hostels actually work: the floor in-charge verifies the routine day outing, while the warden handles overnights and exceptions. The demo shows the request tracker moving through submitted, floor in-charge and gate-scan stages so the student always knows where their request stands.
Is this project suitable for a final-year project?
Yes — for Computer Science, IT and Web Development programs. It models a multi-role approval workflow, policy-driven automation, QR pass generation, gate-side scanning logic and an enforcement rule engine, all mapped to a real hostel operation. Suitable for B.E./B.Tech final-year projects in Computer Science, IT and Web Development.
Components & software requirements
- HTML5 · CSS3 · vanilla JavaScript (ES6)
- Single-file front-end app (no build step)
- browser localStorage persistence
- QR-code rendering (client-side)
- Timeline/progress UI components
- Responsive CSS Grid/Flexbox layout
Delivery information
Built-to-order project. Delivery timeline is shared after order confirmation based on current queue.
Support terms
Complete documentation, setup guide, and viva preparation included. Support for setup and explanation provided.
Download free synopsis (PDF)
Enter your name and WhatsApp number — the synopsis PDF downloads immediately. We may send occasional project updates on WhatsApp; no spam.