Society Maintenance and Visitor Management Portal

Housing societies still run maintenance on WhatsApp groups and paper registers: a resident reports a leaking tap in a chat buried under two hundred messages, nobody tracks whether the plumber actually came, and the committee keeps no record of repeat complaints. At the gate, the security guard maintains a handwritten visitor register that is illegible, unsearchable and impossible to audit — a resident cannot pre-authorize a guest, and the committee cannot answer the simplest question: who is inside the society right now? Both problems share one root: no single system owns the society's operational data. This project builds that system — a web portal with two modules on one database. The maintenance module turns complaints into tickets with priorities, deadlines and statuses the committee can genuinely manage. The visitor module replaces the paper register with a guard console, resident pre-approvals and a write-once audit log. Together they give a society traceable maintenance and a verifiable gate.

1. A resident signs in and the session routes them to the resident dashboard, scoped to their flat number so every screen shows only their data.
2. For maintenance, the resident submits a ticket with category, priority and a description; the ticket lands in the committee queue with a deadline computed from its priority's SLA.
3. The committee reviews the queue, acts on the ticket and updates its status inline; the change is visible on the resident's dashboard immediately.
4. Before a guest arrives, the resident pre-approves them with a name, type and valid date; the approval appears live on the guard's console.
5. At the gate, the guard checks in a pre-approved visitor with one tap or logs a walk-in through the entry form; both paths write exactly one row to the write-once audit log with the entry time, and the exit time is marked when the visitor leaves.
6. The committee watches the SLA dashboard for breached tickets and the audit trail for gate activity; residents can read only their own flat's visitor rows.

Tech stack:

• PHP 8, Laravel (backend + routing)
• MySQL (relational data)
• Blade templates, Tailwind CSS (frontend)
• JavaScript (guard console interactivity)
• Laravel Sanctum (API/session authentication)
• Dompdf (receipt and report PDFs)
• Shared hosting deployment (PHP 8.1+, MySQL)

• [Multi-role access control] Three login roles — resident, security guard and committee admin — each with its own dashboard and menu. Every screen and action is scoped by role: a resident sees only their own flat's tickets, while the guard sees the full gate queue and the committee sees everything.
• [Maintenance ticket lifecycle] Residents raise tickets with a category, priority and description. Statuses move Open → In Progress → Resolved, and the committee updates them inline while the resident watches the progress on their own dashboard.
• [SLA tracking for the committee] Each priority carries a response deadline — 24 hours for high, 72 hours for medium, 7 days for low — and the admin dashboard flags breached tickets in red, so an overdue lift repair or leak never slips by silently.
• [Guard gate console] The guard logs visitor name, type, flat to visit, purpose and vehicle number in one form. Every entry writes a single row to the audit log with an entry timestamp, and exits are marked with one tap when the visitor leaves.
• [Resident pre-approval] Residents pre-approve guests and service visitors with a valid date, and the approval appears live on the guard's console. The approval stays in a pending list and only enters the gate log when the guard checks the visitor in — so no-shows never pollute the audit trail.
• [Write-once visitor audit log] Once written, a gate-log row cannot be edited or deleted by any role. The committee can review exactly who entered, when, for which flat and when they left — the register the paper book could never be.
• [Maintenance billing view] The resident dashboard shows the month's maintenance due, paid receipts and per-flat payment status, driven by the society's own billing rules (configurable).

Implemented in the base build: all features above. Optional on request: WhatsApp/SMS alerts for ticket updates and visitor arrivals, payment gateway for maintenance-dues collection, QR-based gate passes. Future scope: ANPR camera integration at the gate, intercom auto-dial to the flat.

• Complete portal source code (backend, frontend, database migrations)
• Seeded demo database with realistic society data
• Single-file working HTML demo for review and viva demonstration
• Setup and shared-hosting deployment guide
• Project report PDF (requirements, ER diagram, DFDs, test cases)
• PPT presentation for final review
• Viva Q&A preparation document (RBAC, sessions, audit-trail design, SLA logic)