Last updated August 16, 2026.
What Is a California Lien Waiver and Release?
Short answer: It is a statutory document through which a construction claimant conditionally or unconditionally waives and releases specified mechanics lien, stop payment notice, and payment bond rights in connection with a progress or final payment.
Waiver and release documents are a routine part of California construction payment administration. An owner may request releases before advancing funds. A direct contractor may collect releases from subcontractors and suppliers with each payment application. A subcontractor or supplier may sign a release to confirm the scope of rights being exchanged for payment.
The document is not a casual receipt. California Civil Code sections 8120 through 8138 establish a statutory framework and provide four forms. The correct form depends on two questions: Is the payment a progress payment or a final payment, and has the claimant actually been paid?
California law generally requires a waiver and release to be in substantially the statutory form, executed, and delivered by the claimant. For a conditional release, the law also requires evidence of payment before the release operates against the owner, construction lender, or payment bond surety. That is why the form, the payment record, and the underlying project documents should be evaluated together.
Why the Through Date Matters
The two progress payment forms contain a field labeled Through Date. That date defines the cutoff for the labor, services, equipment, and materials covered by the release. It is not automatically the same as the invoice date, payment application date, check date, or signature date.
A claimant should compare the Through Date with its schedule of values, approved billing period, delivery records, and change order log. An owner or direct contractor should compare it with the payment application being funded. If the date extends beyond the work included in the payment, the release may reach rights associated with work that the claimant did not intend to include.
Practical example
A subcontractor submits a payment application for work performed through July 31. The proposed progress release lists August 15 as the Through Date. Before signing, the parties should determine whether work performed during the first half of August is being paid and, if not, whether the date or exceptions need to be corrected.
The statutory progress forms also address rights tied to written change orders that were fully executed before the claimant signs. Those rights can be swept into the release through the stated date unless they fall within a listed exception. The change order log should therefore be reviewed before the release is signed.
Payment Proof for Conditional Releases
A conditional release is designed to become effective only when payment is received. California Civil Code section 8124 identifies evidence of payment as either the claimant’s endorsement on a single payee or joint payee check that has been paid by the financial institution, or the claimant’s written acknowledgment of payment.
Delivering a check is not necessarily the same as proving that the check was paid. A check can be returned, stopped, or delayed. The same practical concern applies to a joint check. Owners, developers, contractors, and claimants should retain documentation that connects the payment to the release, including the payment amount, payee, project, payment application, and applicable Through Date.
For an electronic payment, the parties should maintain the transaction record and obtain an appropriate written acknowledgment from the claimant. The payment confirmation, release, and project accounting should agree on the amount, payee, project, and payment period. Any discrepancy should be resolved before the release is treated as complete.
Read and Complete the Exceptions
The statutory forms do not all preserve the same exceptions. Progress payment forms identify categories such as retention, unpaid extras, and certain contract rights. The conditional progress form also provides space for earlier conditional progress releases for which payment has not been received.
The final payment forms are broader. Their stated exception is for disputed claims for extras in an identified amount. A claimant with an unresolved change order, retention balance, backcharge dispute, delay claim, or other open item should not assume that the word “final” leaves that issue intact. The language of the statutory form, the listed exception, the contract, and the specific facts all matter.
- Confirm the correct claimant, customer, owner, and job location.
- Match a progress release’s Through Date to the payment scope.
- Reconcile retention, extras, change orders, and prior unpaid releases.
- State permitted exceptions clearly and use accurate amounts.
- Confirm the signer has authority to bind the claimant.
- Keep the signed form with payment and accounting records.
A Practical Release Workflow
Identify the payment stage. Determine whether the payment is progress or final and whether the claimant has actually received collected funds.
Select the statutory form. Use the conditional or unconditional form that matches the actual payment status. Avoid substituting a generic receipt or a form from another state.
Reconcile the scope. Compare the release with the pay application, contract, Through Date, retention, extras, change orders, and any disputed amounts.
Coordinate payment and proof. Track the check, joint check, ACH, or wire and preserve records showing what was paid, to whom, and for which billing period.
Store a complete record. Keep the executed release, payment proof, payment application, exception support, and relevant correspondence in the project file.
For owners and developers, this workflow helps connect funding decisions with the correct tiered releases. For direct contractors, it supports consistent collection of releases from subcontractors and suppliers. For claimants, it reduces the risk of releasing more rights than the payment supports.
Common Waiver and Release Problems
Common release disputes can arise from a mismatch. The wrong form is used, an unconditional release is signed before funds clear, the Through Date is copied from an earlier application, or an unresolved extra is omitted. Other problems arise when the project name or customer is wrong, the payment amount does not match the release, or a customized form changes statutory language.
Owners and developers should also avoid treating a stack of signed conditional releases as conclusive without checking payment evidence. Contractors should avoid making release collection a purely clerical exercise. Claimants should avoid signing under schedule pressure without reconciling the document against their receivables and project records.
A sound process does not eliminate every dispute, but it makes the transaction easier to understand and document. A significant payment, disputed change order, troubled project, or uncertain release language may warrant legal review before the document is signed or accepted.
Official Sources
The following public sources contain the governing statutory framework and official form language:
