A generic booking form was never going to keep up with a busier hall.

I’m a trustee of a charity that runs a hall — no operational role day to day, just someone who sees the reports. Bookings there go through a generic form on the website. What actually happens after someone submits it, I honestly couldn’t tell you for certain. Probably an email lands in our facility manager’s inbox. Maybe.

What I do know is what the form doesn’t do: it doesn’t show what’s actually free, it doesn’t confirm anything automatically, and it doesn’t chase up payment or details once a booking’s made. All of that would land on our facility manager — who’s part-time, and whose actual job is opening the building, staying on top of maintenance, fundraising, managing the bookings already in the diary, and the odd stretch of grounds work besides. The hall’s been getting busier every month. The form hasn’t changed to match.

So I started building Hallsea — not just to fix one hall’s form, but as something any facility in the same spot could use: live availability, one-tap approvals, automatic follow-up on payments and details, and a report a trustee can actually read in one click, because I wanted that visibility as much as I wanted the admin gone.