Forty people register for the fall picnic. Twenty-six show up. Next year, someone orders food for forty again, because that is the number everyone remembers. Half the hot dogs go home in a cooler, and the person who did the ordering feels foolish for reasons that were never really their fault.
The fix is not a better guess. It is a habit: write down who registered, write down who actually walked in, and keep both numbers where next year’s planner can find them. Do that for a couple of events and the gap between the two numbers stops being a mystery and starts being data you can plan around.
Why the gap exists at all
It is worth sitting with the hot-dog example a moment longer, because it is really a stand-in for every event a small church runs. Someone takes on the job of ordering food, renting tables, or lining up childcare workers, and they need a number before the event happens, not after. If the only number they have is registrations, and registrations always run ahead of who actually shows, they will over-order every single time — and they will not know it, because nobody wrote down what actually happened last time to compare against. This is not really a food-ordering problem. It is a memory problem, and the fix does not require new software or a committee. It requires one person writing two numbers on one line, once, per event.
Registering for something is cheap. It costs a click, a name on a clipboard, a reply to a text thread. Showing up costs an actual Saturday morning, a babysitter, a change of plans when the weather turns. Some of that gap is unavoidable — people mean it when they sign up, and life intervenes anyway. Some of it is predictable, which is the useful part: a free event with no commitment attached will always lose more people between sign-up and showing up than one with a deposit, a ticket, or a reserved seat next to a friend’s name.
None of that means registration numbers are worthless. It means they measure intent, not turnout, and the two should never be filed under the same number.
Two numbers, not one
The simplest version of this system is a sheet with two columns per event: registered and attended. Registered is whatever came in ahead of time — a sign-up sheet in the lobby, a form, a reply in a group chat. Attended is a headcount taken at the event itself, ideally by someone standing at the door with a clicker or a simple tally, not by someone guessing from memory the next morning.
The habit that makes this work is writing the attended number down the same day, while it is still accurate. A week later, everyone remembers the event as “pretty full,” and pretty full could mean anything from twenty people to fifty.
Where the two numbers live in SundayBridge
Gatherings take registrations against an event on the calendar, so the registered number already exists without extra paperwork — it is whoever signed up for that gathering. Attendance is a separate module, read-only from inside the app itself: a session gets logged there and it charts against its own history, but you cannot add a session from inside the app. The workaround most churches settle on is a simple one — count heads at the door with a tally or a clicker, same as you always would, and write that number next to the registration count for the event in your notes or your planning document. The comparison is what matters, and it does not require any particular tool to make.
What the gap actually tells you
Once you have a few events with both numbers logged, patterns show up fast. A picnic that always runs seventy percent of its registration count is telling you something different than a retreat that runs ninety-five percent. The picnic has low friction to sign up and low cost to skip. The retreat probably has a deposit, a ride to coordinate, or people traveling — anything that raises the cost of backing out raises the percentage that show.
A church of 150 that logs three fall events might end up with something like this after a season:
- Picnic: 40 registered, 27 attended — 68 percent
- Men’s retreat with a $15 deposit: 22 registered, 21 attended — 95 percent
- New members’ dinner: 18 registered, 14 attended — 78 percent
None of those percentages is right or wrong. They are just what this particular church, with this particular calendar, actually does. Next year, whoever orders the hot dogs has a real number to start from instead of a guess.
It is tempting to want one universal rule — “plan for seventy-five percent of registrations” — but that rule breaks the first time it meets an event unlike the ones it was built from. A church plant that skews younger and more spontaneous will see different behavior than a congregation of longtime members who RSVP and follow through out of habit. The point of tracking your own numbers, event by event, is that you stop borrowing someone else’s ratio and start using the one that actually describes your people.
Fixing the number, not just recording it
A gap that is unusually wide is worth asking about before you assume it is normal. Sometimes it is a reminder problem — nobody texted the registered list the week of the event, so half of them forgot. Sometimes it is a friction problem — the sign-up sheet was easy to add a name to in the lobby, with no real intention behind it. And sometimes the event itself changed after people signed up: a rescheduled time, a different location, a speaker who canceled.
A short reminder a day or two before an event, sent by whatever means your team already uses, tends to close a surprising amount of the gap on its own. That is a process fix, not a software one — SundayBridge does not send messages on your behalf, so this step happens through your own text thread, email list, or phone tree, same as it always has.
Building the habit into your planning rhythm
The whole system falls apart if the attended number never gets written down, so it helps to attach it to something that already happens. If your team does a weekly admin rhythm, add “log final attendance for last week’s event” as one line in that routine. It takes thirty seconds if the headcount was already taken at the door, and it is the difference between having real numbers next fall and starting from a guess again.
The same discipline pays off past the event itself. When a guest signs up for something and actually shows, that is one of the clearer signals you will get on the path from guest to member. Someone who registers and never comes is a different kind of lead than someone who has now walked through your door twice — worth remembering which one you are looking at before deciding how to follow up.
What to do with a big Sunday’s numbers
Events tied to a big Sunday — a baptism service, an Easter outreach, a sign-up table after a sermon series — deserve the same two-column habit, just compressed into a shorter window. The registered number is whoever put a name down that morning; the attended number is who actually shows up to the follow-up gathering a week or two later. That comparison is exactly the kind of thing covered in following up after a big Sunday, where the size of the gap tells you how much energy a moment actually had versus how much it felt like it had in the room.
Keep the record where the next person can find it
The last piece is boring and it is the one people skip: put both numbers somewhere that survives a change in who is planning the event. A spreadsheet works. A notes doc works. What does not work is a number that lives only in one volunteer’s head, because that volunteer moves, takes a season off, or simply forgets by the time next year’s picnic comes around. Write down the event, the date, the registered count, and the attended count, in one place, every time. A year from now, whoever is planning does not have to guess. They can just look it up.