Shared office workstations
Jose Losada / Unsplash, from the original FLYDESK article. Illustrative office, not a customer result.

Key takeaways

  • Distinguish capacity, inventory and booking-rule problems.
  • Check peak days and workspace suitability, not just average demand.
  • Test real workflows before selecting a provider or expanding a pilot.

Separate a booking problem from a capacity problem

When employees cannot find a suitable desk, the cause may be a full office, an inaccurate floor plan, a reservation nobody cancelled or rules people do not understand. Buying another tool will not resolve all four in the same way. Start by recording what failed, on which day and for which type of workspace.

This guide is an operational checklist, not a promise of savings or a ranking based on product testing. A booking describes intended use. It does not prove that someone arrived, stayed all day or did productive work.

Challenge 1: the average looks fine, but Tuesday is full

Compare demand with usable desks for each day, not only a weekly average. Exclude desks unavailable for maintenance or reserved for a particular requirement. Include the space needed for visiting colleagues and the different equipment people require.

For illustration, an office with 60 usable shared desks expects 35, 72, 66, 40 and 22 bookings across the week. Average demand is 47, yet Tuesday is 12 desks short and Wednesday six short. These are invented planning numbers. First check whether teams can change days without losing necessary collaboration; otherwise arrange suitable overflow or revisit capacity.

Reducing the number of reservations does not automatically reduce rent or operating cost. Assess changes against the work and against expenses that can actually change.

Challenge 2: reserved desks are apparently unused

Make cancellation easy to find and explain why it matters. Ask teams to review recurring reservations when projects, travel or working patterns change. Give employees a clear contact when a booked desk is unusable or someone else is occupying it.

If you are considering check-in or automatic release, ask the provider to demonstrate the complete workflow, including grace periods, delayed arrivals and equipment failures. Do not assume that a booking tool includes these features or that a missed check-in means a person did not attend. Start with a clear rule and an exception route before adding enforcement.

Challenge 3: a free desk is not a suitable desk

Keep location names, desk numbers and amenities consistent between the booking record and the physical office. Record practical differences such as monitor connections, adjustable furniture or quiet areas. Explain how people request a workspace that meets a specific need without making private information visible to colleagues.

Walk the office with the map or list used for reservations. Can a new starter find the right floor, locate the desk and connect their equipment? Assign an owner to update the inventory after moves or maintenance; a polished map of the wrong layout creates more confusion, not less.

Challenge 4: last-minute changes cause competing claims

Define how far ahead people may reserve, whether part-day use is supported and which route is authoritative. A team chat message and an app reservation should not create two competing allocation systems. State what happens if no suitable desk is available before someone starts travelling.

Test a cancellation, a same-day change, a failed reservation and a colleague booking on someone else's behalf if that workflow is needed. Any priority rules should be understandable and have a named decision owner. A QR code can provide a convenient link, but it is not by itself a check-in system or evidence that capacity is accurate.

Challenge 5: office days do not bring collaborators together

Coordinate the purpose and participants of an office day before filling seats. A project workshop may need a room and several desks; an individual focus day may need a different setting. Do not use nearby seat availability as the only reason for asking a team to attend.

Keep shared-day planning and resource booking connected, with clear instructions about whether employees need to complete one action or two. Consider parking and other constrained resources separately instead of assuming a desk reservation includes them.

Evaluate providers with the same real scenarios

FLYDESK, Envoy, Robin, Kadence and Eden appeared in the original article. Retain that shortlist as a starting point, not a claim that their products, plans or commercial terms are equivalent. FLYDESK is the publisher of this guide and offers desk and shared-resource booking; confirm your required workflows and plan in a demonstration.

The official Envoy, Robin, Kadence and Eden pages below provide current product information. For each provider, demonstrate your actual inventory, a peak day, cancellation and an exception. Ask which functionality needs configuration, a particular plan or another product. Request commercial and data-handling terms separately; this guide has not independently tested every service.

Run a small pilot before changing the whole office

Choose a representative area and agree what success means before introducing the process. Review peak-day shortages, failed bookings, cancellations, unsuitable desks and employee feedback. Separate planned reservations from any independently observed use, and explain how operational data will be used and retained.

  • Assign owners for inventory, rules, employee support and review.
  • Test access from the devices employees actually use.
  • Include someone unfamiliar with the office in the trial.
  • Record exceptions and fix the rule or workflow that caused them.
  • Expand only when people can reliably find and release suitable space.

Continue reading