Space Utilization RFP: Requirements to Put in Your Tender

It is Thursday, the procurement portal closes on Monday, and the technical section of your draft is fourteen lines long. Six of those lines describe the dashboard. One says "the system shall measure occupancy." Nothing says which spaces, how accurately, what happens to the images, or how the data gets into the finance team's BI tool. You already know what will happen: bidders will ask forty clarification questions, and the answers will be incomparable. This article is about fixing that before Monday. It sets out the specific requirements a buyer should write into a space utilization RFP, grouped the way a bidder's technical team will read them: sensors, accuracy, privacy and reporting.

If you still need to settle what space utilization analytics is and what it is used for, start with our space utilization analytics FAQ. What follows assumes you know why you are buying and need to write what you are buying.

Start with a space inventory, not a wish list

Every other requirement depends on this one. Attach a schedule listing each space type in scope, the number of each, and the measurement you want for it. Entrance counting, zone-level occupancy, desk-level presence and meeting-room utilization are four different measurements with four different sensor requirements and price points. A tender that asks for "occupancy" without this schedule invites one bidder to price doors only and another to price every desk.

A workable format is one row per space type: name, quantity, measurement required, reporting interval needed (live, hourly, daily), and any constraint such as ceiling height, glass walls, exterior doors or a privacy sensitivity flag. Bidders can then propose hardware per row, and you can compare rows across bids instead of comparing totals that mean different things.

Sensor requirements in a space utilization RFP

Do not specify a sensor brand. Specify what the sensors must do and what the platform must accept. The clauses that earn their place:

• Sensor-agnostic platform: the analytics layer must ingest data from multiple hardware manufacturers and sensor types, such as stereo cameras, thermal, time-of-flight and infrared, and from existing infrastructure where appropriate. Ask the bidder to list the sensor families currently supported in live deployments, not on a roadmap.
• Sensor type per space type: require the bidder to state, per row of your inventory, which sensor they propose and why. This is where you expect infrared or thermal in a library or washroom corridor and camera-based counting at a main entrance.
• Site survey before firm pricing: require the bidder to confirm which prices are survey-dependent. Lighting, mounting height and door width change hardware choices, and a bidder who prices every door identically without seeing them has not priced your building.
• Installation dependencies: ask for power and network requirements per sensor type (PoE, battery, Wi-Fi), so your IT and estates teams can estimate their own costs rather than discovering them at kick-off.
• Replacement path: require that historical data is retained if a sensor is swapped for another manufacturer's device later. This protects your ability to re-tender the hardware layer separately.

Accuracy: write a clause, not an adjective

"Highly accurate" is a brochure phrase. A tender needs a number, a measurement method and a consequence. A clause that bidders can genuinely accept reads: the supplier guarantees a minimum counting accuracy of 96%, verified by manual count audits at agreed intervals, with defined remediation if the threshold is not met. Vemco Group contracts at that 96% minimum and typically delivers 98 to 99% where lighting, layout and visitor behaviour allow. Treat any bidder offering a flat 99% regardless of conditions as a scoring risk: either they have not looked at your atrium or they do not expect to be audited.

Three details make the clause enforceable. First, define accuracy per measurement type; a door count and a desk presence reading are verified differently. Second, specify who performs the audit, how long it lasts and what sample of sensors it covers. Third, state what remediation means: recalibration, hardware replacement, service credits, or a combination. Ask bidders to accept the clause as written or to propose amendments in a marked-up copy. The mark-ups tell you more about a vendor than the demo will.

Privacy requirements a bidder cannot answer with a logo

Privacy sections in tenders are often a single line asking for "GDPR compliance." Every bidder ticks it. Replace it with questions that require a specific technical answer:

• Data captured: for each proposed sensor type, state exactly what the device records and what leaves the device. Does any image or identifiable data leave the sensor? If so, where is it stored, for how long, and who can access it?
• Documentation: require a Data Processing Agreement with the bid, plus the material you will need for your own Data Protection Impact Assessment. Score the documents supplied, not the promise to supply them.
• Hosting: require the bidder to state whether they offer hosted (SaaS) and private cloud deployment and to price both. Public bodies with data residency obligations cannot use a SaaS-only answer. Vemco supports either model, which keeps the decision with your IT governance.
• Data ownership and exit: all utilization data belongs to the buyer. Any vendor use for aggregated benchmarking must be explicitly opt-in. Full historical export in a documented, machine-readable format at contract end, at no extra cost, with the export specification included in the bid.
• Security evidence: ISO 27001 or SOC 2 attestation where your sector requires it, with the certificate attached rather than referenced.

Reporting: define the metrics, the interval and the exit route

The sensors almost always work. What fails is the layer above them, and it fails because the tender never described it. Write three things down. The metrics you need, with their definitions: peak occupancy, average occupancy during core hours, utilization rate as a percentage of capacity, and the time window each is calculated over. The interval each must be available at, from live for room panels to daily for portfolio reporting. And the destinations: name your IWMS, BI platform, booking system and ERP in the tender so bidders must confirm an integration with each, not with "leading systems."

Require a documented, open API and at least one reference where each named integration is already live. Vemco connects occupancy data to BI, ERP and CRM environments through its VemFusion integration layer; whichever vendor you are assessing, ask for the reference contact, not the case study. Also require that standard reports can be scheduled and exported without professional services, and that raw data, not only aggregates, is accessible to you.

Make the response format do the comparison for you

A space utilization analytics tender is only as useful as the answers it forces. Issue a response template with fixed columns: unit price per sensor type, platform licence per space or per building, installation per unit, annual support, and separately listed exclusions. Ask for unit pricing at pilot volume and at full-estate volume in the same table, so a low pilot price cannot hide a phase-two margin recovery. Add a five-year total cost of ownership line including expected sensor replacement, calculated on assumptions you specify, so every bidder uses the same ones. When every bid arrives in the same shape, evaluation takes days rather than months.

Frequently asked questions

Should the RFP specify a sensor technology or leave it to bidders? Specify the measurement and the constraint for each space type, and require the bidder to propose and justify the sensor. Mandating a technology narrows the field and shifts responsibility for a poor fit onto you. Requiring a sensor-agnostic platform keeps future hardware choices open.

Is a 96% accuracy clause too low to be useful? No. It is the floor a serious supplier will sign for across all conditions, with 98 to 99% typical where the environment allows. A higher flat figure without a verification method is not a stronger clause; it is an unenforceable one.

How much privacy detail belongs in the tender versus the contract? The questions belong in the tender, because the answers differentiate bids. Ask what each sensor captures, what leaves the device, hosting options and export terms up front, and attach the DPA to the bid. Leaving these for contract negotiation means scoring bids without knowing which ones your data protection officer will reject.

Drafting a space utilization RFP and want a supplier's candid view on which clauses are realistic and which will inflate every bid without adding value? Contact Vemco Group and we will review your draft requirements, including how a 96% contractual accuracy guarantee, sensor-independent architecture and your privacy obligations translate into tender language your procurement team can score.