A lien waiver is a signed statement from a vendor giving up the right to file a mechanics lien against the project for work covered by the waiver. Conditional waivers take effect only after payment clears. Unconditional waivers take effect the moment the vendor signs, regardless of whether payment ever arrives. The difference matters because picking the wrong one at the wrong time is how builders lose lien rights and how owners pay twice.
The four variants
Every U.S. residential project uses some combination of these four waivers. The names differ by state but the function does not.
| Waiver | When used | Takes effect | Who it protects |
|---|---|---|---|
| Conditional progress | Each interim draw | When payment clears | Vendor |
| Unconditional progress | After interim payment received | On signature | Builder / owner |
| Conditional final | Final draw, before payment | When final payment clears | Vendor |
| Unconditional final | After final payment received | On signature | Builder / owner |
The timing rule
The rule that protects everyone is straightforward and rarely followed by accident: a vendor signs conditional on the way out and unconditional on the way back. The conditional waiver is delivered with the invoice, attached to the draw package, and certified to the lender. Once the wire arrives and the vendor confirms the funds are in their account, the vendor signs an unconditional waiver covering that period. The builder collects the unconditional waivers and ships them with the next draw to prove prior periods are clean.
When this sequence is reversed (vendor signs unconditional first), the vendor has waived lien rights for work they have not yet been paid for. If the check bounces, the bank pulls financing, or the project changes hands mid-build, the vendor has no recourse. Sophisticated subs refuse to sign unconditional waivers ahead of payment for exactly this reason.
State variation matters
Ten states require statutory waiver language: California (Civ. Code §§ 8132–8138), Texas (Property Code Chapter 53), Florida (Fla. Stat. § 713.20), Georgia, Mississippi, Missouri, Nevada, Utah, Wyoming, and Arizona. Using a generic AIA waiver in a statutory state can leave the waiver vulnerable to challenge if a dispute reaches court.
California is the strictest example. The four variants are spelled out in statute with exact language; substituting a non-statutory form is unenforceable. Texas added similar requirements in 2011 and tightened them in subsequent revisions. Florida requires unconditional waivers to recite the exact dollar amount of payment received and the date the funds cleared.
On any project that crosses a state line for an out-of-state lender, or on any project where the title company is in a different state from the work site, the waiver template needs to match the state where the work is performed, not where the lender or builder is based.
Practical recommendations
- Default to conditional for every interim draw. The conditional progress waiver protects the vendor against payment failure and still satisfies the lender, because the lender is the one releasing the funds the waiver is conditioned on.
- Issue unconditional progress waivers within 48 hours of payment. Wait for the wire to clear and the vendor to confirm receipt, then send a single-link e-signature request. Done same week, the next draw includes them automatically.
- Use statutory templates when the state requires them. Keep a per-state library and pick by project location, not by the builder’s office state.
- Track partial vs. final. A vendor doing both rough and finish work on the same trade gets conditional/unconditional partial waivers on the rough phase and conditional/unconditional final waivers when the finish work closes out. Mixing the two is a common audit finding.
What a clean waiver trail looks like
On a residential project with twelve to twenty vendors and seven to eight draws, a clean waiver trail is a folder containing: one conditional progress waiver per vendor per draw they billed, one unconditional progress waiver per vendor per draw after payment, one conditional final and one unconditional final per vendor at project close. For a typical build, that is roughly 200 documents. The sole reason it is hard to maintain is that nobody is paid to chase them on a schedule, and they are easy to defer until the lender asks.
The mechanism that makes this tractable is generating the waivers from the same line-item data that drives the draw package. When a vendor is billed on a draw line, the conditional waiver is produced automatically. When the lender wires the draw, the unconditional waiver is queued for vendor signature. The vendor signs from one link, and the document files itself against the project. None of this is sophisticated software; the value is the discipline of doing it on the same schedule as the draw, every time.