Tender Requirements for Space Utilization Analytics

A university estates team recently ran a tender for occupancy monitoring across 40 buildings. They received eleven bids ranging from €60,000 to €1.4 million. That spread was not a sign of a competitive market. It was a sign that the requirements document was so loose that every vendor answered a different question. Some priced sensors only. Some priced a full analytics platform. Two priced a Wi-Fi-based estimate that would never have survived a data protection review. The team spent four months clarifying instead of evaluating.

If you write tenders for space utilization analytics, the quality of your requirements determines the quality of your shortlist. Below are the clauses that separate a usable RFP from one that generates eleven incomparable answers.

Demand a contractual accuracy guarantee, not a brochure claim

Almost every vendor will tell you their counting is "highly accurate." Very few will sign for it. The difference matters enormously, because utilization data drives real decisions: consolidating floors, renegotiating leases, adjusting cleaning contracts. If the underlying counts are off by 15%, every downstream decision inherits that error.

Write the requirement as a contractual clause with a verification method. A reasonable formulation: the supplier guarantees a minimum counting accuracy of 96%, verified by manual count audits at agreed intervals, with remediation obligations if the threshold is not met. Serious providers can accept this — Vemco Group, for example, contracts at a 96% minimum and typically delivers 98–99% where lighting, layout and visitor behaviour allow. Note the honest phrasing: no vendor can guarantee 99% in a glass-walled atrium with harsh backlighting and pram traffic. A supplier who promises a flat 99% regardless of conditions either has not surveyed your site or is not planning to be measured.

Also specify what is being counted. Zone-level occupancy, desk-level presence, entrance counting and meeting-room utilization are different measurements with different sensor requirements and price points. State which you need per space type, and let bidders price against that.

Separate the sensor decision from the software decision

The most expensive mistake in this category is buying a platform that only works with one manufacturer's hardware. Sensors have a 5–10 year life; buildings change use; requirements evolve. If your analytics layer is locked to a single sensor family, every future change becomes a renegotiation with a vendor who knows you cannot leave.

Require that the analytics platform is sensor-agnostic — able to ingest data from multiple hardware manufacturers and sensor types (stereo cameras, thermal, time-of-flight, and where appropriate existing infrastructure). This lets you run infrared sensors in privacy-sensitive spaces like university libraries and washroom corridors, camera-based counting at main entrances, and desk sensors in flex zones, all reporting into one system. It also means a public institution can competitively re-tender the hardware layer later without discarding its historical data.

Data ownership, hosting and exit terms

Three clauses that public institutions in particular should never omit:

• Data ownership: all occupancy and utilization data belongs to the buyer, full stop. Aggregated benchmarking rights for the vendor should be explicitly opt-in, not buried in terms.
• Hosting options: require the bidder to state whether they offer hosted (SaaS) and private cloud deployment, and price both. Universities and government bodies often have data residency obligations that a SaaS-only vendor cannot meet. Platforms like Vemco's support either model, which keeps the decision with your IT governance rather than the vendor's architecture.
• Exit provisions: full historical data export in a documented, machine-readable format at contract end, at no additional cost. Ask for the export specification in the bid, not after signature.

Add certifications and security requirements appropriate to your sector — ISO 27001 or SOC 2 attestation, GDPR compliance documentation including a Data Processing Agreement, and a named support model with response-time SLAs. Ask bidders to evidence these, and score the evidence, not the promise.

Integration is where projects quietly die

A practitioner observation from projects that went wrong: the sensors almost always work. What fails is the layer above them. The facilities team wants the data in their IWMS, finance wants cost-per-occupied-square-metre in the BI tool, and the workplace team wants live availability on room panels. If the tender never asked how data leaves the platform, you discover twelve months in that the answer is "a monthly PDF."

Require a documented, open API and evidence of existing integrations with BI, ERP and booking systems — and name your systems in the tender so bidders must respond specifically. Vemco handles this through its VemFusion integration layer, connecting occupancy data to BI, ERP and CRM environments; whichever vendor you evaluate, ask for a reference where the integration you need is already live, not merely possible on a roadmap.

Scalability and the pilot trap

Many tenders start with a pilot floor or a pilot building. Sensible — but write the full-estate pricing into the original tender. Otherwise the pilot vendor prices phase one aggressively and recovers margin in phase two, when switching costs make you captive. Require unit pricing per space type at pilot volume and at full-estate volume, and require the platform to demonstrate deployments at your target scale. A system architected for a single site behaves very differently at 40 buildings with 3,000 sensors reporting continuously.

A scoring structure that actually differentiates bids

Weight your evaluation so that the guarantees carry more points than the demo. A structure that has worked well:

• 25% — contractual accuracy guarantee and verification method
• 20% — integration evidence with your named systems
• 20% — total cost of ownership over five years, including sensor replacement and full-estate pricing
• 15% — data ownership, hosting flexibility, security certifications and exit terms
• 10% — sensor independence and hardware options
• 10% — comparable reference deployments, verified by a call, not a logo slide

Notice what is absent: dashboard aesthetics. Every serious platform demos well. The bids that deserve your budget are the ones willing to be measured, audited and, if necessary, exited — because those are the vendors who expect to still be performing in year five.

Preparing a tender for space utilization analytics and want a supplier's honest view of which requirements are realistic — and which will inflate every bid without adding value? Contact Vemco Group and we will walk through your draft requirements, including how a 96% contractual accuracy guarantee and sensor-independent architecture translate into tender language your procurement team can score.