Retainage is a common construction practice in which a portion of payments due to a contractor or subcontractor is withheld until agreed project milestones or completion requirements have been satisfied. When used appropriately, retainage is intended to incentivize contractors and subcontractors to complete work to the expected standard and ensure that defects or deficiencies are remedied before final payment is released.
In contrast to unexpected payment delays, retainage is intentionally withheld under contractual terms. As such, disputes do not typically center on whether funds are owed, but on whether the conditions for release have been met and when the retained funds should be released.
This article explores how retainage disputes can arise, the regulatory landscape, and the steps contractors and subcontractors can take to reduce the risk of payment delays.
Retainage can strain cash flow at every tier of the contracting chain. In some cases, retained funds represent a substantial portion of a project’s profit margin. This can leave contractors to cover labor, materials and other operating expenses before payment is received. The impact may be particularly significant for subcontractors, who often complete their scope well before the project finishes and may wait weeks, months or even years for release of retainage. These challenges may increase on projects involving multiple tiers of subcontractors, where retainage must pass through several parties before reaching the contractor owed payment.
Compounding the issue, retainage is often not released until “substantial completion,” a term with no universal definition. Contract language can be vague or open to interpretation. For example, one party may believe substantial completion is achieved when the work is usable for its intended purpose, while another may contend that outstanding punch-list or project closeout items must be completed first. Such disagreements can delay the release of retained funds. This can prolong cash-flow challenges and increase tension between parties.
Retainage disputes are not limited to disagreements over substantial completion. Broader project disputes, such as allegations of defective work, project delays, backcharges or other contractual deficiencies, may also result in retainage being held pending resolution of the underlying issues. In some cases, the dispute may have little to do with retainage itself; instead, the retained funds serve as leverage in a broader disagreement over project performance.
Matters can be further complicated if a subcontract ties the release of a subcontractor’s retainage to the general contractor’s receipt of retainage from the owner. In such cases, a subcontractor may face payment delays because of disputes or delays elsewhere in the contracting chain, even if their own work is complete and undisputed.
Retainage practices are often subject to statutory and regulatory requirements. Depending on the jurisdiction, state retainage and prompt-payment laws may restrict the amount of retainage that can be withheld, establish timeframes for its release or impose other requirements. Regulatory requirements can vary by jurisdiction and between public and private construction projects, and may change over time. As such, retainage provisions that are compliant on one project may not be compliant on another. Organizations should review applicable requirements at the outset of a project and consider having contracts reviewed by an attorney.
Organizations should also consider the following measures to reduce the likelihood of retainage disputes:
While retainage is intended to protect project stakeholders, unclear contract provisions and disputes over project completion can create payment delays and cash-flow challenges. Organizations can reduce the risk of disputes by understanding applicable state and federal requirements, establishing clear contract language and maintaining thorough documentation to support the timely release of retained funds.
Contact us today for additional risk management guidance.
Article Published By: Zywave, Inc.