How Amenity Booking Works in Plinth

How amenity booking works in Plinth

Admins define amenities and booking guardrails at Admin → Amenities; residents reserve slots at Amenities. The database enforces one booking per time window plus booking notice/advance limits.

Admin: create an amenity

1. Open Admin → Amenities.
2. Add an amenity e.g. Clubhouse, Gym, or Party hall.
3. Optionally add a description.
4. Set booking guardrails:
   • Minimum notice before residents can book.
   • Maximum days in advance.
   • Maximum booking duration.
   • Resident cancellation cutoff.
   • Maximum guest count.
5. Toggle requires approval if the committee must sign off before the slot is firm (party halls, large gatherings).
6. Leave approval off for self-serve facilities like the gym bookings confirm immediately.

Resident: book a slot

1. Open Amenities.
2. Pick an amenity and choose start and end time.
3. Optionally note guest count and link the booking to your flat.
4. Submit Plinth processes your booking:
   • Confirmed if approval is not required.
   • Pending if the amenity needs admin approval.
5. Booking is rejected if it violates notice/advance/duration/guest limits.
6. If someone else already holds that window, booking fails the slot is not silently overwritten.

Admin: review pending bookings

1. On Admin → Amenities, open pending bookings.
2. Tap Approve status becomes confirmed (blocked if another booking overlaps).
3. Use Reject with a reason when a request does not meet society rules.
4. Every approval or rejection is audit-logged.

Cancel a booking

Residents can cancel their own bookings before the amenity cancellation cutoff. Admins can cancel any pending/confirmed booking. Status becomes cancelled and the slot reopens.

Post-usage closure

Admins can close confirmed bookings as completed or no_show so monthly usage reports and dispute handling stay accurate.

Admin guide · Resident guide · FAQ.