Skip to content

How to introduce desk booking in a hybrid office

A hybrid-office booking system should answer one practical question before somebody commutes: where can I work, and is that place really available? The answer depends on resource design and operating rules, not on drawing more boxes in a calendar.

Updated · By

Start with the places people actually use

Do not begin by importing an organisational chart. Begin with the physical choices employees make: a shared desk area, a dedicated workstation, a quiet zone, a project room or a meeting room. Each option needs a name people recognise, a capacity and a booking mode.

  • Shared area: several people can reserve seats until its configured capacity is reached.
  • Dedicated workstation: one specific desk is booked as a complete resource.
  • Meeting room: one active booking occupies the room, regardless of how many attendees arrive.

Keeping these models separate prevents the common mistake of treating every office resource identically. Capacity matters for a hot-desk area; exclusivity matters for a specific workstation or meeting room.

Write the booking policy before configuring the tool

The software can enforce a rule only after the business has made it explicit. Decide how far ahead people can reserve, whether same-day bookings are allowed, when a reservation is released after a missed check-in and who can create operational blocks.

A useful starting policy is simple: publish real opening hours, limit advance booking to the period employees can reasonably plan, and make cancellation available until the desk can still be reused. Avoid adding restrictions merely because the system supports them.

Capacity must be evaluated for the requested time

A shared area with twenty desks is not unavailable because one reservation exists. The system must total the seats occupied by overlapping active bookings and compare the result with capacity. A request for three people is accepted only when at least three places remain for the whole requested interval.

Back-to-back reservations are valid: a booking ending at 11:00 does not conflict with another beginning at 11:00. Maintenance and internal events should be represented as operational blocks so the reason remains distinct from customer or employee usage.

Boris calendar showing reservations across office resources
A shared operational calendar keeps desks, rooms and blocks visible without giving them identical booking rules.

Make the mobile flow the default case

Most employees decide whether to attend the office away from a desktop computer. They need to see the date, available area, capacity and confirmation without zooming or navigating an administrative calendar. Staff may need more controls, but the everyday booking path should remain short.

Roll out with a measurable pilot

  1. Choose one office area and a representative group of employees.
  2. Publish the real desks and opening hours instead of an idealised floor plan.
  3. Run the pilot for two to four weeks.
  4. Review rejected requests, cancellations, no-shows and peak occupancy.
  5. Change only rules supported by those observations before expanding.

The goal is not to maximise the number of bookings. It is to make availability dependable enough that people trust the answer before travelling to the office.

Frequently asked questions

Should desk booking start from the org chart?

No. Start from the physical choices employees actually make: a shared desk area, a dedicated workstation, a quiet zone, a project or meeting room. Each needs a name people recognise, a capacity and a booking mode — and keeping shared areas separate from exclusive resources prevents the usual mistake of treating every office resource identically.

How far ahead should employees be allowed to book?

Far enough to plan, no further, and it is a policy decision to make before configuring anything. The software can only enforce a rule the business has already made explicit — how far ahead, whether same-day is allowed, when a missed check-in releases the desk, and who may create operational blocks. Avoid adding restrictions merely because the system supports them.

Is a shared area unavailable as soon as one person books it?

No. Capacity has to be evaluated for the requested interval: total the seats held by overlapping active bookings and compare that with capacity. A request for three people is accepted only if at least three places remain for the whole window.