Worked decision · EXAMPLE-OCC-001
This is not a buyer recommendation or vendor ranking. It demonstrates the governed decision method and deliberately preserves unresolved evidence gaps.
1.Define
2.Evidence
3.Compare
4.Decide
5.Prove
A credible worked example of how Prove TDI structures an occupancy-intelligence decision. Customer context is illustrative; cited product claims are attributable public evidence checked on 1 September 2026.
01 · Decision
A 20-office portfolio has inconsistent occupancy evidence. Booking and badge data cannot reliably explain how desks, rooms and open areas are actually used.
Required outcome
Create a privacy-conscious, portfolio-scale occupancy evidence layer that supports space planning, room optimisation and future building automation.
Decision boundary
Select the measurement and analytics layer. This example does not select an IWMS, booking platform or BMS replacement.
Accountable owner
Corporate Real Estate Director (illustrative)
Stakeholders
Workplace · IT · Information Security · Facilities · Finance
Timing
Decision within 12 weeks (illustrative)
Commercial boundary
Commercial terms deliberately excluded until comparable supplier evidence is available.
02 · Requirements
The requirement baseline is explicit, weighted and traceable. Public evidence can inform fit, but it cannot silently rewrite what the organisation needs.
Avoid collecting directly identifiable workplace behaviour as part of routine space measurement.
One evidence layer must support the main workplace space types.
Support operational use cases as well as periodic planning.
Keep data usable in booking, IWMS, analytics and automation workflows.
Compare utilisation patterns across buildings without rebuilding reports manually.
Installation model, power and maintenance affect whole-life effort.
03 · Market
The broader market includes dedicated sensor platforms, network-derived occupancy, booking-derived signals and IWMS-native analytics. Three dedicated platforms are compared deeply because their public evidence directly addresses the stated measurement boundary.
Explicit exclusions
04 · Evidence
These sources establish a credible research baseline. They are vendor-authored and therefore remain source-backed rather than independently validated.
The platform exposes live occupancy, workplace analytics, API access and integrations; the vendor states that sensors capture XY coordinates rather than identifiable imagery.
First-party vendor evidence
Source-backed, not independently corroborated
Density positions its workplace platform as anonymous at source, camera-free, supported by occupancy sensors, workplace analytics and API integrations.
First-party vendor evidence
Source-backed, not independently corroborated
Density describes radar-based occupancy sensors, real-time measurement and a camera/microphone-free sensing model.
First-party vendor evidence
Source-backed, not independently corroborated
VergeSense describes an occupancy intelligence layer that combines existing workplace signals with sensors and provides portfolio, space-utilisation and reporting capabilities.
First-party vendor evidence
Source-backed, not independently corroborated
05 · Comparison
Positions below are illustrative evidence-adjusted decision positions, not permanent vendor scores. Missing independent corroboration and buyer-specific artefacts constrain confidence.
Pass on public claims
Supported strengths
Open evidence
Pass on public claims
Supported strengths
Open evidence
Pass on public claims
Supported strengths
Open evidence
06 · Challenge
A recommendation is not strengthened by hiding objections. The challenge layer records what could reverse it.
If existing badge, booking and Wi-Fi data can answer the agreed planning questions with acceptable confidence, adding a dedicated sensor layer may not justify its change cost.
The decisive capability and accuracy claims in this public example are vendor-authored. Independent validation and buyer-specific proof remain open.
If long-life wireless deployment is weighted materially above live operational response, VergeSense could overtake the current leading position.
Information Security may reject a technically strong option if data flows, retention, subprocessors or regional hosting do not meet policy.
A sensor programme can fail despite accurate hardware if installation coverage, floor-plan maintenance, integrations or operating ownership are weak.
Reopen the recommendation if controlled validation shows a mandatory privacy, accuracy, integration or deployment requirement is not met.
07 · Recommendation
Advance XY Sense as the conditional lead for controlled validation, with Density and VergeSense retained as live alternatives. Do not award on this public evidence alone.
Conditions before award
08 · PROOF
Evidence coverage
Public evidence establishes a credible starting position, but independent corroboration and buyer-specific artefacts remain incomplete.
Approval
Not approved — illustrative recommendation only
Outcome review
If approved after validation, schedule outcome reviews at 90 and 365 days against coverage, data reliability, adoption and decision-use metrics.
Publication blockers retained