Unconditional waiver and release upon final payment: only sign after the money clears

An unconditional final waiver, formally the unconditional waiver and release upon final payment, releases all your lien rights on the whole job the moment you sign, whether or not the money ever arrives. Sign it only after the final payment has cleared your account.

A subcontractor signs an unconditional waiver and release upon final payment, then watches the wire reverse three days later.

That's the worst sentence in construction payments, and it's why this form has a warning printed at the top. The unconditional final waiver releases every lien right the sub has on the job, the moment they sign. Whether the money actually arrives is irrelevant to the form's enforceability.

If you're a GC asking subs to sign one, this post explains when the form is appropriate and when it isn't. If you're a sub being asked to sign, this post is the one-line rule: not until the money clears.

The legal anchor

Two statutes prescribe the exact language for the unconditional waiver and release upon final payment in the two states where most U.S. construction dollars get spent:

• California Civil Code §8138 — Unconditional Waiver and Release on Final Payment (leginfo.legislature.ca.gov)
• Texas Property Code §53.284(e) — Unconditional Waiver and Release on Final Payment (texas.public.law)

Both statutes say the same thing two ways. The form releases all lien, stop-payment, and bond rights for the whole job, the moment the claimant signs. The claimant warrants in the document that the final payment has actually been received. And both statutes attach a warning notice at the top of the form (bold type in Texas, the largest type on the form in California), which the claimant has to see before signing.

Eleven states require a specific statutory final waiver form: California, Texas, Nevada, Arizona, Georgia, Mississippi, Missouri, Wyoming, Utah, Massachusetts, and Michigan. Florida publishes a final payment form in §713.20(5) but enforces other waivers on their own terms. The rest accept reasonable forms, but most professional GCs use a state-specific template anyway because the legal certainty is worth more than the saved minutes of using a generic.

For a state-by-state breakdown, see our guides to California lien waiver requirements and Texas lien waiver requirements.

What the form actually says

Both statutory forms include four moving parts. They look slightly different on the page, but the legal effect is identical.

1. The warning at the top. California §8138 spells it out:

NOTICE TO CLAIMANT: THIS DOCUMENT WAIVES RIGHTS UNCONDITIONALLY AND STATES THAT YOU HAVE BEEN PAID FOR GIVING UP THOSE RIGHTS. THIS DOCUMENT IS ENFORCEABLE AGAINST YOU IF YOU SIGN IT, EVEN IF YOU HAVE NOT BEEN PAID. IF YOU HAVE NOT BEEN PAID, USE A CONDITIONAL WAIVER AND RELEASE FORM.

The font has to be at least as large as the largest type elsewhere in the form. If you shrink it, the form fails substantial conformance and is unenforceable. That's not commentary. That's the rule under §8138's preamble.

2. The release language. The claimant releases all lien rights, stop-payment rights, and payment-bond rights for the entire project. Not "through a date." The whole job, top to bottom.

3. The warranty. In Texas, §53.284(e) requires the signer to warrant that they've already paid (or will promptly pay) all of their own laborers, subcontractors, materialmen, and suppliers from the funds received. California has similar trust-fund language baked in by case law.

4. The signature block. Claimant name, claimant title, date, and the claimant's signature. No notary required in California or Texas. Mississippi's statutory forms and the form printed in Wyoming's statutes include a notary block. Massachusetts doesn't: its form is signed under the penalties of perjury instead.

When to sign — the only rule that matters

Sign the unconditional final waiver after the money is in your bank account. Not when the check arrives. Not when the wire confirmation pings. After the bank says funds available.

Three reasons that matters:

• Wires reverse. ACH and wire transfers can be reversed within a window. A "received" wire is not a cleared wire until the bank confirms posting and the holding period expires.
• Checks bounce. A check from a GC's escrow account is paper until it clears. The sub's bank can show "deposited" while the funds are still on hold for 5–10 business days.
• The form is binding the second you sign. California and Texas law both say the unconditional waiver is enforceable from the moment of signature, regardless of whether the underlying payment ever lands.

If a GC asks you to sign before the funds clear, the right answer is "I'll sign the conditional final waiver now, and the unconditional once your wire posts." That's not being difficult. That's the system working as designed. The conditional version exists exactly for this gap.

For more on the conditional version, see conditional waiver and release upon final payment and what is a conditional lien waiver.

Common mistakes that turn into lawsuits

Five patterns that show up in construction litigation across the cluster of unconditional-final cases:

• Signing on the promise of payment. "We'll wire it Friday." Friday comes, the wire doesn't, and the sub has already given up their lien rights. The form doesn't care about Friday.
• Using a generic form in California or Texas. Both statutes require substantial conformance to the prescribed text. A waiver that says "I release all lien rights for the project" without the warning, the warranty, and the section structure is not enforceable. The claimant can take the payment, sign the bad form, and still file a lien.
• Removing or shrinking the warning. The notice is part of the form. If your template doesn't have it (or it's in 8-point gray text at the bottom), the form is technically unenforceable in California under §8138's preamble.
• Forgetting to carve out retention. The unconditional final waiver releases everything. If retention is being held back and not released until later, that needs to be a written exception on the form. Otherwise the sub has just signed away their right to chase the held-back retention.
• Mixing up the through-date. The final waiver isn't a through-date form. If your template still has a "through" field, it's the progress version. Final means the whole job. There is no "through."

The classic 11-day disaster: GC sends the wire, sub signs the unconditional final waiver same day, GC's bank reverses the wire on day 4 because of an account-name mismatch, GC's controller goes on PTO on day 6, sub finds out on day 11 the money never arrived, sub has no lien rights left to file. This is the exact scenario the conditional final waiver was designed to prevent. People still skip it.

How GCs should run the close-out

The clean closeout sequence for a final payment looks like this:

1. Final pay app submitted. Sub sends the final invoice with retention released.
2. Conditional final waiver signed. Sub signs §8136 in California or §53.284(d) in Texas. Lien rights release on payment clearing. Not before.
3. Payment issued. Wire, check, or ACH leaves the GC's account.
4. Funds clear. Sub's bank confirms posting. Check the actual ledger, not the deposit notification.
5. Unconditional final waiver signed. Sub signs §8138 in California or §53.284(e) in Texas. The job is closed out. No lien rights remain.
6. PDF filed. Both signed waivers go into the project's closeout folder with timestamps.

Step 4 is where most GCs cut corners and most subs get burned. The fix is asynchronous. The GC doesn't have to chase the sub the day the wire posts, and the sub doesn't have to refuse a same-day signature when the timing actually works. The fix is sending the conditional first and the unconditional second, with a clear handoff between them.

This is exactly the loop LienDone's lien waiver software was built to handle. Send the conditional with the pay app. Wait for the wire to clear. Send the unconditional. The sub signs from their phone. The PDFs file themselves.

What to ask before signing (sub side)

If you're the sub being asked to sign an unconditional final waiver, four questions before you put pen to paper:

• Has the money cleared my bank account? Not "has the wire been initiated." Cleared.
• Does the form include retention? If retention is still being held, is it carved out on the form?
• Are there outstanding change orders? If yes, those need to be on the form as exceptions or paid in full.
• Is this the right statutory form for the state? A California §8138 form on a Texas job is not enforceable. State matters.

If any of those four answers feels wrong, sign the conditional version and ask the GC to send the unconditional after the funds post. A professional GC will accept that. An unprofessional one will pressure you to sign anyway. That pressure is the warning sign. It's the same energy that shows up in why subcontractors don't sign lien waivers.

How LienDone handles the unconditional final

Send the conditional final with the final pay app. The sub opens the link on their phone, reviews the form, and signs. No login, no app to install.

Once the wire has cleared, open that signed waiver and create the unconditional final from it. LienDone sends the §8138 (California) or §53.284(e) (Texas) form with the statutory warning, and the project details carry over from the conditional you already sent. The sub signs again, from a new link.

LienDone never sends the unconditional on its own. You confirm the money landed, then you send it. The signed PDF lands in your closeout folder with the timestamp, the IP address and a unique token for the audit trail.

For the broader framework on which form fits which moment, see conditional vs unconditional lien waivers.

The takeaway

The unconditional waiver and release upon final payment closes out a construction project's lien rights with a single signature. It's the legal equivalent of a final receipt. Like a receipt, it should only be issued after the money has actually changed hands.

For GCs: send the conditional first, wait for clearance, send the unconditional second. That's the safe pattern in every state.

For subs: don't sign the unconditional until your bank says funds available. The form's warning is there for a reason.

For both: use the statutory form for the state. California §8138 and Texas §53.284(e) are the two big ones. A generic form in either state can be unenforceable, which is the worst of both worlds: the sub gives up their rights and the GC doesn't get the legal protection they thought they paid for.