Organizing Meeting Rooms
Across Floors and Buildings

Short answer: use a consistent, front-loaded naming scheme — location, then floor, then a unique name — and tag every room with capacity and features. When names sort correctly and read unambiguously, room finders, calendar pickers, and door displays all stay legible even at 200 rooms across five cities.

A single office with four rooms can name them anything. A company with three buildings, twelve floors, and rooms named "The Serengeti" quickly discovers that nobody knows where "The Serengeti" is, two floors have a "Boardroom," and someone in Berlin just booked a room in Boston. Structure is what keeps a growing room estate usable. Here's how to build it.

Start with how names are actually read

Room names show up in three places, and your scheme has to work in all of them:

1. The calendar room picker — an alphabetical list, often truncated. Front-loaded, sortable names win.
2. The door display — a glance from the hallway. Short, human names win.
3. Directions people give each other — "meet in..." Memorable names win.

These pull in different directions, which is why the best schemes combine a structured code with a friendly name.

A naming scheme that scales

Front-load the parts that group and sort, and keep them consistent everywhere:

[Site]-[Floor]-[Name] ([Capacity])

Examples:

The structured code lives in the calendar system's room resource name, so pickers sort by site then floor automatically. The friendly name is what the door display shows big. See meeting room names for picking names people remember.

Choose stable prefixes

Your site and floor prefixes are the backbone — get them right once:

• Site codes: 3-letter airport-style codes (BOS, BER, LDN) read instantly and never collide. Avoid full city names that push the useful part off a truncated list.
• Floor numbers: always zero-pad (01, 02 … 12) so they sort correctly as text. "10" sorting before "2" is the classic room-list mess.
• One scheme, everywhere. The moment one building does it differently, the sort breaks and trust in the list evaporates.

Tag capacity and features, don't bury them in names

Resist cramming everything into the name. Most calendar systems let room resources carry structured attributes — capacity, video conferencing, accessibility, whiteboard. Use them:

• Capacity as a number people can filter by — critical for stopping a two-person call from taking the 14-seat boardroom. See meeting room booking best practices.
• Features as tags (VC, display, accessible, phone-booth) so people find the right room, not just a free one.

Set these up properly in your platform: Google Calendar room resources or Microsoft 365 room mailboxes. The door display then simply reflects whichever room it's assigned to.

Avoiding ambiguity across floors and buildings

The failures are predictable, so design them out:

• Never reuse a friendly name across sites. Two "Boardrooms" guarantees a wrong booking. If themes repeat (rivers, trees), give each site its own theme.
• Make the site visible on the display too. A small "BER · Floor 1" line under the big room name removes all doubt for visitors.
• Group by floor for wayfinding. Numbering rooms in a walking order per floor helps people find the room after they've booked it.
• Decide a phone-booth convention early. Tiny one-person rooms multiply fast; a "-POD" suffix keeps them out of the way of real meeting rooms in lists.

Multi-city and time zones

Once rooms span time zones, the room's location must carry its zone in the calendar system so availability shows correctly for a booker in another city. Displays show local time for the room they're mounted at. Keep the site code in every name so a remote booker instantly sees they're about to grab a room 4,000 miles away.

Rolling it out without a big-bang rename

You rarely get to name everything from scratch. To retrofit a scheme:

1. Lock the new convention (sites, floor padding, name-vs-tag split).
2. Rename room resources building by building, newest or lowest-traffic first.
3. Update door displays as you go — reassigning a display to its room takes seconds.
4. Communicate per building: "Floor 3's rooms are now BOS-03-…".

The rollout checklist works just as well for a rename as for a fresh install.

Frequently asked questions

Should the structured code or the friendly name go on the display?

The friendly name, large, with a small site/floor line beneath it. The structured code lives in the calendar system for sorting and filtering.

How do I stop people booking the wrong-size room?

Put capacity in the room's attributes and encourage filtering by it. A display also shows the room's name and next meetings so a mismatch is obvious on arrival.

What about themed names — are they a bad idea?

They're great for memorability, but keep them unique per site and always pair them with a structured code so lists still sort and group.

How many rooms is "too many" to name ad hoc?

Roughly once you pass one floor or one building. If you're scoping, see how many meeting rooms you need.

Does The Room Display care what I name rooms?

No — it shows whatever the room resource is called. Good naming just makes assigning displays and reading them effortless.

Related guides

• Meeting room names that people remember
• How many meeting rooms do you need?
• Meeting room booking best practices