What drives risk in data centre tenders

A data centre tender looks like a building tender and prices like a plant tender. The structure and envelope are a small share of the money. The equipment inventory behind the halls, the power train, the cooling, the controls and the fire and security systems, is where the value, the lead times and the risk sit.

The clients are hyperscalers, colocation operators and the developers building for them, often on design and build or a two-stage model with a hard date attached. Below is where that shape lands in the documents, and what to check first. For other types, see what a school, a metro line, a dam and a hospital have in common.

What makes a data centre tender different

The inventory is the project. On a conventional building the technical installations are one package among several. In a data centre they are often the larger part of the contract value, and the critical path runs through switchgear, generators, UPS and chillers rather than through the frame. The scope breakdown has to be built from that inventory, not from a building template with an M&E line added.

Security shapes how you can read the pack. Vetted labour, badged access, restricted drawings and documents issued in a data room with limited export are common. That shapes staffing, logistics and how the team can share and check documents. It should be priced and planned at tender, not discovered at mobilisation.

The client’s revenue starts at commissioning. Speed to market shows up as hard milestones per hall, phased handover, liquidated damages and acceleration mechanics. The programme is a commercial term in its own right.

The specification keeps moving. Rack density, cooling topology, redundancy level and now liquid cooling are decided by the end tenant, and they change late. Design freeze is rarely frozen. How change is priced after award matters more than the base price.

Much of the plant is owner-furnished. Generators, UPS and switchgear are often procured by the client directly. Your scope is installation, interfaces and commissioning, which is where a responsibility matrix either exists or does not.

The risk drivers and where to find them

1. Specification revisions and change control. Which revision governs, and what the mechanism is once the tenant changes its mind. It sits in the particular conditions, the document register and the order of precedence. Check first: Revision dates against the tender issue date, and what the change clause pays for when the design moves.

2. Milestones and damages. Ready for fit-out, mechanical completion and the commissioning levels are often defined differently in the contract, the programme and the spec. Check first: The definition of each milestone, the damages rate, and whether there is a cap.

3. Commissioning and integrated systems testing. Level 1 to 5 commissioning, witnessing, and the IST that proves the facility under load. Who owns the commissioning agent and who sets pass or fail. Check first: Whether the IST sits inside your completion date, and who carries a failed test.

4. Redundancy the drawings may not show. N+1, 2N and concurrent maintainability double the quantities and the interfaces. The spec states a topology and the single-line and schematic drawings show one. Check first: Count the paths on the drawings against the words in the spec. On quantities, see can AI read construction drawings and do the take-off.

5. Owner-furnished equipment at the boundary. Delivery dates, offloading, storage, warranties and who commissions what. Check first: Whether a responsibility matrix exists, and whether the client’s delivery dates leave room for your installation and testing.

6. Long-lead items and price validity. Switchgear and generators can carry lead times longer than the tender programme allows. Check first: Whether the pricing instructions ask for fixed prices on items you cannot secure, and what reservations the tender allows.

7. Power, at the start and at the end. Whether the grid connection agreement is in place and who holds it, and what construction power is available before it lands, both sit outside your control. Temporary supply and generator hours are real cost, and the IST normally needs the permanent supply. Check first: Energisation dates against the commissioning programme, and which party carries delay from the grid operator.

Scope and interfaces

The risk concentrates in three packages. Electrical, from the intake through switchgear, generators and UPS to the busbar. Mechanical, from chillers and pumps to the room units. Controls, safety and security, covering the building management and power monitoring systems, fire detection and suppression and access control. Build the breakdown on that split rather than one M&E lump, so every interface has an owner.

The boundaries to watch are the owner-procured plant, the IT fit-out (often racks, containment and cabling by the tenant or a separate contractor) and the grid connection. Each needs a line in the scope matrix saying who supplies, who installs, who commissions and who warrants.

How Volve covers it

Volve reads the spec, drawings and particular conditions against the data centre project type and against each other. It flags where the single-line diagrams and the spec disagree on redundancy, pulls milestones, damages and change mechanics into one view, and marks owner-furnished items at the boundary. The decisions stay with your team.

See how it runs in Contract and risk and Cost and estimating, or send the core documents of a data centre tender for a free tender analysis. If you would rather see it first, book a demo.

Patterns, not advice. These are patterns we see across tender packs. The contract and the tender instructions govern each case.