# Lien Waiver

> The signed release by which a party gives up its mechanic's lien or bond-claim rights in exchange for payment — conditional or unconditional, progress or final.

- Source: https://briq.ai/acu/object/lien-waiver
- Department: Contracts, Compliance & Risk (https://briq.ai/acu/department/contracts)
- Catalog code: CON 204 · Level: Practitioner · Track: Finance · 10 min read
- Also known as: Lien Release, Waiver and Release, Mechanic's Lien Waiver, Release of Lien

## Definition

A lien waiver is a signed document in which a contractor, subcontractor, or supplier releases its right to file a mechanic's lien (or a claim against a payment bond) against a property for work or materials furnished, in exchange for payment. Waivers come in four standard combinations: conditional or unconditional, and progress (partial) or final. A conditional waiver takes effect only once payment actually clears, protecting the signer if a check bounces; an unconditional waiver is effective on signature regardless of whether payment is ever received. Progress waivers release rights through a specific date or payment; final waivers release all remaining rights on the project. A lien waiver is not a receipt and not a substitute for verifying payment — signing an unconditional waiver before the money is in hand can extinguish a valid lien right for a payment that never comes.

## Why it matters

Lien waivers are how an owner and general contractor obtain clean title to each payment and protect the property from double exposure. Collecting waivers down through every tier at each draw ensures that the money paid actually discharged the lien rights it was meant to, so a paid party cannot later lien the project. Missing waivers from lower-tier subs and suppliers are the classic way an owner pays the GC yet still faces liens from parties it never contracted with.

They protect the party signing them just as much, if the right type is used. The conditional-versus-unconditional distinction is the entire ballgame: a signer who gives an unconditional waiver on the promise of payment, rather than a conditional one that springs only when the check clears, can lose its lien rights for money it never receives. This single choice decides who bears the risk between signature and funds clearing.

Waivers govern the flow of money through the whole payment chain and are usually a hard condition of each draw. A general contractor typically cannot get paid without submitting waivers from its subs, who cannot be paid without waivers from their suppliers, and so on. When waivers are late, incomplete, or the wrong type, payment stalls for everyone upstream and downstream, making waiver management a direct driver of project cash flow.

Several states dictate the exact statutory form and prohibit deviation, so form choice is a legal question, not a preference. States such as California, Texas, Florida, Georgia, and others prescribe specific waiver language and forms, and a non-conforming waiver may be void or, worse, may waive more than intended. Using the wrong form for the project's state is a quiet but serious error that surfaces only when a lien fight begins.

## Lifecycle

1. **Contractual requirement set** — The prime and subcontracts specify which waivers are required at each payment, from which tiers, and in what form. Well-drafted contracts require conditional waivers with the pay application and unconditional waivers for the prior payment.
2. **Waiver request with the pay application** — As each draw is prepared, the paying party requests waivers covering the current period. The correct form and the correct through-date must be specified, or the waiver will not cover what it needs to.
3. **Preparation and signature** — The signing party completes the waiver with the payment amount, through-date, project, and — critically — the correct type. Signing an unconditional waiver here instead of a conditional one is the most common and dangerous error.
4. **Collection down the tiers** — The GC gathers not only the subs' waivers but the subs' suppliers' and lower-tier waivers, since those parties hold independent lien or bond-claim rights. This lower-tier collection is where waiver programs most often fall short.
5. **Verification against the pay application** — The waivers are checked against the schedule of values and the amounts being paid to confirm they cover the right parties, periods, and dollars. Mismatches between waived amounts and paid amounts are a routine catch.
6. **Payment release** — Once conforming waivers are in hand, payment is released. For conditional waivers, the release itself is what makes the waiver effective, so the sequence — waiver then payment — must be respected.
7. **Reconciliation and rolling coverage** — Each period's unconditional waiver for the prior payment confirms the last check actually cleared, creating a rolling chain that leaves no uncovered gap. Broken chains — a missing prior-period unconditional waiver — are a red flag of a payment dispute.
8. **Final waivers at closeout** — At final payment, unconditional final waivers are collected from all tiers to release remaining rights and clear title completely. Final payment and retainage release usually hinge on the full set being in hand.

## Anatomy

- **Type (conditional/unconditional)** — Whether the waiver is effective only on payment clearing or immediately on signature. The single most consequential field on the document.
- **Scope (progress/final)** — Whether it releases rights through a date or payment (progress) or all remaining rights (final). Signing final when only progress is due over-releases.
- **Claimant and signer** — The party releasing rights and the individual signing with authority. A waiver signed by someone without authority may not bind the claimant.
- **Property/project identification** — The specific project and, in many states, the legal property description. A waiver tied to the wrong project protects nothing.
- **Through/effective date** — The date through which rights are released. Work or materials after this date remain lienable and must be covered by a later waiver.
- **Payment amount** — The specific sum for which rights are released. Must reconcile to the pay-application amount; a mismatch leaves a gap either way.
- **Exceptions/exclusions** — Amounts expressly reserved — disputed change orders, retainage, unbilled work. What is not waived is as important as what is.
- **Statutory form compliance** — Whether the waiver matches the state-prescribed form where one exists. A non-conforming form can be void or over-broad.
- **Notarization** — Whether the state or contract requires the waiver to be notarized. A missing notarization can invalidate an otherwise correct waiver.
- **Tier** — The claimant's position — GC, sub, sub-sub, supplier. Determines whose waiver is needed to clear a given payment down the chain.
- **Conditioning language** — For conditional waivers, the exact language making effectiveness contingent on payment. Weak conditioning language can accidentally make it unconditional.

## Failure modes

- **Unconditional waiver signed before payment clears** — A party signs an unconditional waiver on the promise of a check, the check bounces or never comes, and the lien right is already gone. This one substitution — unconditional where conditional was appropriate — is the costliest waiver mistake there is.
- **Missing lower-tier waivers** — The GC collects the subs' waivers but not the subs' suppliers' or sub-subs' waivers, and those parties retain independent lien rights. The owner pays in full and still faces liens from parties it never dealt with directly.
- **Wrong statutory form** — A generic or out-of-state waiver form is used in a state that prescribes a specific form. The waiver is void, or it waives more than intended, and the defect is discovered only when a lien is filed or contested.
- **Through-date and payment-amount mismatch** — The waiver's through-date or dollar amount does not line up with the pay-application period, leaving a slice of work uncovered. A gap remains lienable even though everyone believed the period was released.
- **Final waiver signed when only progress is due** — A party signs a final unconditional waiver for a progress payment, releasing all remaining rights including retainage and future work. It has waived far more than it was paid for, often without realizing it.
- **Retainage not excepted** — A progress waiver fails to reserve retainage, so the signer waives its rights to money still being withheld. When retainage release stalls, the party finds it has no lien leverage left to compel it.
- **Broken rolling chain** — A prior-period unconditional waiver is never collected, so no one confirmed the last payment actually cleared. A hidden payment dispute festers, and the uncovered gap only surfaces when a later lien reveals it.

## Metrics

- **Waiver collection completeness** — Share of required waivers, by tier, collected for each draw. Incomplete lower-tier collection is the primary title-exposure gap.
- **Correct-type rate** — Share of waivers submitted in the correct conditional/unconditional and progress/final combination. Measures process and legal discipline.
- **Form-compliance rate** — Share conforming to the governing state's statutory form where one is required. Catches void or over-broad waivers before reliance.
- **Waiver-to-payment reconciliation rate** — Share of waivers whose amount and through-date reconcile to the pay application. Detects uncovered gaps in coverage.
- **Rolling-chain integrity** — Share of periods with a matching prior-period unconditional waiver confirming payment cleared. A broken chain flags a payment dispute.
- **Waiver cycle time** — Days from waiver request to conforming waiver in hand. Long cycles stall the entire upstream payment chain.
- **Lien/bond-claim incidents** — Count of liens or payment-bond claims filed despite payment. The ultimate outcome measure of waiver-program effectiveness.

## The AI shift

- **Conversational** — You can ask the waiver record what it actually shows: which draws are missing lower-tier waivers, which submitted waivers are the wrong type for the payment, whether the rolling unconditional chain is intact, and which waivers do not reconcile to the amounts paid — with the specific waiver, tier, and pay application cited.
- **Generative** — Waivers are generated in the correct state-specific statutory form with the type, through-date, payment amount, and exceptions (including reserved retainage) populated from the pay application, so a party signs a conforming draft instead of guessing at a form. The system produces the right conditional-versus-unconditional variant for the point in the cycle.
- **Orchestrated** — Waivers become part of the payment loop rather than a side file: required waivers by tier are derived from the schedule of values and subcontracts, each waiver is reconciled against the pay-application amount and period, the rolling conditional-then-unconditional chain is enforced, and payment release is gated on a conforming set being present.
- **Autonomous** — The waiver perimeter runs itself: required waivers requested automatically each draw down through the tiers, incoming waivers checked for correct type, form compliance, through-date, amount, and reserved retainage, and payment held until the conforming set is complete — while a human resolves disputed exceptions, decides whether to accept a non-conforming waiver, and authorizes every payment.

## Prompts

### Conversational — Reviewing a draw's waivers before you release payment.

```text
Review the lien waivers submitted with this month's pay application against the schedule of values and the amounts we are paying. Tell me which required waivers, by tier, are present and which are missing — including lower-tier supplier and sub-sub waivers. For each waiver present, verify it is the correct type for this payment (conditional progress with this draw, unconditional progress for the prior payment), that its through-date and payment amount reconcile to what we are paying, that retainage is properly reserved, and that it conforms to this state's statutory form if one is required. Flag every deficiency specifically and tell me whether the rolling unconditional chain from prior periods is intact.
```

**Expected output:** A waiver-by-waiver review against the pay application identifying missing, wrong-type, non-conforming, and non-reconciling waivers, plus a rolling-chain integrity check.

**Follow-ups:**

- Which missing waivers must be collected before we can release payment?
- Draft the waiver requests for the missing lower-tier parties.
- Is any waiver a final release where only a progress release should be?

### Generative — A subcontractor needs the correct waiver drafted for this payment.

```text
Generate the correct lien waiver for this subcontractor's current progress payment on our California project. Populate it as a conditional progress waiver in California's statutory form, with the through-date matching the pay-application period, the exact payment amount, the project and property identification, and an express reservation of retainage and of the two disputed change orders that are not being paid this cycle. Then also generate the unconditional progress waiver they will sign once this payment clears, in the correct statutory form, so both are ready. Explain in one line why each is the correct type and form for its point in the cycle.
```

**Expected output:** The correct conditional and unconditional progress waivers in the state's statutory form, with retainage and disputed amounts reserved and the type/form rationale stated.

**Follow-ups:**

- Produce the same pair for a Texas project and note what changes in the form.
- Draft the final unconditional waiver they will sign at closeout.
- What lower-tier waivers should we also collect alongside these?

### Orchestrated — You want the whole payment chain's title exposure mapped before closeout.

```text
Map our lien-waiver coverage across the entire payment chain on this project. From the subcontracts and the schedule of values, derive every party at every tier that holds lien or bond-claim rights, then match our collected waivers against that map period by period. Identify every tier and party with missing waivers, every waiver of the wrong type or non-conforming form, every through-date or amount that does not reconcile to what was paid, and every progress waiver that failed to reserve retainage. Show where the rolling unconditional chain is broken. Return a title-exposure report ranking each gap by the dollar amount left lienable and by whether the party has actually been paid.
```

**Expected output:** A chain-wide title-exposure report tying each waiver gap to a party, tier, and dollar amount, with the rolling-chain breaks and highest-risk gaps ranked.

**Follow-ups:**

- Draft the collection plan for the highest-exposure gaps before final payment.
- Which paid parties still have live lien rights against us?
- What must be complete before retainage can be released cleanly?

### Autonomous — Standing policy for running the waiver program each draw.

```text
Operate our lien-waiver program each payment cycle under these rules. From the subcontracts and schedule of values, determine the required waivers at every tier and request them automatically each draw, specifying the correct type and through-date. As waivers arrive, verify type (conditional progress with the current draw, unconditional progress for the prior payment), state statutory form compliance, notarization where required, through-date and amount reconciliation to the pay application, and reservation of retainage; reject and re-request any that fail. Hold payment on any party until its conforming waiver set is complete, and flag any broken rolling unconditional chain. Never accept a non-conforming or wrong-type waiver as sufficient, never waive the lower-tier collection requirement, and never release a payment — route every exception and all payment authorizations to the project accountant with the details.
```

**Expected output:** A continuously run waiver program with a payment-hold and exception queue, where humans resolve disputed exceptions and authorize all payments, backed by a full audit trail.

**Follow-ups:**

- Show me every payment held for missing or deficient waivers this cycle.
- Which parties submitted the wrong waiver type and were re-requested?
- List all broken rolling chains across the project.

## Maturity ladder

- **Level 0 — Level 0 — Whatever they send** — Waivers are collected loosely, types are not scrutinized, lower tiers are ignored, and the property is exposed to liens despite full payment.
- **Level 1 — Level 1 — Checklisted** — A checklist tracks required waivers per draw, but type, form compliance, and reconciliation to payment are manual and inconsistent.
- **Level 2 — Level 2 — Linked** — Waivers are tied to the schedule of values, subcontracts, and pay applications, so required parties by tier and amount reconciliation are visible.
- **Level 3 — Level 3 — Assisted** — Correct-type, state-form waivers are generated, incoming waivers are checked automatically, and rolling-chain and title-exposure gaps are surfaced for review.
- **Level 4 — Level 4 — Operated** — Waiver request, verification, and payment gating run unattended each draw, while humans resolve disputes, accept exceptions, and authorize all payments.

## FAQ

### What is the difference between a conditional and an unconditional lien waiver?

A conditional waiver becomes effective only when the payment it references actually clears, so if the check bounces or never arrives, the signer keeps its lien rights. An unconditional waiver is effective the moment it is signed, regardless of whether payment is ever received. The safe practice is to give a conditional waiver with the current pay application and an unconditional waiver for the prior payment only after that prior payment has cleared, which protects the signer while still giving the payer the clean release it needs.

### Why do lower-tier lien waivers matter if we only contracted with the general contractor?

Because mechanic's lien and payment-bond rights generally run with the party that furnished labor or materials, not with privity of contract. A subcontractor's supplier or a sub-subcontractor can lien the property or claim against the payment bond even though the owner never contracted with them, and even if the owner paid the general contractor in full. Collecting waivers down through every tier at each draw is the only way to confirm the money actually discharged the lien rights it was intended to, which is why lower-tier collection is where waiver programs most often fail.

### Can we use a generic lien-waiver form in any state?

No. Several states prescribe specific statutory waiver forms and language and prohibit or disfavor deviation, and a non-conforming waiver in those states can be void or can inadvertently waive more than intended. States including California, Texas, Florida, and Georgia have their own required forms and rules, so the governing state's law must drive the form choice for every waiver. Using an out-of-state or generic form is a quiet error that typically surfaces only when a lien is filed and the waiver is challenged.

## Related objects

- [Pay Application (AIA G702/G703)](https://briq.ai/acu/object/pay-application)
- [Preliminary Notice](https://briq.ai/acu/object/preliminary-notice)
- [Subcontract](https://briq.ai/acu/object/subcontract)
- [Retainage](https://briq.ai/acu/object/retainage)
- [Joint Check](https://briq.ai/acu/object/joint-check)
- [Schedule of Values (SOV)](https://briq.ai/acu/object/schedule-of-values)