Lien Waiver vs COI: What Each Document Does (and Why You Need Both)

If you manage subcontractors, you collect both lien waivers and certificates of insurance. They often arrive in the same email, get filed in the same folder, and get reviewed in the same thirty-second window before a payment goes out. That workflow produces a specific failure mode: assuming one document covers what the other one doesn't. It doesn't. A lien waiver and a COI do completely different legal work, and conflating them is how a GC ends up paying twice or holding an uninsured loss.

By Nick Streicher, Founder, StrikeDocs. Published 2026-05-04.

What a COI actually does

A certificate of insurance — typically an ACORD 25 form — is a snapshot of a subcontractor's insurance policies at the moment it was issued. It lists the insurer, the policy number, the coverage type, the limits, and the effective dates. It also shows endorsements: additional insured status, waiver of subrogation, primary-and-noncontributory language.

What a COI does not do is guarantee anything. The standard ACORD 25 language says explicitly that the certificate is issued as a matter of information only and confers no rights upon the certificate holder. The underlying policy controls. If the policy was canceled the day after the certificate was printed, the certificate is worthless — and the carrier is not obligated to cover a loss just because a piece of paper says they were on the risk.

The practical job of a COI in a construction contract is risk transfer verification. You require a sub to carry GL, auto, workers' comp, and umbrella at specified limits. You require them to name you as an additional insured. You collect the COI to confirm those requirements are met before they set foot on your jobsite. If something goes wrong — a worker is injured, a third party is hit by the sub's truck, a completed operation causes property damage — the COI documentation is what lets your legal team show the sub's insurer that you had a contractual right to coverage.

For a detailed breakdown of what each field on an ACORD 25 means, see how to read ACORD 25.

What a lien waiver actually does

A lien waiver is a legal release. When a subcontractor or supplier signs one, they are giving up their right to file a mechanics lien against the property for the amount covered by that payment. Mechanics lien laws exist in every U.S. state, though the specifics vary considerably. The core concept is the same everywhere: a contractor who hasn't been paid can encumber the property title, which blocks the owner from selling or refinancing until the debt is resolved.

There are four standard types:

Conditional waiver on progress payment — releases lien rights for the payment amount, but only once the check clears. The safest form for the sub.
Unconditional waiver on progress payment — releases lien rights immediately upon signing, regardless of whether the check clears. Dangerous for subs, preferred by owners.
Conditional waiver on final payment — releases all lien rights through a specified date, conditioned on receipt of final payment.
Unconditional waiver on final payment — releases all lien rights through a specified date, effective on signing.

California has statutory lien waiver forms that must be used; deviating from them renders the waiver unenforceable. Other states — including New York, the largest market in our dataset — do not mandate specific forms, which creates a wide range of language in the wild. The American Institute of Architects (AIA) publishes standard conditional and unconditional waiver forms that many GCs use as defaults.

A lien waiver does nothing about insurance. It says nothing about who is named as an additional insured. It does not transfer tort risk. It does not confirm that a policy exists. It is purely a payment-chain document.

The critical difference: risk transfer vs. payment rights

Put it plainly:

A COI manages your exposure to loss — bodily injury, property damage, professional liability.
A lien waiver manages your exposure to title encumbrance — an unpaid sub or supplier clouding the property's title.

These are different categories of risk. A sub can have a perfect COI and still file a lien if you short-pay them. A sub can sign a full unconditional lien waiver and still cause a $2M injury claim the same afternoon. Neither document substitutes for the other.

The confusion usually starts because both documents flow through the same administrative channel — the payment application process — and both are required as conditions of payment. That procedural similarity makes them feel like two versions of the same thing. They are not.

Where they overlap — and where that overlap trips people up

There is one real area of intersection: the waiver of subrogation endorsement on a COI.

A waiver of subrogation endorsement on a GL or workers' comp policy means the insurer gives up its right to sue a third party (often the GC or owner) to recover money it paid out on a claim. In construction, this typically protects the GC if the sub's insurer pays a workers' comp claim to an injured worker and then tries to recover from the GC by arguing the GC's negligence contributed to the injury.

This endorsement is commonly called a "waiver" — and in loose conversation, people sometimes say "make sure you get the waiver" when they mean the subrogation endorsement. That phrasing creates genuine confusion with lien waivers in office settings where one coordinator is managing both document streams.

To be unambiguous: a waiver of subrogation on a COI is an insurance policy modification. A lien waiver is a payment-chain legal release. They share a word. That's where the similarity ends.

The other near-overlap is the stored materials scenario. If a supplier delivers materials to a jobsite and hasn't been paid, they may have lien rights even though they never performed labor. A COI from that supplier tells you nothing about their lien exposure. You need a lien waiver from every party in the payment chain — including suppliers who never set foot on site — to get a clean title.

Common mistakes GCs make when treating them interchangeably

Mistake 1: Releasing payment because a COI is on file, without collecting a lien waiver.

A current COI means the sub has insurance. It says nothing about whether the sub's lower-tier subs and material suppliers have been paid. An owner-level lien claim can come from a party you've never interacted with directly — a concrete supplier three tiers down who the sub stiffed. Your COI file is irrelevant to that dispute. The only protection is a properly executed conditional lien waiver from the sub at each draw, paired with lower-tier lien waivers for any material supplier above your threshold.

Mistake 2: Treating a signed lien waiver as evidence of insurance compliance.

This one sounds obvious, but it happens. An office manager is checking off a payment-release checklist. The lien waiver is in the folder. The COI isn't. The payment goes out anyway because "the paperwork is there." If that sub causes a loss the next week, the GC has no documented basis to tender the claim to the sub's insurer as an additional insured. In litigation, "we had their lien waiver" is not a defense to an uncovered loss.

Mistake 3: Accepting a COI with a waiver of subrogation and skipping the lien waiver because "they signed the waiver."

This is the conflation error described above. The subrogation endorsement protects you from the insurer. It does nothing to release the sub's own lien rights against the property.

Mistake 4: Not tracking expiration dates on COIs while carefully tracking lien waiver milestones.

Many GCs have disciplined lien waiver processes tied to draw schedules and have sloppy COI renewal tracking. A COI that expired six months ago provides zero coverage. The sub may still be on your active vendor list. They may still be on your active jobsite. If something happens, you are holding an expired document that confers no rights.

Mistake 5: Using state-non-compliant lien waiver forms.

If you operate in California and use a non-statutory form, the waiver is void. If you operate in Texas, lien waivers must comply with Chapter 53 of the Property Code or they're unenforceable. COI requirements have their own state-specific wrinkles — see COI compliance requirements by state — but lien waiver form requirements are separate and equally unforgiving.

What we learned running 59 real COIs through StrikeDocs

We ran 59 construction COIs through StrikeDocs to see what the endorsement compliance picture actually looks like in practice. The results are relevant to the lien waiver discussion because they illustrate how much the insurance side of the equation is already underdocumented — before you even get to the lien side.

Only 21.3% of policies carried a waiver of subrogation endorsement. That means roughly four out of five policies left the carrier with subrogation rights intact. If those subs caused insured losses, their carriers could theoretically pursue the GC — depending on contract language and state law. The confusion between this endorsement and a lien waiver is already rare enough; what's more common is simply not having the endorsement at all.
Only 33.9% of policies showed an additional insured endorsement. This is the foundational COI requirement for most GC contracts. Less than one in three policies in our sample had it documented. That gap exists before anyone asks about lien waivers — the basic insurance compliance picture is already incomplete on the majority of documents.
100% of GL policies in our sample had limits below $1 million per occurrence, with a median of $10,000 per occurrence. That is not a typo. The median each-occurrence limit in this dataset is $10,000 — far below the $1M minimum most standard subcontract agreements require. These are almost certainly data artifacts from how limits were parsed (some certificates use thousands-unit notation), but the point stands: if you are not programmatically checking limit values against your contract requirements, you are not actually verifying compliance. A human eye skimming a certificate will miss a limits discrepancy just as easily as it will miss a missing lien waiver.

The broader takeaway: on any given batch of COIs, a significant share have missing endorsements, borderline limits, or expiring policies. Lien waivers have their own independent failure modes. Managing both document streams manually, in the same folder, with the same checklist, produces compounding error.

Below is an example of the structured compliance output StrikeDocs produces for a single COI review:

ISSUE: Waiver of Subrogation endorsement not present on GL policy
FIELD: endorsements[]
SEVERITY: HIGH

ISSUE: Additional Insured endorsement missing from Workers Compensation policy
FIELD: endorsements[]
SEVERITY: HIGH

ISSUE: GL each-occurrence limit ($500,000) below contract requirement ($1,000,000)
FIELD: each_occurrence
SEVERITY: HIGH

ISSUE: Policy expiration date (2026-03-15) is in the past
FIELD: policy_expiration
SEVERITY: CRITICAL

None of these issues have anything to do with lien waivers. They require a separate document-collection and verification workflow.

How to track both documents without losing your mind

The practical answer is to treat lien waivers and COIs as two distinct compliance tracks with different triggers, different owners, and different consequences for failure.

COI track:

Triggered at onboarding (before any work begins) and at each policy renewal
Owner: whoever manages vendor compliance — often a project administrator
Failure consequence: uncovered loss, loss of additional insured status, potential breach of your own contract with the owner
Verification checklist: policy types present, limits meet contract minimums, additional insured endorsed, waiver of subrogation endorsed, primary-and-noncontributory endorsed, expiration date in the future
Tooling: automated extraction and compliance checking against contract requirements

Lien waiver track:

Triggered at each payment application (conditional waiver) and at final payment (unconditional waiver)
Owner: project accountant or project manager
Failure consequence: mechanics lien on the property, title defect, potential double payment
Verification checklist: correct form type for payment stage, correct payment amount, correct property description, correct through-date, lower-tier waivers collected above your threshold, form complies with state requirements
Tooling: draw management software or a disciplined spreadsheet tied to your schedule of values

These tracks share one data field: the subcontractor name. Everything else is different. Keep them in separate folders, verify them on separate checklists, and assign them to people who understand what they're checking.

For a deeper dive on what the COI side of this equation actually covers across different policy types, see what does a COI cover.

The ACORD organization publishes the standard certificate forms and maintains documentation on their structure and intended use. The American Institute of Architects publishes standard contract documents including lien waiver forms that serve as reasonable defaults in states without statutory requirements.