How to Run Meeting Room Bookings: A Practical Guide
Double bookings, unprepared rooms, and meetings that start fifteen minutes late because the video link doesn’t work, these are process failures, not bad luck. A meeting room booking SOP fixes them with one booking method everyone uses, a setup checklist for the room, a cancellation rule, and a reset routine after each meeting. The goal is simple: the right people in a ready room at the right time, with no surprises.
When to Use This
Use this SOP in any office with shared meeting rooms, even two rooms are enough to need it. It’s most needed when bookings happen informally (“I told Sara we’re using room 2”), when rooms are booked but sit empty, or when people arrive to find the previous meeting’s mess. If your office has external clients visiting, the stakes are higher: a client walking into an unprepared room is a first impression you don’t get back.
The SOP also covers the equipment and catering that turn a booked room into a working meeting, projectors, video links, water, and food ordered with enough notice to actually arrive.
How to Fill It Out
The header box. Who prepared it, who owns it, the version, the date issued, and the review date. The owner is usually the office manager, the person who deals with the fallout when bookings go wrong.
Fields to complete before use. Replace every bracketed field: the booking system or shared calendar everyone must use, the maximum booking length, the office manager’s name (for approving longer meetings), and the catering notice period. Then delete the example rows. One booking method is the foundation of the whole SOP, if bookings live in two calendars, you don’t have a booking system, you have a collision generator.
Booking rules. Book only through the named system, with the meeting title, organiser, expected attendee count, and start and end times. Fill in the booking parameters table: maximum length (for example, 2 hours, long enough for real meetings, short enough to stop room-hoarding), a 15-minute gap between bookings so rooms can be reset, and the approval route for longer meetings. The gap is the rule people resist and the rule that makes everything else work: without it, back-to-back meetings mean back-to-back chaos.
Room setup checklist. The standard the room must meet before anyone arrives: chairs set for the attendee count, table clear, whiteboard wiped with at least two working markers, screen or video link switched on and tested five minutes before the start with the meeting link pasted in the calendar invite, and drinking water and glasses for meetings over an hour. Decide who does the setup, the organiser, reception, or a rota, and write it down. A checklist with no named owner is a wish list.
Cancellations and no-shows. Cancel at least one hour before the start and delete the calendar entry, a cancelled meeting left on the calendar still blocks the room. And the release rule: a room unoccupied 15 minutes after the booked start may be released to another team. The release rule is what stops phantom bookings from wasting rooms all day; publish it visibly so nobody’s surprised when their empty room gets reallocated.
Equipment and catering requests. Note the lead times: catering needs the notice period you filled in (24 hours is typical), and equipment requests, projectors, extra chairs, video setup, go through whoever owns them with their own lead time. Requests made after the deadline don’t get promised; the SOP should say so, because “can you just” requests are how catering fails.
End-of-meeting reset. The organiser’s closing routine: chairs back, whiteboard wiped, rubbish cleared, equipment switched off, personal items taken. The next meeting’s setup starts with the previous meeting’s reset, this is the rule that keeps the system self-sustaining instead of depending on one person tidying all day.
Completion checklist. The routine confirmation: bookings in the system with full details, setup done before start time, cancellations processed, rooms reset after use.
Common Mistakes
1. Two booking methods. A shared calendar plus “just message the group chat” equals double bookings. One system, no exceptions, and the exceptions people make “just this once” are the ones that collide.
2. No gap between bookings. Back-to-back bookings look efficient and feel terrible: late starts, no reset time, the next group hovering in the corridor. The 15-minute gap costs a little capacity and buys a lot of reliability.
3. Setup with no owner. Everyone assumes someone else prepares the room, so nobody does. Name the owner of the setup, organiser, reception, or rota, in the SOP itself.
4. Phantom bookings never released. Rooms booked “just in case” and never used waste your scarcest resource. The 15-minute release rule only works if someone actually enforces it, give that job to reception or the room owner, not “whoever notices.”
Who Needs to Sign Off
The office manager prepares and owns this SOP; a senior manager approves it. If rooms are shared across departments, the department heads should agree to the booking rules and the release policy, a release rule imposed on one team and ignored by another will cause friction. Reception or whoever manages the rooms day-to-day reads it and applies the setup and release routines.
How Often to Review and Update
Review every six months, and update when the office changes: new or reconfigured rooms, a new booking system, changed catering arrangements, or new video equipment. Track the pain points, if double bookings keep happening, the problem is usually the booking method or enforcement, not the people. Adjust the maximum booking length and gap based on how rooms are actually used; a rule nobody follows is a rule that needs redesigning, not re-announcing.
Download the free Meeting Room Booking SOP template.