A community group asks the office if they can use the hall on a Saturday. The office says that sounds fine. Two weeks later the youth lead, who booked the same hall by writing it on the wall planner in March, arrives to find forty strangers setting out chairs. Everyone involved acted reasonably. The building still got double-booked, because at no point did anyone establish who was actually allowed to say yes.
The request with no front door
Organizations with a building almost always solve the calendar before they solve the decision. They buy a booking system, put the rooms in it, and consider the problem handled. Then the requests keep arriving by every route except that one: a conversation after a meeting, an email to whoever the requester happens to know, a message to the person who has the keys, a note left on a desk.
Each of those routes reaches a different person, and each of those people has a different idea of their own authority. The calendar is not wrong. It simply never heard about two of the four bookings, because a booking system records decisions and nobody agreed who makes them.
This is why double-bookings survive the purchase of software designed to prevent them, and it is why the fix is an approval ladder rather than a better calendar.
What a space request actually asks for
A request for a room looks like a question about availability. It is really four questions bundled together, and the bundling is what causes the trouble, because different people are qualified to answer different parts.
- Is the space free? The only genuinely factual part, and the only one a calendar answers on its own.
- Is this an appropriate use? A judgement about the organization, not the building. Whether a political meeting, a paid class, or a private party belongs in your space is not a scheduling question.
- What does yes cost us? Heating, cleaning, someone to open and lock up, wear on equipment, and the staff hour spent coordinating it. Free use of a building is never free.
- What has to be true before they walk in? Insurance, a deposit, safeguarding checks, a named responsible adult, a risk assessment for anything unusual.
Most organizations have a person who can answer the first question and no agreed answer to the other three. So whoever receives the request answers all four by instinct, and the instinct is usually to be helpful.
Build the ladder once, in writing
An approval ladder is a short table that says which kinds of request can be decided by whom. It takes about an hour to write and it resolves most of these problems permanently, because it turns a judgement call into a lookup.
| Kind of request | Decided by | Extra conditions |
|---|---|---|
| Internal team, existing room, in hours | Whoever holds the calendar | None |
| Internal team, out of hours or needs setup | Facilities or operations lead | Confirmed opener and closer |
| Regular external group, already approved | Facilities or operations lead | Agreement and insurance on file, in date |
| New external group, one-off | Operations lead with a second sign-off | Insurance, deposit, named contact |
| Anything paid, ticketed, or public facing | Leadership or director level | Insurance, agreement, and a fee decision |
| Anything involving children or vulnerable adults | Safeguarding lead, no exceptions | Checks verified before the date is held |
Adapt the rows to your organization, but keep two properties. Every row names a role rather than a person, so it survives someone leaving. And every row that carries real risk requires a second pair of eyes, because the failure mode you are protecting against is one helpful person acting alone at short notice.
A booking system records decisions. It does not make them, and it will happily record two contradictory ones.
Give the request one way in
The ladder only works if requests arrive somewhere it can be applied. That means one route, published, that everyone is redirected to, including staff.
- Put a form where people already ask. A short request form on your site, linked from the contact page and sent as the reply to every informal ask. It should collect the date, the times including setup and clear-down, the group, a named responsible person, expected numbers, and anything unusual about the activity.
- Route it into the same place as everything else. A request that lands in one person’s inbox has not entered a system, it has entered a queue of one. It needs to sit where the calendar, the group’s record, and the approval history all already live, so that the request, the booking, and the paperwork are one object rather than three.
- Answer with a hold, not a yes. The reply to a new request is that the date is held pending approval, with a date by which they will hear. This single change removes almost all accidental commitments, because a hold is provisional in a way that a friendly yes never is.
- Set a response deadline you can meet. Five working days is fine. Silence is not. A process people cannot get an answer out of is the reason they went round it and asked the caretaker in the first place.
- Redirect every informal ask, every time. The hardest part, and the only part that matters. When someone asks in a corridor, the answer is that it sounds good and here is the form. One exception rebuilds the old system.
The conditions that should be automatic
A handful of conditions are worth attaching to external use permanently, so that no individual has to remember to raise them or feel awkward about asking.
- Public liability insurance, in date, on file. Ask for the certificate and record the expiry. A regular group whose cover lapsed in March is the most common gap in an otherwise tidy process.
- A named responsible person who will be present. Not the person who booked it. The person who will actually be in the building.
- Opening and closing, assigned by name. Every out-of-hours booking needs a person who opens and a person who locks up, agreed in advance and recorded against the booking.
- Setup and clear-down inside the booked time. Bookings that quietly assume an extra hour either side are the source of most back-to-back collisions.
- A written condition of the space. A photo before and after costs nothing and ends every argument about damage and rubbish.
- An agreed cost, even if it is zero. Writing “no charge for this booking” is very different from never discussing money, particularly when the third booking arrives.
Saying no without losing the relationship
Most organizations avoid building this process because they do not want to seem unwelcoming. In practice the opposite happens: the absence of a process means refusals are inconsistent and personal, and the reasons sound like excuses because they are invented on the spot.
A written policy makes a no easier to give and much easier to receive. It is not a judgement on the group, it is a rule that applies to everyone, and you can hand it over. Three things make refusals land better.
- Answer quickly. A no in two days is a courtesy. A no in three weeks, after they have advertised, is a problem you created.
- Give the actual reason. Capacity, an existing commitment, insurance, or use of the space. Vagueness reads as dislike.
- Offer the nearest yes. A different room, a different date, or the conditions under which the answer would change. Most groups accept a no with a route attached.
Key takeaways
- Double-bookings are usually approval failures. A calendar records decisions, it does not decide who is entitled to make them.
- Write the ladder once. A short table mapping request types to roles turns a judgement call into a lookup that survives staff turnover.
- One front door, and hold rather than confirm. Replying with a provisional hold ends almost all accidental commitments.
- Attach conditions to the policy, not to the person asking. Insurance, a named responsible adult, and assigned opening and closing should never depend on someone remembering.
Questions to ask your team
We are a small team. Is an approval ladder overkill?
Small teams need it more, because informal authority is broader and one person is often covering three roles. It is shorter for you, perhaps three rows, but the value is the same: it is written down, so it holds when the person who knew everything is away.
What about regular groups who have used the space for years?
Give them an annual agreement rather than approving each booking. Their term of dates goes into the calendar in one go, and the annual renewal is when you check that insurance and contacts are still current, which is exactly the check that long-standing arrangements tend to lose.
Should we charge for space we are not using anyway?
Use has a cost even when the room is idle: heat, light, cleaning, wear, and staff time. You may well choose to waive it, but decide the number first and then decide to waive it. Organizations that never price their space end up subsidizing whoever asks most often rather than whoever they meant to support.
How do we stop staff booking rooms informally between themselves?
Make the official route faster than the informal one for internal use. If booking a meeting room takes thirty seconds and needs no approval, nobody writes it on a wall planner. Friction is what created the shadow process.
Who should own this if we have no facilities manager?
Whoever holds the master calendar, with a named second person for anything external or out of hours. The requirement is not a job title, it is that the role is written down and one person is not silently carrying all of it.
