Bidding a live data center expansion: price the approved work window
Level live data center expansion bids against the approved intervention window, readiness work, attendance, and return-visit assumptions.
Author
Ido Gedanken, CEOPublished

Bring a data-center trade package. See how Piper compares the drawings, specifications and subcontractor bids, with source-linked findings your estimating team can review.
Book a demo- Type
- Guide
- Read
- 6 min
- Published
On this page
Before carrying a mechanical or electrical subcontract for an expansion in an operating data center, ask whether the price covers the work within the window the operator will actually authorize. An installation estimate alone does not answer that question. The GC also needs the price and ownership of preparation, approvals, operations attendance, and a return if the work cannot proceed or finish.
This is a bid-leveling decision. Piper compares subcontractor proposals against project scope with source-linked findings, while the estimating team reviews the evidence and chooses the carry. The useful comparison is not simply whose installation number is lower: it is whose proposal covers the same intervention conditions and what remains open.
Installation hours are not an authorized window
First establish the unit behind the subcontractor's labor estimate. Eight labor-hours could mean one person for eight hours or two people for four hours. Neither tells the GC that the operator has authorized eight hours of intervention, that the work can be split, or that another crew member can perform the same work concurrently. Ask the bidder for crew composition, elapsed duration, dependencies and the portion that must occur during the controlled window.
Separate three clocks: preparation before the window, elapsed time authorized for the intervention, and work or attendance after it. The project documents and operator determine what belongs inside each boundary. A crew may be present before the start without permission to begin the intervention; similarly, a nominal four-hour window does not establish four hours available for installation if other approved activities must occur within it.
This approach applies when live operations constrain work. The operator and engineer own the procedure and safe operation. The GC identifies commercial scope and obtains their decisions, not the operating sequence.
A fictional mechanical extension quote
Assume an estimator is comparing proposals for a mechanical extension at an occupied facility. In this invented example, the bidder estimates eight labor-hours of installation, performed by one installer in eight elapsed hours. The project team has identified only a four-hour operator-approved intervention window for the proposed work. These durations are illustrative, not benchmarks. The bidder has not shown that any installation can move outside the window or that extra workers can reduce the duration.
The proposal includes the installation labor and assumes the operations team will approve access and attend. It excludes a return visit if the window is aborted, but gives no return price. The documents call for an approved method and coordination with operations; the cost and responsibility for preparing and revising the method are not clear in the quote. No one has confirmed how much of the window is available to the installer after operator-controlled activities.
The low cover price is therefore not a complete comparable carry. The conflict is not merely that eight is greater than four: labor-hours are not inherently elapsed hours. Here the bidder's one-person assumption makes the eight hours elapsed, and the bid offers no approved way to fit that work into the shorter window. Adding another person to the estimate without the bidder and operator confirming feasibility would turn an open issue into a false solution.
Request a revised approach and price on the actual conditions: what can be prepared outside the window, what duration and crew are proposed within it, and whether the operator and engineer accept that division. If a different window or multiple interventions are proposed, obtain the responsible people's approval and a price for that basis. Until then, show the mismatch and unresolved exposure alongside the bid, rather than treating the installation price as a complete fixed carry.
Separate readiness, attendance and installation
A proposed readiness owner is not proof that the work is included. Check who prepares submissions, responds to comments, coordinates access and identifies materials. Record the required revision and approval evidence.
In its February 25, 2015 article on methods of procedure, Uptime Institute describes approvals, permits and access among potential prerequisites, along with version review and integration into change management. It is a historical operations-process reference, not a construction pricing standard or authority for this project's procedure. Use the actual site requirements to determine the work and approvals to price.
Attendance differs from preparation. The sub may assume an operator attends without including that cost. Ask who arranges and pays for each participant, when the clock starts, and what happens if permission arrives late.
If owner-furnished equipment is involved, the same review should address the handoff between the owner, supplier and installer. The owner-furnished equipment bid-leveling guide provides a broader way to compare those interfaces. For the larger transition into this work, see data center preconstruction versus commercial preconstruction.
Copy the window register into the bid review
Use one register for each proposed intervention and keep the underlying document revision beside the row. The following entries continue the fictional example. Confirmed inclusion describes only what the invented proposal says; it is not approval to execute. Replace every entry with project evidence and record the actual decision maker and date.
| Review item | Proposed scope owner | Confirmed inclusion and evidence | Unresolved price or basis | Human approval or decision |
|---|---|---|---|---|
| Readiness and method submission | Mechanical sub proposed | Proposal silent; project documents require an approved method | Preparation and revisions unpriced | Operator and engineer identify applicable review and approve method |
| Access and permission | Operator proposed | Bid assumes approval; no approval evidence in quote | Waiting and late-permission cost unresolved | Operator confirms access and intervention authorization |
| Operations attendance | Operator proposed | Sub assumes attendance; funding not established | Attendance and extended time unresolved | Operator confirms availability and commercial owner |
| Installation crew and window | Mechanical sub proposed | One installer, eight labor-hours per quote; four-hour window identified | Feasible duration and any revised crew or extra window unpriced | Operator and engineer assess proposed approach; estimator selects carry |
| Abort and return | Mechanical sub proposed for return | Quote excludes return after an aborted window | Standby, remobilization and return scope unpriced | Operator controls stop and renewed authorization; GC decides commercial treatment |
| Evidence and closeout | GC to coordinate, subject to agreement | Required records and provider not confirmed | Documentation and follow-up attendance unresolved | Operator and engineer confirm required evidence and acceptance |
An allowance for a return does not authorize it. An approved method does not establish who pays for a waiting crew. The estimate needs both answers from the appropriate parties.
Price a failed window before comparing bids
Ask each bidder to distinguish a delayed start, a stop before installation begins, and an intervention that cannot finish in the authorized time. For each condition, request the included attendance, standby basis, minimum call-out or remobilization charge if applicable, and the scope assumed on a return. Identify whether the price includes a new submission or review, and who bears costs of other participants. These are questions for the particular contract and quote, not automatic entitlements.
Do not combine every contingency into an unexplained plug. Put the base scope, priced alternative, allowance or open exposure in separate lines, with the trigger and source. Compare bidders on the same assumed window and return scenario. If one quote excludes return and another includes one return under defined conditions, show the difference before selecting a carry. If no reliable price is available, identify the exposure and owner for resolution; an unpriced row is not a zero-cost row.
The wider process for reviewing subcontractor exclusions and qualifications helps move those conditions from the proposal into the award discussion. Record the final agreed commercial basis in the appropriate scope or subcontract documents, subject to the project team's review.
Ask for a quote that can be leveled
Send the same clarification to each bidder, with the current scope and the proposed window basis:
Identify the crew and elapsed time assumed for installation, the work proposed before, during and after the authorized window, and the approvals and attendance on which your price depends. State what your base includes for preparation and revisions, waiting for permission, an aborted window and a return visit. Price any excluded return or alternative approach separately, identify its assumptions, and cite the applicable proposal and scope revisions. Confirm whether your proposed approach is subject to operator and engineer approval.
A response that says "per plans" does not settle the conflict. Retain the response with the estimate and revisit the crew, window, attendance and return assumptions together if the approach changes.
Review the window against the project scope
For a live expansion, bring the actual scope, current proposals and clarifications into a Piper bid-leveling review. Piper compares bids against project scope and links findings to their sources; the estimating team checks the documents, resolves questions with the responsible parties and decides the carry. The fictional register above illustrates the review method, not an actual Piper result. The operator and engineer retain the decisions about procedure, authorization and safe operation.
Related reading
Data center precon is not commercial precon with more power
On a data center the risk leaves the building and moves into owner-furnished gear, commissioning, and a schedule set by power. What changes for GC precon.

How to review subcontractor exclusions and qualifications
Subcontractor bids bury risk in exclusions and qualifications. Identify them, classify impact, normalize the comparison, and lock decisions into the subcontract scope letter before award.

Leveling bids when the owner buys the equipment
On an OFCI data center, an electrical bid prices custody steps, not gear. How to level each owner-furnished item from receiving to integrated testing.

Piper removes manual review from the critical path and brings project data, company knowledge, and expert checks into every preconstruction decision and workflow
Review one data-center package with Piper
Bring a current or completed package, including drawings, specifications and subcontractor proposals. See how Piper compares scope boundaries and qualifications with the source behind each finding. Your team reviews the findings and decides what to carry.