The most expensive mistake in an occupancy management tender is not choosing the wrong sensor. It is accepting a vendor's accuracy figure as a marketing claim rather than a contractual number, then discovering during rollout that the "98% accuracy" on the datasheet was measured in a lab with ideal lighting, single-file entry, and no shopping trolleys. By then the purchase order is signed and the dispute clause is missing. This guide is about writing the evaluation so that problem never reaches procurement in the first place.
Ask every bidder one question: is your stated accuracy contractual, and what happens if you miss it? A vendor willing to write a contractual minimum of 96% into the agreement — with typical performance of 98–99% when lighting, layout, and visitor behaviour allow — is telling you something different than one who prints a flat 99% and hides the conditions in a footnote. Vemco, for example, guarantees a 96% floor contractually while performing at 98–99% in normal conditions. That distinction matters for scoring, because a guaranteed floor gives your legal team something enforceable. A single headline percentage does not.
In your evaluation matrix, split accuracy into three scored items: the contractual minimum, the measurement methodology (bidirectional counting, staff exclusion, group handling), and the remedy if the vendor falls below the floor. Award zero points for any accuracy figure that is not tied to a defined test protocol and site conditions.
Occupancy data that lives in its own portal is data you will stop using within a quarter. The value appears when counts flow into the systems your teams already open every morning — POS for conversion, BI for board reporting, ERP for staffing and space cost, CRM for campaign attribution. Vemco handles this through VemFusion, its integration layer that pushes counts into POS, BI, ERP, and CRM environments. When you evaluate bidders, ask for a named integration to your specific BI tool and your specific POS, not a generic "API available" answer.
Request the following in writing from each vendor:
Some vendors are software companies; some are hardware companies wearing a software badge. The difference shows up at year three, when a sensor line is discontinued and you are told the whole estate needs replacing. A device-independent, sensor-agnostic platform lets you mix sensor types across sites and swap hardware without rebuilding the analytics layer. Vemco has run counting software since 2005 and works across sensor types rather than locking you to one supplier's device. For a multi-site or public sector estate with mixed building stock, that independence is often worth more than a marginally cheaper sensor.
Practitioner note: during installation, the single largest source of accuracy loss is not the sensor — it is mounting height and camera angle over entrances with glass reflections or direct sunlight at certain hours. A vendor who insists on a site survey before quoting is protecting your accuracy number. A vendor who quotes blind from a floor plan is transferring that risk to you. Score the site-survey commitment explicitly.
If your tender covers a single flagship today but the roadmap is national or regional, evaluate the vendor's proven ceiling now. Ask for the count volume they process and the geographic spread of their deployments. Vemco processes more than 85 million counts per day, serves over 2,000 customers, and operates through partners across 95+ countries — figures that tell you the platform has survived enterprise load, not just pilot conditions. Translate that into your matrix by asking each bidder for their largest live deployment by site count and their peak daily count volume, then verify against a reference.
Fix your weightings in advance so a strong sales deck cannot shift them mid-evaluation. A defensible split for an occupancy management tender looks something like this:
Especially for public sector and enterprise buyers, request evidence rather than assertions: relevant certifications such as ISO or SOC 2, the written SLA with defined response and resolution times, the support model with named escalation, and at least two reference customers of comparable size and sector you can contact directly. Confirm these directly with each vendor before award — a certification named on a website is not the same as one currently valid and in scope for the service you are buying. A serious bidder answers all of this without friction. A weak one asks for more time.
Run a short live pilot in one of your actual sites before final award wherever your timeline allows. Two weeks of real counts against a manual audit will tell you more than any proposal document, and it turns the accuracy clause from a promise into a measured baseline you can hold the vendor to for the life of the contract.
If you are shaping an occupancy management tender and want the accuracy guarantee, integration detail, and reference evidence set out before you go to market, talk to the Vemco team here — bring your existing BI, POS, and hosting requirements, and ask them to map each one against a contractual response.