Sign up today and save $20 on your first TRMNL e-ink display
LOBBY
Office Management· 9 min read

Meeting Room Booking Policy: A Template You Can Copy (and the Rules That Matter)

A complete meeting room booking policy you can copy into your handbook today, plus an honest breakdown of which clauses actually change behaviour, which ones are decoration, and why a policy nobody sees at the door does not work.

The policy already exists. It is a document from 2021, written by someone who has since left, and it says people should book rooms "considerately" and "cancel if their plans change". Three people have read it. Nobody has ever been shown it at the moment they were about to hold a two-person catch-up in the twelve-seat boardroom, which is the only moment that would have mattered.

This post hands you a complete meeting room booking policy you can lift into your own handbook today. Then it goes clause by clause through which rules actually change behaviour and which ones are decoration. The argument underneath it: a policy is only as strong as the system that enforces it, and that system is your calendar platform and the screen on the door, not a PDF in a shared drive.

The template: copy everything between the markers

Written for an office of roughly 20 to 100 people with somewhere between three and twelve bookable rooms. Replace the bracketed values with your own. If a clause does not fit how you work, delete it rather than softening it. A short policy that is true beats a long one that is aspirational.

[ START OF TEMPLATE ]

1. Scope

This policy covers all shared meeting rooms at [Office name]. It does not cover desks, phone booths or focus pods, which are first come, first served and are never booked in advance.

2. How to book

All rooms are booked through [Google Calendar / Outlook] by adding the room as a resource to the calendar event. Bookings made any other way (a note on a whiteboard, a message in a channel, a verbal agreement) do not count and will not be honoured.

3. Booking window and length

  1. Rooms can be booked up to [60] days in advance.
  2. The maximum single booking is [4 hours]. Longer sessions such as offsites and workshops require approval from [Office Manager].
  3. Book the time you actually need. Default to 25 or 50 minutes rather than 30 or 60 so people can move between rooms.

4. No-shows and release

  1. If nobody has arrived [10] minutes after the start time, the room is considered free and anyone may take it for the remainder of the slot.
  2. Whoever takes a released room should update the calendar so the display is correct.
  3. Repeated no-shows on the same recurring booking will be raised with the organiser by [Office Manager].

5. Recurring meetings

  1. Recurring bookings may run for a maximum of [13 weeks] before they expire and must be re-created.
  2. [Office Manager] reviews all recurring room bookings once per quarter and cancels any series with a pattern of no-shows.
  3. Recurring bookings on the largest room ([Room name]) require approval.

6. Cancelling and shortening

  1. If a meeting is cancelled or moves online, delete or decline the room booking. Do not leave it in the calendar.
  2. If a meeting ends early, end the booking. The room is then free.
  3. Cancelling late is not a failing. Not cancelling is.

7. Room sizing

Book the smallest room that fits the group. A one-to-one or a three-person stand-up should not occupy [Room name] while it is the only space that seats [12]. If the only free room is oversized, take it, but release it if a larger group needs it.

8. Rooms are not desks

Meeting rooms are for meetings. Using a room as a personal office for a full day is not permitted, including for calls. [If you have booths or pods, name them here as the alternative.]

9. Priority

Bookings are honoured in the order they were made. There is no seniority override. Meetings with external visitors take priority over internal meetings for the rooms nearest reception ([Room names]), and the organiser of the internal meeting will be asked to move with at least 24 hours of notice.

10. Exceptions

Anything outside this policy (all-day bookings, standing holds, blocking a room for equipment) is approved by [Office Manager] and recorded so the exception does not quietly become the norm.

11. Review

This policy is reviewed every [6 months] against actual booking and utilization data. Owner: [Name], [email].

[ END OF TEMPLATE ]

Which clauses actually change behaviour

Five of the clauses above do real work. The rest exist so the document reads as complete.

Maximum booking length

This is the single highest-leverage rule, because it is enforceable in software and because long bookings are what starve a small office of rooms. One person holding the only large room from 09:00 to 17:00 removes an entire room from the pool for a day. A four-hour cap with a named approval path for genuine exceptions costs you nothing and removes the failure mode.

The release window for no-shows

The 10-minute rule is the clause people actually remember, because it gives them permission to do something they already want to do: walk into an empty booked room. Without a written window, people hover in the corridor and the room stays empty for the full hour. With it, the space gets reused. Ten minutes is the number to pick. Five feels aggressive when someone is genuinely walking from another floor. Fifteen means you have lost a quarter of a standard slot.

Recurring meeting review cadence

Recurring bookings are where room capacity goes to die. They are created once, when the meeting mattered, and then outlive the project. An expiry (13 weeks is a reasonable default) plus a quarterly human review is the only mechanism that reliably clears them, because no automated system can tell the difference between a recurring meeting that is still valuable and one that has become a habit. This is the clause most policies leave out and the one that recovers the most room-hours.

Who can book the big room

Gating the largest room behind approval for recurring use is worth the small amount of friction. Note the shape of the rule: it does not gate one-off bookings, because that creates a bottleneck and makes people route around the system entirely. It gates the standing hold, which is the thing that causes the damage.

Cancellation expectations, framed as no-fault

The wording matters more than the rule. "Cancelling late is not a failing. Not cancelling is." removes the social cost of releasing a room at short notice. Most people do not leave phantom bookings out of selfishness. They leave them because cancelling feels like admitting the meeting was unnecessary.

The clauses that are theatre

Be honest with yourself about these. They belong in the document for completeness, but do not expect them to change anything on their own.

  • "Book the smallest room that fits." Nobody knows the capacity of each room from the calendar picker. This clause only works if the room name or the display carries the number.
  • "Clean up after yourself." Real, but it is meeting room etiquette, not booking policy. Putting it here dilutes the rules that need enforcing.
  • Escalation ladders and warnings. In a 40-person office nobody is going to formally warn a colleague about a room booking. Pretending otherwise makes the whole document less credible.
  • "Respect other people's time." Delete it. If a clause cannot be violated in a way you could point at, it is not a rule.

Enforce the parts you can enforce in software

Three of the numbers in the template can be moved out of prose and into your calendar platform, where they apply whether anyone has read the policy or not.

Microsoft 365

Room mailboxes have booking guardrails built in. The booking window and maximum duration are set per room:

Connect-ExchangeOnline

Set-CalendarProcessing -Identity "Boardroom" `
  -AutomateProcessing AutoAccept `
  -BookingWindowInDays 60 `
  -MaximumDurationInMinutes 240 `
  -AllowConflicts $false

The default booking window is 180 days and the default maximum duration is 1440 minutes (24 hours), so both of these are worth setting explicitly. If you also run Teams panels, the "release room if no one checks in" setting turns clause 4 into an automatic decline rather than a norm people have to enforce socially.

Google Workspace

Google's automatic room release exists but is narrower than most people assume. It releases a room when all but one invitee has declined the event, and it is available on Enterprise Standard, Enterprise Plus and the Education tiers, not on Business Starter or Standard. It is not an occupancy-based no-show release. If you are on a Business plan, clause 4 stays a human rule.

A policy nobody can see at the door does not work

Here is the uncomfortable part. Every clause above is enforced at a specific place and time: standing outside a room at 09:12, wondering whether the meeting inside is real. The document is in a handbook. The decision is in the corridor. Those two things are not connected in most offices.

That gap is why the 10-minute release rule fails in practice more often than any other clause. The person in the corridor does not know when the booking started, whether anyone checked in, or whether the group inside is the one on the calendar. They guess, and guessing usually means walking away. A display on the door closes that gap, because it puts the booking state at the point of the decision: who booked it, when it started, when it ends, and whether the next slot is free.

You do not need a display to have a policy. You do need one for clauses 4, 7 and 9 to mean anything at 09:12 on a Tuesday.

The buy side of this decision

You can build the display side yourself. A Raspberry Pi, a browser in kiosk mode and the Graph or Google Calendar API will get you a working room panel in a weekend, and we have written about exactly that elsewhere on this blog. The reason people stop doing it is not the first room, it is the fifth: token refresh, device reboots, one screen that quietly froze three weeks ago showing Tuesday's schedule.

Lobby is the buy side of that. It syncs in real time with Google Workspace and Microsoft 365 room resources, and gives you three ways to show the same view: a physical e-ink panel on TRMNL hardware, a virtual display that is just a URL in any browser tab on a tablet or TV, or a room overview board for reception.

The hardware is bought direct from the TRMNL shop and we take no markup on it. Volume pricing applies: USD 139 per device for 1 to 9 devices, USD 119 each from 10 to 20, USD 109 from 21 to 50, and down to USD 99 each at 151 or more. Same list price in the EU and the USA, with tax, duties and shipping on top. You buy it once and keep it, it mounts magnetically, and it runs up to 12 months on a battery charge.

The software has three plans. Free is free forever for up to three active displays, with 15-minute e-ink updates and no credit card. It is not a trial. Unlimited is USD 30 per month billed yearly, which is USD 360 a year, or USD 50 per month if you pay month to month, and covers unlimited rooms and displays. Pro Unlimited is USD 60 per month billed yearly, USD 720 a year, or USD 100 per month month to month, and adds 5-minute e-ink updates, custom templates, removal of Lobby branding, your own logo, room feedback with free QR stickers, a Slack /book command, priority support, full EU hosting for TRMNL devices, battery saver mode and smart updates. Yearly billing saves 40 percent and there is no annual contract lock-in, so you can cancel any time. Setup takes under 10 minutes and there is no sales call.

What Lobby does not do, plainly: no desk booking, no visitor management, no room automation or AV control, no enterprise SSO or SCIM at scale, no MDM on the TRMNL hardware, no occupancy sensors, and no on-premises Exchange without a hybrid setup. If your policy needs any of those, this is not the tool. It shows the booking state on the door and lets people book from it. That is the whole product. Lobby is made by Vikba ApS in Denmark and is not affiliated with Microsoft or Google.

TL;DR

  • Copy the template above. Replace the bracketed values. Delete anything that does not describe your office honestly.
  • Five clauses do the work: maximum booking length, the no-show release window (10 minutes), a recurring-meeting expiry and quarterly review, approval for standing holds on the largest room, and no-fault cancellation wording.
  • Most other clauses are decoration. Keep them short or cut them, because a long policy makes the enforceable parts harder to find.
  • Move the booking window and maximum duration into the calendar platform. In Microsoft 365 that is Set-CalendarProcessing. In Google Workspace, automatic room release is Enterprise-tier only and only fires on declines, not on no-shows.
  • A policy is enforced in a corridor, not in a handbook. Without something at the door showing booking state, clauses 4, 7 and 9 are honour-system only.

Related reading

Sources

Try Lobby — free forever up to 3 displays

Room booking that just works.

Get started →