LOBBY
Guides· 9 min read

Room Scheduler: The Word Means Four Different Things. Here Is How to Tell Which You Need

Ask four people what a room scheduler is and you get four answers: the panel by the door, the software behind it, the office manager who actually does the scheduling, and the rules that decide who gets the room. Each has a different fix, and buying the wrong one is how offices end up with a panel that solves nothing.

Four people in the same procurement thread can use the phrase "room scheduler" and mean four unrelated things. The AV vendor means a panel screwed to a wall. The IT manager means a piece of software. The operations lead means Sofia, who runs the booking spreadsheet. The consultant means the rules that decide who gets the boardroom on Thursday.

That is not a pedantic distinction. It is the reason offices buy hardware to solve a policy problem and then wonder why the complaints did not stop. A panel on a wall cannot stop the sales team booking the biggest room for a two person call. Better rules cannot stop two groups arriving at the same door.

Here are the four meanings, each taken seriously, including the human one, because in a lot of 20 to 60 person offices the room scheduler is a person and the right first move is to give that person better rules rather than more software. Then a short diagnostic for working out which one you actually have.

Meaning 1: the panel by the door

In the AV world, "scheduler" is a product category. Zoom calls the mode a Scheduling Display. Logitech sells the Tap Scheduler. Neat sells the Neat Pad, which can run either as a room controller or as a scheduling panel. Poly's touch controllers can be set to a room scheduling role. Cisco has the Room Navigator. Crestron sells room scheduling touch panels. If a salesperson says "how many schedulers do you need", they are counting doors.

One caveat before you compare any of them on price. Several of those devices are broader in scope than a scheduling panel: the Neat Pad, Poly's touch controllers and the Cisco Room Navigator are also in-room video controllers, and are sold and licensed as part of a video conferencing system. Compare them on the scheduling role only when scheduling is the job you are buying for, and compare the whole system when it is not.

What a panel is genuinely good at is narrow and valuable: answering "can I go in" from a few metres away, without anybody touching anything. The screen state is the whole product. Colour or a clear label for free or busy, the room name, what is next, and when the state changes. Everything beyond that is decoration for a device that people look at for two seconds while walking.

Three things to get right if this is what you need.

  • Mounting. Read-only panels sit comfortably at 1400 to 1600 mm centre. Touch panels have to keep every target within reach, which pulls them lower. Get this wrong and you either have a screen nobody can read or a screen nobody can press. The detail is in how to mount a meeting room display.
  • Power. Power over Ethernet is clean when the cabling exists and expensive when it does not. Battery panels move the cost from the electrician to a recurring charging task. Mains means a visible cable or a wall chase.
  • Failure behaviour. A panel that has lost its calendar connection normally keeps displaying the last data it received, and on e-ink the image survives a flat battery entirely, so a dead device looks exactly like a working one showing "free". Ask any vendor to show you what the screen does when the network drops and when the device stops reporting.

The counterargument, which is worth stating plainly: a panel does not change anybody's behaviour. It does not stop no-shows, it does not recover an unused room unless it is paired with check-in and release, and it does not stop the boardroom being booked for two people. It solves confusion at the door. That is one problem, it is a real one, and it is the only one it solves. If your complaint list is mostly about behaviour, panels are the wrong first purchase.

If a specific vendor's panel is already on your shortlist, the alternatives posts for Logitech Tap Scheduler, Poly TC10 and Crestron room scheduling compare them on price shape and licensing.

Meaning 2: the software that schedules the rooms

The second meaning is the system: whatever holds the bookings, resolves conflicts, and decides that 10:00 on Tuesday belongs to one team and not another. In almost every office reading this, that system already exists and is called Google Calendar or Outlook.

Rooms are first-class objects on both platforms. On Microsoft 365 they are room mailboxes that accept or decline on their own, with AutomateProcessing, a booking window, a maximum duration, conflict rules and capacity. On Google Workspace they are calendar resources with buildings, floors, capacity and features. The scheduling engine is included in the licence you already pay for, and it already handles conflict rules, capacity, booking windows and duration limits without any additional product.

What third-party software adds is real but specific: displays at the door, check-in and auto-release, utilisation reporting, floor plans, approval workflows beyond a delegate, and admin that an office manager can use without a global admin role. That list, and what each item is worth, is the subject of our meeting room booking system guide.

The thing to check before you buy in this meaning: does the tool read your calendar, or does it become a second source of truth. If people can book in two places and the two places do not reconcile perfectly, you have not bought a scheduler, you have bought a second calendar to keep in sync. That distinction is the whole of meeting room display vs room booking software.

Meaning 3: the person

In a large share of 20 to 60 person companies, the room scheduler is a human being. Somebody in operations or an EA who gets asked "can you find us a room for six on Thursday", who knows that the room labelled as seating eight really seats five with the whiteboard out, and who is the only person who knows that the Wednesday board slot is untouchable.

This gets treated as a problem to be automated away. It usually is not. A person applying judgement is better at room allocation than most software, because the important variables are not in any system: this client visit matters more than that internal sync, this team needs the room with the good camera because two of them are remote, the workshop needs the room you can rearrange.

The failure mode is not that the person exists. It is that the knowledge lives only in their head. It looks like this: they go on holiday, and for two weeks the office books rooms badly, double books the good one twice, and somebody moves a client meeting into the room with the noisy air conditioning. Nothing is written down, so nothing survives the absence.

The fix, roughly in order of how much effort each takes:

  1. Write down the rules they already apply. One page. Which rooms need asking about, which are free for anybody, how far ahead you can hold the big one, what happens when two teams want the same slot. This is a transcription job, not a policy exercise, and it takes an hour with the person who already knows.
  2. Encode what the calendar can enforce. Booking windows, maximum durations, capacity, equipment attributes and restricted booking on the two rooms that need it. Every rule you move from a person's head into the resource settings is a rule that works when they are away.
  3. Give them the tools to see the whole estate at once, so that answering "what is free on Thursday afternoon" takes ten seconds rather than opening six calendars.
  4. Give them admin rights over rooms without giving them the keys to the tenant. Adding a room, renaming one, changing capacity and fixing a display should not need a ticket.

Only after all four does it make sense to ask whether software would remove the remaining work. Often it removes some of it and leaves the judgement calls, which is the correct outcome. The wider version of this job is set out in the office manager's meeting room operations playbook.

Meaning 4: the scheduling logic

The fourth meaning is the least visible and the one that decides whether the other three work. It is the set of rules that determine who gets a room: booking windows, duration caps, approval queues, priority, and what happens when two claims collide.

The important rules, and what each one is for:

  • Booking window. How far ahead a room can be held. Without one, the best room disappears for the next quarter within a week of anybody discovering they can do that. Ninety days is a common starting point for general rooms, shorter for the popular one.
  • Maximum duration. Stops a single booking eating a day. Four hours is a reasonable default with an exception for the workshop space.
  • Conflict rules for recurring series. This is where quiet double bookings come from. On Microsoft 365, AllowConflicts, ConflictPercentageAllowed and MaximumConflictInstances decide whether a weekly series may partly overlap an existing booking. Left at a permissive setting, a series lands on top of other meetings and nobody finds out until two groups meet at the door.
  • Approval and priority. Some rooms need a gatekeeper. Both platforms can do this without extra software: on Microsoft 365 with BookInPolicy, AllBookInPolicy and ResourceDelegates, on Google Workspace by restricting who can book a resource. Use it on the two or three rooms that genuinely need it and nowhere else, because an approval queue on a huddle room is a way of making a four person meeting take a day to arrange.
  • Recurrence expiry. Require an end date on recurring series and audit anything older than six months. One weekly series that nobody attends removes 52 slots a year from the room everybody wants, which is the arithmetic behind recurring meetings blocking rooms.
  • Release rules. How long an unclaimed booking is held before the room goes back. Fifteen minutes for a longer meeting, ten for a short one, with a visible countdown. Covered in how to release a meeting room automatically.

Two honest warnings about rules. They are invisible when they work, so nobody thanks you, and every one of them creates a case where somebody legitimately needs the exception. Write down who can grant the exception and how, or your careful ruleset becomes a queue outside one person's desk. And do not stack them: a system with a booking window, a duration cap, an approval step and an aggressive release rule feels hostile, and people respond to hostile systems by booking a room under a colleague's name.

How to tell which one your problem is

Take your last ten complaints, not your impression of them, and sort each into one bucket.

  • "We stood outside arguing about whether the room was free." "The meeting ended early and nobody knew the room was available." That is meaning 1. You need a screen at the door. No amount of policy fixes it.
  • "The room does not show up in the picker." "Two meetings got accepted for the same slot." "We have no idea how much our rooms get used." That is meaning 2, and probably configuration rather than a purchase. Start with the Microsoft 365 checklist or the Google Workspace checklist.
  • "Nobody except Sofia knows which room to use for what." "When she is off, room booking falls apart." That is meaning 3. Write the rules down before you buy anything.
  • "The same team holds the best room every week for four people." "Someone booked the boardroom for a year." "People book rooms they never use." That is meaning 4. Rules and one uncomfortable conversation, with auto-release doing the enforcement so it is not personal.

The pattern most offices find is that complaints cluster in two buckets, not one, and usually meanings 1 and 4: confusion at the door plus behaviour nobody has written a rule about. That combination is cheap to fix. Displays plus a one page policy plus release rules will clear most of it, and neither half works well without the other.

Where Lobby fits

Lobby only addresses meaning 1, and does it by reading the system you already have. It connects read-only to Google Workspace or Microsoft 365 room resources, never writes to your calendar, and drives three display types on the same plan: a 7.5-inch e-ink panel by the door readable from about five metres, a virtual display which is the same view as a URL on any tablet, TV or monitor you already own, and a room overview board showing every room on one screen. The overview board is the one that helps meaning 3, because it gives whoever runs your rooms a single glance at the whole estate.

Free forever up to three active displays with no credit card, USD 30 per month billed yearly for the Unlimited plan, USD 60 per month billed yearly for Pro Unlimited, which adds custom templates, your own logo, room feedback with QR stickers, a Slack /book command and a five minute e-ink refresh. Never per room, never per user. Hardware is bought direct from the manufacturer at USD 69 per device at 1 to 9 units, dropping to USD 62.99 at 10 or more, owned outright, with no markup from us. Setup takes under ten minutes with no sales call and no integrator.

What Lobby does not do, which matters here more than usual: it is not a scheduling engine. It cannot enforce a booking window, run an approval queue, set priority between teams, or release a room, because it does not write to your calendar. Those are meaning 4 problems and they are solved in Set-CalendarProcessing or the Google Admin console, for free. It also does not do desk booking, visitor management, floor plans or wayfinding, occupancy sensors, room automation or AV control, digital signage playlists or video, enterprise SSO or SCIM at scale, MDM on the e-ink hardware, or on-premises Exchange without a hybrid setup, and there is no mobile app.

TL;DR

  • "Room scheduler" means four things: the panel by the door, the software platform, the person who does the scheduling, and the rules that decide who gets the room.
  • The AV industry uses it for hardware. Zoom's Scheduling Display, Logitech Tap Scheduler, Neat Pad, Poly's controllers, Cisco Room Navigator and Crestron panels all sit in this meaning, though several of those devices are video controllers as well, so compare on the scheduling role only when that is what you are buying.
  • A panel solves exactly one problem: confusion at the door. It does not change behaviour, does not stop no-shows on its own, and does not stop the wrong room being booked.
  • Check what a panel does when it loses its connection. Most keep showing the last data, and on e-ink a flat battery leaves the last image in place, so a dead device looks like a working one showing "free".
  • The scheduling engine you need almost certainly already exists in Microsoft 365 room mailboxes or Google Workspace calendar resources, and is usually half configured.
  • In many 20 to 60 person offices the room scheduler is a person, and the first fix is to write down the rules in their head, not to buy software that cannot hold the judgement they apply.
  • The rules that matter are the booking window, maximum duration, recurring conflict settings, approval on the two rooms that need it, recurrence expiry and release timing.
  • Do not stack rules. A window plus a cap plus approval plus aggressive release feels hostile, and people work around hostile systems by booking under someone else's name.
  • Sort your last ten complaints into the four buckets. Most offices land in two, usually the door and the rules, and that pair is cheap to fix together.

Related reading

Sources

Prices verified 11 August 2026. Tier-based and quote-based pricing changes, so confirm directly with each vendor.

Try Lobby — free forever up to 3 displays

Room booking that just works.

Get started →