Construction lien waivers are simple in concept and complicated in practice. Every state has its own statutory landscape, several states mandate prescribed forms, notarization rules vary, and a waiver for the wrong amount or on the wrong form can void a sub's payment or expose a GC to lien liability. This is a working guide to the four types of lien waivers, the state-by-state form requirements every commercial sub and GC needs to know, the common mistakes that delay payment, and how AOS handles all 51 jurisdictions automatically.
If you're a sub bookkeeper signing waivers every month, a GC's accountant collecting them from subs, or a controller responsible for closeout binders — this is for you. Note up front: this is general informational content, not legal advice. State lien statutes evolve and contract terms vary; consult your construction attorney on specific situations.
What a lien waiver is, and why it matters
A lien waiver is a document signed by a party in the construction payment chain — subcontractor, supplier, or sometimes the GC itself — that gives up (waives) the signer's right to file a mechanic's lien against the project property for the specified amount and conditions.
Mechanic's liens are powerful: when a sub or supplier isn't paid, they can file a lien against the property, which clouds title, can interfere with the owner's financing, and forces a resolution. Owners, lenders, and title insurers all care a lot about lien risk. Which is why every commercial pay-app cycle involves lien waivers from every party that contributed labor or materials.
The flow runs roughly like this:
- The sub completes work in a billing period and submits a pay application
- Before the GC certifies the pay app to the owner, the GC collects a conditional lien waiver from the sub (and often from the sub's lower-tier suppliers) covering the period
- The owner pays the GC; the GC pays the sub
- Upon receipt of payment, the sub provides an unconditional lien waiver covering the dollars actually received
- At closeout, a final unconditional waiver covers all remaining amounts including retention
Missing waivers, wrong-form waivers, or wrong-amount waivers all stop the cycle until corrected.
The four types of lien waivers
Lien waivers vary on two axes: conditional vs. unconditional, and progress vs. final. That gives four combinations, all of which a typical commercial sub uses regularly.
1. Conditional waiver and release on progress payment. Signed by the sub before receiving a progress payment, conditional on the payment actually clearing. If the payment doesn't clear (bounced check, owner default, etc.), the waiver is void and the sub's lien rights are preserved. This is the safest waiver type from the sub's perspective and is commonly required by GCs before pay-app certification.
2. Unconditional waiver and release on progress payment. Signed by the sub after receiving the progress payment, with no conditions. The sub is giving up lien rights for the covered period, period. This is the riskiest waiver type for the sub — if the sub signs an unconditional waiver before the check actually clears, they may lose lien rights with no recourse if the payment fails. Best practice: never sign an unconditional waiver until the payment is actually in the bank.
3. Conditional waiver and release on final payment. Signed by the sub before receiving the final payment (including retention), conditional on payment. Covers everything through final completion.
4. Unconditional waiver and release on final payment. Signed after final payment has cleared. The sub gives up all remaining lien rights on the project. This is the form that gets signed at closeout and is the one that closes out the lien-waiver lifecycle.
Most pay-app cycles involve types 1 and 2. Closeout involves types 3 and 4. Subs operating in states that prescribe statutory forms (more below) need to use the correct prescribed form for the correct type — substitutes are often not enforceable.
The states that prescribe statutory lien-waiver forms
Several major commercial-construction states have statutes that prescribe specific lien-waiver forms. Using a custom or non-conforming form in these states can either void the waiver entirely or limit its enforceability. The states to know about include:
California. California Civil Code Section 8132-8138 prescribes the exact text and format for all four lien-waiver types (conditional progress, unconditional progress, conditional final, unconditional final). Custom forms are not enforceable against the sub's lien rights — California is among the strictest. If you're working on California projects and your GC sends you a non-statutory waiver form to sign, do not sign it without legal review. The statutory forms are the only ones that work.
Texas. Texas Property Code Chapter 53 prescribes statutory waiver forms similar in concept to California's. Both progress and final waivers have specific required language. Subs should use the statutory forms for Texas projects.
Florida. Florida Statute Section 713.20 governs lien waivers. Florida is somewhat less restrictive than California on form, but the statutory waiver forms are still the safe choice. Notarization requirements apply in some circumstances.
Georgia. Georgia OCGA Section 44-14-366 prescribes a specific lien-waiver form that includes statutory language about when the waiver becomes enforceable (when payment clears). Subs should use the prescribed form.
Missouri. Missouri has statutory waiver requirements with specific language.
Mississippi. Similar prescribed-form requirements.
Wyoming. Statutory waiver requirements apply.
Arizona, Nevada, Utah. Each has its own statutory framework with prescribed elements.
Other states (New York, Illinois, Pennsylvania, Ohio, North Carolina, South Carolina, Washington, Oregon, and many more) regulate lien waivers but don't always prescribe a specific form. In these states, custom forms can be enforceable if they include the necessary release language and signatures — though best practice is still to use a recognized industry-standard form.
Notarization rules: where it's required and where it isn't
Notarization adds time and friction to the lien-waiver workflow, but is required in some jurisdictions and prudent in others. A high-level guide:
- Required for some waiver types: Several states require notarization for unconditional waivers, especially final unconditional waivers at closeout. Others require it for all waivers above certain dollar thresholds.
- Required for filing or recording: Even where not strictly required for waiver enforceability, notarized waivers are sometimes required for the GC's lender or title insurer's closing binder.
- Best practice for high-dollar waivers: Notarize final unconditional waivers regardless of strict legal requirement — they're the most consequential documents in the lien-waiver lifecycle and the cost of notarization is trivial relative to the protection.
- Online notarization: Most states now permit remote online notarization (RON), which can compress the waiver workflow significantly. Check your state's RON provisions.
The seven mistakes that delay payment via lien waivers
Across mid-market sub and GC accounting teams, the same seven errors account for nearly every lien-waiver-related payment delay.
1. Wrong-amount waiver. The waiver dollar amount has to exactly match the payment amount being released — not the pay-app billed amount, not the contract sum, not a round number. A waiver covering $47,318.42 must say $47,318.42. Off by a penny and the waiver may not enforce against the released amount; off by more and the GC's accountant will reject it.
2. Wrong-state form. Subs working in multiple states sometimes default to one state's waiver form for all projects. In California or Texas, this voids the waiver. Always check the controlling state for the project and use the correct form.
3. Conditional vs. unconditional mixed up. The most common error: signing an unconditional waiver before payment clears, or signing a conditional waiver after payment clears (which is harmless but pointless). Conditional waivers go before payment; unconditional go after.
4. Missing supplier waivers. Many commercial contracts require the sub to provide not just their own lien waiver, but waivers from their suppliers and lower-tier subs. Forgetting to collect these — or collecting them late — delays the GC's certification of the sub's pay app.
5. Notarization missed where required. Submitting an un-notarized waiver where the state or contract requires notarization means the waiver gets bounced for re-execution, delaying payment.
6. Improper signing authority. Waivers signed by someone without authority to bind the sub — usually a junior staffer signing for an owner or officer — can be challenged. Use the correct authority and document it.
7. Date errors. Waiver effective dates have to match the payment period and the conditional/unconditional status. A waiver dated wrong — especially backdated — can be invalid or, worse, give rise to a fraud claim.
The lien-waiver lifecycle most subs and GCs actually run today
The typical mid-market workflow looks like this:
- The GC's accountant emails the sub a PDF lien-waiver form — sometimes the right state's statutory form, sometimes a custom GC form, sometimes a form from a different state
- The sub's bookkeeper fills in the amount (re-typing from the pay app), the dates, the project info
- The sub's owner or controller signs — sometimes notarized, sometimes not
- The sub emails the executed PDF back to the GC
- The GC's accountant attaches the PDF to the pay-app record (somewhere)
- For the supplier waivers, the sub chases their own suppliers via email and forwards what comes in
- At closeout, somebody assembles the lien-waiver section of the closeout binder from the PDF archive
This is heavy on PDF passing and re-typing, light on systematic tracking. The error rate is meaningful: most experienced GC accountants will tell you that some percentage of pay-app cycles — usually 10-20% — get delayed by a lien-waiver issue.
How AOS handles lien waivers across all 51 jurisdictions
In AOS, the lien waiver is generated, not hand-filled. Specifically:
- The platform knows the controlling state for each project. When a waiver is needed, AOS generates the correct state's statutory form (California Civil Code Section 8132 form for California projects, Texas Property Code Chapter 53 form for Texas projects, and so on across all 51 jurisdictions including DC).
- The dollar amount is the exact released amount, computed from the pay-app record. No retyping, no rounding errors. Conditional waivers are queued at pay-app certification; unconditional waivers are queued at payment receipt.
- Notarization workflow is built in for jurisdictions and waiver types that require it, with remote online notarization support where the state permits.
- Supplier waiver collection is tracked — AOS knows which lower-tier suppliers are on each project and queues their waivers automatically. The sub can email a token-scoped collection link to suppliers off-platform; suppliers on AOS provide waivers directly cross-tenant.
- Closeout binder is assembled continuously, not at the end. Every waiver attaches to the right pay-app record, the right CO, the right payment. At substantial completion, the lien-waiver section of the closeout binder is essentially complete.
- State statute changes propagate automatically. When a state updates its statutory waiver form — California has done so several times in the last decade — AOS updates the template platform-wide. No version drift across customer firms.
- Audit trail per waiver: who signed, when, on what form version, with what notarization, against which payment record. Defensible if a lien dispute ever arises.
The sub accounting role page walks through the AR / pay-app / lien-waiver workflow. The GC accounting role page covers the collection-and-attachment side. The AIA G702/G703 guide covers how lien waivers interlock with the pay-app cycle. The retention rollforward guide covers how lien waivers interlock with retention release at closeout.
The lien-waiver readiness checklist
Run your current process through these questions:
- Does your team know which states prescribe statutory waiver forms, and do you use them?
- Are your waiver dollar amounts being typed in manually, or generated from the pay-app record?
- Do you have a systematic process for collecting supplier waivers, or is it email-based?
- Can you produce the lien-waiver section of a closeout binder in under a day, or does it take a week of digging through PDFs?
- If a lien dispute arose tomorrow, could you produce the full audit trail of a specific waiver — signer, date, form version, notarization, attached payment record?
- When California (or any other state) updates its statutory waiver form, how do you know? And how does the update propagate to your templates?
If most answers are "no" or "with significant effort" — that's the gap AOS closes.
If you'd like to see it on your own data
We're in private-beta design-partner mode for commercial subs and GCs. If you want to walk through how AOS handles lien-waiver lifecycle on a real project — particularly one with multi-state work — apply to the beta. We'll show you the workflow end-to-end.