Sunnybank Church of Christ
Hall hire that cannot double book, and a roll call that survives bad wifi
A church with halls the community hires and a congregation to keep track of. One build covers the church's website, public hall hire with staff approval, and an iPad roll call for the people marking attendance on the day.
Running on this page
Two of the moving parts, live
Not screenshots. Both are the church's own code, running here on sample halls and invented people. They run themselves. Touch either one to take over.
1. What the hirer uses
2. What the roll call team uses
What is running
What is behind the booking form and the roll call
Seven mechanisms. One line each.
Two approved bookings cannot overlap
The database itself refuses a second approved booking for the same hall at an overlapping time, even if two staff approve at the same second. So double booking is impossible, not just unlikely.
A before and after record of every change
Every change to a booking, hall, hirer or blocked date writes a row showing what it was, what it became and who did it. So any question about who changed what has an answer.
One checked door for every request
A booking request is checked for notice period, clashes including pack down time, church use, blocked hirers and too many requests from one email in an hour, then saved in full or not at all. So staff only ever see requests that could actually go ahead.
Staff decisions follow fixed moves
A request can only go from pending to approved or declined, and an approval to cancelled. Declining needs a note to the hirer, and a past request cannot be approved. So the booking diary cannot end up in a state nobody intended.
Church use is held back automatically
Regular church activities are turned into real dates a year ahead and blocked from hire, and a single week cancelled by hand stays cancelled. So the calendar a hirer sees is the one the church actually keeps.
A roll call that survives bad wifi
Marking someone present is a swipe on an iPad. If the connection drops, the swipes wait on the iPad and send themselves when it returns, and sending twice changes nothing. So nobody has to mark the roll again.
Several markers, one answer
The roll is built for four people marking it together. The database combines their marks, will not close a roll while anyone is undecided, and needs a reason to overrule. So the final count is agreed, not whoever saved last.
What this makes possible
Two sides of the same build
For the hirer
- See which days and times are free before asking, not after.
- Request a hall in a few steps and get a reference straight away.
- Never be told a booking is confirmed and then find it was double booked.
For the church
- Approve or decline requests from one screen, with a note saved for the hirer.
- Know who changed any booking, and what it was before.
- Take the roll on iPads without worrying about the wifi.
Not finished
In build, not yet public
The new site has not launched. It is running on sample halls, rates and bookings until the church's own details go in, and the emails that tell a hirer about a decision are still being built.
Worth saying plainly
No one client has done the whole journey yet
Every piece of it is live somewhere, and we can show you each one.
Book a call