Current state
Measure the same asset, scope, time window, conditions, and process the proposal intends to change.
A benefit is not a return until you can trace it.
Build the case from a real operating baseline. Separate cashable change, avoided exposure, service and resilience value, strategic options, full lifecycle cost, and claims that remain unverified.
Start with a value register.
For every claimed benefit, record the affected workflow or outcome, current baseline, mechanism, beneficiary, cash or non-cash treatment, observation method, owner, timing, confidence, and the cost or dependency required to sustain it.
Return in view
Measure before and after.
A return case needs a comparable baseline, full implementation cost, and evidence from the operating asset.
01
02
03Published 8 September 2026 · reviewed 9 September 2026. Editorial illustrations generated for Hamed Helped; they do not depict a named site, vendor, or client.
Decision criteria
Six ledgers make the business case harder to fool.
Cashable change
Identify when energy, labor, maintenance, revenue, or other changes alter an actual budget or cash flow.
Avoided exposure
Describe the scenario, consequence, existing control, changed likelihood or impact, and evidence limits.
Operational value
Record service, insight, resilience, comfort, control, compliance, or strategic options separately from cash.
Lifecycle burden
Include design, equipment, network, integration, migration, security, training, support, updates, replacement, and exit.
Evidence quality
State the method, data rights, counterfactual, attribution limits, owner, review date, and confidence.
Questions to ask
Make every value claim pass through the asset.
- What is the baseline?
Use comparable asset conditions, scope, weather or occupancy context, workflow, time period, and measurement method.
- Who receives the value?
Separate owner, operator, tenant, occupant, service provider, insurer, regulator, and community outcomes.
- Does the change reach cash?
Show the budget line, timing, contract or behavior needed, leakage, rebound, and who can realize it.
- What new cost and dependency appear?
Include integration, networks, data, licenses, support, cybersecurity, operating labor, updates, replacement, and exit.
- Can the team attribute the result?
Define comparison, confounding conditions, data quality, exclusions, owner, and decision rule before launch.
- What remains if the vendor leaves?
Test data, configuration, devices, controls, integrations, operating knowledge, and replacement economics.
Evidence table
Label value by type and confidence.
| Claim or decision | Evidence | Owner | When checked |
|---|---|---|---|
| Cashable saving | Comparable baseline, observed consumption or labor change, tariff/cost basis, budget realization | Finance + operations | Before approval and after stable operation |
| Avoided exposure | Named scenario, consequence, control change, incident or engineering evidence, residual risk | Risk owner | Design and periodic review |
| Service outcome | Defined user, experience or response measure, consent and data basis where relevant | Service/experience owner | Pilot and post-occupancy review |
| Lifecycle cost | Capital, implementation, network, integration, security, support, update, replacement and exit model | Asset manager + procurement | Business case and renewal |
| Attribution | Measurement plan, counterfactual, exclusions, quality checks, data rights and analyst | Evidence owner | Before implementation |
Failure modes
Four ways ROI becomes a decoration.
Savings before baseline
A percentage is carried into the model without comparable asset conditions, scope, period, method, or denominator.
Benefits counted twice
One operational change appears as energy, maintenance, asset value, satisfaction, and resilience without separating overlap.
Risk treated as guaranteed cash
Avoided exposure is added like a certain saving without scenario, probability, control, timing, or residual risk.
Lifecycle cost stops at launch
Network, integration, security, support, updates, data work, operating labor, replacement, and exit disappear from the model.
Test the assumptions
Score whether the pilot can produce the evidence your model needs.
Evidence trail
Sources behind this guide
- 01NIST GCTC Smart Buildings SuperClusterBenefit, Value and Return on Investment Considerations (external link)
Framework for considering operational, strategic, resilience, and other smart-building value dimensions.
- 02Telecommunications Industry AssociationWhite Paper: Building Operating Systems (external link)
Industry guidance on design, procurement, deployment, interoperability, and data-management effects across the lifecycle.
- 03BOMA BEST Field GuideR1.1 Data Access and Ownership (external link)
Owner/operator guidance on data access and export needed for durable measurement and control.