Occupancy-aware facilities: a bounded operations pilot

Plan one facility decision with clear occupancy definitions, stakeholder review, representative observation checks, visible uncertainty and an accountable operating response.

Proposed pilot · By Admin · Reviewed 20 October 2026. Original proposed operational workflow; no installed count, privacy audit or measured benefit reported.

Begin with one shared area and a facility question, such as whether a reviewed service schedule matches actual space use. Define the observation before selecting a sensor. The pilot supports a facility review; it does not identify staff, judge attendance or control an essential service automatically.

Define what the observation can answer

A defined signal

Desk occupied/unoccupied, people crossing a doorway and estimated room occupancy are different observations. State the boundary, reporting window and meaning of unknown. Do not translate one into another without a justified method.

An agreed purpose

The facility owner and relevant stakeholders review purpose, data collected, notice, access and retention before a trial. Collect the least detail needed for the question; a non-camera sensor still needs a review of its data use.

An accountable response

Name the reviewer, permitted operational decision and fallback when observations are missing or doubtful. Keep comfort, accessibility and service constraints explicit rather than assuming an apparently empty space can be disabled.

From a defined space to a reviewed action

1 · Bound the question and area

Assign an area and observation-point identity, intended use and responsible facility reviewer. Record what the pilot must answer and what it excludes. Do not start with an unnamed building-wide surveillance or employee-performance purpose.

2 · Approve the data path

Describe what each device observes, local processing, transmitted data, cloud/third-party access, retention and export. Record stakeholder decisions and the agreed notices and operating policy. Verify the proposed configuration rather than relying on a privacy slogan.

3 · Check representative conditions

Use authorised reference observations with minimal personal detail. Include quiet seated work, group movement, occlusion, alternate entrances and relevant accessibility needs for the chosen method. Record where the result is not representative; this framework supplies no universal accuracy threshold.

4 · Preserve uncertainty and time

Keep observation time, receipt time, detection/reporting delay and configuration together. Distinguish unoccupied, offline, stale and unobserved. Doorway-based estimates need a documented starting state, boundary and reconciliation process.

5 · Review an operating decision

The facility reviewer investigates an agreed schedule or service question, records the decision and checks the relevant comfort/accessibility constraints. Keep a local fallback and a way to report a wrong observation. Any later control integration needs its own approved design and tests.

6 · Recheck and maintain

Track wrong states/counts, unresolved intervals, complaints, review effort and maintenance. Recheck after furniture, partitions, device placement or workflow changes. Expand only when the evidence answers the agreed question without exceeding the permitted data purpose.

Define pilot evidence before the trial

Retain the observation definition, expected coverage and approved reference method. Review false occupied and false vacant states separately, or count differences for the defined doorway/window. Record detection delay, stale intervals and relevant conditions instead of collapsing everything into one promotional accuracy percentage.

Make the privacy review concrete

Document purpose, data fields, access roles, retention, exports, deletion and any proposed linkage with other records. Consider what could be inferred from a time series even without a name attached. Revisit the review if the use, granularity or receiving system changes.

Separate useful operations from individual assessment

The proposed pilot concerns space/service operations. It does not authorise employee attendance inference, individual productivity scoring, access denial, emergency headcounts or life-safety certification. Those purposes are outside this editorial workflow.

Keep controls and service constraints explicit

Observe and review first. Any lighting, ventilation, heating or access-control integration requires a supported interface, named authority, approved limits, accessible local override and tested recovery appropriate to the site. A missing or quiet signal must not silently become permission to interrupt service.

Distinguish the provider questions

An under-desk presence route and a doorway-counting route answer different questions. Evaluate the measurement scope, delay, installation, radio/network, data handling, platform and service responsibilities for the actual choice rather than ranking unlike outputs as interchangeable.

Measure operational usefulness

Record context-complete reviews, false-state investigations, agreed actions, service issues and actual maintenance effort. Any claim about space, energy, cleaning cost or wellbeing needs its own suitable baseline and evidence. No occupancy, saving or wellbeing result is reported here.

Prepare a requirements brief

Describe the shared area, facility decision, desired signal, current process, stakeholders, expected reporting window and privacy/service constraints. Prepare a private requirements enquiry for Admin review. Keep credentials, private personal records and security-sensitive drawings out of the initial brief. Onward sharing is optional.

Sources and applicability

PNNL's 2020 review documents testing and placement/configuration challenges; it is used for evaluation principles, not as a ranking of current models. NIST's Privacy Framework is a voluntary risk-management tool, not a local legal approval. The six-stage pilot, evidence checks and limits above are original editorial planning guidance and require adaptation to the actual workplace and responsible owners.

PNNL review of occupancy-sensor test methods

NIST Privacy Framework

Return to Buildings and cities · How we assess evidence