The 50-state conditional progress lien waiver pack federal-construction primes use to send the statutorily-correct form to every sub on every pay app. California §8132, Texas §53.284, Florida §713.20, and 47 more.
Why federal-construction primes need a 50-state conditional progress lien waiver pack
There is no such thing as “the” conditional progress lien waiver. There are fifty of them, and the wrong one, used in the wrong state, is either unenforceable, overbroad, or in the case of California, Texas, Mississippi, Missouri, Wyoming, Nevada, Utah, and Florida, statutorily defective. A waiver that doesn’t match the state-mandated form is treated as no waiver at all, or worse, as evidence that the GC is trying to pull something on the sub. Either way, the project gets paid late.
Most operators discover this the hard way. A prime running a project in Sacramento sends every sub the same lien waiver template their counsel drafted three years ago for a Phoenix job. Half the subs sign it. The other half, usually the larger ones with their own counsel, bounce it back asking for the California Civil Code §8132 form. Now the prime’s contracts admin has two parallel waiver workflows on the same project, the AP team is holding pay apps because the waivers in the file don’t match what the sub’s lien rights actually look like, and the lender’s draw inspector is flagging the package as non-compliant.
The 50-state pack solves this by giving the prime one logical template that has fifty correct variants. California gets the §8132 statutory form, with the through-date and payment-amount fields placed exactly where the statute requires and the operative language quoted verbatim. Texas gets the §53.284 form, which differs from California’s in seven specific ways. Florida gets the §713.20 form. New York, which has no statutory form, gets a non-statutory waiver that’s been pressure-tested against §34 of the New York Lien Law. Every state’s variant is in the pack, organized by state, with the statutory citation, notarization requirement, deadline-to-execute requirement, and any special conditions called out in a single index sheet.
The federal-construction operator angle matters here because federal projects span states and frequently involve subs that operate across state lines. A prime running a VA hospital project in Phoenix and a Corps of Engineers project in Sacramento has to maintain two separate lien waiver workflows because of state-specific statutory differences. The Miller Act doesn’t preempt state lien-waiver formality requirements on the federal-prime/sub relationship. The pack handles this. It’s the artifact a multi-state federal prime uses to standardize lien-waiver workflow without sacrificing per-state statutory accuracy.
What this is NOT: it’s not legal advice on whether to use a conditional vs unconditional waiver (that decision lives in the K021 decision matrix), it’s not a substitute for state-licensed counsel review of your specific subcontract language, and it’s not a mechanics-lien filing checklist (that’s). It’s a starting-point template pack for the operator who has to actually generate, send, collect, and file 50–500 lien waivers per month across a multi-state portfolio. Use it. Have your state-licensed construction counsel review the specific variants you’ll use. Then run the workflow.
Who this 50-state pack is for
- Multi-state commercial GCs running projects across 3+ jurisdictions where state lien-waiver formality differs
- Federal prime contractors maintaining state-by-state lien-waiver workflows on federal projects in California, Texas, Florida, Mississippi, Missouri, Nevada, Utah, Wyoming, and the 8 other statutory-form states
- Specialty subcontractors working in multiple states who need to recognize when a GC is sending the wrong-state waiver
- Contracts administrators assembling pay-app packages that include conditional progress waivers from every tier-1 and tier-2 sub
- AP teams gating pay-app release on receipt of a properly-formed conditional waiver
- Project finance and lender draw inspectors verifying the waiver pack matches each state’s statutory requirement
If you’re trying to decide between conditional vs unconditional in the first place, work through the conditional vs unconditional release decision matrix before downloading the 50-state pack.
The 12 content categories the 50-state pack covers
The pack covers 12 categories of content the prime needs across the 50-state set. Every state’s waiver in the pack addresses each of these. The variant differs by jurisdiction, but the structure is consistent so the contracts admin doesn’t have to relearn the form for every state.
- State-specific statutory form requirements. The pack identifies which states (California §8132, Texas §53.284, Florida §713.20, Mississippi §85-7-419, Missouri §429.620, Nevada §108.2453, Utah §38-1a-802, Wyoming §29-2-115, Georgia §44-14-366, Michigan §570.1115, and 6 others) require the statutory form verbatim and which states allow custom drafting. Using a non-statutory form in a statutory-form state renders the waiver void.
- Notarization requirements by state. California requires no notarization for §8132 progress waivers. Texas requires no notarization for §53.284. Mississippi requires no notarization. Florida requires no notarization for §713.20. But Wyoming, Missouri, Louisiana, and Nevada all require notarization on certain progress-waiver classes, and the pack flags each. The notarization-required column on the index drives whether the prime sends the waiver as a fillable PDF or a notarial-block-ready DOCX.
- Through-date and payment-amount conditional language. Every conditional progress waiver is conditioned on (a) the through-date, the cut-off date through which the sub is waiving, and (b) the payment amount, the specific dollar figure the sub is conditionally accepting. The pack’s variants place these fields per each state’s statutory positioning. California requires the through-date to appear immediately after the operative waiver clause. Texas requires both fields to appear in the heading paragraph. Florida is more flexible.
- Effective release on receipt of payment (standard conditional language). The defining feature of a conditional progress waiver: the release is effective only upon the sub’s actual receipt of the specified payment amount. Until the check clears, the sub retains lien rights. The pack uses each state’s statutorily-required language to express this: “shall be effective only upon” in California, “is conditional upon” in Texas, etc. Using the wrong verb in a statutory-form state can convert the waiver into an unconditional one inadvertently.
- Reservations of rights for unbilled work and change orders. Every state’s variant reserves the sub’s lien rights for (a) work performed but not yet billed through the through-date, (b) pending change orders, (c) retention/retainage held back, and (d) extras that have been performed but not yet been the subject of a change order. The reservation language differs by state. California §8132 has a fixed reservation block, Texas §53.284 leaves room for negotiated reservations, and non-statutory states require the operator to draft the reservation explicitly.
- Joint check provision compatibility. When a payment is going to be made via joint check (typically GC-to-sub-and-supplier), the conditional waiver must address the joint check explicitly so the sub doesn’t waive lien rights for the supplier-portion of the payment. The pack’s variants include joint-check-aware language for the states where joint checks are common (California, Texas, Florida, New York) and a generic joint-check optional rider for the rest.
- Required signature blocks by state. Some states require the waiver to be signed by an authorized officer of the sub (Florida §713.20). Some states allow signature by any authorized agent (California §8132). Some require both the sub’s signature and the sub’s surety’s signature when bonds are involved (rare but appears in Wyoming and Mississippi for certain project classes). The pack’s signature block per state matches the statutory expectation.
- Deadline-to-execute requirements. Several states impose a deadline by which a conditional progress waiver must be executed and delivered relative to the payment-receipt date. Failure to meet the deadline can render the waiver ineffective or expose the sub to lien-bond/penalty exposure. The pack flags states with deadlines (Mississippi: 30 days; Missouri: 10 days; Wyoming: 30 days) and includes a deadline-tracking field on the index sheet.
- Identification of the project (legal description, address, owner, prime, GC). Every state’s variant requires the project to be identified specifically enough that a recorded lien (if filed against the same project) would clearly relate to the same matter. The pack standardizes the project-identification section: legal description, project address, owner of record, prime contractor of record, and GC if different from prime. Vague project identification (“the Smith building project”) is a common reason waivers get challenged in lien-bond hearings.
- Identification of the claimant (sub legal entity, contact, services performed). Mirror requirement on the claimant side: the sub’s legal entity name (matching the subcontract signature block and the sub’s W-9), the sub’s tier (tier-1 to GC, tier-2 to another sub), and a brief description of the services or labor and materials provided. Discrepancies between the sub’s name on the waiver and on the subcontract are the most common reason waivers are rejected in lien-bond claims.
- State-specific exclusions and exceptions. Several states allow specific categories of work or claims to be excluded from the waiver’s scope by the sub. California §8132 allows reservation of disputed claims explicitly. Texas §53.284 allows reservation of unsettled change orders. Florida §713.20 allows reservation of work performed within the 30-day window before the through-date. The pack’s variants include the state’s standard exclusion language.
- Amendments and modifications cycle when payment terms change. When the prime renegotiates payment terms mid-project (e.g., switches from monthly to biweekly draw, increases retention from 5% to 10%, etc.), the conditional waiver template should be updated so the sub isn’t signing waivers that reference outdated payment cycles. The pack includes an amendment log on the index sheet that tracks which state’s variant was used in which month, so a multi-state prime can audit its own waiver workflow when terms change.
How to send the right state’s waiver on every pay-app cycle
Use the index sheet first. It’s an Excel sheet listing all 50 states, the form variant (statutory or non-statutory), the citation, notarization requirement, deadline, and the corresponding Word file in the pack. Pull the right state’s Word file for the project’s jurisdiction, fill in the project, claimant, through-date, and payment amount, and route to the sub for signature.
For each pay-app cycle:
- 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).
- Fill the project-identification block (legal description, address, owner, prime, GC) and the claimant-identification block (sub legal entity, tier, services).
- Fill the through-date (cut-off through which the waiver applies) and the payment amount (the conditional amount).
- Route to the sub’s authorized signer per the state’s signature-block requirement.
- If the state requires notarization (Wyoming, Missouri, Louisiana, Nevada. See index), route through the notary first.
- File the executed waiver in the pay-app package and release the corresponding payment. The waiver becomes effective on the sub’s actual receipt of payment. Log the receipt date for the file.
Refresh the pack annually because state statutes change. Confirm with state-licensed construction counsel before relying on any specific variant for a live project.
Stop maintaining 50 separate lien waiver templates
The 50-state pack solves the template-collection problem. It doesn’t solve the workflow problem. Sending the right state’s variant to the right sub on the right pay cycle, collecting it back inside the deadline, validating that the sub used the correct statutory form, tracking the through-date and payment amount, and filing the executed waiver in the project package. That’s still 30+ minutes of contracts-admin work per pay app, multiplied by every active sub on every active project. Contracts Connected’s Contract Intelligence feature reads the project’s state of jurisdiction from the prime contract, auto-generates the correct state’s waiver variant pre-filled with project, claimant, through-date, and payment amount, sends it to the sub for e-signature, and files the executed waiver back in the project package. All without the contracts admin opening Word once. Same 50-state pack, runs itself.
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 progress lien waivers
What’s the difference between conditional and unconditional progress waivers?
Conditional progress waivers waive lien rights only upon the sub’s actual receipt of the specified payment amount. Until the check clears, the sub retains lien rights. Unconditional progress waivers waive lien rights immediately upon execution, regardless of whether payment has been received. Conditional waivers are signed and delivered with the pay app to support the GC’s draw request to the lender; unconditional waivers are signed after the sub has the cash.
Which states require a statutory form for conditional progress waivers?
California (Civil Code §8132), Texas (Property Code §53.284), Mississippi (§85-7-419), Missouri (§429.620), Nevada (§108.2453), Utah (§38-1a-802), Wyoming (§29-2-115), Georgia (§44-14-366), Michigan (§570.1115), Florida (§713.20), and a handful of others require the statutory form to be used verbatim. Using a non-statutory form in a statutory-form state renders the waiver void or unenforceable. The 50-state pack includes the correct statutory form for each state.
What if my project crosses state lines?
Use the state where the work is being performed, not where the sub is based or where the GC is headquartered. For projects on state-line construction (very rare. Typically only certain bridge or highway work), consult state-licensed counsel; the pack’s per-state variants assume single-state work. Most multi-state federal projects involve discrete buildings on single-state sites, so the per-state variant rule applies cleanly.
Do I need to notarize a conditional progress waiver?
It depends on the state. California, Texas, Florida, Mississippi, and most other statutory-form states do not require notarization for the conditional progress waiver. Wyoming, Missouri, Louisiana, and Nevada require notarization on certain progress-waiver classes. The 50-state pack’s index sheet flags each state’s notarization requirement. When in doubt, notarize. A notarized waiver is rarely worse than a non-notarized one in litigation.
Can I use the same waiver for multiple pay-app cycles?
No. Every pay-app cycle requires its own conditional progress waiver because the through-date and payment amount change each cycle. Re-using a prior cycle’s waiver creates two problems: (a) the sub may inadvertently waive lien rights for the new cycle’s work, and (b) the through-date no longer matches the work being paid for. Generate a new waiver per cycle from the pack’s templates.
How long should I retain executed waivers?
The relevant state’s statute of limitations on lien claims, plus a margin. Typical retention: 5–10 years post-substantial-completion. California’s §8412 is 90 days from completion; Texas’s §53.052 is 4 months from last work; but the limitations periods on related contract claims (breach, indemnity) extend much longer. Most multi-state primes retain executed waivers for 10 years post-project-closeout to cover the full statute-of-limitations period across all relevant states.