The 50-state conditional final lien waiver pack federal-construction primes use at closeout to send the statutorily-correct form to every sub on final payment. With the unsettled-dispute and pending-change-order carve-out generic templates miss. California §8136, Texas §53.281, Florida §713.20, and 47 more.
Why federal-construction primes need a 50-state conditional final lien waiver pack with the unsettled-dispute carve-out
The conditional final lien waiver is the single highest-stakes piece of paper on the project. Once the sub signs it and the final check clears, every lien right that sub had against the property, for every dollar of base contract, every approved change order, every retention release, and (depending on how the carve-out is drafted) every still-pending change order or unsettled dispute, is gone. There is no “we’ll fix it on the next pay app” with a final waiver. There is no next pay app. The check clears, the waiver attaches, and the file closes.
Most operators learn this the wrong way. A prime is at substantial completion on a $14M Sacramento medical-office building. The mechanical sub has a pending CO #17 for $186K. Extra ductwork the agency requested in the final 30 days, paperwork still moving through the owner’s review queue. The contracts admin sends the standard final waiver template counsel drafted three years ago for a Phoenix job, the sub’s project manager signs without flagging CO #17, the final payment clears, and six months later the agency denies CO #17 in closeout review. The sub now has $186K of work performed, no payment, and no lien rights. Because the final waiver they signed didn’t carve out unsettled change orders. That’s the conditional-final waiver problem in one sentence: the carve-out is the entire game, and most templates online don’t even mention it.
This 50-state pack solves the template-collection half of the problem. Every state’s statutorily-correct conditional final lien waiver is in the pack, organized by jurisdiction, with the right citation (California Civil Code §8136, Texas Property Code §53.281, Florida §713.20, Mississippi §85-7-419, Missouri §429.620, Nevada §108.2453, Utah §38-1a-803, Wyoming §29-2-115, Georgia §44-14-366, Michigan §570.1115, and the rest), the right notarization requirement (Florida, Mississippi, Texas, and Wyoming require notarization on final waivers. Most other states don’t), and the right deadline-to-execute requirement called out on the index sheet.
The wedge most templates online miss: the unsettled-disputes carve-out. Generic legal-template SaaS sells a “final lien waiver” as one document for the whole project. Fill in the project name, fill in the final payment amount, sign, done. That’s fine when nothing is in dispute. It’s catastrophic when CO #17 hasn’t been resolved yet. The 50-state pack treats the carve-out as a first-class field on every state’s variant. There is a dedicated, statutorily-aware exclusion block on the form where the sub lists every pending change order, every unsettled dispute, every retention claim that has not yet been resolved, with dollar amounts and the basis for the carve-out. California §8136 explicitly permits the carve-out. Texas §53.281 explicitly permits the carve-out. Florida §713.20 permits the carve-out with specific format requirements. The pack honors each state’s drafting rules so the sub’s reservation actually holds up if it ever gets challenged in a lien-bond hearing or substitute-bond proceeding.
The federal-construction operator angle matters here because federal projects span jurisdictions and frequently end with contested closeout. The agency disputes a CO at the eleventh hour, the lender’s draw inspector flags a non-compliant waiver in the final package, the sub’s attorney spots a missing carve-out, and the project drags an extra 60 days while everyone re-papers the closeout. The pack is the artifact a multi-state federal prime uses to standardize the final-waiver workflow without sacrificing per-state statutory accuracy or the operator-grade carve-out language that protects everyone in the chain. It is, intentionally, deeper than the K003 conditional progress pack. Final-payment stakes are an order of magnitude higher than progress-payment stakes, and the form has to reflect that.
What this is NOT: it’s not legal advice on whether to sign a final waiver in your specific situation, it’s not a substitute for state-licensed construction counsel review of your particular subcontract or the unsettled-dispute language, and it’s not a replacement for the K021 decision matrix that tells you whether to use conditional vs unconditional in the first place. It’s a starting-point template pack for the operator who has to actually generate, send, collect, validate, file, and (when things go sideways) reissue 50–500 final waivers per year across a multi-state portfolio. Use it. Have your construction counsel review the specific variants you’ll use, especially the carve-out language for any project with open disputes. Then run the workflow.
Who this 50-state final-waiver pack is for
- Multi-state commercial GCs closing out projects across 3+ jurisdictions where state final-waiver formality differs
- Federal prime contractors running closeout on federal projects in California, Texas, Florida, Mississippi, Missouri, Nevada, Utah, Wyoming, and the other statutory-form states
- Specialty subcontractors at substantial completion who need to recognize when a GC is sending the wrong-state final waiver or a final waiver missing the unsettled-dispute carve-out
- Contracts administrators assembling final pay-app packages and project closeout files
- AP teams gating final payment release on receipt of a properly-formed conditional final waiver with full carve-out documentation
- Project finance and lender draw inspectors verifying the closeout waiver pack matches each state’s statutory requirement and accounts for every pending claim
- Risk managers and CFOs signing off on closeout exposure when pending change orders or disputes remain unresolved at final payment
If you’re closing out a project where the K003 conditional progress waiver has already been running cycle-by-cycle, this pack is the natural next step. Same format, same index, but tuned for the final-payment stakes. If you’re trying to decide between conditional final and unconditional final in the first place, work through the conditional vs unconditional release decision matrix before downloading.
The 11 fields the conditional final waiver carries on every state variant
The pack covers the 11 fields a real conditional final lien waiver carries on every state’s variant. The variant differs by jurisdiction (statutory citation, notarization, signature block, retainage rules), but the fields are consistent so the contracts admin doesn’t have to relearn the form for every state. There is no padding here. These are the 11 fields that actually appear on the document.
- Claimant name and contractual role. The sub’s full legal entity name (matching the subcontract signature block and the W-9), the entity type (corporation, LLC, partnership), and the tier on the project. Tier-1 to GC, tier-2 to another sub, supplier-of-fixtures, etc. Discrepancies between the claimant name on the final waiver and the name on the subcontract are the single most common reason final waivers get rejected in lien-bond claims and substitute-bond proceedings, especially when the sub operates under a DBA or a parent/subsidiary structure.
- Property owner of record. The owner of the real property as of the through-date. Agency name on a federal project, fee owner on a private project, master-lessee on certain ground-lease structures. The owner-of-record field exists because lien rights attach to the real property; a waiver running to the wrong owner doesn’t waive anything. On federal projects, list both the agency and the agency’s contracting office; on private projects with complex ownership, list the entity recorded on the title.
- Prime contractor name. The general contractor or design-build entity that holds the prime contract with the owner. On most projects, prime and GC are the same entity; on construction-management-at-risk and certain joint-venture structures, they differ. The prime field matters because the waiver flows up the contract chain. It identifies the entity through whom the sub’s claim runs.
- Project name and full address. Project name as it appears in the prime contract (not the marketing name), full street address, and a brief legal description sufficient for a recorded lien to clearly relate to the same matter. Vague project identification (“the Smith building project”) is the second-most-common reason final waivers get challenged in lien proceedings. The recorder can’t match the waiver to the property without specificity.
- Final payment amount, invoice number, payment date, and through-date. The dollar figure of the final payment the sub is conditionally accepting (base + retention release + approved COs through the through-date, less prior payments), the final invoice or pay-app number, the date the final payment is to be made, and the through-date. The cutoff through which the sub is waiving for all work performed. On a true final waiver, the through-date is the substantial-completion date or the project completion date; on a partial-final waiver structured around a phased completion, the through-date is the date that phase wraps.
- Effective-upon-payment conditional language. The defining feature of any conditional final waiver. The release is effective only upon the claimant’s actual receipt of the specified final payment amount. Until the check clears, the sub retains lien rights for the entire final payment. The pack uses each state’s statutorily-required language: “shall be effective only upon” in California, “is conditional upon” in Texas, “becomes effective when” in Florida. Using the wrong verb in a statutory-form state can convert the waiver into an unconditional one inadvertently and waive the sub’s lien rights before the cash arrives.
- Final-payment scope description. A plain-English description of the scope the sub is releasing claims for. Typically “all labor, materials, equipment, and services provided under the subcontract through the through-date.” On projects with multiple-prime structures or split scopes, the description has to be specific enough to distinguish the releasing sub’s scope from any related entity’s scope on the same project. The scope description is what a court will read first when interpreting the waiver if it’s ever challenged.
- Pending change orders and unsettled disputes carve-out. This is the field that separates a defensible final waiver from a malpractice claim. Every pending change order, every unsettled dispute, every claim for delay damages or impact costs, every retention amount still in escrow. Listed individually with dollar amount, status (submitted, in review, contested), and the basis for the carve-out. The pack treats this as a first-class form field on every state’s variant. California §8136 permits the carve-out. Texas §53.281 permits the carve-out. Florida §713.20 permits the carve-out with specific format. If the sub leaves this field blank, the final payment waives those claims permanently. By statute in most states.
- Pre-printed retainage release language. Final waivers typically release retainage simultaneously with the final base payment. The pack includes pre-printed retainage release language on every state’s variant, “claimant acknowledges receipt of all retention or retainage previously withheld in connection with the work”, because retainage is often the highest-value line item on the final waiver and forgetting it leaves money on the table. On states where retainage has its own statute (Texas Property Code §53.107 for retainage interests), the pack’s retainage block honors the statutory requirement.
- State-specific statutory form notice block. The pack identifies which states require the statutory form to be used verbatim (California Civil Code §8136 conditional final waiver, Texas Property Code §53.281, Florida §713.20, Mississippi §85-7-419, Missouri §429.620, Nevada §108.2453, Utah §38-1a-803, Wyoming §29-2-115, Georgia §44-14-366, and Michigan §570.1115). Every variant in the pack includes the state’s mandated statutory-notice block. Usually the bold-printed or all-caps notice telling the claimant their rights are being affected. Missing the notice block in a statutory-form state can void the waiver.
- Notarization block (Florida, Mississippi, Texas, Wyoming, and other notarial states). Florida §713.20 requires a final-waiver notarization. Mississippi §85-7-419 requires notarization on certain final-waiver classes. Texas Property Code §53.281 requires the form be either notarized or sworn under penalty of perjury. Wyoming §29-2-115 requires notarization. The pack’s notarization block is included on every state’s variant where notarization is required and stays optional on the rest, with the index sheet flagging each state’s requirement. Sending an unnotarized final waiver in a notarial state is the third-most-common reason final waivers get bounced at lender draw review.
How to run a defensible final-waiver workflow at every project closeout
Use the index sheet first. It’s an Excel sheet listing all 50 states with the form variant (statutory or non-statutory), the citation, the notarization requirement, the deadline-to-execute, and the corresponding Word file in the pack. Pull the right state’s Word file for the project’s jurisdiction, then run the workflow.
For each project closeout:
- Identify the project’s state of jurisdiction (where the work is performed, not where the sub is based).
- Pull the matching state’s variant from the pack (Word for editable, PDF for print).
- Run the carve-out audit before sending. Identify every pending change order, unsettled dispute, delay claim, retention claim, and any other unresolved item with the sub. Write each one into the carve-out block with dollar amount and status.
- If the carve-out block is blank, the sub waives those claims permanently when the check clears. Do not skip this step.
- Fill the project-identification block (project name, address, owner, prime, GC), the claimant-identification block (sub legal entity, tier, role), and the final-payment block (final amount, final invoice number, through-date, payment date).
- Route to the sub’s authorized signer per the state’s signature-block requirement. Most states allow any authorized agent; Florida §713.20 requires a corporate officer’s signature. Mississippi requires notarization in addition to the corporate-officer signature.
- If the state requires notarization (Florida, Mississippi, Texas, Wyoming, Louisiana, Nevada. See index), route through the notary first.
- File the executed waiver in the project closeout file, release the final payment, and log the actual payment-receipt date on the file. The waiver becomes effective on the sub’s actual receipt of payment. The receipt date is the date the conditional release converts to an unconditional release in operation.
- Repeat per sub. Most projects have 15–80 subs at final payment; every one needs its own state-correct conditional final waiver.
Refresh the pack annually because state statutes change. Confirm with state-licensed construction counsel before relying on any specific variant for a live project, especially on any project with open carve-out items at final payment.
Stop running closeout waivers manually
The 50-state pack solves the template-collection problem. It does not solve the closeout workflow problem. Sending the right state’s final waiver to the right sub for the right final amount, running the carve-out audit on every open change order and dispute before send, validating the sub used the correct statutory form and signed in the right block, tracking which subs have returned executed waivers and which haven’t, and assembling the final closeout package the lender or agency will actually accept. That’s still 60+ minutes of contracts-admin work per sub at final payment, multiplied by 15–80 subs per project. Contracts Connected’s Contract Intelligence feature reads the project’s state of jurisdiction and the open-CO/dispute log from the prime contract and pay-app history, auto-generates the correct state’s final waiver pre-filled with project, claimant, final amount, and through-date, populates the carve-out block from the pending-CO log so nothing gets missed, sends to the sub for e-signature, files the executed waiver in the closeout package, and logs the payment-receipt date when the cash clears. Same 50-state pack, but the carve-out audit and the closeout package run themselves.
For educational purposes. These templates, checklists, and trackers are operator-built starting points designed to help you move faster on the kind of work that usually drowns construction admins in email chains. They are not legal, insurance, accounting, or tax advice. Each project, jurisdiction, and contract has its own quirks. Review the document, refine the language, and consult your attorney, broker, CPA, or compliance officer before relying on it for a live project decision.
Frequently asked questions about conditional final lien waivers
What’s the difference between a conditional final and an unconditional final lien waiver?
A conditional final waiver releases the claimant’s lien rights only upon actual receipt of the specified final payment. Until the check clears, the sub retains every lien right they had. The conditional final is what the sub signs and delivers with the final pay app, supporting the GC’s draw request to the owner or lender. An unconditional final waiver releases lien rights immediately on execution, regardless of payment. The unconditional final is what the sub signs after the cash has arrived and cleared. Conditional final goes out with the final pay app; unconditional final closes the file. The decision matrix is in K021. Sending the wrong one, or signing the wrong one, is one of the most expensive mistakes a contracts admin can make, because final-payment stakes are larger than progress-payment stakes by an order of magnitude.
What happens to a pending change order if I sign a final waiver without listing it in the carve-out?
By default, in most states, the pending change order is waived permanently when the final payment clears. California Civil Code §8136 explicitly waives “all claims” through the through-date unless specifically excepted. Texas Property Code §53.281 operates similarly. Florida §713.20 waives all claims unless listed in the reservation. The pack treats the carve-out as a mandatory pre-send field for exactly this reason. The cost of leaving the carve-out blank is forfeiting the value of every unresolved claim, which on a federal closeout can run into hundreds of thousands or millions of dollars. The fix is procedural: never send a final waiver without running the carve-out audit, and never sign a final waiver counsel sent you without confirming the carve-out block reflects every open item on your books.
Which states require the statutory form for conditional final waivers?
California (Civil Code §8136), Texas (Property Code §53.281), Mississippi (§85-7-419), Missouri (§429.620), Nevada (§108.2453), Utah (§38-1a-803), Wyoming (§29-2-115), Georgia (§44-14-366), Michigan (§570.1115), and Florida (§713.20) all require the statutory form to be used verbatim for final waivers. Using a non-statutory form in a statutory-form state renders the waiver void or unenforceable, and in some jurisdictions creates a presumption of bad faith. The 50-state pack includes the correct statutory form for each state. New York, Massachusetts, Pennsylvania, and most New England states allow custom drafting. The pack’s variants for those states are non-statutory but pressure-tested against the underlying lien statute.
Do I need to notarize a conditional final lien waiver?
Florida §713.20 requires notarization on final waivers. Mississippi §85-7-419 requires notarization on certain final-waiver classes. Texas Property Code §53.281 requires the waiver to be either notarized or sworn under penalty of perjury. The form has both options. Wyoming §29-2-115 requires notarization. Louisiana, Nevada, and a handful of other states require notarization on certain final-waiver classes. Most other states do not require notarization for the final waiver, but a notarized waiver is rarely worse than a non-notarized one in litigation. The 50-state pack’s index sheet flags each state’s notarization requirement; when in doubt, notarize.
What’s the deadline to execute a conditional final waiver after final payment is made?
Most states impose no deadline. The conditional final waiver is executed before or with final payment, and the conditional release converts to an unconditional release as soon as the payment clears. A few states impose deadlines on related actions: Mississippi requires the waiver to be executed within 30 days of payment receipt for certain classes; Missouri imposes a 10-day window on final waivers in certain commercial classes. The pack flags these on the index sheet. As an operating rule, get the conditional final waiver executed and on file before the final check is cut, then log the receipt date when the cash hits. That closes the conditional-to-unconditional loop cleanly.
How long should I retain executed final waivers?
The relevant state’s statute of limitations on lien claims, plus a margin. Typical retention: 7–15 years post-substantial-completion for final waivers, longer than progress waivers because final waivers tend to be the documentary anchor in any post-closeout dispute. California’s §8412 is 90 days from completion for the lien itself, but the limitations periods on contract breach and indemnity claims run 4–6 years; Texas’s §53.052 is 4 months for lien filing, but breach-of-contract is 4 years and indemnity is up to 8. Most multi-state primes retain executed final waivers for 10–15 years post-project-closeout to cover the full statute-of-limitations period across all relevant states. Federal projects often retain longer because the agency’s own document-retention rules drive a longer tail.