Conditional lien waiver: the pillar guide for GCs and subs (2026)

A conditional lien waiver is the form you send before the payment clears. If the funds settle, the lien rights release. If they don't, the lien rights stay alive.

That one sentence is the whole product. The rest is plumbing: which of the four variants fits the moment, which states make you use a specific form, and how to keep the through-date from drifting one pay period off your check.

This guide is the pillar version. If you only need the short answer, what is a conditional lien waiver covers the basics in seven minutes. This post goes wider: the legal mechanics, the four-form matrix, every U.S. state with a statutory requirement, the timing rules, and how to avoid the four mistakes that make GCs eat checks twice a year.

What a conditional lien waiver actually does

A lien waiver is the signed receipt that a contractor, subcontractor, or supplier gives up their right to file a mechanic's lien for a specific scope of work. The signature is the consideration. The check is the consideration on the other side. Sign and pay, and the dispute layer goes away.

The "conditional" part adds one rule: the release of lien rights only fires after the payment described on the form actually clears.

It's a contingent promise. The sub signs first. The GC sends the check. When the funds settle in the sub's account, the waiver's condition is met and the lien rights release on that date for that amount. If the check bounces, the wire reverses, or the ACH gets rejected by the sub's bank, the waiver has no legal effect. The sub keeps every lien right they walked in with.

Compare that to an unconditional lien waiver, which releases lien rights the moment the sub signs. There's no condition, no clearing window, no safety net. That's why these two forms exist as a pair. One is for "we're about to pay." The other is for "we already paid, here's the audit trail."

The four-type matrix

Lien waivers fall into a 2x2: payment phase (progress vs final) on one axis, payment status (conditional vs unconditional) on the other.

Type	When to send	What it releases
Conditional progress	You're cutting a check today for work through a specific date	Lien rights through that date, only after the payment clears
Unconditional progress	The check for that pay period already cleared the sub's account	Lien rights through that date, immediately on signature
Conditional final	You're sending the last payment of the job	All lien rights for the entire project, only after the final payment clears
Unconditional final	The final check cleared and you want the closeout document	All lien rights for the entire project, immediately on signature

The pattern that makes this easy to remember: conditional is for "we're about to pay," unconditional is for "we already paid." Progress vs final is just the time horizon — one pay period or the whole job.

Two of the four are conditional. Those two are the workhorses. About 90% of waivers a healthy GC sends in a year are conditional progress, with conditional final at closeout. The unconditional versions are audit-trail forms that show up in your dashboard after the money moved, not before.

For the side-by-side breakdown, conditional vs unconditional lien waivers goes deeper on the four types and the trap GCs fall into when they reverse the order.

Conditional progress payment waiver

This is the form you send most often. Cut a check today for work through April 30, generate a conditional progress waiver, sub signs, you release the funds, the funds settle, the lien rights for that period release.

The form itself needs five elements regardless of state:

• Claimant identification. Legal name of the sub or supplier.
• Project identification. Job address and owner name.
• Through-date. The cutoff date for the work being released.
• Payment amount. The dollar figure the release is conditioned on.
• Signature. Wet or electronic. The federal E-SIGN Act makes electronic signatures valid in every U.S. state for this kind of document.

What the form deliberately leaves alive: disputed claims, retentions, unbilled extras, change orders not yet billed, and anything covered by a prior unconditional waiver. Most statutory forms list these carve-outs by name so a sub doesn't accidentally release a retention or a pending change order.

Send this with every pay app. It is the cheapest insurance you'll ever pay for, because the cost is one signature and the upside is the sub keeps their lien rights alive if your check fails.

Conditional final payment waiver

Same structure, different scope. The conditional final waiver releases all lien rights for the entire project, on the condition the final payment clears.

Send it with the final pay app. The sub signs, you cut the final check, the funds settle, and the sub's lien rights for the whole job release on that day. The signed PDF becomes your closeout document.

A few patterns where the conditional final is the right call but GCs send the wrong form:

• There's an open change order dispute. Don't send a conditional final. Send a conditional progress waiver for the undisputed work, leave the disputed amount alive, and resolve that piece on its own track.
• The retention hasn't released yet. Send the conditional final without the retention amount, and a separate conditional progress waiver when the retention finally moves. Two forms, two clean releases.
• The sub still has warranty work pending. The conditional final releases lien rights for the work, not the warranty obligation. The sub's warranty exposure survives the waiver. Make sure the sub knows that before they sign anything.

The Construction Financial Management Association covers more of these closeout edge cases in their lien waiver essentials guide.

States that prescribe a specific conditional form

For most U.S. states, a clean conditional waiver in plain English with the five elements above is legally sufficient. In twelve states, the statute prescribes specific language, and a generic form is unenforceable.

The twelve: California, Texas, Florida, Nevada, Arizona, Georgia, Mississippi, Missouri, Wyoming, Utah, Massachusetts, and Michigan. Five of those (CA, TX, FL, NV, AZ) cover the lion's share of U.S. construction volume, so most GCs hit the statutory-form requirement on at least one of their projects.

California: Civil Code §8132 and §8136

California is the model the other statutory states tend to copy. Four sections of the Civil Code prescribe four forms.

• Civil Code §8132: Conditional Waiver and Release on Progress Payment.
• Civil Code §8136: Conditional Waiver and Release on Final Payment.

The official text lives on the California Legislative Information site. The conditional progress form requires the claimant, customer, owner, job location, through-date, and payment amount. The conditional final adds the line that releases lien rights for the entire project, contingent on the final payment.

For the full California breakdown including the unconditional variants and the bold-warning rule, California lien waiver requirements walks through all four Civil Code sections.

Texas: Property Code §53.284

Texas Property Code Chapter 53, Subchapter L did the same job in 2012. Section 53.284 prescribes four forms by reference to specific statutory language.

The conditional progress payment waiver is the most-used form on a Texas job. Section 53.281 makes any waiver that doesn't substantially follow the statutory text void, so a generic PDF is worse than no waiver at all.

A useful Texas-specific quirk: HB 2237 eliminated the notarization requirement on lien waiver forms after January 1, 2022. Older forms still circulating online sometimes show a notary block. You can drop it.

For the full Texas Property Code Chapter 53 walkthrough, Texas lien waiver requirements covers all four forms and the §53.286 prohibition on contractual lien waivers in advance.

Florida: §713.20

Florida is the soft-statutory state. The Florida Construction Lien Law (Chapter 713 of the Florida Statutes) provides a statutory form for lien waivers, but it doesn't make non-statutory forms void the way California and Texas do. What §713.20 does say: the parties cannot be required to use a non-statutory form. So if a sub demands the statutory form, the GC has to honor it.

Most Florida GCs use the statutory form anyway because it's the path of least resistance. The conditional progress and conditional final variants follow the same structure as California's §8132 and §8136.

Arizona: §33-1008

Arizona Revised Statutes §33-1008 prescribes four forms with the same conditional/unconditional × progress/final matrix. A waiver of lien that doesn't comply with the statutory form is void as against public policy.

The Arizona conditional progress waiver carries one specific quirk: a 90-day rule on retention. The form has a carve-out for retention amounts that aren't yet due, and the statute treats failure to include that carve-out as a substantial deviation. Use the Arizona statutory form directly, don't paraphrase.

Nevada: §108.2453 and §108.2457

Nevada Revised Statutes §108.2453 (conditional progress) and §108.2457 (conditional final) prescribe the two conditional forms. The structure mirrors California's: claimant, customer, project, through-date, amount, signature. Nevada also prohibits advance waivers of lien rights, like Texas, with a few narrow exceptions.

The other seven statutory states

Georgia, Mississippi, Missouri, Wyoming, Utah, Massachusetts, and Michigan round out the list. Each prescribes its own variant of the conditional progress and conditional final forms. The structure is similar across all of them because most copied California's 2012 model.

The fix for GCs working across multiple states: don't keep one PDF template and hope. Pick the state on every waiver request and let the right statutory language fill in.

How a conditional waiver actually fires (the timing rules)

The "release fires when the payment clears" language is a real legal trigger. Three timing rules matter.

Rule 1: "clears" means the funds settled, not "the bank acknowledged." A wire that posts to the sub's account but reverses two days later didn't clear. An ACH that lands and stays lands. A check that the sub deposits but the bank flags isn't cleared until the bank's hold drops.

Rule 2: the amount on the form has to match the payment. If the form says $48,200 and the GC pays $42,200, the conditional release fires for $42,200, not the form amount. Some courts have read the mismatch as a substantial deviation that invalidates the whole release. Match the numbers.

Rule 3: the through-date has to be earlier than the payment date. Sounds obvious. It isn't. A waiver dated April 30 with a through-date of May 15 releases lien rights for work that hadn't happened when the form was signed. That's the form the sub's lawyer wants on cross-examination.

Most software handles these for you. If you're sending waivers by email and PDF, double-check the dates and amounts the way you'd double-check a wire confirmation.

Common mistakes that cost GCs money

Four patterns show up in lien waiver disputes more than any others.

Sending unconditional with the check. The sub doesn't have the money yet. They sign, the check sits in their other receivables behind two weeks of work, the funds finally settle, and now the unconditional release fires retroactively to the signature date. If the sub catches it, you have a friendly dispute. If they don't catch it, you have a relationship problem six months later.

Using a single PDF template across all 50 states. Works in 38 states. Fails in California, Texas, Florida, Nevada, Arizona, and the other seven statutory states, which together include the largest construction markets in the country.

Skipping the through-date. A conditional progress waiver without a through-date releases lien rights for an indefinite period of work. Some courts will narrow it. Many won't. It's the line item GC controllers most often miss when they cut and paste from a previous waiver.

Resending an old signing link instead of generating a new request. A waiver signed six weeks after the pay period ends doesn't reference the right scope. The dates on the form drift, the amount drifts, the through-date drifts. Generate a fresh request, don't recycle.

For more on what makes subs hesitate to sign, why subcontractors don't sign lien waivers covers the seven reasons subs push back and how to fix the workflow before it becomes friction.

How LienDone handles conditional waivers

When you generate a waiver request in our lien waiver software, the type defaults to conditional progress. That's the right answer for 90% of pay periods, and the form picker will surface the right state-specific statutory language the moment you pick the project state.

The amount and through-date pre-fill from the pay app. Your sub clicks the link in their email, signs in two minutes on their phone, and the signed PDF lands in your dashboard with a timestamp and IP address logged for the audit trail. No login. No account creation on their side. The signing experience markets your professionalism, not LienDone's.

When the funds settle, you can send the matching unconditional waiver in one click to close out the audit trail. The unconditional form pulls the same statutory language for the same state, so the pair always matches.

For a step-by-step walkthrough of the day-to-day flow, how to send a lien waiver in two minutes covers the four-step pattern from generate to file.

Where the conditional waiver fits in the bigger picture

The conditional lien waiver is one form in a wider compliance loop. It sits alongside the waiver of lien form (the broader category), the contractor lien waiver (the GC's signed release upstream), and the contractor lien release (the document filed once a lien has already been recorded).

For closeout specifically, conditional waiver and release upon final payment goes deeper on the final variant and how it interacts with retention and warranty.

If you've got a project in California, Texas, Florida, Nevada, or Arizona, the right move is to combine this guide with the state-specific deep dive. Use the right statutory form for the right state, on every progress payment and at closeout. That's the entire compliance loop, and it's the loop that prevents 80% of lien disputes from happening at all.

The takeaway

A conditional lien waiver releases lien rights only when the payment clears. It's the form you send before you cut the check, on every progress payment and at closeout. Pick the right state form, fill the through-date and amount honestly, and file the signed PDF the moment the funds settle.

That's the rule. Everything else in this post is a footnote.

FAQ

What is a conditional lien waiver?

A signed release that only takes effect once the payment described on the form actually clears. If the check bounces, the waiver has no effect and the lien rights stay alive.

When should you use a conditional lien waiver instead of unconditional?

Any time the payment hasn't cleared yet. Switch to unconditional only after the funds settle in the sub's account.

What's the difference between a conditional progress and conditional final waiver?

Progress releases lien rights for work through a specific through-date. Final releases all lien rights for the entire job, on the condition the final payment clears.

Do all 50 states use the same conditional lien waiver form?

No. Twelve states require a specific statutory form. The other 38 accept a generic waiver with the right elements.

Is a conditional lien waiver legally binding?

Yes. It's a binding contract once signed. The condition just means the release only triggers when the payment goes through.

Can a subcontractor refuse to sign a conditional lien waiver?

They can, but most won't. Conditional is the form that protects the sub. A refusal usually signals a billing dispute on the underlying invoice.