Procurement Guide for Occupancy Monitoring Requirements

Most occupancy monitoring tenders fail before evaluation because the requirement document specifies a technology instead of an outcome. A spec that reads "supplier must provide thermal sensors" quietly locks out better options, invites single-source pricing, and forces a hardware refresh the moment your building layout changes. The requirement you actually want to write is about counting accuracy, data availability, and integration — not the box on the ceiling.

This guide walks through how to structure occupancy monitoring requirements so your evaluation rewards suppliers who can deliver, and so the winning bid still performs three years into the contract.

Separate occupancy from footfall in the requirement itself

Buyers routinely conflate two different measurements. Footfall counts entries and exits over time. Live occupancy is the running total of people inside a space at any given moment — entries minus exits, maintained continuously. A retailer optimising staff rosters cares about footfall curves. A public sector buyer managing a library, museum, or leisure centre with a statutory capacity limit needs live occupancy with a defined refresh interval and an alerting threshold.

State which one you need, and if you need both, say so. The reason matters: occupancy accuracy degrades faster than footfall accuracy because errors accumulate. A sensor that miscounts one person in fifty on a single entrance is fine for daily footfall totals but can drift meaningfully on a live occupancy figure by mid-afternoon unless the system corrects for it. Ask specifically how a supplier handles cumulative drift and whether occupancy resets on a schedule.

Write accuracy as a contractual figure, not marketing copy

Any vendor can print "99% accurate" on a datasheet. What survives procurement scrutiny is a number written into the contract with the conditions attached. Vemco, for example, offers a contractual minimum of 96%, typically reaching 98–99% when lighting, store layout, and visitor behaviour allow. That structure — a guaranteed floor plus a realistic operating range — is exactly what belongs in a tender, because it gives you something enforceable rather than aspirational.

When you draft the accuracy clause, require the supplier to define:

• The guaranteed minimum accuracy percentage and how it is measured (over what period, at which counting lines).
• The conditions under which that figure applies — entrance width, mounting height, lighting, group behaviour.
• The validation method: a supervised manual count against system output, and who runs it.

Treat a supplier who refuses to commit to a floor as a red flag. Treat one who promises a flat 99% guaranteed with no conditions as either inexperienced or optimistic.

Insist on sensor-agnostic and device-independent architecture

The single most expensive mistake in occupancy procurement is coupling your data platform to one hardware vendor. When the sensor manufacturer discontinues a model or raises prices, a locked platform leaves you with no negotiating position. A device-independent, sensor-agnostic software layer — the model Vemco has built since 2005 — lets you mix hardware across sites, replace failed units with a different make, and keep one consistent data view. For a system integrator running a multi-site rollout, this is the difference between one integration project and a dozen.

Put a requirement in the tender that the platform must ingest data from at least two distinct sensor types, and ask bidders to name the models they have deployed in production.

Specify integration before you specify features

Occupancy data has no value sitting in a proprietary dashboard nobody opens. Its worth comes from feeding your existing systems — POS to correlate conversion, BI for reporting, ERP or CRM for planning. Require documented integration with these categories, delivered through an API or a middleware layer such as Vemco's VemFusion, and ask for a reference where that integration is live, not planned.

A practitioner note worth remembering: integration effort is almost always underestimated because the counting data is the easy part. The hard part is time-zone alignment across sites, mapping store IDs between the counting system and the ERP, and agreeing whose "day" boundary wins when a store trades past midnight. Ask bidders how they handle these, and you will quickly separate teams who have done enterprise rollouts from teams who have not.

Size the platform to the deployment you will actually have

A pilot in three stores tells you little about behaviour at three hundred. Ask for evidence of scale. Vemco processes more than 85 million counts per day across a base of 2,000+ customers with partners in 95+ countries, and supports deployments from a single store to full enterprise — that kind of operating volume is what you want to see proven, not promised. For public sector buyers, also confirm the hosting model: whether the supplier can offer both hosted and private cloud, because your data residency and security policies may rule out a shared public deployment.

The tender checklist that protects the budget

Beyond accuracy and integration, require every bidder to submit:

• SLAs covering uptime, data availability, and incident response times — with credits for breach.
• Certifications relevant to your risk profile, such as ISO or SOC 2, confirmed against current documentation.
• A clear support model: who you call, in which language, during which hours, and escalation paths.
• Named reference customers at comparable scale who will take a call.
• Total cost across the contract term, including sensor replacement and any per-site licence fees.

Weight your scoring toward accuracy guarantees, integration evidence, and proven scale rather than dashboard aesthetics. The prettiest interface will not save you when the occupancy figure at your capacity-limited venue is quietly wrong on a busy Saturday.

If you are drafting occupancy monitoring requirements now and want the accuracy clauses, integration questions, and SLA language reviewed against real deployments, talk to the Vemco team — they can help you shape a tender that measures what matters and stays enforceable for the life of the contract.