Lien waiver management: the four waiver types and when to use each

What are the four types of lien waivers, and when do you use each?

A lien waiver is a signed document in which a party that did work or supplied materials gives up its right to file a mechanics lien against the project, in exchange for payment. On a commercial job that money flows in cycles, so waivers flow in cycles too, and there is not one form but four. The four come from combining two independent pairs.

The first pair is about timing. A conditional waiver only takes effect once the payment it references actually clears. An unconditional waiver releases the lien right the moment it is signed, whether or not any money ever arrives. The second pair is about scope. A progress waiver covers work through one pay period. A final waiver covers the entire scope at job closeout. Cross the pairs and you get the four documents every back-office lead handles: conditional progress, unconditional progress, conditional final, and unconditional final.

The rule of thumb that keeps you out of trouble fits in one line. Sign a conditional waiver before money moves, and an unconditional waiver only after the funds have cleared. Conditional is the safe form to exchange against a pay application because it has no force until payment lands. Unconditional is the receipt you give once the cash is in the account and there is nothing left to protect. Get that ordering backwards and you have handed away a lien right for a payment you may never collect.

It helps to be precise about what each timing word does to the document. A conditional waiver carries language that makes the release contingent: the lien right is given up only upon, and to the extent of, actual receipt of the stated payment. If the check never clears, the waiver never bites, and the lien right survives intact. An unconditional waiver carries no such condition. It states that the lien right is released, full stop, for the amount and period shown, the instant the signature is on the page. That is why the unconditional form is dangerous to release early and harmless to release once the money is already sitting in your account. The progress-versus-final pair behaves the same way regardless of timing: progress covers work through a billing date and leaves future work and unbilled retainage protected, while final extinguishes everything for that party on the project, which is why a final waiver should never go out while any retention or open change order is still in play.

The waiver exchange flow, general contractor to sub to supplier

Waivers move alongside the monthly billing. The cycle on a typical commercial project looks like this. Each subcontractor submits a pay application for the period, usually on an AIA G702 cover with a G703 continuation that breaks the billing down by line against the schedule of values. With that application, the sub also submits a conditional progress lien waiver for the amount being billed this period.

The general contractor reviews and certifies the applications, rolls them into its own pay application to the owner, and submits its own conditional progress waiver for the combined amount. The owner pays the GC. The GC pays each sub. Only after a sub's payment clears does that sub provide its unconditional progress waiver for the prior period, which the GC collects before or alongside releasing the next round of funds. The unconditional waiver for one period typically arrives with the conditional waiver for the next, so the paperwork is always one cycle deep.

The same handshake repeats one tier down. The subcontractor must collect waivers from its own suppliers and lower-tier subs, because those parties can lien the project even though the owner and GC never paid them directly. Those are second-tier waivers, and they ride the same conditional-then-unconditional rhythm. The GC that only tracks its direct subs is exposed to every supplier invoice it never sees.

Where do these documents live in the billing package? In practice the waivers travel as attachments to the pay application itself, not as a separate stream. A complete application for the period is the G702 cover and G703 continuation, the conditional waiver for the current billing, and the unconditional waiver for the prior billing now that it has been paid, plus the lower-tier waivers the sub is required to furnish. Back-office leads who treat the waiver as part of the application rather than an afterthought rarely fall a cycle behind. The discipline is to refuse to certify or release a payment until that party's prior unconditional waiver and current conditional waiver are both in hand and both reconcile to the numbers on the schedule of values.

Worked example: a progress-payment waiver timeline

Walk one electrical sub through a single April billing cycle to see where each form lands.

The sub's contract value is 600,000 dollars (illustrative). Through March it had completed and been paid for 180,000 dollars. In April it completes another 90,000 dollars of work. Standard 10 percent retainage applies, so the April payment due is 90,000 x 0.90 = 81,000 dollars.

The timeline runs like this. On April 25 the sub submits its G702/G703 pay application showing 270,000 dollars completed to date (180,000 + 90,000) and a current payment due of 81,000 dollars, paired with a conditional progress waiver stating 81,000 dollars for the April period. On May 10 the GC, having been paid by the owner, issues the 81,000 dollar check. On May 13 the check clears the sub's bank. Only then, on May 14, does the sub hand over the unconditional progress waiver for 81,000 dollars covering April.

Notice the three figures that must agree: the 81,000 dollars on the conditional waiver, the 81,000 dollars certified and paid, and the 81,000 dollars on the unconditional waiver. If a mid-month change order had bumped the billing to 84,000 dollars but the waiver still read 81,000, the file is now 3,000 dollars short of releasing what was actually paid, and that gap will surface at closeout.

Worked example: counting waivers on a 20-sub job

Volume is what makes waiver management a real back-office function rather than a filing chore. Count the documents on a mid-size job to see the scale.

Assume 20 direct subcontractors and a 12-month build. Each sub bills monthly, and each billing cycle produces two waivers from that sub: one conditional progress with the current application, one unconditional progress for the prior period once paid. That is 20 subs x 12 months x 2 = 480 waivers from the direct tier alone over the life of the job.

Now add the second tier. Say each sub averages 3 lower-tier suppliers or subs that also need to be waived each month. At one conditional and one unconditional apiece, that is 20 x 3 x 12 x 2 = 1,440 second-tier waivers. Combined with the 480 first-tier documents, the job runs 480 + 1,440 = 1,920 waivers across the year, plus the final waivers at closeout: 20 direct subs and their roughly 60 second-tier parties give another 80 unconditional final waivers. The job clears 2,000 waivers, and any one missing document can hold up a draw or a closeout.

At that volume a spreadsheet stops being a control. The team needs a register keyed to each pay application that shows, per party per period, which waiver type is expected, what amount it should state, whether it has been received, and whether the amount matches the certified pay. That last column is the one that catches money leaking out of the job.

Tracking at scale and state variation

The tracking discipline is a matrix: every party that can lien the project, crossed with every pay period, crossed with the two waiver types. Each cell is either satisfied or open, and each satisfied cell carries a dollar figure that must reconcile to the certified application and the actual payment. Tie the register to the pay application rather than to the calendar, because the waiver only means something in relation to a specific certified amount.

State variation sits on top of all of this. Some states mandate statutory waiver forms with prescribed wording, and a form that does not conform can be unenforceable or simply invalid in that jurisdiction. Other states leave the form to the parties. Because the requirements differ by state and change over time, confirm the correct form for each project's jurisdiction with your counsel rather than reusing one template across a portfolio. The four-type framework in this guide holds everywhere; only the specific wording and which form is mandatory shift by location.

Where waiver management goes wrong

Three failure modes account for most of the damage, and each maps to a control you can put in the register.

The first is signing an unconditional waiver before payment. This is the cardinal error: an unconditional waiver releases the lien right the instant it is signed, so handing one over against a promise rather than cleared funds means giving up leverage on money you may never see. The fix is procedural. Conditional goes out with the application; unconditional is released only after the deposit clears, never before.

The second is missing second-tier coverage. The GC collects clean waivers from all 20 direct subs and feels protected, while a tier-two supplier that was never paid by one of those subs still holds a live lien right against the owner's property. The register has to extend below the direct contracts, and the requirement to furnish lower-tier waivers belongs in the subcontract from the start.

The third is waiver amounts that do not match the pay applications. When a change order, a retainage release, or a partial payment moves the billed figure but the waiver still carries the old number, the file silently releases too much or too little. The control is the reconciliation column: waiver amount equals certified amount equals payment, checked every cycle.

These are document-matching problems at heart, which is exactly the kind of reconciliation that software handles better than a person at scale. Tying waivers, applications, and payments into one reconciled ledger is part of what good construction invoice software is for, and it is where the 2,000-waiver job stops being a liability. For the broader back-office and estimating workflow these documents sit inside, start from the construction guides hub and work outward to the specific cycle you are managing.