Who pays for the final clean: GC scope vs owner scope
On most data center projects the general contractor carries the final clean, priced into general conditions rather than billed to the owner as a separate line. The exceptions are real, and they are almost always created by the specification rather than by negotiation.
Final clean is the cleaning performed after all trades have demobilized and before owner handover. It covers white space, electrical and mechanical rooms, corridors and support areas, and it is the condition the owner acceptance walk is measured against. It is distinct from construction cleanup, which runs continuously during the build.
The default, and why it holds
Absent language saying otherwise, final clean is a general conditions cost. The GC is responsible for delivering the building in a condition fit for acceptance, and cleaning is part of delivering it. Owners rarely want to hold a separate cleaning contract for a two week window at the end of a build, because coordinating it against a commissioning schedule they do not control is a worse problem than paying for it.
What makes data center projects different is that acceptance is measured rather than judged. On a conventional building the final clean is accepted on a walk. On a data hall it may be accepted on a particle count, and a measured standard changes who carries the risk of failing it.
The three way split
Most disputes come from treating this as a two way question. There are three parties, and the middle column is where the arguments happen.
| Scope item | Usually GC | Usually owner | Usually trade |
|---|---|---|---|
| Progressive cleanup during construction | Yes | No | Own debris only |
| Debris removal and dumpsters | Yes | No | To designated point |
| Rough clean at drywall complete | Yes | No | No |
| Final clean before handover | Yes | No | No |
| Cleaning to pass a particle count | Varies | Varies | No |
| Re clean after a failed count | Varies | Varies | No |
| Cleaning between commissioning levels | Varies | Varies | No |
| Ongoing facility cleaning after acceptance | No | Yes | No |
| Protection of installed equipment | Yes | No | Own equipment |
Four rows say varies. Those four rows are the entire dispute, and every one of them sits at the boundary between construction and commissioning.
What Division 01 does to the default
Division 01 74 00, Cleaning and Waste Management, is where the default gets confirmed or overturned. If cleaning is specified there, it sits in the GC scope by definition, and the argument is over.
The problem is that most data center specifications either copy generic language that was written for a commercial office fit out, or say nothing about measured cleanliness at all. Generic language creates the worse outcome, because it looks like the question has been settled when it has not. A spec that requires the building to be left broom clean and free of debris has not addressed a particle count in any way, and both parties will read it as supporting their position.
Read the spec before the bid, not after the failure. If Division 01 is silent on measured cleanliness, that silence is a commercial position somebody is going to take.
Where the line actually moves
Cleaning required to pass a measured cleanliness test is frequently treated as a commissioning cost rather than a construction cost, and that single distinction moves the budget line more often than any negotiation does.
The logic is that construction cleaning delivers a building fit for acceptance, while commissioning cleaning delivers an environment fit for equipment. They are different standards with different acceptance criteria, and on many projects they are carried by different parties. Where an owner has engaged a commissioning agent, cleaning performed at the agent’s direction commonly follows the commissioning budget.
This is worth settling explicitly, because the money involved is not trivial and the schedule exposure is worse than the money. A failed count late in commissioning is a schedule problem first.
The three arguments that actually cause the dispute
- Nobody defined the standard. The spec says clean, the owner expects measured, and neither party wrote down which. This is the most common of the three by a wide margin.
- Nobody defined the retest path. Everyone agrees a count will be taken. Nobody agreed who pays for the re clean and the second count if the first one fails, which means the failure is also a negotiation.
- The trades left after the clean. Final clean happened, then two trades came back for punch work, and now the question is who pays for the second final clean. A sequencing problem that presents as a cost problem.
How to settle it before the schedule gets tight
Four things, all of which are easier to agree in preconstruction than in the last six weeks of a build:
- Name the standard and the method of measurement, or state plainly that acceptance is visual
- Assign the retest path in advance, including who pays for the second count
- Fix the sequence, so that final clean follows punch rather than preceding it, and state what happens if a trade returns
- Put one name on acceptance, on each side
None of this is expensive to agree. All of it is expensive to argue about in November when energization is scheduled for December.
Frequently asked questions
Who pays for the final clean on a data center project, the general contractor or the owner?
On most projects the GC, priced inside general conditions rather than billed separately. The exception is cleaning performed to pass a measured cleanliness test, which is often carried as a commissioning cost. The specification decides it, so read Division 01 before the bid.
Is post construction cleaning part of the GC scope?
Yes by default. Progressive cleanup, debris removal, rough clean and final clean all sit with the GC unless the contract moves them. Ongoing cleaning after owner acceptance is the owner responsibility and is a separate contract.
Are trade contractors responsible for their own final clean?
Trades are responsible for removing their own debris to a designated point during construction. They are not normally responsible for the final clean, which is a single coordinated scope. Making each trade clean its own area at the end produces gaps at every boundary.
Is commissioning cleaning a separate budget line?
Frequently yes. Cleaning performed at the direction of a commissioning agent, or required to pass a measured cleanliness test, is often carried on the commissioning budget rather than construction. Confirm it in preconstruction, because it is rarely stated in the specification.
What happens if a data center fails its cleanliness test?
The area is re cleaned and retested. The cost question is who pays for the second cycle, and the schedule question is what it does to energization. Both should be assigned in the contract before the first count is ever taken.
Writing a data center cleaning scope right now?
Send us the spec section and the commissioning schedule and we will tell you where the gaps are, before they turn into a conversation in the last six weeks.