Deposits, progress payments and retainage. Who is protected by each one

Three terms appear on almost every contract for work of any size, and they are routinely treated as interchangeable ways of splitting a payment up. They are not. Each one was invented to solve a specific problem, each one protects a different party, and a contract that includes one but not the others leaves a particular risk sitting entirely on one side.

Worked through in the order they occur on a job.

The deposit: funding the start, and demonstrating commitment

A deposit is money paid before work begins. It does two things. It funds the contractor's initial outlay, which on a job requiring materials, permits or a subcontractor's mobilization can be substantial. And it demonstrates that the customer is serious, which matters because a contractor turning down other work to hold a date is taking a real risk on someone's intentions.

The party protected is the contractor, against a customer who cancels after materials have been ordered or who never intended to proceed.

What makes a deposit reasonable is proportionality to what it funds. A deposit covering materials and a mobilization cost is defensible and normal. A deposit approaching half the contract value on a job with modest material content is not, and it inverts the risk: the customer has now funded work that has not happened and holds nothing.

Several states cap deposits on residential home improvement contracts, either as a percentage or as a dollar figure, and some require the deposit to be held in a separate account. Check your state's rule before agreeing to a figure, on either side of the transaction.

The practical middle ground on most residential work: a deposit sized to cover the materials that must be ordered specifically for the job, invoiced with the supplier quote attached so both parties can see what it is for.

The progress payment: keeping the two sides roughly level

A progress payment is money released as defined stages of work are completed. It exists to solve a problem that neither party can solve alone, which is that on any job of length, one side is always ahead of the other.

If the customer pays everything at the start, the contractor holds the money and the customer holds nothing but a promise. If the customer pays everything at the end, the contractor has financed weeks of labor and materials for someone who may not pay. Progress payments keep the exposure small in both directions by settling up repeatedly along the way.

The design principle is that each payment should be tied to an observable event rather than to a date or to a percentage of time elapsed. Good triggers are things anyone can walk up to and verify: rough framing complete, mechanical rough in passed inspection, drywall hung, cabinets set. Bad triggers are things that require an argument: fifty percent complete, work substantially advanced.

Tie payments to inspections where inspections exist. A municipal inspector signing off on rough electrical is an independent third party confirming a stage was reached, which removes the disagreement entirely and costs nothing extra because the inspection was happening anyway.

Retainage: the last piece, held back deliberately

Retainage is a percentage of each payment withheld until the job is complete and any defects are corrected. Five to ten percent is the common range, and it is standard in commercial construction while less common on small residential work.

The party protected is the customer, against the specific failure that progress payments do not address: a contractor who completes ninety-five percent of the job and loses interest in the last five. The punch list items are the ones with the worst ratio of effort to remaining payment, and without something held back there is very little incentive to return for them.

Retainage has a cost, and it falls on the contractor. Money withheld across a long job is working capital tied up, and for a small business that can be the difference between comfortable and stretched. Which is why the terms around its release matter as much as the percentage.

Two provisions make it workable. A defined release trigger: substantial completion, final inspection, punch list signed off, with a specific number of days attached. And a reduction step on longer jobs, where the percentage held drops once the job passes a defined stage, so the amount tied up does not grow indefinitely.

Many states regulate retainage on public projects and some regulate it on private ones, setting maximum percentages and required release timelines. Those rules exist because holding retainage indefinitely was a common abuse.

Putting the three together

A payment schedule that works for both parties on a residential job of moderate size generally looks like this. A deposit sized to the materials that must be ordered up front. Three or four progress payments tied to observable, verifiable stages. A modest amount held back until the punch list is complete, released within a stated number of days of sign off.

Write the whole schedule into the contract before work starts, with the trigger for each payment written as an event and the amount as a figure rather than a percentage of something to be calculated later. Ambiguity in a payment schedule is discovered at exactly the moment when neither party is inclined to be generous about it.

The document that makes all of it enforceable

One more piece belongs alongside these three, and it is the one most often skipped. A written change order for anything that alters scope, signed before the changed work is done, stating what changed and what it costs.

Changes are where payment disputes actually originate. The work grew, nobody wrote it down, and at the end there are two honest recollections of what was agreed. A change order takes two minutes and it converts the single most common source of construction disputes into a piece of paper both parties already signed.

Handled this way, the payment terms stop being a negotiation about trust and become a mechanism. Each party is exposed only for the length of one stage, each release is triggered by something visible, and the final payment is tied to the job actually being finished rather than to someone's willingness to keep asking.