Retainage Caps Are Changing State by State in 2026 — Is Your Contract Language Keeping Up?

Retainage law isn't static, and 2025–2026 produced a concrete example of that. New York's SB 5655, signed into law in December 2025, capped private-project retainage at 5% and voided contract terms that exceed it. That's not a minor technical adjustment — it directly overrides a GC's standard contract language if that language tries to withhold more than the new statutory cap allows, at least for the projects the law covers.

California similarly caps retainage at 5% on many projects, though the specifics vary by project type and whether the owner is public or private. This is a genuine, active area of legislative change, not a settled body of law — which means contract language that was standard and enforceable a few years ago may no longer be, depending on where the project sits today.

New York's move is also a useful signal of direction: retainage-reform legislation in recent years has moved almost uniformly toward lower caps and more protection for subcontractors, not the reverse — worth keeping in mind for any state where reform is currently being debated but hasn't passed yet.

Other states have taken different approaches to the same underlying concern — some cap the retainage rate directly, others require retainage to be reduced or released at a defined project-completion percentage — which means "know the cap" alone isn't always enough; the specific mechanism a state uses also affects how and when the protection applies.

This is the detail that trips up multi-state subcontractors and suppliers most often: retainage caps, like most construction-specific protections, are generally tied to the project's actual location — its situs — not to where your company is headquartered or where the contract happens to be signed. A Georgia-based supplier shipping materials to a New York job is subject to New York's 5% cap on that project, even though the company's home state has no such rule.

For a firm working across a handful of states, this means the "standard" retainage percentage the sales team quotes internally may simply be wrong for a specific project — not because anyone made an error, but because the legal ceiling shifted underneath a contract term that used to be fine.

This is closely related to the broader governing-law-versus-project-location confusion that trips up multi-state contractors on other clauses too — the project's physical location, not the contract's stated governing law or your company's home state, is almost always the controlling factor for these construction-specific statutory protections.

Here's the part that actually costs money: a contract stating 10% retainage on a New York private project isn't automatically corrected to 5% just because the law says so. Someone has to notice the conflict, raise it, and get the contract language or the actual withholding amount corrected — otherwise the higher number simply gets applied in practice, law or no law. An unenforceable contract term doesn't enforce itself out of existence.

That means the practical financial protection only exists if the mismatch between the contract's stated retainage and the project state's actual cap gets caught before (or during) the job — which requires knowing both the contract language and the current state-specific rule at the same time, for every project, in every state you work.

In practice, this often means money simply isn't returned unless someone actively requests it — a GC withholding at the old, higher rate has little incentive to proactively flag that the law has since capped it lower, especially if no one on the subcontractor's side has raised it.

Retainage caps and their exceptions are a moving target — more states have adjusted their rules in the past two years than in the prior decade, largely in response to the same cash-flow pressure covered in our piece on the industry's 56-day average payment wait. For a firm with projects active in five or six states at once, keeping a mental (or even spreadsheet) map of which cap applies where, and cross-checking every incoming contract against it, is a real, recurring task — not a one-time lookup.

For more background on how retainage terms work generally and what to negotiate, see our broader look at retainage law and standard positions.

A manual spreadsheet approach to tracking this also has an obvious failure mode: it's only as current as the last time someone updated it, and given how frequently these caps are changing right now, a spreadsheet built even a year ago may already be quietly wrong for several states.

Two concrete steps: first, know the project's actual jurisdiction — not your home state — before reviewing any contract's retainage clause, since that's the law that governs. Second, treat retainage-cap checking as a standard, repeatable step on every contract, not a one-off research task, since the rules keep changing.

This is exactly the kind of deterministic, jurisdiction-specific check a contract-review system should apply automatically to every contract — comparing the stated retainage against the project state's actual rule, every time, regardless of how many states you're juggling. See how RCS applies jurisdiction-specific review to catch exactly this kind of mismatch.

Whichever process you use, the goal is the same: turn a check that currently depends on someone remembering a specific state's current rule into one that happens automatically and consistently, on every contract, regardless of who's reviewing it that day.

Given how much retainage legislation has shifted just in the past year, it's reasonable to expect further changes in additional states over the next year or two — building this check into a standing process now means each new legislative update simply gets absorbed rather than requiring a fresh scramble.