Society Hall Booking Web App with Availability Calendar and Payment Records

Most housing societies still manage their community hall with a paper register kept by a committee member, backed up by scattered WhatsApp messages. Nobody can see at a glance whether next Saturday is free, clashes surface only when two residents turn up with claims, and money collected — cash, UPI, cheques — gets noted in loose sheets that go missing by year-end. Residents must call or message someone just to check availability, and the committee has no clean record of who paid and for which event.

This web app moves the process online. A month-view availability calendar shows every date as available, partially booked, fully booked or under review. Residents pick a date and a slot (morning, afternoon, evening or full day), see the charges upfront, and send a booking request. The managing committee approves or rejects each request; approval locks the slot so the same date-slot cannot be approved twice. Payments collected outside the system are recorded against each confirmed booking with a receipt number, so the society always knows what is paid and what is still due.

1. The resident opens the portal and views the month calendar, where each date is colour-coded by availability and past dates are disabled.
2. Clicking a date shows its four slots with the applicable member or outsider price; booked slots are greyed out and cannot be selected.
3. The resident fills the request form (name, flat, mobile, event type, expected guests) and submits; the slot is marked "pending review" on the calendar.
4. The committee admin opens the pending-request queue, reviews the details, and approves (slot locks, fee confirmed) or rejects the request.
5. After approval, the committee records each payment as it arrives — UPI, cash or cheque — with the mode noted against a generated receipt number.
6. The resident's request page updates with approved status, paid amount and balance due; the full booking history stays searchable for audits.

Tech stack:

• HTML5, CSS3, JavaScript (responsive frontend)
• Node.js + Express (backend REST API)
• MySQL (users, slots, bookings, payments)
• Session/JWT authentication with resident and committee roles
• Date-picker calendar logic with slot-state rendering
• Receipt-number generation and audit-style record views

• [Availability calendar] Month-view calendar with every date marked available, partially booked, fully booked or pending review; past dates are locked so nobody can book backwards.
• [Booking request workflow] Residents submit a request with name, flat, mobile, event type and guest count; it stays in a pending queue until the committee acts on it.
• [Slot conflict prevention] Approving a request locks that date-slot in the database, so a second pending request for the same slot can no longer be approved.
• [Payment record tracking] Committee members record UPI, cash or cheque payments manually against each confirmed booking; the system assigns a receipt number and shows a receipt view.
• [Member vs outsider rate slabs] Four per-day slots (morning, afternoon, evening, full day) with separate charges for society members and outsiders, plus a configurable refundable deposit.
• [Admin dashboard] Pending-approval count, monthly bookings, payments collected and overdue amounts at a glance, with a searchable booking history.
• [Status tracking for residents] Every request shows its live status — pending, approved, rejected — with the fee, receipt number and balance due.
• [Receipt view] Printable receipt-style view for each payment record, showing booking details, total fee, amount received and balance due.

• Complete frontend + backend source code
• MySQL database schema with realistic seed data
• Setup and hosting instructions (database import, configuration)
• Working single-file demo walkthrough of the resident and admin flows
• Project report PDF (background, methodology, schema design, screenshots)
• PPT presentation for the final review
• Viva Q&A preparation document (roles, workflow, conflict logic, schema)