Request a quote
Emergency SectorsCareers About us Blog Get in touch
Long open-plan office with glass walls and colleagues at their desks in the sunlight

Desk booking software: the system, and what it needs from your network

Desk booking software looks like an app decision. In practice it rests on three things you already have: your user accounts, your Wi-Fi, and the question of who will later see who sat where. Sort those out first and almost any product will do; skip them and in six months you have a desk booking system nobody looks at.

6 min read Written by the ITproposal team
Short answer

Start with the question the system has to answer: are there too few desks on busy days, or does nobody know where colleagues are sitting? That decides whether you need check-in and sensors or just a floor plan.

Connect desk booking software to your existing accounts with single sign-on and automatic provisioning. Otherwise you maintain a second list next to HR that is always out of date.

Sensors and check-in need Wi-Fi at every desk, a separate network segment for the devices and an early decision on who sees the occupancy data. UK GDPR and the ICO’s guidance on monitoring workers apply.

Desk booking software: the question it has to answer

At its core, desk booking software does three things: it shows which desks exist, it lets someone reserve one, and it releases a desk when that person does not turn up. Everything beyond that, from interactive floor plans to utilisation reports, is extra.

Which of the three you need depends on the problem you actually have. There are two, and they ask for different things:

  • Too few desks on busy days. Then releasing no-shows matters most. A desk that is booked but stays empty is worse than no booking at all, and without check-in you cannot tell the difference.
  • Nobody knows where colleagues are. Then visibility matters most and check-in is secondary. A shared floor plan showing who is in on which day often solves it.

Write that question down before you watch any demos. A vendor will show you the full feature list, and the features you do not need still have to be administered.

A dedicated product, Microsoft 365, or part of something bigger

There are roughly three routes. Dedicated desk booking software, usually a cloud service with an app and a web portal. The features in Microsoft 365: Microsoft has brought desk and room booking into Outlook and Teams with Places, which is attractive if everyone already works there all day. And a module of a wider workplace or facilities platform, alongside visitor management and room booking.

The choice between them is less about features than about where you want the administration to live. For each route, ask:

  • Which licence it needs, and whether everyone needs one or only the people who book.
  • Whether the data can be exported, floor plans and booking history, for when you switch later.
  • Where the data is held and whether a data processing agreement comes with it, because bookings are personal data.
  • How check-in works, because that determines what the desk booking system needs from your network (see below).

Tie it to your identity, not to a separate list

The most underestimated part of a desk booking system is the user list. A product with its own usernames means a second list next to your HR records, and it always lags: new starters cannot book in their first week and leavers keep their regular Tuesday desk.

So insist on two things. Single sign-on with your existing accounts, for most organisations Microsoft Entra ID, so signing in needs no new password and multi-factor authentication comes along. And automatic provisioning and deprovisioning (often via SCIM), so that someone who leaves disappears from the system the moment their account is disabled.

Use the groups you already have. If a team may only book in its own neighbourhood, or a department has fixed desks, handle it with the group that already exists in your identity platform rather than a manual list inside the product.

What check-in needs from your Wi-Fi and network

Check-in comes in a few forms, and each puts a different demand on the network:

  • A QR code or NFC tag on the desk. The colleague scans it with a phone. Simple, but it only works where there is mobile signal or Wi-Fi, including the corner by the stairwell where nobody sits today.
  • Check-in through the network. The system sees a laptop connect at a particular spot, on an access point or a network port. That needs integration with your network management and a network where you know which port or access point belongs to which desk.
  • A kiosk screen at the entrance to a zone. Useful for people without the app, and it needs a wired connection with Power over Ethernet in a place that rarely has a socket.

Have the Wi-Fi measured before you introduce check-in, and measure the desks that will be used, not the ones people use now. An office moving to hot desking often shifts where it gets busy.

Occupancy sensors: which kind, and what they connect to

Sensors measure whether a desk is actually occupied, regardless of what has been booked. Some sit under the desk and detect movement or heat; others are ceiling-mounted and count a whole area. Choose one that measures occupancy, not people: a sensor that says someone is there, not who. Cameras do not belong here.

For IT, three questions matter more than the type:

  • How they communicate. Many sensors run on batteries and talk wirelessly to a gateway, which in turn sits on your network. That gateway belongs in its own segment, separate from user devices. How to set that up is in our article on what a VLAN is.
  • Who updates the firmware. A gateway is a network device running software, and that software either gets updates or it does not. Agree who does it.
  • Who replaces the batteries. A hundred battery sensors means a ladder a hundred times every few years. Put it in the maintenance plan, or they go quiet one by one and the occupancy data slowly stops being true.

Who sees the occupancy data

Desk booking software knows who was in the office and when, and with sensors added, for how long. That is personal data, and it is suitable for checking attendance even if that was never the intention.

Decide in advance what is kept per person and for how long. For space planning you usually only need figures per area and per day. Individual bookings can be deleted or aggregated after a short period, and most products let you configure that. Also decide who may open reports per person; ideally nobody.

In the UK, UK GDPR applies and the ICO has published guidance on monitoring workers that covers exactly this: be transparent, collect no more than you need, and consider a data protection impact assessment where monitoring is involved. Talk to staff, and to any recognised union or works council, before you buy rather than at rollout.

Where our work stops

We install the network and Wi-Fi the system relies on, place gateways, sensors and kiosk screens, segment the network and connect the product to your accounts. After that we manage it as part of the workplace.

  • The software belongs to a third party. The desk booking software comes from its vendor, with its own terms and support. We help choose and integrate, but we are not the maker.
  • The policy is yours. How many desks per employee, whether teams get fixed neighbourhoods and how often people come in is an organisational decision.
  • So is the legal assessment. Whether sensors are proportionate, and how you consult staff, is for a lawyer or your data protection officer. We supply the facts about what is measured and stored.
  • No building work. We run data cabling and mount equipment; electrical circuits and ceilings are for the installer.
Frequently asked

Questions we get about this

The five that come up most often.

What is the best desk booking software?

It depends on your problem. If there are too few desks on busy days, choose a system with solid check-in and automatic release of no-shows. If you mainly want to know who is coming in, a simple overview or the feature in Microsoft 365 is often enough. Either way, check single sign-on, automatic provisioning and whether you can export your data.

Can you book desks in Outlook or Teams?

Yes, Microsoft has brought desk booking into Outlook and Teams with Places. The advantage is that no separate app is added and your accounts and groups are already correct. Do check which licence it requires and whether its check-in and reporting do what you need.

Do I need occupancy sensors?

Only if you want to know whether a desk is actually used, separate from the booking. For releasing no-shows, check-in is often enough. Sensors need a gateway on its own network segment, firmware updates and battery replacement, and someone has to own that maintenance.

Is using occupancy sensors allowed under UK GDPR?

It can be, provided the monitoring is transparent, proportionate and limited to what you need, and the ICO’s guidance on monitoring workers sets out what that means. Sensors that count occupancy rather than identify people make that much easier. Whether it holds in your situation is for a lawyer or your DPO; we supply the technical facts.

Do you supply the desk booking software too?

We help choose it, connect it to your accounts and install the network, Wi-Fi, sensors and screens. The software itself comes from its vendor, with their terms and support. The policy, such as how many desks per employee, is yours to set.

Related services

Further reading

What the desk booking system rests on.

Shall we check what your network can already handle?

Tell us how many desks there are, which product you are considering and whether sensors are part of it. We will tell you what Wi-Fi, cabling and network segmentation are needed before the first desk is booked.

Practical IT knowledge in your inbox

New guides on management, security and the workplace, written by the people doing the work. No sales talk, and you can unsubscribe in one click.

We use your address for the newsletter only. See our privacy policy.

Request a quote Call