Multi-office meeting rooms: room lists, time zones

Someone in the Copenhagen office opens Outlook, types "Meeting Room 2" into Room Finder, sees it is free at 09:00 and books it. At 09:00 they walk down the corridor and Meeting Room 2 is occupied, because the room they booked is Meeting Room 2 in Berlin, which was free at 09:00 Berlin time, which is 09:00 CET, which is the same, except the Berlin room now has a Copenhagen meeting sitting on its calendar and a Berlin team standing outside it.

This is not a hard problem, but it is a problem nobody solves until it happens three times. This post covers what actually breaks when you have rooms in more than one office: room lists and building metadata per site, the time zone mistakes people make, naming that stops sites colliding in Room Finder, who administers what without handing out global admin, comparing utilization between sites, and the hardware logistics of maintaining displays in a building you are not in. It ends with the honest position, which is that a three site company of eighty people usually needs consistent naming and a display at each door, not a platform.

Three problems that look like one

When people say "we need to manage rooms across offices", they usually mean one of three different things, and the answers barely overlap:

Discovery. People cannot find the right room, or find rooms in the wrong city. This is a directory and metadata problem.
Operations. Somebody has to keep each site's rooms, displays and policies working. This is a delegation problem.
Reporting. Leadership wants to compare sites. This is a data problem, and the smallest of the three.

Fix them in that order. Discovery causes daily pain, operations causes weekly pain, and reporting causes a quarterly meeting.

Room lists and building metadata, per site

Microsoft 365

The two objects that matter are room lists (a special kind of distribution group) and Place metadata on each room mailbox. Room Finder builds its city and building navigation from these, and if they are missing, everything shows up in one flat list where Berlin and Copenhagen rooms sit next to each other with no way to tell them apart.

Connect-ExchangeOnline

# One room list per building, not per company
New-DistributionGroup -Name "CPH HQ" -RoomList `
  -PrimarySmtpAddress roomlist-cph@example.com

Add-DistributionGroupMember -Identity "CPH HQ" `
  -Member room-cph-nyhavn@example.com

# Place metadata drives Room Finder filtering
Set-Place -Identity room-cph-nyhavn@example.com `
  -CountryOrRegion "DK" `
  -City "Copenhagen" `
  -Building "HQ" `
  -Floor 3 `
  -FloorLabel "Third" `
  -Capacity 8

Three things Microsoft's own documentation is explicit about, and which people get wrong:

Each room list should contain rooms from one city only. A single "All Rooms" list spanning three countries defeats the city navigation entirely.
Allow 24 to 48 hours for changes to appear in Room Finder. When your test booking still shows the old data an hour later, that is expected, not broken. Plan your cutover around it.
Capacity and floor are what make filtering useful. Setting them is five minutes of scripting and is the difference between Room Finder being helpful and being a list.

Google Workspace

Google's model is closer to the physical world. You create buildings first, then floors, then resources inside them, in the Admin console under Directory, Buildings and resources. Users then see the building and floor alongside the room name when they book, plus any features you have defined (video conferencing, whiteboard, and so on).

The limits are generous enough that you will never hit them: Google documents up to 10,000 buildings, 10,000 resources and 100 features per domain. Bulk upload by CSV exists, which is how you should do this rather than clicking through 30 rooms.

Time zones and the bookings they break

Time zones cause fewer problems than people expect and different problems than people expect. Both Microsoft 365 and Google Workspace store events in absolute time and render them in the viewer's zone, so the naive failure ("I booked 09:00 and it appeared at 10:00") is rare.

What actually goes wrong:

Booking a room in a city where it is 07:00. The system is perfectly correct and the room is perfectly free. Nobody is there. This is the most common multi-site booking error and it is a human one.
Working hours not set per room. A room mailbox has its own working hours and time zone. If every room in your tenant was created from the same template, your London rooms may be advertising Copenhagen working hours. Set Set-MailboxCalendarConfiguration per room, or at least per site.
Daylight saving transitions that do not align. The EU and the US change clocks on different dates, so for a couple of weeks each year a recurring 16:00 Copenhagen call is at a different local time in a US office. Recurring series booked across that boundary drift relative to each other.
Recurring series booked from the wrong side. A weekly series created by someone in one zone and attended in another will follow the organiser's zone through DST, which is usually correct and occasionally surprising.

The practical mitigation is not technical. Put the city in the room name, so that anyone about to book a room 900 km away sees it in the picker before they click.

Naming that keeps sites separate

This is the single highest leverage thing on the list, and it costs nothing but an afternoon of agreement.

A workable pattern for multi-site:

[SITE] [Floor or wing] - [Room name] ([capacity])

CPH 3 - Nyhavn (8)
CPH 3 - Christiania (4)
BER 1 - Spree (12)
BER 2 - Tiergarten (6)
LON G - Thames (10)

Why each part earns its place:

Site code first means alphabetical sorting groups by office automatically, in every picker, including the ones that ignore your room lists.
Floor next means a person on floor 3 can scan for rooms on floor 3.
A real name, not a number. "Nyhavn" is memorable and unique across the estate. "Meeting Room 2" exists in every office you have and is the direct cause of the scene at the top of this post.
Capacity in the display name stops two people booking the twelve seat boardroom, in every client, whether or not that client respects the capacity field.

Do not use city names as room names in a multi-city company. A room called "Berlin" in the Copenhagen office is a joke that stops being funny during the first cross-site booking.

Who administers what

The realistic model for three sites and eighty people is a split:

Central IT owns room mailbox creation and deletion, calendar processing settings, room list structure, naming standard, and the integration with whatever display product you use. These are things that must be consistent, and consistency does not survive being everyone's job.
A local office manager owns the physical layer: display mounted straight, batteries charged, room name on the wall matches the room name on screen, broken equipment reported. These are things that must be done by somebody who is in the building.

Delegating without handing over global admin

The mistake is making the Berlin office manager a Global Administrator so they can rename a room. Do not do that. Microsoft 365 gives you narrower options:

Exchange Online role groups let you grant recipient management rights without assigning a broad Entra directory role at all. This is the cleanest path for "can edit room mailboxes, can do nothing else".
The Exchange Recipient Administrator role covers read access to recipients and write access to their attributes, which is most of what room management needs.
In Google Workspace, the Buildings and resources administrator privilege is a specific delegated admin privilege you can grant on its own.

Whichever you use, write down who holds it. In a three site company the person who set this up leaves eventually, and undocumented delegated permissions are how you end up with nobody able to rename a room.

Comparing utilization between sites

Cross-site comparison is seductive and mostly misleading, because the sites are not comparable. Before you draw a conclusion from "Berlin is at 70 percent and Copenhagen is at 40 percent", check:

Rooms per head. If Berlin has four rooms for thirty people and Copenhagen has eight for thirty, the difference is inventory, not behaviour.
Anchor days. If Berlin's team all comes in on Tuesday and Wednesday and Copenhagen's attendance is flat, peak contention differs even when weekly averages match. Compare peak windows, not weekly averages.
Room mix. One site with three huddle rooms and one boardroom behaves nothing like a site with four identical eight-person rooms.
Whether the calendar is actually the truth. A site with a high ghost booking rate looks busier than it is. Booking data measures intent everywhere, not attendance.

The comparison that is genuinely worth making is peak contention per site: during each site's busiest two hours, what fraction of rooms are booked, and how often does someone fail to find one. That number tells you where to add a room. Weekly average utilization tells you almost nothing.

Hardware logistics across sites

The thing nobody plans for. Whatever display you put on the doors, somebody in each building has to deal with it physically.

Who mounts it? If the answer is a cabling contractor, you are booking three contractors in three cities, coordinating three landlord permissions, and your rollout timeline is now set by whoever is slowest. Mounting that an office manager can do in five minutes removes a whole project workstream.
Who charges or powers it? Mains and PoE devices need cabling once and then never again. Battery devices need somebody local to notice a low battery. Both are fine, but pick one and name the person.
Who holds the spares? Buy at least one spare unit per site. Shipping a replacement panel across a border for a customs delay of a week is a poor use of everyone's time.
Who updates the room name on the wall? When Central IT renames a room in Exchange, the vinyl letters next to the door do not change. Make this an explicit handoff step in your naming change process, or you will have two names for one room within a month.

The honest conclusion

Most three site companies of around eighty people do not need a workplace management platform. Platforms like Skedda have shipped genuinely useful multi-venue features (an organisation-level hub aggregating utilization across venues, for example), and if you are running fifteen sites with a real estate team, that is exactly the tool for you.

At three sites, what actually fixes the problem is:

A naming standard applied everywhere, including the physical signs.
Room lists and Place or building metadata set correctly, once.
Auto-accept and sensible booking horizons on every room mailbox.
A display at each door so people can see availability without opening a laptop.
One named local person per site for the physical layer.

That is a week of work and no new platform. If you do all five and still have a problem, then go shopping.

The buy side of this decision

Point four is what we sell, so here is the disclosure. Lobby syncs in real time with Google Workspace and Microsoft 365 room resources and shows availability at the door. For a multi-site setup the relevant bits are: one dashboard covering every site, and pricing that does not scale per room, so a third office does not triple the bill.

The Free plan covers up to 3 active displays with no credit card, and it is free forever rather than a trial. Unlimited is USD 30 per month billed yearly (USD 50 per month if you pay month to month) for unlimited rooms and displays. Pro Unlimited is USD 60 per month billed yearly (USD 100 per month month to month) and adds a 5 minute e-ink refresh, full EU hosting for e-ink devices, custom branding and templates, room feedback with free QR stickers, a Slack /book command and priority support. Paying yearly saves 40 percent, with no annual contract lock-in.

The multi-site practicality: the e-ink option is a 7.5-inch e-ink panel from USD 69 per room that you buy once and own, with a keyhole slot for single-screw mounting and a 3 to 6 month battery, so an office manager mounts it without a contractor and there is no cabling contract per site. The hardware comes direct from the manufacturer with no markup from us, and volume pricing means USD 69 each applies to 1 to 9 units, dropping to USD 62.99 at 10 or more, which matters once you are kitting out three offices at once. Taxes, duties and shipping are not included. The virtual option is just a URL, so a site with tablets or TVs already on the wall needs no hardware at all. A room overview board covers a reception. Setup is under 10 minutes per site, self-serve, no sales call.

What Lobby does not do, plainly: no desk booking, no visitor management, no room or AV automation, no enterprise SSO or SCIM at scale, no MDM on the e-ink hardware, no on-premises Exchange without hybrid, and no occupancy sensors. It also does not rewrite your room names or fix your room lists, which is genuinely the first thing you should do and which no display can do for you.

TL;DR

Multi-site room management is three problems: discovery, operations, reporting. Fix them in that order.
In Microsoft 365, use one room list per building, keep each list to a single city, and set Place metadata (city, building, floor, capacity). Allow 24 to 48 hours for Room Finder to catch up.
In Google Workspace, create buildings and floors first, then resources, and bulk upload by CSV.
Time zone failures are mostly human, not technical. The fix is putting the site code in the room name. Also set working hours per room and expect drift around DST transitions.
Name rooms SITE Floor - Name (capacity). Never reuse "Meeting Room 2" across offices.
Central IT owns mailboxes, settings and naming. A named local person owns the physical layer.
Delegate with Exchange Online role groups or the Google buildings and resources privilege. Do not hand out global admin to rename a room.
Compare peak contention per site, not weekly average utilization, and check rooms per head first.
Plan hardware logistics: who mounts, who powers, who holds spares, who updates the sign on the wall.
At three sites and eighty people, consistent naming plus a display at each door beats a platform.

Sources

Configure rooms and workspaces for Room Finder, Microsoft Learn (room lists per city, 24 to 48 hour propagation).
Set-Place, Microsoft Learn (city, building, floor, floor label, capacity).
Manage resource mailboxes in Exchange Online, Microsoft Learn.
Permissions in Exchange Online, Microsoft Learn (role groups without Entra directory roles).
Create buildings, features and Calendar resources, Google Workspace Admin Help (limits, bulk upload, admin privilege).
Use Google Calendar structured resources, Google Workspace Admin Help.
Skedda (multi-venue organisation hub, vendor source).

Vendor features referenced above are taken from each vendor's own published pages and were verified on 5 August 2026. Features and pricing change. Confirm the current position directly with the vendor.

Managing Meeting Rooms Across Multiple Offices (Without an Enterprise Platform)