Meeting Room Booking Screen: What to Show

Two separate arguments hide inside the phrase "meeting room booking screen". The first is a design argument about what fits on a panel the size of a paperback. The second is a policy argument about what a person standing in a corridor should be allowed to do to a meeting they are not part of.

Vendors answer the first with feature lists and the second by shipping every button and letting you turn things off later. Both defaults are wrong. The design answer is that four items earn their place and everything else is decoration, and the policy answer is that the number of destructive actions available to an anonymous passer-by should be zero.

This is a post about screens and rules rather than hardware. If you are still choosing a device, start with the practical guide to what goes outside the door and come back.

The design constraint nobody designs for

The panel is read while walking, from two to five metres, in about two seconds, by someone whose attention is on their laptop and the meeting they are late for. Every design decision follows from that sentence.

The honest test for any element on the screen: could a person answer "can I go in there" without stopping? If they have to stop and squint, the element is not helping, it is competing.

Contrast matters more than resolution. E-ink and a matte finish beat a glossy IPS panel in a corridor with ceiling spots, because the failure mode of a glossy screen is a perfect reflection of a light fitting sitting exactly over the status word. That is a mounting problem too, covered in how to mount a meeting room display.

What earns its place

Status right now. The largest thing on the screen, by a lot. It should read as a state before it reads as a word: a filled block, an inverted panel, something you register at five metres with your peripheral vision. If your screen is monochrome e-ink, that means using the whole area, not a coloured dot.
Time until the state changes. "Free for 40 min" or "Busy until 15:30". This is the single most useful line on the panel and the one most often missing. The person in the corridor is not asking whether the room is busy, they are asking whether they can have it for the next twenty minutes.
What is next. One line: time and, if policy allows, a title. Two lines at most. This is what stops someone starting a call in a room that empties in six minutes.
The room name. Exactly as it appears in the calendar system people book from, and exactly as it appears on the door. Three different names for one room is a surprisingly common and entirely self-inflicted problem. See meeting room naming conventions.

Optional, if there is genuinely space left: capacity, one or two facilities, and a small freshness marker so a frozen panel is detectable. That marker matters more than it sounds, because a dead panel shows its last frame forever and looks identical to a working one.

What does not earn its place

The full day agenda in 8pt. Six bookings listed in type nobody can read from standing distance. It looks thorough in a screenshot and is unreadable on a wall. If someone needs the full day, they will look at their laptop.
Organiser photos. A person's face on a wall in a corridor is a data protection question you did not need to open, and it takes space from the status block. If you show organisers at all, show a name, and check that your calendar settings are not already stripping the private flag from meetings that were marked private. That mechanism is in how the panel talks to your calendar, and the compliance framing is in GDPR and meeting room booking data.
Weather, news tickers, company announcements. These belong on a signage screen with a content owner, not on a 7 inch panel with one job. We separate the two categories in room panels versus signage screens.
A large clock. Everyone in the corridor has a phone and most have a watch. A clock competes with the status block for the largest-element slot and wins, because clocks are inherently attention-grabbing.
Utilisation percentages and analytics. Those are for a dashboard read by one person once a month, not for a wall. Meeting room analytics covers where they do belong.

The counterargument to my own list: on a larger panel (10 inch and up) the day agenda genuinely does help in rooms with high turnover, because people plan around the gaps. Fine. Show three upcoming slots, not twelve, and keep the status block dominant.

The permissions question

Now the harder half. A booking screen with touch is a control panel for other people's calendars, mounted in a public corridor, with no authentication. Decide each action deliberately.

Book the room from the wall

The least dangerous action, because it only takes time that was free. It also captures ad hoc use that would otherwise be invisible, which is the strongest argument for touch panels and the reason utilisation data from a walk-in culture is fiction without it.

Bound it: allow bookings that start now, cap the length (30 or 60 minutes is plenty), and do not allow booking into tomorrow from the wall. A panel is for the next hour, not for planning. The mechanics of the flow are in booking a room on the display.

End someone else's meeting

Do not enable this for anonymous users. It is the one action on the panel that destroys something a colleague created, and there is no undo that puts everyone back in the room.

The abuse case is not hypothetical and it is not usually malicious. Someone needs a room, sees a room with two people in it who look like they are finishing, taps End, and the room shows free. Now a third party walks in on a meeting that never ended. This is a social problem created entirely by a button.

If you must have it, restrict it to the organiser, which requires identity, which the wall does not have. That constraint is the whole argument for QR-based actions below.

Extend

Extend looks harmless and is not. It silently takes time from whoever is next, and the person who loses the room finds out by standing outside it. The rule that works: allow extension only when the following slot is free, cap it at one extension of 15 minutes, and refuse if another booking starts within 30 minutes. If the next slot is booked, the panel should say so rather than offering a button that fails.

Check in

The most defensible touch action of all, because it can only release a room, never take one. A check-in requirement plus automatic release after 10 minutes is the single most effective fix for the empty-but-booked problem, and it is worth more to most offices than every other interactive feature combined. See reducing no-shows, automatic room release and the real cost of a ghost meeting.

One honest caveat. Check-in adds a step to everyone's day to solve a problem caused by a minority of bookings, and if you set the release window too short you will strand people who are two minutes late from another building. Ten minutes is a reasonable default and you should say so publicly, in writing, before you switch it on.

The anonymous booking problem

A wall panel has no idea who is standing in front of it. That has consequences that people discover months later.

Whoever books from the panel is recorded as whatever account the display uses, so the calendar entry says "Meeting Room 3" or a service account name rather than a person. Then nobody can be contacted when the room is needed, no-show reminders have no recipient, and your utilisation report cannot tell you which team is consuming the rooms. You have collected the booking and lost the information that made it useful.

Four ways out, roughly in order of how much friction they add:

A QR code. The person scans it, the booking page opens on the phone they are already holding, and they are already signed in to Google or Microsoft on that phone. Identity solved, no keyboard on the wall, no anonymous action. See QR code meeting room booking.
Chat. A Slack or Teams command that books the nearest free room. Identity comes free with the chat account, and people are already in that window. Booking rooms from Slack covers the pattern.
Badge tap. Clean when you already have readers, and a project with an access control vendor when you do not. It also creates a record of who was physically at which door, which your works council or data protection officer will want to discuss.
PIN on the panel. Works, gets shared within a week, and turns into a shared secret written on a whiteboard. Treat it as attribution theatre rather than identity.

Why read-only plus a QR code often wins

Put the two halves together and a specific design falls out. A read-only panel at the door showing status, time remaining, next up and the room name, with a QR code in a corner that opens an authenticated booking page on the phone.

What you get: no anonymous destructive actions, real identity on every booking, a panel that can be e-ink and therefore battery-powered and therefore mountable anywhere without an electrician, and a mounting height chosen for legibility instead of reach. What you lose is the tactile satisfaction of tapping a wall, which demos beautifully and is used, in most offices, a handful of times per room per week.

The honest counterargument: QR codes require a phone, a camera, a work account on that phone, and a moment of goodwill. Visitors will not have the account. People with an aversion to scanning codes will not scan. If your building has a lot of external guests booking rooms on the fly, a touch panel with a bounded book-now action really is the better tool, and you should accept the anonymous booking trade that comes with it.

Accessibility, which quietly decides the mounting height

The moment a screen has controls on it, those controls become operable parts, and operable parts have to be reachable by someone seated in a wheelchair. Under the ADA Standards the reach range is a maximum of 1220 mm and a minimum of 380 mm above the floor. In practice that means a touch panel centred around 1100 to 1200 mm, with every button inside the range rather than just the top of the screen.

A read-only panel has no operable parts, so it can go at 1400 to 1600 mm to centre, which is eye level for a standing adult and considerably more legible in a corridor. European guidance points the same direction: ISO 21542 and the EN 17210 family put controls in a similar band, and national building regulations vary, so check the ones that apply to your building rather than assuming the American figures transfer.

Three consequences people miss:

Touch costs you legibility. Lower panel, worse sightline, more likely to be blocked by a person standing in front of it. That is a real cost of interactivity, paid every day by everyone who walks past.
Touch targets have a minimum size. WCAG 2.2 sets a minimum target size of 24 by 24 CSS pixels at level AA, and that is a floor for a mouse-driven web page, not a good target for a cold finger at a door. Design bigger. Four large buttons beat nine small ones.
E-ink and touch are an awkward pair. A partial e-ink refresh takes a noticeable moment, so a tap does not produce instant visual feedback, so people tap again. If you want a genuinely good touch experience, use an LCD and accept the cable.

Also worth writing down: a screen at 1150 mm is at head height for a child and at kicking height in a busy corridor. Panels near doors that swing get hit. That is a mounting decision, not a software one.

A default policy that survives contact with an office

If you want a starting position to argue with, use this one:

Read-only panel at the door, 1400 to 1600 mm to centre.
Status, time until change, next up, room name. Nothing else above the fold.
Titles shown for ordinary meetings, suppressed for anything marked private, and verify at the calendar layer that the private flag actually survives to the room's copy.
QR code in the corner for booking, which carries identity from the phone.
Check-in required, automatic release after 10 minutes, announced in writing two weeks before it goes live.
No End Meeting button available to anonymous users. Ever.
Extension allowed only into a free slot, one extension, 15 minutes.

Then publish the rules where people can read them, because a screen enforcing an unwritten policy generates more arguments than it settles. The meeting room etiquette guide is a reasonable template.

Where Lobby fits

Lobby is deliberately on the read-only side of this argument. It reads Google Workspace or Microsoft 365 room resources and never writes to your calendar, which means it cannot create, extend or end a booking, and it means an anonymous person at the panel cannot destroy anything. Booking happens where identity already exists: in Outlook or Google Calendar, or through the Slack /book command on Pro Unlimited.

The panel itself is a 7.5-inch e-ink display that hangs on one screw via the keyhole slot on the back, battery-powered for 3 to 6 months depending on refresh rate, and readable from about 5 metres, which is what makes the higher and more legible mounting position possible. The same view is available as a virtual display (a URL in a browser tab on any tablet, TV or monitor you already own) and as a room overview board covering every room on one screen. All three types are on the same plan: free forever up to 3 active displays, USD 30 per month billed yearly for unlimited, USD 60 per month billed yearly for Pro Unlimited, which adds custom templates, your own logo with Lobby branding removed, room feedback with free QR stickers, and 5-minute e-ink refresh instead of 15. Hardware is bought direct from the manufacturer from USD 69 per unit and owned outright, with no markup from us.

The limitation is the same as the design position, stated plainly: if you want tap-to-book, tap-to-extend or tap-to-end on the wall, Lobby does not do that and a touch panel from another vendor will serve you better. Lobby also does no desk booking or visitor management in the rooms product, no room automation or AV control, no occupancy sensors, no floor plans, no enterprise SSO or SCIM at scale, no MDM on the e-ink hardware, and no on-premises Exchange without a hybrid setup.

TL;DR

Four things earn their place on a booking screen: status now, time until the state changes, what is next, and the room name. Everything else competes with them.
"Free for 40 min" answers the question people are actually asking. "Free" does not.
Cut the full day agenda in 8pt, organiser photos, weather, news and the large clock. They are signage content on a panel that has one job.
Booking from the wall is the safe interactive action if you bound it: starts now, capped length, no booking into future days.
Do not give anonymous passers-by an End Meeting button. The common abuse is not malice, it is someone in a corridor guessing that a meeting is nearly over.
Extension silently takes time from the next booker. Allow it only into a free slot, once, for 15 minutes, and refuse when a booking starts within 30 minutes.
Check-in with a 10-minute automatic release is the most valuable touch feature, because it can only free a room, never take one. Announce it in writing before switching it on.
A wall panel has no identity, so bookings made on it are attributed to a service account and your utilisation data loses the person. A QR code hands the booking to an already signed-in phone and solves this for free.
Touch turns the screen into an operable part, so the ADA reach range (1220 mm maximum, 380 mm minimum) pushes it down to roughly 1100 to 1200 mm centre, against 1400 to 1600 mm for read-only. Interactivity costs legibility every day.

Sources

US Access Board: ADA Accessibility Standards, for reach ranges and the definition of operable parts that drives the mounting height of a touch panel.
W3C: Web Content Accessibility Guidelines 2.2, for the minimum target size success criterion referenced above.
Microsoft Learn: Set-CalendarProcessing, for the settings that control whether a private meeting stays private in the room's own calendar.
EUR-Lex: Regulation (EU) 2016/679 (GDPR), for the data minimisation principle that applies to organiser names and photos on a wall in a shared corridor.
Lobby hardware, for the e-ink hardware price and volume tiers quoted in the Lobby section.

Meeting Room Booking Screen: What It Should Show, and Who Should Be Allowed to Touch It