When Not to Measure At All

Not every space question needs sensors. Recognising which ones do not saves money and avoids a monitoring programme nobody wanted.

The practical lesson in “When Not to Measure At All” is to connect a measurement to a named decision without treating the number as certainty. Teams exploring employee monitoring for performance reviews can review Monitask as one source of time and project context, while retaining direct feedback and documented outcomes as the basis for interpretation.

When you already know

A floor that is visibly empty every day does not need six months of data to confirm it.

For a public, independent reference related to “When Not to Measure At All”, consult the CIBSE Knowledge Portal. Its principles provide a useful check on scope, terminology, governance and the claims made during procurement or review.

Walking the building for a week, at varied times, produces a usable picture for free.

Install sensors when the question is quantitative and contested, not when it is obvious and uncontested.

When the decision is already made

If the lease break is next quarter and the decision is fixed, data gathered now informs nothing.

Programmes started to justify a decision rather than to inform one produce selective readings and damage trust in every future programme.

If somebody asks for measurement to support a conclusion, that is worth naming.

When the space is too small

Below a certain number of people, aggregated figures stop being anonymous.

A floor with five occupants produces data about five identifiable people whatever the dashboard says.

Its own note covers small numbers. The short version: at that scale, ask them.

When the question is about quality

"Is this a good working environment" is not answerable by counting.

Surveys, observation and conversation answer it; sensors do not.

Attempting it with occupancy data produces precise numbers about the wrong question, which is more misleading than no numbers.

When you will not act

If no plausible reading would change anything, the programme is decoration.

It still costs money, still requires consultation, and still creates a data holding you must protect.

The threshold test in its own note catches this: if you cannot state a reading that would change the decision, do not start.

When consultation would fail

In jurisdictions requiring employee consultation, a programme introduced without it is both a legal problem and a trust problem.

If you are not prepared to consult properly, that is a reason not to proceed rather than a step to skip.

Cheaper alternatives worth trying first

Observation rounds: a person with a clipboard, three times a day, for two weeks.

Booking data you already have, which costs nothing and answers more than people expect.

Badge data you already hold, with the limitations in its own note.

Asking people, which is unfashionable and informative.

Do these first. If they settle the question, the programme is unnecessary.

What to check

Would any reading change your decision?

Have you walked the space, at varied times?

Is the question quantitative, or is it about quality?

And could the data you already hold answer it?