You can’t lien federal property, so this template waives the Miller Act payment-bond rights that actually exist, with a state-aware addendum for the work that isn’t on federal land.
Why a “federal lien waiver” is not really a lien waiver at all
Here is the thing almost every “federal lien waiver” online gets wrong, and it gets it wrong in the first word. You cannot put a mechanic’s lien on federal property. The land belongs to the United States, and the government holds sovereign immunity against lien claims, so the remedy you would use on a private job simply does not exist on a federal one. That means a document literally titled “federal lien waiver” is, on a true federal project, waiving a right that was never there. What it is actually releasing is something else entirely, and if you do not understand which right you are signing away, you can hand over real money for nothing.
On a federal construction project, the protection that replaces the mechanic’s lien is the Miller Act payment bond. The prime posts a payment bond, and subs and suppliers who go unpaid pursue the bond instead of the property. So when a sub signs a “waiver” on a federal job, the thing of value being released is the right to make a claim against that payment bond, plus any contract or general payment-claim rights, through the date and dollar amount stated. Get the through-date wrong, sign before the check clears, forget to carve out a pending change order, and the sub has waived a live bond claim. That is the actual stakes, and it is why a single generic waiver form copied off a legal-template site is the wrong tool for this work.
This template is built for the messy reality most federal subs and primes actually live in. Pure federal projects run on bond-claim rights. But a huge share of the work is mixed: a federally funded project sitting on land the government does not own, a state or local pass-through job, a private project for a federal contractor, or a portfolio where the same admin papers all of it single-handedly. On the non-federal portions, real lien rights do exist and state law governs the waiver word for word. So this is two documents in one. The core form is a partial or final waiver written for the federal bond-claim and payment-claim context. The state-aware addendum handles the state-law portions for any work that is not on federal land, where the right being waived really is a mechanic’s lien and the form has to respect the local statute.
One more piece almost nobody flags. On a Miller Act job, a broad waiver of payment-bond rights signed in advance of the work, or as a blanket condition buried in the subcontract, is widely treated as unenforceable. The bond protections are not something a sub can be made to sign away up front. A properly scoped waiver releases rights only for labor and materials already furnished through a stated date, in exchange for a stated payment received. This template is drafted around that principle: conditional on payment, limited to a through-date, with an explicit exclusions block for everything still open. If you manage these at any volume, the lien waiver management software side of this is what keeps the whole stack correct.
One honest note on what this is and is not. This is an operator-built starting point, not legal advice and not a substitute for construction counsel reviewing the specific language against your subcontract and the relevant jurisdiction. Lien and bond rules vary by state and by project type, and the consequences of getting a final waiver wrong are large. Use the form to get organized and to stop sending the wrong release on the wrong project. Have your attorney confirm the variant you will actually use, especially the exclusions language on anything with an open dispute.
Who this template is for
- Federal general contractors and primes collecting waivers from subs as a condition of progress and final payment on Miller Act projects
- Federal subcontractors and suppliers who need to recognize when a waiver is releasing bond-claim rights, not lien rights, and scope it accordingly
- 8(a) and small-business federal subs acting as primes on set-aside contracts who manage their own sub waivers
- Contracts administrators running mixed portfolios of federal, state-funded, and private work with one admin
- AP and project-finance teams gating payment release on a properly formed, payment-conditioned waiver
- Risk managers and CFOs signing off on closeout exposure when change orders or disputes are still open at final payment
If you are deciding between conditional and unconditional, or progress and final, work through the conditional final lien waiver 50-state pack before you send anything on a project where state lien rights actually apply.
The 13 fields on the federal lien waiver template
The template carries the 13 fields a properly scoped federal-context waiver needs, including the federal addendum block and the state-aware section for non-federal work. The core fields stay consistent so the admin does not relearn the form for every project; the addendum and the state section flex to the project type.
- Project type and jurisdiction selector. Before anything else, the form forces a single decision: is this work on federal land (bond-claim rights, no mechanic’s lien), on non-federal land (state lien rights apply), or mixed. This field drives which sections of the rest of the form are operative. Getting this wrong at the top is how a sub ends up signing a state lien-waiver form on a job where the only right that existed was a bond claim, or vice versa.
- Claimant name and contractual role. The sub or supplier’s full legal entity name matching the subcontract signature block and the W-9, the entity type, and the tier on the project. Name discrepancies, especially with a DBA or a parent and subsidiary structure, are a common reason waivers and bond claims get challenged. The role also signals whether the claimant is first-tier to the prime or further down the chain, which matters for bond-claim notice rules.
- Prime contractor and payment bond reference. The prime that holds the federal contract and posted the Miller Act payment bond, plus the bond number, surety name, and surety claims contact where known. On a federal job this is the field that anchors the whole document, because the bond is the right being affected. Leaving it blank produces a waiver that does not clearly connect to the instrument it is releasing rights against.
- Owner or contracting agency of record. On a federal project, the contracting agency and its contracting office; on non-federal or mixed work, the fee owner recorded on title. The form keeps both because mixed projects have both. This field also tells a later reader, an auditor or a surety, what kind of project they are looking at without having to dig.
- Project name and full description. The project name as it appears in the prime contract, not the marketing name, plus enough address or description that the waiver clearly ties to one specific project. Vague identification is a recurring reason waivers get challenged, since a reviewer cannot match the release to the work.
- Waiver type: conditional or unconditional. Conditional means rights are released only when payment is actually received; unconditional means rights are released on signing regardless of payment. The form defaults to conditional and warns in plain language that an unconditional waiver signed before the money is in hand is how subs get burned. The choice is explicit, never assumed.
- Payment timing: progress or final. A progress waiver is partial and limited to a through-date and a stated amount, leaving future and retained work intact. A final waiver releases everything for the project. The form treats these as different documents with different consequences and makes the operator pick, because confusing the two at closeout is the most expensive mistake on this form.
- Through-date. The single date through which rights are being released. Every dollar of labor and material furnished on or before this date is covered; nothing after it is. This is the field that most often gets left at a default or a stale value, which silently expands or shrinks what the sub is giving up. The form flags it as required and as the most consequential entry on the page.
- Payment amount and consideration. The specific dollar amount being received in exchange for this waiver. The form never permits a blank or a “paid in full” with no number, because a waiver not conditioned on a specific amount received is the classic trap. On a conditional waiver this is the amount whose receipt triggers the release.
- Exclusions and reservations block. A dedicated, first-class section where the claimant lists everything not being released: pending change orders by number and amount, unsettled disputes, retention not yet released, and any back charges in question. On a federal job this is where the sub preserves bond-claim rights for open items; on a state job it preserves lien rights. A waiver without a working exclusions block is how a sub loses a six-figure pending change order at final payment.
- Federal bond-claim addendum. A short attached block, operative only when the project type is federal or mixed, that states plainly the release runs to payment-bond and contract payment-claim rights rather than to a mechanic’s lien, references the Miller Act payment bond framework, and confirms the waiver is conditioned on payment and limited to the through-date. This is the piece that makes the document honest about what it actually does on federal land.
- State-aware section for non-federal work. Operative when the project type is non-federal or mixed, this section flags that state law governs the waiver of any real lien rights, that some states mandate a specific statutory waiver form, and that notarization and exact wording requirements vary by jurisdiction. It deliberately does not assert a particular state’s statute section, because those change and vary; it points the operator to use the matching state-specific waiver where a statutory form is required.
- Signature, authority, and notarization block. Signer name, title, and confirmation of authority to bind the entity, the execution date, and a notarization block that is used where the governing jurisdiction requires it. The authority line matters because a waiver signed by someone without authority to bind the entity invites a later challenge, and a missing notarization can void the document in states that require it on final waivers.
How to use it
Start with field 1 and answer the jurisdiction question honestly, because everything downstream depends on it. For a true federal project, the bond-claim addendum is operative and the state section is informational only. For non-federal work, the reverse. For mixed, both apply and you scope each to the right portion. Default every waiver to conditional and to progress unless you are genuinely at closeout. Set the through-date deliberately on every single waiver; never let it ride. Fill the exclusions block before you fill the payment amount, so open change orders and disputes are captured first. Where a state mandates a statutory waiver form, use that state’s form for the lien portion and attach this as the federal-context cover. The Excel version includes a per-field completion check so an AP team can see at a glance whether a received waiver is fully and correctly filled before they release payment.
Stop sending the wrong waiver on the wrong project.
Federal jobs run on bond-claim rights, state jobs run on lien rights, and a mixed portfolio runs on both, papered by one person. Contracts Connected reads waivers, contracts, and bond documentation as they come in, ties each to the right project type, and flags the through-dates, exclusions, and missing fields before anyone releases payment. The template tells you what a correct waiver looks like. CC keeps the whole stack of them correct so you are not catching a void final waiver at closeout.
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 the federal lien waiver template
Can you file a mechanic’s lien on a federal construction project?
No. Federal property is owned by the United States and is protected by sovereign immunity, so a mechanic’s lien cannot attach to it. That is the entire reason the Miller Act exists. Instead of a lien, subcontractors and suppliers on a covered federal construction contract are protected by a payment bond the prime is required to post. A federal lien waiver, then, is really releasing rights against that payment bond and any contract payment claim, not a lien on the land.
What does a federal lien waiver actually waive?
On a true federal project it waives the claimant’s right to pursue the Miller Act payment bond, plus contract and general payment-claim rights, for labor and materials furnished through the stated date and amount. It does not waive a property lien, because none exists on federal land. On mixed or non-federal portions of work, where the project sits on land the government does not own, real lien rights can exist and the waiver of those is governed by state law. That is why this template separates the federal bond-claim addendum from the state-aware section.
Is a Miller Act payment bond claim subject to deadlines?
Yes, and they are strict. Under the Miller Act framework, a claimant without a direct contract with the prime generally must give the prime written notice within 90 days of last furnishing labor or materials, and any claimant must file suit within one year of last furnishing. A claimant with a direct contract with the prime is generally not required to give the 90-day notice but is still bound by the one-year suit deadline. Because these deadlines are unforgiving, the exclusions block on a waiver matters: signing away bond-claim rights for an open item can leave a claimant with no remedy.
Can a subcontractor be required to waive payment-bond rights in advance?
This is a critical wrinkle on federal work. A broad waiver of Miller Act payment-bond rights signed in advance of performing the work, or imposed as a blanket subcontract condition, is widely treated as unenforceable. The bond protections are not something a sub can be forced to sign away up front. A properly scoped waiver releases rights only for work already furnished through a stated date, conditioned on a stated payment received. This template is drafted around that principle, which is also why blank, advance, or unconditional-before-payment waivers are flagged as the wrong tool.
What is the difference between a conditional and an unconditional waiver?
A conditional waiver releases rights only once payment is actually received, so if the check never clears, the claimant has given up nothing. An unconditional waiver releases rights on signing, regardless of whether payment ever arrives. On both federal and non-federal work, signing an unconditional waiver before the money is in hand is the most common way subcontractors lose claims. The safe default, and this template’s default, is conditional, limited to a through-date, and tied to a specific dollar amount received.
Does this template replace a state-specific lien waiver form?
Not for the lien portion of non-federal work. Several states mandate a specific statutory waiver form, and using a non-statutory form in those states can render the waiver void or invite a challenge. For any non-federal work where state lien rights apply, use the matching state-specific waiver for the lien release and treat this template as the federal-context cover plus addendum. On pure federal projects, where the only right at issue is the bond claim, the federal-context form is what you need. When in doubt, have construction counsel confirm the right form for the jurisdiction.