The mechanism
An owner withholds a percentage of each progress payment until the work reaches substantial completion. AIA A201 provides for it, the owner-contractor agreement sets the number, and the number is conventionally 5 or 10 percent.
The stated purpose is security. If a contractor walks off, the owner holds enough cash to finish the work without suing anyone, and that logic is sound as far as it goes.
What the logic ignores is where the money is actually sitting.
Run the numbers from the sub's side
A drywall subcontractor takes a two million dollar scope. Their bid carries a 4 percent net margin, so the job is worth eighty thousand dollars of profit if it goes well.
The general contractor withholds 10 percent under the subcontract, matching what the owner withholds from them. Across the life of that scope, two hundred thousand dollars accumulates in retainage.
The sub's entire profit on the job is eighty thousand. The withheld amount is two and a half times that, and it is unavailable for anywhere between four months and two years depending on when the project reaches closeout.
That subcontractor is not being asked to post security worth a fraction of their upside. They are financing the owner's risk with money they have already earned and already spent on labor, because payroll went out weekly while the retainage accrued.
Why it compounds down the tier
Retainage cascades. The owner holds from the general contractor, the general contractor holds from each subcontractor, and a subcontractor with a second-tier sub holds again.
Each tier passes the withholding down while absorbing none of it, so the party furthest from the money, usually the smallest company with the thinnest balance sheet and the least access to credit, carries the largest proportional burden. A specialty sub on a fifty thousand dollar scope is out five thousand dollars, which for a four-person shop is a payroll cycle.
That is the structural reason retainage reform keeps appearing in state legislatures. Most states now cap retention on public work and set a release clock, and a number require the withheld funds to be held in an interest-bearing escrow account rather than in the owner's operating cash.
The part that turns bad into worse
Retainage on completed work keeps getting held for reasons that have nothing to do with that work.
A curtain wall sub finishes in month nine of a twenty-two month job. Their scope is complete and the inspector has signed it off. Their retainage stays withheld until the project reaches substantial completion, because the release is tied to the project milestone rather than to the scope milestone, and a landscaping delay in month twenty holds their money as effectively as a defect would.
Early release provisions exist to fix this. They appear in negotiated subcontracts more often than in the ones a sub receives as a take-it-or-leave-it package, and they are worth asking for by name: partial release of retention on scopes that have reached final acceptance.
The second problem is closeout paperwork. Final retainage typically releases against a package of as-builts, warranties, operation and maintenance manuals, final lien waivers, and consent of surety. Any one missing document holds the whole payment, and the missing document is frequently a warranty letter from a manufacturer no one has chased since spring.
What a system should do about it
Retainage is arithmetic that a database can do continuously and a spreadsheet does quarterly, which is the whole gap.
A subcontractor should be able to answer three questions without calling anyone. How much of my money is currently held, across how many jobs. Which of those scopes has reached final acceptance and is therefore eligible for early release under the subcontract terms I signed. Which specific closeout document is blocking each release.
Most firms cannot answer the first question quickly, because retainage lives as a column on individual pay applications rather than as a balance on a counterparty. Aggregating it across eleven active jobs means opening eleven files.
Track the withholding as a running position rather than a line item, tie its release to the scope's own acceptance date instead of the project's, and attach the closeout checklist to the payment it gates. None of that is difficult engineering. It is a modeling decision about what the primary record is, and treating a pay application as the primary record is what makes retainage invisible until someone goes looking for it.
The uncomfortable arithmetic
A subcontractor running eight jobs at 10 percent retention with an average sixty percent completion is carrying a mid-six-figure receivable that no bank will lend against at a good rate, on margins in the low single digits.
That position is why a healthy contractor with a full backlog can fail inside a quarter, and it is worth understanding before you decide their payment terms are unreasonable.