The Problem with PIR for Occupancy Analytics

How It Quietly Exposes the Designer, Specifier and the Buyer

Let’s get something out of the way early, because dancing around it hasn’t helped anyone so far.

Using PIR sensors as a proxy for occupancy analytics is not just technically weak – it is conceptually wrong. And the longer organisations cling to it, the more it exposes uncomfortable truths about how decisions are being made in building technology.

This isn’t about shaming anyone. But it is about honesty. Because when PIR-based logic is sold, specified, approved, and defended as “occupancy intelligence,” it reveals far more about the maturity of the decision-making process than about the building itself.

PIR Was Never Meant to Answer the Question We’re Asking It

PIR sensors were designed to answer a very narrow question: Did something warm move across this sensor’s field of view?

That’s it.

They don’t know:

• How many people are present
• Whether people are seated or active
• How long a space has truly been occupied
• Whether the space is being used meaningfully
• Whether occupancy is rising, falling, or stable

They detect motion. Momentary, binary motion.

Trying to extract behavioural truth from that is like trying to understand traffic patterns by listening for car horns. You’ll hear something, but you won’t understand anything.

Why This Gets Labeled “Dumb” (Not Just Inaccurate)

Calling this dumb isn’t about insult – it’s about mismatch.

Occupancy analytics is a behavioural problem. PIR is a physics shortcut. The two don’t belong together.

At a technical level, PIR fails immediately:

• A still person disappears
• A passing person becomes “occupancy”
• A cleaner becomes a utilisation event
• A meeting room full of people looks empty after five minutes

At an operational level, this creates chaos:

• Lights switching off mid-use
• HVAC reacting to ghosts
• Space reports that contradict lived experience
• Occupants losing trust in automation

At a strategic level, it becomes embarrassing:

• Space utilisation decisions based on fiction
• Portfolio metrics that cannot be defended
• Leadership asking questions no one can answer confidently

This is not intelligence. It’s noise dressed up as insight.

The Specifier Problem: When Convenience Replaces Responsibility

Here’s where things get uncomfortable.

When a consultant, integrator, or designer specifies PIR-based occupancy analytics, it usually signals one of three things:

1. They don’t understand the difference between presence and occupancy
2. They understand it, but chose convenience over correctness
3. They assumed no one would question it later

None of these age well.

Specification is an act of responsibility. It’s a declaration that this system will represent reality accurately enough to be used for decisions. PIR simply cannot meet that bar for occupancy analytics, and anyone deeply familiar with building behaviour knows this.

So when PIR is specified anyway, it quietly exposes a gap – not in technology, but in intent.

The Buyer Problem: When Box-Ticking Replaces Thinking

On the buyer side, the exposure is different – but just as real.

Approving PIR-based occupancy analytics usually happens because:

• It’s cheaper
• It’s “already there”
• It sounds good in presentations
• It ticks a smart-building checkbox

And that’s how buildings end up with dashboards no one trusts and reports no one uses.

When leadership later asks:

• “Are we actually underutilised?”
• “Can we reduce space?”
• “Why is comfort inconsistent?”

…the answers fall apart quickly.

At that moment, the problem isn’t the sensor. It’s the decision framework that allowed something so weak to be elevated to strategic importance.

Why PIR + “Analytics” Is a Particularly Bad Combination

Using PIR alone is one thing. Calling it analytics is where credibility collapses.

Analytics implies:

• Accuracy
• Repeatability
• Explainability
• Decision-readiness

PIR provides none of these at scale.

What it provides is a false sense of certainty. Numbers that look precise but aren’t meaningful. Heatmaps that feel scientific but collapse under scrutiny. Confidence without defensibility.

And once these outputs enter board decks or portfolio discussions, the exposure becomes unavoidable.

The Human Cost: Occupants Always Figure It Out First

Here’s the part many technology discussions miss.

Occupants know when systems are dumb.

They experience:

• Lights switching off while they’re working
• HVAC behaving erratically
• Spaces feeling “hostile” rather than responsive

They don’t blame PIR sensors. They blame the building. And by extension, the organisation running it.

At that point, all the talk of “smart workplaces” rings hollow. Technology stops feeling like enablement and starts feeling like negligence.

What Real Occupancy Intelligence Actually Requires

If you genuinely care about occupancy, utilisation, and behaviour, the bar is much higher.

Real occupancy intelligence requires:

• Continuous presence detection, not motion snapshots
• Ability to count, not just detect
• Context about space type and usage
• Correlation with time, schedules, and patterns
• Validation against lived experience

This cannot be achieved with PIR. Full stop.

Trying to stretch PIR into this role doesn’t make the system smarter – it makes the organisation look unserious.

Why This Keeps Happening Anyway

Because PIR is easy.

It’s already installed.
It’s cheap.
It’s familiar.
It doesn’t challenge procurement or design norms.

And because for a long time, no one asked hard questions.

But those days are ending.

As AI, space optimisation, ESG reporting, and portfolio-level decisions become more prominent, weak data becomes a liability. You can’t build intelligence on top of fiction. You can’t defend decisions made on signals everyone knows are flawed.

A Simple Test That Ends the Debate

Ask this one question in any meeting:

“Would you be comfortable making a long-term space or capital decision based solely on this data?”

If the answer is no – and it usually is – then calling it occupancy analytics was never honest to begin with.

A Closing Thought

PIR sensors are not bad technology. They are just wildly misused.

The real issue isn’t that PIR exists. It’s that organisations keep pretending motion equals meaning, presence equals behaviour, and cheap signals equal insight.

And in doing so, they quietly expose two things:

• The specifier who didn’t push back
• The buyer who didn’t ask deeper questions

In a world that increasingly values intelligence, adaptability, and defensible decisions, this is not a mistake that stays hidden for long.

Because eventually, someone will ask the right question.

And PIR will have nothing intelligent to say.