12Rental & Booking · Custom software
Venue and hall booking with conflicting-resource checks
A venue operator booking halls, equipment and staff that cannot be double-allocated.
- Multi-resource booking
- Conflict detection at confirmation
- Package and add-on pricing
- Deposit and balance schedule
The problem
Bookings for the hall, the equipment in it and the staff running it were kept in three places. Conflicts surfaced on the day, and resolving them meant disappointing someone who had already paid.
What we built
We modelled every bookable thing as a resource with its own calendar, so a booking that requires hall, equipment and staff checks all three before it can be confirmed.
Modules delivered
- Multi-resource booking
- Conflict detection at confirmation
- Package and add-on pricing
- Deposit and balance schedule
- Setup and teardown buffers
- Booking sheet for the day
What changed
What the delivered system does differently from the process it replaced.
- A booking cannot confirm if any required resource is taken
- Setup and teardown time is reserved, not assumed
- The day sheet is generated from live bookings
Built with
The stack chosen for this build.
- Next.js
- TypeScript
- PostgreSQL
Why this customer is not named
Most of our customers allow the work to be described but not their name published. Where a customer has given permission, their name and testimonial appear here.
Independent accounts of our work are published by customers themselves on our Facebook reviews page.
Related case studies
Does this look like your problem?
If any of this is familiar, the first step is the same one this project started with: a free requirement study that ends in a written scope and a fixed price.