The invoice said $3,200 in "standby charges." The homeowner had never heard the term before it appeared on paper.
Here's what happened. A bathroom remodel in a mid-sized suburban home. The tile crew was scheduled to start on a Monday. They didn't show. No call. The general contractor's project manager said the crew was "finishing another job" and would arrive the following Monday. That slipped too. The tile crew finally walked in fourteen days behind schedule.
Then the invoice arrived. The contractor billed $3,200 for "crew standby and remobilization" — the argument being that because the tile couldn't be laid on time, the plumber and the electrician had to be rescheduled, and those trades charged a re-visit fee that got passed straight through to the homeowner. A delay the contractor's own scheduling created had been converted into a line item the homeowner was expected to pay.
How the language did the work
The contract had one sentence that made this possible: "Client is responsible for costs arising from delays affecting the project schedule." No definition of who caused the delay. No carve-out for contractor-side scheduling failures. Just a blanket clause that reads reasonable until it's aimed at you.
That sentence is doing something specific. It removes the question of fault entirely. It doesn't say "delays caused by the client." It says "delays affecting the schedule" — and every delay affects the schedule, including the ones the contractor is responsible for. The homeowner assumed the phrase meant homeowner-caused delays: a late material selection, a change order, a locked gate. It meant all of them.
The clause never said whose fault. That's not an accident — vague fault language always defaults to the party writing the invoice.— construction dispute mediator
What the money actually looked like
Break down the $3,200. The plumber's re-visit fee was $650. The electrician's was $500. The tile crew billed $1,400 in "remobilization" — the cost of tearing down and setting up again, even though they'd never set up in the first place. The remaining $650 was a flat "schedule disruption" fee with no supporting math at all.
The homeowner paid it. Not because they agreed, but because the final 40% of the contract balance hadn't been released, and the contractor made clear that the tile wouldn't be grouted and the project wouldn't be closed out until the standby charge was settled. That's leverage. When your money has already left your control and the work is 90% done, disputing a $3,200 line item means risking a stalled, half-finished bathroom.
The fix that would have stopped it
Two things would have prevented this, and they work together.
First, delay language that assigns fault. A single revision — "Client is responsible only for costs arising from delays caused by the client, including late selections and change orders" — turns the contractor's blank check into a defined, defensible clause. Standby charges tied to the contractor's own late crew become unbillable on their face.
Second, and more structural: milestone-based escrow. When funds are held in escrow and released against completed milestones — rough-in passed, tile set, final walkthrough — a surprise standby charge can't be used as a hostage. The homeowner isn't choosing between paying a disputed invoice and living with a grouted-halfway bathroom. The money for the tile milestone releases when the tile milestone is genuinely complete, and a disputed add-on gets negotiated on its merits, not under threat of a stalled job.
The reason this scenario works so cleanly for the contractor is timing: the leverage lands after the money is committed but before the work is closed. Escrow flips that. It keeps the payment tied to the deliverable instead of to the contractor's willingness to finish.
If you want a delay clause that names who caused the delay, and a payment structure that doesn't hand your leverage away on day one, start by working with contractors who already build this way.