The difference between pay-if-paid and pay-when-paid clauses comes down to one question: if the owner never pays the general contractor, does the general contractor still owe the subcontractor? Under a pay-when-paid clause, yes — payment is only delayed. Under a pay-if-paid clause, often no, because the owner’s payment is a condition the subcontractor must wait on, perhaps forever. That single difference can decide who absorbs hundreds of thousands of dollars in loss when a project goes sideways.
What a Pay-When-Paid Clause Actually Does
A pay-when-paid clause is a timing mechanism. It says the general contractor will pay the subcontractor within a set number of days after the contractor receives payment from the owner. A typical version reads: “Subcontractor will be paid within seven days after Contractor’s receipt of payment from Owner for Subcontractor’s work.” The duty to pay is not in doubt. Only the schedule depends on the owner.
What happens when the owner’s check never arrives is the part that matters. Courts treat a pay-when-paid clause as a covenant to pay within a reasonable time, even if the owner goes silent or disputes the invoice. The contractor still owes the money. The collection risk stays with the contractor.
“Reasonable time” is less tidy. Courts have found waits of more than two years unreasonable, and one federal court drew the same line at three years. Below that, there is no bright line at six months or a year. For a subcontractor stuck waiting past a few months, the lien and bond deadlines keep running regardless, and they will not pause while anyone argues over what reasonable means.
What a Pay-If-Paid Clause Actually Does
A pay-if-paid clause is a different animal. It makes the owner’s payment to the general contractor a condition precedent to the contractor’s obligation to pay the subcontractor. In plain terms: no payment from the owner, no payment to the sub. The risk of owner nonpayment shifts downstream to the party with the least leverage over the owner.
The practical reach is wider than most subcontractors expect when they sign. The sub finishes the work, pays its workers and suppliers, and then learns that its right to be paid depends on a financial relationship it has no part in. If the owner disputes the contractor’s billing, files for bankruptcy, or refuses to pay for reasons unrelated to the sub’s performance, the sub may have no contractual remedy against the contractor at all.
How to Tell Which Clause You Have
The two clauses often look alike on the page, and the difference turns on a few words. In a majority of jurisdictions, courts require the phrase “condition precedent” to appear in the contract before they will enforce a clause as pay-if-paid. Writing “if” instead of “when” is not enough on its own. What courts look for is whether both parties clearly intended to shift the risk of owner nonpayment to the subcontractor.
Consider two clauses side by side. “Contractor shall pay Subcontractor within 30 days of receipt of payment from Owner” looks like it might shift the risk, but most courts read it as pay-when-paid because it does not create a condition precedent or state that the sub assumes the collection risk. Compare: “Receipt of payment from Owner is an express condition precedent to Contractor’s obligation to make payment to Subcontractor, and Subcontractor assumes the risk of Owner’s non-payment.” That second version has the specificity courts demand.
When language falls somewhere in between, the default is pay-when-paid. Courts presume parties did not intend to shift collection risk unless the contract makes that shift unmistakable. Ambiguity works in the subcontractor’s favor.
Where Pay-If-Paid Clauses Are Void or Limited
A carefully drafted pay-if-paid clause can still be unenforceable depending on where the project sits. Several states have banned these clauses outright or sharply restricted them. California’s Supreme Court voided pay-if-paid clauses on the ground that they function as a waiver of subcontractors’ constitutionally protected mechanics lien rights. New York, North Carolina, and Massachusetts have reached similar conclusions through different legal reasoning.
States that do enforce pay-if-paid clauses impose guardrails. The language must be unambiguous. The subcontractor must clearly understand what it is agreeing to. The clause often must be conspicuous rather than buried in boilerplate. Ohio courts, for example, have held that the words “condition precedent” are clear enough to signal that a subcontractor is giving up its right to payment if the owner defaults, including giving up mechanics lien rights. That is the opposite conclusion from California on the same question.
This is also where the pay-if-paid question connects to lien rights more broadly. In a majority of states, courts find that a valid pay-if-paid clause effectively waives the sub’s mechanics lien and payment bond remedies, on the theory that the sub agreed to the condition and accepted the risk. A substantial minority treat lien rights as statutory or constitutional protections that private contracts cannot waive. Because a mechanics lien attaches to the property itself and can force a sale to satisfy the debt, it is often the sub’s strongest leverage. Losing it leaves a breach-of-contract claim against a potentially insolvent contractor and no security interest in the project.
The lesson for anyone working across state lines: the same clause can flip from enforceable to void depending on jurisdiction. Assuming it works the same way everywhere is one of the more expensive mistakes in construction contracting.
The Prevention Doctrine
Even in states that enforce pay-if-paid clauses, the contractor cannot cause the condition to fail and then hide behind it. The prevention doctrine holds that if the contractor is the reason the owner did not pay, the contractor cannot use the pay-if-paid clause to avoid paying the sub. The principle is simple: you cannot benefit from the failure of a condition you caused.
This covers the obvious case of a contractor who never submits pay applications. Courts have gone further. At least one has held that the prevention doctrine does not distinguish between deliberate and inadvertent conduct. If the contractor’s sloppy paperwork or its own dispute with the owner caused the payment to stall, and the sub had nothing to do with the problem, the contractor may not be able to rely on the clause at all.
For subs, this is a critical fallback. Proving that the contractor caused the nonpayment takes documentation: submittals, change orders, inspection approvals, and the paper trail between the contractor and owner about any payment dispute.
Federal Projects Override Both Clauses
On federal construction work, the question is largely settled by regulation. The Federal Acquisition Regulation requires every contract over $100,000 for construction, alteration, or repair of federal buildings or public works to include both a performance bond and a payment bond under the Miller Act.1Office of the Law Revision Counsel. 40 U.S. Code 3131 – Bonds of Contractors of Public Buildings or Works The payment bond must equal the total contract amount unless the contracting officer finds that impractical, and it cannot be less than the performance bond.
Federal prompt payment rules effectively override pay-if-paid clauses. The FAR requires every prime contractor to include a clause in each subcontract obligating the contractor to pay the sub within seven days of receiving payment from the government, with an interest penalty for late payments at the rate set by the Secretary of the Treasury. These requirements flow down to every tier.2Acquisition.gov. 52.232-27 Prompt Payment for Construction Contracts
Subcontractors on federal projects who have not been paid in full within 90 days after finishing their work can sue directly on the payment bond. A sub-subcontractor with no direct relationship to the prime can do the same if it gives written notice to the contractor within 90 days of completing work. The action must be filed in federal district court within one year of the last day labor was performed or material was supplied.3Office of the Law Revision Counsel. 40 U.S. Code 3133 – Rights of Persons Furnishing Labor or Material Courts hearing Miller Act claims have generally refused to let pay-if-paid clauses defeat recovery on the payment bond.
Practical Steps for Subcontractors
Knowing the difference is the first step. The real question is what to do when a contract lands on your desk with payment-conditioning language in it.
- Read for “condition precedent” before you sign. Pay-if-paid language is routinely buried in standard forms. If the clause says you assume the risk of owner nonpayment, it is pay-if-paid regardless of whether it uses “if” or “when.”
- Ask to convert the clause. Many general contractors will agree to swap a pay-if-paid clause for pay-when-paid with a defined timeframe. A contractor who refuses may be telling you something about the project’s financial health.
- Request a joint check agreement. This requires the owner to make checks payable to both the contractor and the subcontractor so neither can cash them alone. It does not change the contract, but it blocks the contractor from diverting your payment.
- Ask for a subcontract payment bond on private projects. These typically cover 100 percent of the subcontract amount with first-dollar coverage and no deductible.
- Preserve lien rights regardless of what the contract says. Send preliminary notices and file within your state’s deadlines. In states that protect lien rights from contractual waiver, the lien is your strongest tool. In states that allow waiver, filing promptly at least preserves the argument.
- Document everything. If the prevention doctrine comes into play, your records of submittals, approvals, and correspondence about any payment dispute between the contractor and owner are what the argument rests on.