The bride’s mother calls in June about a Saturday in October. The sanctuary, she says, and the fellowship hall for the reception, and could the tables be set up the Thursday before. You write it on a sticky note, or in your own calendar, or in a notebook that lives in the church office — and it is fine, until the day a grieving family calls needing that same Saturday for a funeral, and nobody remembers the wedding until the flowers arrive.
This is not a staffing problem or a communication failure between good people. It is a records problem: two people, two mental calendars, one building. The fix is not more meetings. It is one place both people check before they say yes to a date.
Why the sticky note stops working
In a very small church, one person handles the calendar and the sticky-note system works because there is only one head to hold it all. The trouble starts the moment a second person — an associate pastor, a wedding coordinator, a facilities volunteer — also has the authority to say yes to a date. Now there are two calendars, or one calendar and one memory, and the two are not talking to each other.
Weddings make this worse because they get booked far in advance and touch the building more than once: the rehearsal, the ceremony, the reception, sometimes a rehearsal dinner in the fellowship hall the night before. Funerals make it worse in the other direction — they get booked on a few days’ notice, sometimes less, and whoever takes that call needs to check the calendar fast, not dig through a binder.
One calendar, not a wedding calendar and a “regular” calendar
The habit worth building is small: every use of the building, from the Tuesday quilting circle to a wedding rehearsal, gets logged the same way, in the same place, by whoever takes the call. Not a separate spreadsheet for “special events.” Not a wedding binder kept in a drawer. The same calendar the youth pastor checks before booking a lock-in.
In SundayBridge’s gatherings, that is exactly what a wedding or a funeral is: an entry on the month calendar with a date, a time, and a location field. Type “Sanctuary” or “Fellowship hall” into that field and the room shows up right on the calendar card, next to everything else booked that week. There is no separate facility module to learn and no second system to remember to check — it is the same screen where the potluck and the elders’ retreat already live.
What one wedding, logged well, looks like
- Rehearsal — Thursday evening, sanctuary.
- Ceremony — Saturday afternoon, sanctuary.
- Reception — Saturday afternoon, fellowship hall.
Three gatherings, three rows on the calendar, one family. Anyone scanning that Saturday sees both rooms are already spoken for before they ever pick up the phone to book a men’s breakfast in the fellowship hall at the same hour.
What this does not do for you
It is worth being plain about the edges here, because the honest version of this system is more useful than an oversold one. SundayBridge will not warn you if you try to book two things in the same room at the same time — there is no conflict alert. What it gives you is one shared calendar instead of several private ones, so a person checking before they commit a date can actually see what is already there. The catching still has to happen; the system just makes the catching possible.
It also will not send the family a confirmation email or text. There is no messaging built in. If you tell a family “you’re on the calendar for October 4th,” that confirmation still goes out by phone or by an email you write yourself — the gathering just needs to exist on the shared calendar before you make that promise, not after.
Who should be the one checking
Pick one person, or at most two, who log every use of the building before they confirm it with a family. If the associate pastor handles funerals and the office administrator handles weddings, both of them need to be looking at the same calendar, not two calendars that happen to have similar names. There is one login per church here rather than separate staff accounts, so “the same calendar” is not a coordination problem — whoever is at the keyboard sees everything that is already booked.
That single login cuts the other way too: there is no way to give the wedding coordinator a view that hides the pastoral care records, so whoever checks the calendar can see the whole system, not just the room-booking piece. For most churches this size that trade is fine — the people trusted to book the sanctuary are usually already trusted with more than that.
Weddings booked months out, funerals booked days out
Treat the two differently in timing, not in method. A wedding usually gets logged the week the date is set, months in advance, with the rehearsal and reception added as soon as those times are known. A funeral gets logged the day the family calls, often with only the ceremony time settled and the rest — a visitation the evening before, a reception after — added within the hour. The habit that matters for funerals specifically is speed: check the calendar before you tell the family yes, because there is no time to discover a conflict later.
If your weekly admin rhythm already includes a look at the coming month’s calendar, add one line to it: scan for anything with a location field and make sure two things in the same room haven’t landed on the same day. It takes two minutes and it is the whole prevention.
The same applies to outside groups: a community organization, a support group, or a family with no membership history who wants the building for a memorial gathering. Log those the same way, a gathering, a date, a location, and whatever contact details belong in the notes. What you will not get here is a rental agreement, a deposit tracker, or an automatic invoice — those still live on paper or in whatever system already handles them. The calendar entry’s job is narrower and more useful than that: make sure nobody else books that room on that day.
What to log beyond the date and the room
A gathering entry holds more than a date and a location. Use the notes to write down the parts that are easy to forget under pressure: whether the family needs the kitchen for a reception, whether the sound system has to be run by someone other than the usual Sunday tech, whether a photographer will arrive an hour early to shoot the empty sanctuary. None of that is a special feature — it is the same free-text detail field every other gathering on the calendar already uses for a potluck’s dish sign-up or a youth event’s permission-slip reminder. The discipline is just remembering to use it for a wedding the same way you would for anything else.
Registrations work the same way if a memorial reception needs a headcount for catering, or if a wedding rehearsal dinner needs to know how many chairs to set. It is not a seating chart or a catering order form — it is a simple list of names attached to the gathering, which is often all a volunteer setting up tables actually needs.
The week-before check that catches what the calendar didn’t
Even with everything logged correctly, a room can look free on the calendar and still be a problem in practice — the folding tables from last week’s fellowship dinner never got put away, or the sanctuary carpet is being cleaned the same afternoon as the ceremony. A calendar tells you the room is booked; it cannot tell you the room is ready. Build a short walkthrough into the week before any wedding or funeral: whoever holds the keys checks the space itself, not just the entry that says it is spoken for. The record prevents the double-booking. A pair of eyes in the room prevents the rest.
This matters more for funerals than weddings, precisely because funerals are booked with so little lead time. A wedding coordinator has months to notice a conflict; a grieving family calling on a Tuesday for a Thursday service does not have that cushion. If your church handles funerals often enough that this is a real risk, it is worth deciding in advance who has the authority to say yes on short notice, and making sure that person checks the calendar before the phone call ends, not after.
The habit, not the tool, is what prevents the double-booking
A church of 150 with one part-time secretary and a pastor who also answers the phone does not need a facilities-management system. It needs one calendar that both of them actually check before they say yes to a family. The system just holds that calendar and puts the room right on the card, but the habit — look before you promise a date — is the part that actually stops the wedding and the funeral from wanting the same Saturday afternoon.
If your church is still coordinating this by phone call and memory, the honest first step is smaller than switching software: agree on one place, on paper or otherwise, that every use of the building gets written down before it’s promised. Once that habit is real, moving it off scattered notes and into one system is the easy part.