A Quiet 10-Question Reality Check for Smart Buildings

Almost every conversation I have with building owners and operators starts the same way.
“Yes, we have a BMS.”
“Yes, our systems are integrated.”
“Yes, we are already doing smart buildings.”

And to be fair, most of the time, that’s not untrue.

But here’s the thing I’ve learned after years of walking sites, sitting in control rooms, and reviewing dashboards that look impressive from a distance: confidence in smart buildings often comes from visibility, not from understanding. You can see a lot and still not really know how your building is behaving, why it behaves that way, or what will happen next.

So instead of another maturity model or scorecard, I want to offer something simpler. A quiet, personal exercise. No consultants. No vendors. No presentations. Just ten questions you can ask yourself – or your team, and notice where the answers come easily and where they don’t.

No judgement. No humiliation. Just clarity.

If you answer most of these without hesitation, you’re further along than you think. If some of them make you pause, that pause itself is useful information.

Question 1

If energy consumption increases next month, would you know why within minutes – or only after a review meeting?

Most buildings can tell you that energy went up. Very few can tell you the specific combination of occupancy, weather, scheduling, and system behaviour that caused it – without exporting data and stitching together explanations later or just not responding back.

Question 2

Can your building tell the difference between an actual problem and a familiar pattern?

An alarm is not the same as an issue. Does your system understand what is normal for this building at this time, or does everything outside a static threshold get treated with equal urgency? Do you even know how many alarms or issues real time.

Question 3

If your best operator were unavailable tomorrow, how much understanding would disappear with them?

This isn’t a question about people – it’s a question about dependency. Is operational intelligence stored in systems, or in someone’s head and a few well-worn spreadsheets? 

Question 4

Can you predict which asset is likely to cause trouble next – or do you only know after it does?

Reactive maintenance feels normal because it’s common. Predictive insight feels unusual because it’s rare. Which side does your building fall on?

Question 5

When occupants complain, does the building already “know” something is wrong – or does it learn for the first time from the complaint?

In genuinely smart environments, complaints confirm insights. In less mature ones, complaints are the first signal something wasn’t working.

Question 6

Can you explain your building’s performance in plain language to a non-technical stakeholder?

If the explanation requires dashboards, jargon, and caveats, the building may be instrumented – but not truly intelligible.

Question 7

Do your systems learn over time, or do they behave exactly the same way they did on day one?

Buildings age. Usage changes. Expectations evolve. If your systems haven’t adapted since commissioning, intelligence may be static rather than growing.

Question 8

Can you prioritise actions based on impact – or do you treat all alerts as equally important?

Smart operations are not about seeing more issues; they’re about knowing which ones matter most right now.

Question 9

If you manage multiple buildings, can you compare them meaningfully – or only individually?

Portfolio intelligence is not about having many dashboards. It’s about understanding performance differences, risks, and opportunities across assets without repeating the same analysis building by building.

Question 10

If someone asked what your building will struggle with – in the next six months, could you answer with confidence?

This is often the quietest pause. Not because people aren’t capable – but because most systems were never designed to look forward.

If reading these questions felt comfortable, you’re likely ahead of the curve. (be honest – No judgement. No humiliation. Just clarity)  If a few of them triggered a mental “we should know this, but we don’t,” that’s not a failure. It’s a signal.

Smart building journeys don’t stall because owners or operators are resistant to change. They stall because visibility gets mistaken for insight, and automation gets mistaken for intelligence. The good news is that recognising the gap doesn’t require a reset. It just requires an honest look at where answers come easily – and where they don’t.

The most progressive buildings I see aren’t the ones with the most technology. They’re the ones that can quietly explain themselves, anticipate their own issues, and improve without drama.

If your building is starting to do that, you’re already on the right path. And if it isn’t yet, the fact that you’re asking these questions means you’re closer than you think.