If you run payments for a general contractor, you handle lien waivers every pay cycle. Get the type wrong — or release one a beat too early — and you can pay a subcontractor in full and still face a lien from that same sub. Here is the practical version every AP clerk and project accountant should have memorized.
The four lien waiver types
There are two variables: timing (is the waiver conditioned on payment actually clearing?) and scope (does it cover one progress payment, or the whole job through final?). That gives four documents:
| Waiver | Releases lien rights… | Use when |
|---|---|---|
| Conditional progress | …for this progress payment, only once payment clears | Collecting a waiver before you release a progress payment |
| Unconditional progress | …for this progress payment, immediately | The progress payment has already cleared |
| Conditional final | …through final completion, only once final payment clears | Closing out, before final payment lands |
| Unconditional final | …through final completion, immediately | Final payment has cleared |
The word that matters is conditional. A conditional waiver only takes effect if and when the payment it references actually goes through. An unconditional waiver gives up the lien right the moment it is signed — no strings.
The mistake that creates exposure
The classic error is collecting an unconditional waiver before the payment clears. The sub signs away their lien rights, your check bounces or the ACH reverses, and now the sub is unpaid and has waived their leverage. That is bad for them — and it is exactly the kind of dispute that ends up in front of a judge, with your project caught in the middle.
The mirror-image mistake hurts you: paying a sub and forgetting to collect the unconditional waiver afterward. You hold a conditional waiver, the payment cleared, but you never captured the document that proves the lien right is actually extinguished. On paper, the lien is still live.
The safe sequence for a progress payment is almost always:
- Collect a conditional progress waiver up front.
- Release the payment.
- Once it clears, collect the matching unconditional progress waiver.
Do that every cycle and your lien file is airtight at closeout.
Why this is so easy to get wrong
The sequence above is simple to describe and miserable to enforce by hand. Someone has to email the right waiver type, wait, confirm the payment cleared, then chase the unconditional version — across dozens of subs, every month. A single skipped step two pay periods ago is invisible until you are assembling a closeout packet and find a gap.
This is the entire reason lien waiver software exists: to make the document follow the money automatically instead of relying on someone to remember the order. The strongest version of that idea couples the two together — payment is staged, the sub signs, and the release happens in lockstep, which is the mechanism behind lien waiver escrow.
State rules vary — a lot
Some states (California, Texas, and others) prescribe statutory waiver forms whose exact language you are expected to use; deviate and the waiver may not hold up. Others have no mandated form at all. We keep a 50-state lien waiver library with the rules per state, and a free waiver generator if you just need a clean document right now.
SureHold is not a law firm and these templates are not legal advice. For a high-value dispute, have counsel review the specific waiver language for your state.
The bottom line
Conditional protects the sub until the money is real. Unconditional is the receipt that the lien right is gone. Collect them in the right order, capture the unconditional one every single time, and your project closes out clean.
If you would rather not police that sequence by hand, see how SureHold does it for you — payment and waiver, released together.