A community group calls asking to use the fellowship hall for a Saturday workshop. The office administrator says yes, because it sounds harmless and the room is usually empty on Saturdays. Nobody asks about cleanup, nobody mentions the folding chairs need to be stacked a certain way for Sunday, and nobody thinks to ask whether the group carries its own liability coverage. Three weeks later a different volunteer says yes to a different group for the same Saturday, because nothing was written down anywhere either of them could check.
A facility use policy is not a form. It is the set of decisions your church makes once, on a calm day, so that whoever answers the phone on a busy one is not making them up as they go. It does not need to be long. It needs to answer the same handful of questions every time, in writing, so two well-meaning volunteers never give two different answers to the same kind of request.
Who is allowed to say yes
This is the section that prevents the most damage and gets skipped the most often. Name one person — by name, not just by title — who has the authority to approve a facility request. Name a second person who can approve in that person’s absence. Write down what happens when neither is reachable and a decision cannot wait: does the request simply wait, or does someone else have standing authority to say yes for routine cases?
Vague authority is worse than strict authority. A policy that says “check with the office” invites three different people to each think someone else already checked. A policy that says “Pastor Dave approves all outside requests; Linda approves when he is traveling” leaves no ambiguity for anyone holding the phone.
Who gets priority when two groups want the same date
Write the order before you need it, not while two families are both on the phone. A common order looks like: regular church programming first, then member-sponsored events, then community groups with a standing relationship, then new outside requests. Whatever order your church chooses, put it in writing, because the alternative is deciding case by case under pressure — which tends to favor whoever called most recently or most persistently, not whoever actually had the stronger claim.
This only works if every use of the building lands on one shared calendar that whoever approves requests can actually see before saying yes. If your weekly admin rhythm does not already include a look at the coming month for anything with a room attached, that is worth adding — it is a two-minute habit that catches most conflicts before they become a phone call you dread returning.
What the requesting group is responsible for
Spell out, in a short list, what the group leaves behind when they walk out the door:
- Setup and breakdown — who moves tables and chairs, and whether they go back to the exact configuration the room was in before.
- Cleaning — trash out, surfaces wiped, floor swept, kitchen left the way it was found if the kitchen was used.
- Time limits — when they must be out of the building, including cleanup, not just when the event itself ends.
- Damage — who they report a broken chair or a stained carpet to, and whether repair costs come out of a deposit.
None of this needs legal language. It needs to be specific enough that a volunteer coordinator who was not there when the policy was written can still hold a group to it without guessing.
Money: fees, deposits, and who collects them
Decide, and write down, whether facility use is free, flat-fee, or deposit-based, and whether that answer changes for outside groups versus church members using the building for something personal. If there is a deposit, state what it covers, when it is returned, and who holds the money in the meantime. If fees are waived for certain kinds of groups — a twelve-step meeting, a denominational partner — name those categories rather than leaving it to whoever takes the call to decide who counts as “a good cause.”
Be plain with yourself here: the policy can describe the fee structure, but nothing in a church management system will collect that fee or send an invoice for it. Whatever money changes hands for facility use still moves the way it always has — cash, a check, or however your church already handles it — and the policy should say who is responsible for that handoff.
Insurance, liability, and who signs what
Any group that is not your own congregation using the building introduces a liability question worth answering in writing before the first outside group ever asks: does the group need its own liability insurance, does your church’s policy already cover it, or does someone need to sign a waiver? This is not a section to guess at. It is worth a short conversation with whoever holds your church’s insurance policy, or your denominational office if you have one, before you finalize the wording — the right answer depends on your coverage and your state, not on what sounds reasonable.
Once you have that answer, the policy just needs to state it plainly and say where the signed paperwork, if any, gets filed. A pastoral care case or a giving record has an obvious home in most church systems; a facility use waiver usually does not, and it is fine for the answer to be a folder in a filing cabinet as long as everyone who approves requests knows where that folder is.
Keys, access, and who locks up
A group that has the building for a Saturday morning still needs a way in and a way to leave it secure. Decide whether a key is issued and returned, whether a staff member or trusted volunteer opens and closes the building in person, or whether an access code is used and changed periodically. Write down who is responsible if a door is left unlocked or an alarm is not set — not to assign blame after the fact, but so the person granting access knows, before they say yes, exactly what they are trusting the group with.
Putting the request itself on the calendar
A policy only prevents conflict if every approved request actually lands somewhere someone else can see it before they approve the next one. In SundayBridge’s gatherings, a facility request is logged the same way a potluck or a youth lock-in is: an entry on the month calendar with a date, a time, and a location field. Type the room name into that field and it shows up on the calendar card next to everything else booked that week, so whoever is deciding on the next request can see what is already there. There is no separate approval workflow, no automatic conflict warning, and no way to attach the signed waiver or collect the deposit inside the system — it is simply the one shared calendar that makes the policy’s priority order enforceable instead of theoretical.
That is a modest claim on purpose. A written policy plus one calendar everyone actually checks does more to prevent double-bookings and unpleasant surprises than any amount of software sophistication would. The discipline is checking before you say yes; the calendar just has to be the same one every time.
Writing it down and keeping it current
None of this has to be a formal document reviewed by a committee, though for larger congregations it often should be. For a church of 60 to 250, a single page covering approval authority, priority order, cleanup expectations, fees, insurance, and keys is usually enough — as long as it is written somewhere more durable than one person’s memory, and someone reviews it once a year to update names and numbers that have changed. A policy nobody has looked at since the last pastor left is close to no policy at all.
If your church is still handling all of this on scattered notes and hallway conversations, getting the calendar itself onto one system is worth doing before you finalize the policy, not after — it is easier to write down “check the calendar first” once there is exactly one calendar to check. And if setup and breakdown for facility use falls to the same small group of volunteers who already handle Sunday setup, it is worth reading how to schedule volunteers so that one crew does not quietly end up carrying every event the building hosts.