Liquid cooling flushing scope: who owns the accepted loop after it is opened?
A completed flush does not allocate the work after a later connection. Track the accepted condition, disturbance and return-to-service scope.
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 liquid cooling flushing bid, identify who owns the loop's accepted condition after each handoff and who pays if a later connection disturbs it. One initial flush allowance does not establish who provides renewed testing, samples, temporary equipment or attendance after another party opens the system. The engineer and equipment manufacturers must determine the applicable acceptance and return-to-service requirements; the GC must make the resulting responsibilities and price visible.
The practical question is not simply “who flushes?” It is “what condition was accepted, at what boundary, on whose evidence, and what happens when the next party works there?” A milestone date without those answers can leave the mechanical carry looking complete while the rack connection scope assumes someone else will restore the system.
The handoff is a condition, not just a date
Consider a technology cooling system (TCS) row manifold that passes through hydrotest, cleaning and final flush before a later rack connection. Each milestone has its own extent and record. A final flush record does not automatically assign responsibility for work performed after a connection is opened.
The Open Compute Project's 2025 guidelines for pre-commission preparation of TCS row manifolds call for the construction contractor, IT supplier and fluid supplier to agree on suitable wetted materials and procedures and document them. On page 20, the guidance says to repeat the hydrostatic test if tested and approved row-manifold piping connections are disassembled. Its scope is row-manifold preparation, not every facility-water loop. It is guidance, not a substitute for the project engineer's and OEMs' requirements or an instruction to the estimator to prescribe a test.
That distinction changes the bid review. An accepted test is evidence of a defined condition at a defined point in time. If a later party opens an accepted connection, the team needs a project-specific decision about what must be re-established, by whom and under what price. The necessary response may depend on the actual connection, design and contract documents. Do not assume that every intervention triggers the same test, sample or flush.
Follow a fictional row manifold through three parties
The following example and proposal excerpts are fictional. They illustrate a scope decision, not a measured result or a project procedure.
A GC is leveling one mechanical package for a data hall. The mechanical subcontractor proposes a single hydrotest, cleaning and final flush of the row manifold, with one acceptance package. A specialist is included for the initial flush visit. The owner separately supplies racks, and an IT integrator is expected to make a later connection. The engineer and CxP have not yet issued the return-to-service basis for that handoff.
The fictional mechanical offer says: “One initial flush and report included. Final rack connection by others.” A second offer includes one sample visit but excludes work following third-party connections. Neither offer prices a defined later restoration.
Suppose the initial report is accepted for the identified manifold boundary, after which the integrator must disassemble a previously tested connection to complete its work. The initial acceptance remains a record of the earlier milestone; it does not answer the price and responsibility for whatever the project team requires afterward. The GC should not automatically add a second flush or assume the integrator owns it. First establish the applicable engineering and OEM requirements, then solicit a priced scope from the party assigned to perform them.
Compare the two initial offers only after identifying their included visit, evidence, temporary equipment and removal. Carry the later work as a separately priced scope or a clearly identified allowance with the assumptions and unresolved ownership visible. An allowance is not proof that a subcontractor has agreed to perform the work. If the connection sequence changes, revisit both the technical response and the price.
Build an accepted-condition register
Use one row per boundary and handoff, not one row for the whole cooling system. The entries below continue the fictional example. “Proposed owner” is a prompt for negotiation, not an assignment imposed by this guide.
| Milestone or interface | Accepted state and evidence | Next party and disturbance trigger | Proposed scope owner and pricing status |
|---|---|---|---|
| Initial hydrotest | Defined manifold boundary and accepted test record | Mechanical team continues work; later disassembly of an accepted connection requires review | Mechanical bidder includes one test; later response unresolved |
| Cleaning and final flush | Identified boundary and accepted initial report, subject to project criteria | Custodian holds the system until rack work; loss of the agreed condition triggers review | Mechanical bidder includes one visit; preservation and later response unconfirmed |
| Rack connection | Earlier acceptance is recorded, but later work changes the interface | Integrator opens a previously tested connection in this example | Connection by integrator; restoration owner and price unresolved |
| Return to service | Engineer and OEM define the required evidence for the actual work | CxP and designated recipients review the resulting records | Assign execution, samples, equipment and attendance after technical direction; obtain a separate price |
For each row, record the document revision, boundary, acceptance authority, evidence, custodian and agreed holding condition. Identify the next party’s access and notice obligations. If the requirement is missing, write “open” and link it to an RFI instead of converting an assumption into an inclusion.
The register should also distinguish an accepted report from the work needed to produce it. A price for one sample visit might exclude repeat sampling, laboratory work, temporary pumping equipment or waiting time. Ask who receives and reviews the evidence and who funds a return visit if the agreed sequence changes.
Separate initial acceptance from later disturbance
Start with the physical boundary. Does the mechanical proposal end at a capped manifold, a valve, or another identified interface? Does the integrator's connection require that boundary to be opened? Ask both parties to mark the same drawing and state what each includes. The scope boundary discussion in data center liquid cooling scope boundaries helps locate the interfaces; this register follows the condition across one of them.
Next, ask the engineer, relevant OEMs and CxP what evidence and actions the actual intervention requires. The response should identify the affected extent and acceptance authority. It may also establish whether any equipment, samples, attendance or temporary services are necessary. Obtain that direction before asking bidders to price a common basis. Do not use a general guideline to set pressure, chemistry, intervals or acceptance thresholds for this project.
Then allocate the work in writing. The party that opens a connection, the party qualified to perform any required restoration, and the party paying for it may be different. Compare the mechanical, specialist and integrator scopes at the same boundary. Identify mobilization and access assumptions, a rate or separate price for an authorized return, and who coordinates the sequence. If a bidder excludes an item, verify a corresponding inclusion elsewhere before removing it from the GC carry.
Resolve the mechanical carry before award
Ask for the initial and later work to be priced separately against the confirmed scope. Identify the included number of visits and the treatment of delays, changes in sequence and any required reinspection. Confirm who supplies and removes temporary equipment and who produces, transmits and accepts records. Where an owner-furnished rack changes the sequence, align the responsibility and delivery assumptions with the owner-furnished equipment bid review.
Include the proposed wastewater route in the clarification. Ask which party will provide the equipment, handling and disposition identified by the project specification and applicable local requirements, and what remains to be determined. Do not assume that an initial flush price includes a later event or prescribe a treatment method from a bid review. Price the confirmed route and identify any remaining allowance and owner.
Review the handoff against the proposals
Piper bid leveling compares subcontractor bids with project scope and provides source-linked findings. The estimating team can inspect the proposal language against the handoff requirements, pursue the open technical and commercial questions, and decide the carry. The engineer and OEMs establish the applicable technical requirements; the project team retains acceptance and commercial decisions.
Related reading
Who owns the liquid cooling connection on a data center?
Liquid cooling adds three loops and three owners. The gap sits between facility water, the CDU and the rack: hoses, valves, flushing, fluid and leak detection.

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.

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.

Data center bid review: work through a shared scope omission
Follow a fictional data center bid review from a shared exclusion to a documented scope owner, clarification and carry decision.

Data center load bank bids: compare the test basis before the rental price
Equal load-bank capacity can conceal different test locations, connections and crews. Build a test-basis register before carrying either bid.

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.