California Conditional Lien Waiver (§8132): The Full 2026 Guide

A California subcontractor signs your conditional lien waiver. You cut the check. Two weeks later the check bounces. The sub files a mechanic's lien against your project, walks into court, and wins. Why? Your template used "upon execution of this release" instead of California Civil Code §8132's "effective on receipt of payment". One swapped phrase, and the sub's lien rights never actually transferred.

That is the story most GCs do not hear until it happens on their own job. The conditional progress waiver in California is not a generic form you copy from a vendor's website. It is a statutory form. The legislature wrote it. The legislature requires you to use it. Anything else is, in the language of §8132 itself, null, void, and unenforceable.

This post is the deep walk-through of California Civil Code §8132: what the statute says, what every field on the form means, what voids it, and how to send and track it across a job site with 20 subs and 12 pay periods.

What §8132 actually says

California Civil Code §8132 lives inside Part 6 of Division 4 of the Civil Code — the chapter the state enacted in 2010 to clean up a century of inconsistent lien waiver practice. It went into effect on July 1, 2012. Every conditional progress waiver signed in California since then has to substantially follow the form §8132 prints inside the statute.

Here is what the statute requires. The form is titled in all caps:

CONDITIONAL WAIVER AND RELEASE ON PROGRESS PAYMENT

Right below the title, the statute requires this notice block in all capital letters:

NOTICE: THIS DOCUMENT WAIVES THE CLAIMANT'S LIEN, STOP PAYMENT NOTICE, AND PAYMENT BOND RIGHTS EFFECTIVE ON RECEIPT OF PAYMENT. A PERSON SHOULD NOT RELY ON THIS DOCUMENT UNLESS SATISFIED THAT THE CLAIMANT HAS RECEIVED PAYMENT.

That sentence is the entire deal. The waiver is conditional. The lien rights only transfer once payment actually arrives. If you alter that line, you may have created an unconditional waiver by accident, and the sub will tell that story to a judge.

Then the form lists the identifying fields you have to fill in:

• Name of Claimant (the sub or supplier signing)
• Name of Customer (you, the GC, or whoever is paying)
• Job Location (the project address)
• Owner (the property owner)
• Through Date (the cutoff date for the labor and materials covered)

Then the payment fields:

• Maker of Check
• Amount of Check: $
• Check Payable to

Then the operative release language: the claimant waives lien, stop payment notice, and payment bond rights for labor and service provided and equipment and material delivered through the Through Date, conditional on the claimant's receipt of payment of the Amount of Check.

Then the exceptions. §8132 spells out four things the release does not affect:

1. Retentions held back from the progress payment.
2. Extras for which the claimant has not received payment.
3. Previously-waived progress payments that the claimant has not yet received.
4. Contract rights, including rescission, abandonment, breach claims, and compensation for work that was not paid for.

Finally, the signature block: claimant's signature, claimant's title, and date of signature.

That is the whole form. About 200 words once the fields are filled in. The legislature picked every word on purpose, and §8132 says any deviation pushes you outside the safe harbor.

When to send the §8132 form

Send a §8132 conditional waiver with every progress pay application, before you cut the check. That is the only correct sequence in California.

The flow looks like this. The sub submits a pay application. You review it. You sign the §8132 conditional waiver request and email it to the sub. The sub fills in their name, signs, and returns the PDF. You cut the check. The check clears. The conditional waiver becomes effective the second the bank confirms payment, and the sub's lien rights for that pay period transfer to you.

If you skip the conditional waiver and send only an unconditional waiver after the fact, you have given the sub no reason to sign before the money moves. They will hold the form hostage. Pay delays compound. Payment cycles drift from 30 days to 60.

If you send the conditional waiver after the check clears, you have the wrong tool. Use the §8134 unconditional progress waiver instead.

For the verbatim template you can send today, see the California conditional progress waiver template. For the broader state-by-state context, see the California lien waiver guide and the California lien waiver requirements for 2026.

§8132 vs §8134: conditional vs unconditional progress

Both forms exist in the same chapter of the Civil Code. They are siblings. They cover the same pay period. The difference is timing.

§8132 is the conditional progress waiver. It releases lien rights only when payment clears. Send it before the check. Sign it before the check. The release does nothing until the bank confirms the funds.

§8134 is the unconditional progress waiver. It releases lien rights the moment the sub signs. Send it after the check has cleared. Get it signed as the second half of the pay cycle. No conditionality, no qualifications.

The mistake GCs make is sending the unconditional form too early. The sub signs §8134 before they have the money in hand, the check bounces or never arrives, and the lien rights are gone. Use §8132 first. Use §8134 second. Never the other way around.

For the full breakdown, see conditional vs unconditional lien waivers.

Five things that void a §8132 waiver

These are the five errors a California construction lawyer will look for first when arguing a §8132 waiver should be set aside.

1. Substituted statutory language. The NOTICE block has to read exactly as the statute prints it. ALL CAPS. Verbatim wording. A template that paraphrases the NOTICE in title case, or rewrites "effective on receipt of payment" as "upon execution," falls outside the safe harbor. §8132 says the form must substantially follow the statute. Substantially is the operative word, and courts read it strictly.

2. Missing or blank Amount of Check. The conditional release is keyed to a specific dollar figure. If the field is blank, there is no amount to condition on. The release fails. Fill in the exact pay app dollar to the cent.

3. Wrong or missing Through Date. The Through Date defines the slice of work the waiver covers. Leave it blank and the release covers nothing, or everything, depending on how the court reads it. Either reading is bad for you. Pick the cutoff date and write it in.

4. Missing project identification. Name of Claimant, Name of Customer, Job Location, and Owner all have to be filled in. A waiver that does not identify the project cannot be enforced against work on that project. A waiver that identifies the wrong project releases lien rights on a job the sub never worked on, which gives them grounds to void the form.

5. Missing signature, title, or date. A signed waiver with no printed name is challenged on identity. A signed waiver with no title is challenged on authority. A signed waiver with no date is challenged on timing. All three fields exist in §8132 for a reason. Leave any of them blank and you have created an argument for the other side.

The pattern: every blank field is a thread for opposing counsel to pull. The form takes two minutes to fill in correctly. There is no excuse for sending a half-filled one.

How to send a §8132 form: manual vs LienDone

Manual is what most GCs still do. You open a Word doc copy of the §8132 form. You fill in the fields. You email the PDF to the sub. The sub prints, signs, scans, and emails it back. You save the PDF in a folder called something like 2026-Q2-payapps. Repeat for every sub on every pay period.

This works when you have three subs on one job. It falls apart once the job grows. A 20-sub job with monthly pay apps means 240 conditional waivers per year. The folder structure decays. PDFs go missing. Subs sign the wrong version of the form. Through Dates drift. Someone copies the prior pay period's Amount of Check by accident and now the form is wrong by $4,200.

The LienDone version is one link per sub. You pick the project, pick the pay period, and the system fills in every §8132 field from the project record. The sub gets a clean signing page on their phone. They tap to sign. The signed PDF lands back in your dashboard the moment they submit. Through Date, Amount of Check, Owner, Job Location all pre-filled and validated against the statute.

If you want to check whether your current §8132 template matches the statute today, run a free AI compliance audit. Upload your form. The AI compares every clause to the verbatim §8132 text and tells you in 30 seconds whether the form would hold up in court. No signup, no payment.

FAQ

What is the California §8132 conditional lien waiver?

It is the statutory conditional waiver and release on progress payment form prescribed by California Civil Code §8132. A subcontractor signs it before payment. The release only becomes effective once they actually receive and clear the check.

Can I use my own conditional lien waiver template in California?

No. §8132 says any waiver and release given for a progress payment is null, void, and unenforceable unless it substantially follows the form in the statute. A custom template puts the release at risk. The safest path is the verbatim statutory form.

When should I send a §8132 form to a subcontractor?

Send it with every progress pay application, before the check is cut. The sub signs the conditional waiver, you release the check, and the release becomes effective the moment the check clears the bank.

What is the difference between §8132 and §8134?

§8132 is the conditional waiver on a progress payment. §8134 is the unconditional version, signed after the sub has the money in hand. Send §8132 with the pay app and §8134 as a follow-up only after the check has cleared.

What voids a §8132 waiver in court?

Five things. Substituted statutory language, a missing or moved NOTICE block, a blank Amount of Check field, a wrong or missing Through Date, and a missing signature. Any one of them gives opposing counsel grounds to set the form aside.

Does the §8132 form need to be notarized?

No. California does not require notarization on §8132 conditional progress waivers. A signature, a printed name, a title, and a date are enough.

How long should I keep signed §8132 waivers?

Keep them for at least four years per project. That covers California's general statute of limitations on contract disputes. For larger jobs, hold them for the life of the warranty plus four years.

Next steps

Two ways to take this further.

If you already have a §8132 template you have been sending for years, run a free AI compliance audit on your current template. The AI compares your form to the statutory text and flags every deviation in 30 seconds.

If you want the bigger picture before changing anything, see the full California lien waiver guide. It covers all four California statutory forms (§8132, §8134, §8136, §8138), when to use each one, and how to track signatures across multiple jobs.