Newsroom
ArchitectGeneral contractorSupplier
ArchitectGeneral contractorSupplier

BIM Engine for

  • Architect
  • General contractor
  • Supplier

Company

  • Media kit
  • Contact

Legal

  • Privacy
  • Terms
  • Security

Socials

Ask about BIM Engine:

Cause of extinction: legacy SaaS
Still saving v_final_FINAL(2) when the asteroid hit
Emailed the spec as a PDF. Nobody opened it for 66m years
← Newsroom

The four lien waivers, and the one that costs subs money

Conditional, unconditional, progress, final. Four documents, one grid, and a signature order that decides who absorbs the loss when a payment fails to clear.

Product
BIM Engine Team·June 3, 2026·4 min read

What the document is for

A mechanics lien is the strongest remedy a subcontractor has. It attaches to the owner's title, it survives the general contractor's insolvency, and in most states it takes priority over a construction lender's later advances. Owners hate it, lenders underwrite around it, and title companies exist partly to make sure it is gone before a property changes hands.

A lien waiver releases that right, one payment at a time. You sign, you get paid, the owner's title stays clean for the amount you released.

Four documents do this job. Choosing between them looks clerical and is not.

The grid

Two questions produce four forms. Does the release depend on the payment clearing, and does it cover everything or only the work billed so far?

A conditional waiver takes effect when the money actually arrives, while an unconditional waiver took effect the moment you signed it. A progress waiver covers work through a stated date; a final waiver closes the contract.

Combine them and you get conditional progress, unconditional progress, conditional final, and unconditional final. California codifies all four in Civil Code sections 8132 through 8138, and about a dozen states copy that structure closely enough that the forms travel.

1M10M100M1B10B$1 million$10 million$100 million$1 billion$10 billion
Each release cuts the exposure by one payment, if the sequence holdsBIM Engine

The one that costs money

Unconditional progress is where subs lose.

Here is the sequence a project accountant will walk you through, and it sounds reasonable every time. The GC needs your waiver to assemble their own pay application. Their application is due Friday. Your check goes out after the owner funds, which is roughly the 25th, so they ask for the unconditional form now to keep the package moving.

You sign it. You have released your lien rights for that billing period against a payment that has not been made. If the owner short-funds the draw, or the GC applies your money to a different job, or the whole thing lands in a bankruptcy stay, your remedy is a breach of contract claim against a company that has just demonstrated it cannot pay. The lien, which would have attached to real property worth more than the debt, is gone because you signed it away on a Tuesday.

Conditional waivers exist so this cannot happen. The release is contingent on the funds clearing, which means the document is worthless to a party that does not intend to pay, and that is the entire point.

What good practice looks like

Sign conditional on the way out, unconditional on the way back. You send a conditional progress waiver with the pay application, and you send the unconditional one after the deposit clears your bank, not after the check arrives in the mail.

That second distinction matters more than it reads. A check in hand is not payment. It clears or it bounces, and the gap between those two states is where a sub who signed unconditionally has already given up the security.

Some GCs will push back and say their lender requires unconditional waivers in the draw package. That is sometimes true, and it is negotiable more often than the person asking believes, because the lender's actual requirement is usually a conditional waiver at submission plus an unconditional one at the next draw. Ask to see the loan document language. The request tends to soften.

Where the paperwork breaks

Nothing about the four forms is hard. What breaks is volume and sequencing across a portfolio.

A mid-size GC running eleven active jobs is collecting waivers from perhaps 140 vendors a month, in a dozen state-specific formats, against payment events that land on different days. Someone in accounting tracks it in a spreadsheet with a column for "waiver received" that says nothing about which of the four it was. The unconditional final from a mechanical sub who has three months of work left gets filed next to a conditional progress from a drywall sub who finished in March, and both read as a green cell.

The failure is not that anyone misunderstands lien law. It is that the waiver, the payment, and the billing period live in three systems that reconcile only when a person forces them to, so the sequence rule cannot be enforced by anything except a person remembering it.

Tie the waiver to the payment record and the sequence enforces itself: the unconditional form does not generate until the payment it releases has actually settled. That is a database join, not a policy, and a policy is what most accounting departments have.

The short version

Send conditional. Receive money. Then send unconditional, and only for the period the money covered.

If someone asks you to reverse that order, they are asking you to finance their cash flow with your lien rights.