Meeting room display rollout plan: a two week

Twelve panels arrive on a Thursday. The obvious move is to come in on Saturday, mount all twelve, and have the whole office walk in on Monday to a transformed floor. Do not do that. On Monday you will get twelve simultaneous reports of problems, you will not know which are display problems and which are calendar problems that existed all along, and by Wednesday the collective opinion will be "the new screens are wrong" regardless of what is actually broken.

The rollout that works starts with two rooms and a week of watching. This post is a concrete plan: what to audit before you mount anything, what day one looks like, what week one actually feels like (including the questions people will ask), and how week two goes when you have already found the problems. It ends with the five failure modes, one of which is the classic where the display is completely correct and everyone blames it anyway.

The principle: two rooms, then everything

Start with the two busiest rooms. Not the quietest, not a test room nobody uses. The two busiest, because that is where you get the most feedback fastest, and because those are the rooms whose calendars are most likely to be a mess.

Two rooms gives you a comparison. When someone says the display is wrong, you can check whether the other room is also wrong. If both are wrong, it is your integration. If one is wrong, it is that room's calendar. That diagnostic is worth the extra week.

Before day one: the audit

Do this the week before hardware arrives. Every hour here saves three later.

1. Inventory the room mailboxes

You almost certainly have more rooms than you think, including two that were created for a project in 2022 and never deleted.

Connect-ExchangeOnline

Get-Mailbox -RecipientTypeDetails RoomMailbox -ResultSize Unlimited |
  Select-Object DisplayName, PrimarySmtpAddress, Office |
  Sort-Object DisplayName |
  Export-Csv .\rooms.csv -NoTypeInformation

Open the CSV and mark each row: keep, rename, or delete. Deleting the dead ones now means they do not appear in Room Finder confusing people during rollout.

2. Check and fix auto-accept

This is the single most common cause of "the display says free but it is not". If a room mailbox is set to delegate approval and the delegate is on holiday, bookings sit pending and the room shows free.

# See what you have
Get-Mailbox -RecipientTypeDetails RoomMailbox -ResultSize Unlimited |
  Get-CalendarProcessing |
  Select-Object Identity, AutomateProcessing, AllowConflicts,
    BookingWindowInDays, MaximumDurationInMinutes, AllowRecurringMeetings

# Fix one room
Set-CalendarProcessing -Identity room-nyhavn@example.com `
  -AutomateProcessing AutoAccept `
  -AllowConflicts $false `
  -BookingWindowInDays 180 `
  -MaximumDurationInMinutes 480 `
  -AllowRecurringMeetings $true `
  -AddOrganizerToSubject $true `
  -DeleteSubject $true `
  -DeleteComments $true `
  -RemovePrivateProperty $false

Decide the subject and organiser settings deliberately rather than accepting whatever the mailbox was created with. Whatever you set here is what appears on the panel in a corridor.

3. Clean up recurring bookings

In most offices that have existed for more than two years, a meaningful chunk of the week is consumed by recurring series that no longer happen. Pull the recurring meetings on your busiest rooms and, for each one, find the organiser and ask a single question: does this still happen every week?

Do this before the displays go up, not after. If you do it after, every cancellation looks like the new system deleted someone's meeting.

4. Agree the naming and fix the physical signs

The display shows the name from the calendar system. The wall shows whatever vinyl letters were applied when the office was fitted out. If those disagree, you have created a new problem on day one.

Walk the floor with the CSV from step one and write down what each door actually says. Then decide which one changes, and change it. Ordering new door signs takes a week, which is exactly why this is a pre-rollout task.

5. Check the network

Whatever you are mounting has to reach the internet from a corridor. Things that break this:

Captive portals. A guest network with a click-through page will silently fail for any device that has no browser and nobody to click.
WPA2-Enterprise. Plenty of low power display hardware supports WPA2-Personal only. Check the spec sheet before you assume the corporate SSID will work, and plan a dedicated IoT SSID with a pre-shared key if needed.
2.4 GHz coverage. Many low power devices are 2.4 GHz only. If your access points are 5 GHz optimised and the 2.4 GHz radio is disabled or weak in corridors, walk the floor with a phone and check signal at each door before mounting.
Outbound HTTPS. Devices need port 443 out, plus DNS and NTP. If your firewall does egress allowlisting, get the destinations added now rather than at 09:00 on rollout day.

Day one: mount two

Mount the two busiest rooms. Eye height, on the wall next to the door on the handle side, not on a swinging door.
Stand back 5 m and look at it. Can you read the state from the end of the corridor? If not, the whole point is lost. Adjust height or position.
Book a test meeting from Outlook or Google Calendar and confirm it appears within the expected refresh interval. Know what that interval is before you start staring at the screen.
Cancel it and confirm the panel clears. Cancellation is the path that breaks more often than creation.
Send one short message to the company. Two sentences: what the screens are, which two rooms have them, and where to report problems. Not a deck. Not a training session.

That is the whole of day one. Resist mounting a third.

Week one: watch

The purpose of week one is not to roll out. It is to find out what is wrong with your calendars.

Day 2 to 3: expect the "is this thing live?" question

People will walk past a panel showing a free room and ask whether it is working. This is normal and is mostly a design question: a display that shows nothing when a room is free looks broken. Make sure the free state says something affirmative and has a time on it, so it visibly updates.

You will also get somebody standing in front of it waiting for it to change. Explain the refresh interval once and it stops being a topic.

Day 3 to 4: fix the two rooms whose calendars were wrong

By midweek you will have found at least one of these:

A room whose working hours or time zone were never set, so the panel shows odd availability early or late.
A room where a delegate approval workflow is still in place despite step 2, because somebody re-enabled it.
A recurring series that occupies a slot every week and has not happened since spring.
Two rooms whose names have been swapped on the wall for years and nobody noticed until a screen made it explicit.

Fix each one and note it, because the same fix will apply to the other ten rooms next week.

Day 4 to 5: watch what people actually do

Specific things to look for, because they change your week two decisions:

Does anyone book from the panel, or do they all still use Outlook? If nobody books at the door, do not spend week two teaching them to.
Do people walk into occupied rooms less? That is the primary success metric and you can observe it directly.
Are people looking at the panel and then walking to a different room? That means your problem is finding a free room, and a room overview board near the entrance will do more than twelve door panels.

Week two: roll out the rest

Apply the calendar fixes from week one to every remaining room in one scripted pass, before mounting anything.
Mount the rest. With two weeks of practice this takes an afternoon. Do it in one go so the floor is consistent, which matters more than you would think for adoption.
Publish the booking policy. One page. Book what you need, cancel what you do not, rooms release after 15 minutes if nobody shows, do not book the boardroom for two people. Publish it after the displays exist so it lands as an explanation of something visible rather than an abstract rule.
Set the auto-release window. 10 to 15 minutes is the usual landing zone. Shorter feels aggressive to people who are genuinely walking from another floor. Longer stops recovering meaningful time.
Send the second and final message. All rooms are live, here is the policy, here is where to report a problem. Then stop sending messages about it.
Book a 30 minute review for four weeks out. Pull per-room booking data, look at the ghost rate, and decide whether anything needs to change. Then leave it alone.

The five failure modes

1. Rolling out everywhere at once

Covered above. You lose the ability to distinguish a systemic problem from a per-room problem, at exactly the moment when everyone is paying attention.

2. No announcement

Screens appearing overnight with no explanation generates a specific and unhelpful reaction: people assume they are being monitored. Two sentences in advance prevents an entire category of anxiety. If you have a works council, this conversation happens much earlier and is not optional.

3. Wrong room names on screen

The fastest way to destroy trust in a new system. A panel outside a door labelled "Nyhavn" that says "Meeting Room 3" tells every person who walks past that the system does not know where it is. Everything else it says is now suspect. Fix names before mounting, always.

4. Nobody owns the physical layer

Six months in, one panel is dark, one is crooked, and one is showing a room that was repurposed into a storage cupboard. Name one person per site who walks the floor once a month. It takes ten minutes and it is the difference between a system that works for years and one that quietly degrades.

5. The display is right and the calendar was already a mess

This is the big one, and the one that catches good IT teams. The panel faithfully renders a room that is booked solid by three dead recurring series, and the office concludes that the new screens have made booking harder. The screens changed nothing. They made an existing problem visible for the first time.

The defence is entirely in the pre-work: clean the recurring bookings, fix auto-accept and delete the dead rooms before anyone can see the result on a wall. A display is a mirror. If you do not like what it shows, the fix is upstream.

The one page checklist

Export the room mailbox list. Mark keep, rename, delete.
Set auto-accept, booking window, max duration, and subject and organiser handling on every room.
Audit recurring series on the busiest rooms and cancel the dead ones.
Agree naming. Order new door signs if needed.
Check WiFi band, authentication method, captive portal and outbound HTTPS at each door.
Day one: mount two busiest rooms, test create and cancel, send two sentences.
Week one: watch, fix what surfaces, do not mount anything else.
Week two: apply fixes fleet-wide, mount the rest in one afternoon, publish the policy, set auto-release.
Name a physical owner per site.
Review in four weeks, then leave it alone.

The buy side of this decision

The disclosure, since this is our blog. Lobby is a meeting room display that syncs in real time with Google Workspace and Microsoft 365 room resources. Relevant to a two week rollout: setup is under 10 minutes, self-serve, with no sales call and no integrator, and the Free plan covers up to 3 displays with no credit card, which is enough to run exactly the two room pilot described above at zero cost before you commit. The Free plan is free forever, not a time-limited trial, so the pilot does not expire on you mid-rollout.

The e-ink option is a 7.5 inch panel from USD 69 per room that you buy once and own, hanging on one screw or on adhesive strips, which an office manager puts up in a few minutes with no cabling, and which is what makes a one-afternoon week two rollout realistic. Hardware is bought direct from the manufacturer with no markup from us, and volume pricing applies: USD 69 each covers 1 to 9 units, then USD 62.99 at 10 or more, so a twelve room rollout is not twelve times the single-unit price. Taxes, duties and shipping are not included. There is also a virtual display that is just a URL in any browser tab, and a room overview board for a reception.

Paid plans are USD 30 per month billed yearly (USD 50 per month month to month) for Unlimited, and USD 60 per month billed yearly (USD 100 per month month to month) for Pro Unlimited, which adds a 5 minute e-ink refresh instead of 15, Lobby-hosted e-ink screens rendered and served in the EU, 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.

What Lobby does not do, plainly: no desk booking or visitor management in the rooms product, 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. The e-ink panel is battery powered (3 to 6 months on a charge) and refreshes on an interval, so it is not an instant touchscreen. And it will not fix your recurring bookings, your naming or your auto-accept settings. That is the audit above, and it is your week regardless of what you buy.

TL;DR

Start with the two busiest rooms, not all of them. Two gives you a comparison when something looks wrong.
Audit first: export room mailboxes, delete dead ones, set auto-accept and booking limits, cancel dead recurring series, agree naming, fix the physical door signs.
Check the network before mounting: captive portals, WPA2-Enterprise support, 2.4 GHz coverage at each door, outbound HTTPS.
Day one is two mounts, a create-and-cancel test, and a two sentence announcement.
Week one is for watching, not rolling out. Expect "is this live?", expect two rooms with broken calendars.
Week two: apply the fixes fleet-wide, mount the rest in one afternoon, publish a one page policy, set auto-release at 10 to 15 minutes.
Failure modes: everywhere at once, no announcement, wrong names on screen, no physical owner, and the display being right about a calendar that was already a mess.
A display is a mirror. If you do not like what it shows, fix things upstream.

Sources

Set-CalendarProcessing, Microsoft Learn (AutomateProcessing, BookingWindowInDays, MaximumDurationInMinutes, AllowRecurringMeetings and subject handling).
Manage resource mailboxes in Exchange Online, Microsoft Learn.
Configure rooms and workspaces for Room Finder, Microsoft Learn (propagation timing).
Create buildings, features and Calendar resources, Google Workspace Admin Help.
Track room and resource use in Google Calendar, Google Workspace Admin Help (post-rollout review data).

Meeting Room Display Rollout Plan: The First Two Weeks