Desk and Room Booking Systems

Booking systems record what people planned. Sensors record what happened. Comparing them answers questions neither does alone.

The space evidence in “Desk and Room Booking Systems” cannot explain by itself how project work is distributed or why a team uses the building differently. Used for does microsoft teams track your activity, does microsoft teams track your activity can add time and project context to aggregated occupancy findings, provided the two datasets keep separate purposes and are not merged into a hidden individual attendance score.

What booking data shows

Demand as expressed: what people asked for, when, and for how long.

For a public, independent reference related to “Desk and Room Booking Systems”, consult the GSA workplace innovation resources. Its principles provide a useful check on scope, terminology, governance and the claims made during procurement or review.

Patterns of intent: which rooms are sought after, which times are contested.

And the administrative reality: how far ahead people book, how often they change.

What it does not show

Whether anybody turned up. The no-show rate in meeting rooms is substantial in most organisations and is the single largest distortion in booking-derived utilisation.

How many came. A room booked for twelve and used by three looks fully booked.

How long they stayed. Bookings run to the hour; meetings do not.

And unbooked use, which in open settings is most of the use.

The ghost booking problem

Recurring meetings that continue after they stop being needed.

Blocks held "just in case".

Rooms booked by assistants for calendars that have since changed.

These make a building look full while rooms sit empty, and they are the reason organisations install sensors after already having booking data.

The comparison that earns its keep

Booked hours against sensed hours, by room, over a month.

The difference is your no-show and over-booking rate, and it is usually larger than anybody guesses.

That single figure justifies most occupancy programmes on its own, because it converts directly into either reclaimed capacity or a policy change.

Using booking data well

Treat it as demand signal, not utilisation.

Separate booked-and-used from booked-and-empty, which requires a second source.

Look at booking lead time, which indicates scarcity better than the booking rate does.

And check who books: a small number of heavy bookers is a different problem from broad demand.

Policy follows measurement

Automatic release of unclaimed bookings after ten or fifteen minutes.

Shorter default durations.

Limits on recurring bookings, or expiry after a period.

Each of these is cheap, and each needs the no-show figure to justify it. Its own note covers booking policy changes.

The data protection point

Booking data is identified by design: it carries names.

For space analysis it should be aggregated before it leaves the booking system.

And it should not become a record of who met whom, which is what it is if retained in detail.

What to check

Do you know your no-show rate?

Can you distinguish booked-and-used from booked-and-empty?

How many of your bookings are recurring, and how old are the oldest?

And is booking data aggregated before it reaches space planning?