Pay-When-Paid and Pay-if-Paid Clauses: A Contractor's Guide
Payment clauses that condition what you receive on when or whether the GC gets paid are some of the most litigated language in construction. They are also easy to miss in a long subcontract because they look like timing language, not risk transfer.
Before you price
Pay-when-paid vs. pay-if-paid
These two clauses sound similar and are often confused. They work very differently.
Pay-when-paid sets a timing condition: the GC will pay the sub within a reasonable time after the GC receives payment from the owner. If the GC does not receive payment, the sub is still entitled to be paid. It just takes longer. Courts in most states treat this as a timing provision, not a risk-shifting provision.
Pay-if-paid goes further: if the GC does not get paid by the owner, the sub does not get paid at all. The sub's right to payment is contingent on the owner paying the GC. This is genuine risk transfer from the GC to you.
How to tell which one you have
Courts look at specific language to decide which type of clause is in front of them. The key words are 'condition precedent'.
If the clause says payment from the owner is a 'condition precedent' to the GC's obligation to pay the sub, or uses equivalent language like 'only if', 'solely from', or 'expressly contingent upon', courts are more likely to enforce it as pay-if-paid.
If the clause just says the GC will pay the sub 'when' or 'within a reasonable time after' receiving owner payment, most courts read that as a timing provision. Your right to payment survives even if the GC does not collect.
If you are unsure, read it to a construction attorney. The difference is thousands of dollars in a dispute.
Which states allow pay-if-paid
Several states have laws that make pay-if-paid clauses unenforceable. California, New York, Wisconsin, North Carolina, and others void these clauses or limit how far the risk transfer can go.
Other states enforce them if the language is clear enough. Texas, Florida, and a majority of states will uphold a pay-if-paid clause that explicitly uses condition precedent language.
Know the law in your state before you sign. A clause that is unenforceable in California is a serious risk transfer in Texas.
What to do when you find one
First, identify whether it is pay-when-paid or pay-if-paid based on the language.
Second, assess the owner's creditworthiness. A pay-if-paid clause with a well-funded public agency as the owner is different risk than the same clause on a speculative private development. Owner default risk is what you are accepting.
Third, try to negotiate. Reasonable asks: remove the condition precedent language, cap the pay-if-paid exposure at a percentage of the subcontract, or require the GC to pursue the owner diligently before invoking the clause against you.
Fourth, price the risk. If the clause stays, the job has a tail risk that most jobs do not. That is worth something in your margin.
Fifth, track your notice rights. Most states have lien laws that protect subs regardless of contract language. Know your lien deadline and hit it if payment is slow, regardless of what the contract says.
The clause you actually have to read
Payment clauses are buried in subcontracts, often in the middle of a definitions section or a general conditions flow-down. They do not announce themselves.
The practical move before signing any subcontract: search for the words 'paid', 'condition', 'owner payment', and 'receipt'. Read every sentence that contains those words. That is where the payment risk lives.