These two clauses look almost identical and do completely different things. Pay-when-paid controls the timing of your payment, so you still get paid even if the owner never pays the GC. Pay-if-paid makes the owner actually paying the GC a condition of you ever getting paid at all, so if the money never comes down from the top, you legally eat the loss. One is a schedule. The other is a trap. On a subcontract, this is the clause that decides who carries the risk when the owner goes broke or stops paying, and a handful of states ban the trap version entirely. Here is how to tell them apart and what to do about it.
What pay-when-paid actually means
A pay-when-paid clause sets when the GC has to pay you, not whether. It says the GC will pay you within some period after the GC gets paid by the owner. The key word courts read into it is "reasonable." If the owner drags out payment, the GC can wait a reasonable time, but the GC's promise to pay you is unconditional. If the owner never pays at all, the GC still owes you after a reasonable period has passed. The risk of the owner not paying stays with the GC, where it usually belongs, because the GC is the one who chose the owner and manages that relationship.
What pay-if-paid actually means
A pay-if-paid clause is a condition precedent. It says, in plain effect, that the owner paying the GC is a required condition before the GC owes you anything. No payment from the owner, no obligation to you, ever. This does not delay your payment. It can erase it. The clause permanently shifts the risk of the owner going insolvent or refusing to pay off the GC and onto you, the sub who did the work and has the least control over whether the owner pays. You can install a perfect job and still legally collect nothing.
How to spot the difference in the contract
Courts do not go by the label at the top of the clause, they go by the words. Most courts, when the language is ambiguous, read it against being a condition precedent and treat it as pay-when-paid timing instead. That default protects subs. To create a true pay-if-paid, the risk-shift has to be spelled out, unmistakably, in the contract.
- Language that usually reads as pay-when-paid (timing only): "Contractor shall pay Subcontractor within X days of receipt of payment from Owner," or "payment is subject to receipt of payment from the Owner." Vague conditional wording generally fails to create a true condition precedent.
- Language that creates a real pay-if-paid (the dangerous kind): wording that expressly makes owner payment a condition of any obligation, for example "Contractor's obligation to pay Subcontractor is expressly conditioned upon, and shall not arise unless and until, Contractor receives payment from Owner," or any clause that flatly calls owner payment "a condition precedent."
If you see the words "condition precedent," or "shall not arise unless and until," slow down. That is the version that can leave you unpaid.
Some states ban pay-if-paid outright
This is the part that varies the most, so it is the part you have to check for your own state. A number of states have decided pay-if-paid clauses are void as against public policy, often because they collide with a sub's lien or prompt-payment rights. California, for example, has voided pay-if-paid for decades, and New York treats them as unenforceable as a general rule. Several other states void them too, sometimes only on private work, sometimes with exceptions like owner insolvency. In those states, a pay-if-paid clause in your subcontract is simply unenforceable and reverts to a timing obligation.
In the rest of the country, pay-if-paid is generally enforceable, but only when the risk-shift is unambiguous. Whether your state bans it, allows it, or allows it only with crystal-clear wording is a state-by-state question, and it is exactly the kind of thing that changes with new legislation. Do not assume. Get your state's rule from Working in Your State before you sign or before you decide you are out of options on an unpaid job.
What to do about it before you sign
- Read the payment clause every time, on every subcontract. Look for "condition precedent" and "unless and until."
- Try to strike or soften it. Ask for it to be changed to a straight pay-when-paid, or add a backstop: "in no event shall Subcontractor go unpaid for more than X days after completion, regardless of Owner payment."
- Protect your other rights. A pay-if-paid clause does not automatically kill your mechanic's lien or bond-claim rights, which run against the property or the surety, not the GC's promise. In many states those rights survive even a valid pay-if-paid clause. Send your preliminary notices and preserve your lien and bond deadlines on every job so you have a second way to collect if the contingent-payment clause bites.
- Price the risk. If a GC insists on a true pay-if-paid clause, you are being asked to become the owner's lender for free. Factor that into whether you take the job.
Common questions
Is pay-if-paid legal?
In many states pay-if-paid is enforceable if the contract makes owner payment an unmistakable condition precedent, but a number of states have voided it entirely as against public policy. California and New York are well-known examples of states that treat pay-if-paid as unenforceable, and several others ban it too, sometimes only on private projects. Whether it is legal in your state, and with what exceptions, is strictly a state-by-state question, so confirm it in Working in Your State before you rely on it or fight it.
What is the difference between pay-if-paid and pay-when-paid?
Pay-when-paid controls the timing of your payment and still requires the GC to pay you within a reasonable time even if the owner never pays; pay-if-paid makes owner payment a condition, so if the money never comes down, the GC never owes you. Pay-when-paid keeps the risk of owner non-payment on the GC. Pay-if-paid shifts that risk onto you, the sub. Courts read ambiguous clauses as pay-when-paid, so the dangerous version only exists when the risk-shift is spelled out clearly.
How do I know if my subcontract has a pay-if-paid clause?
Read the payment clause and look for condition-precedent language: phrases like "condition precedent," "shall not arise unless and until," or wording that expressly makes the owner's payment a requirement before the GC owes you. Vague wording like "subject to receipt of payment from Owner" usually reads as pay-when-paid timing, not a true condition. If you see the explicit condition-precedent language, that is the pay-if-paid version, and you should try to strike or soften it before you sign.
Does a pay-if-paid clause kill my mechanic's lien rights?
Usually not. A mechanic's lien runs against the property and a bond claim runs against the surety, so they generally survive even a valid pay-if-paid clause between you and the GC. In many states your lien and bond rights are protected precisely because a pay-if-paid clause would otherwise leave a sub with no way to collect. Whether and how those rights survive varies by state, so send your preliminary notices and calendar your lien and bond deadlines on every job, and confirm the details in Working in Your State.
The honest bit
- Whether pay-if-paid is void, enforceable, or enforceable only with crystal-clear wording is entirely state-specific, and states change these laws. California and New York are named here as long-settled examples of states that void it, not as a national rule. Get your own state's current position from Working in Your State.
- The prompt-payment day-counts that back up a pay-when-paid timing obligation are covered in the retainage and prompt-payment guide, and they also vary by state.
- This is general guidance, not legal advice. For a large unpaid balance under a contingent-payment clause, or before you sign a subcontract with one, a construction attorney is worth the money.
Know someone who needs this?
Keep reading
Templates you might need
Was this guide useful?
Didn't find what you were looking for?
Spotted something wrong or out of date? Email us at hello@kilnguides.co.uk.
In crisis? 988 Suicide & Crisis Lifeline 988 ·