A single defective conditional lien waiver can hold up a six-figure draw request. A missing one can expose your entire project to lien claims.

This checklist is designed for the GC project manager or controller who reviews conditional waivers every billing cycle. Run through it for every waiver you receive from subs and every waiver you issue to owners. Twelve checks. Five minutes per waiver. Zero excuses for preventable errors.

The 12-Point Conditional Waiver Compliance Checklist

Check 1: Verify the Correct Form Type

What to check: Confirm the document is a CONDITIONAL waiver, not an unconditional one.

How to check: Look for conditioning language. The operative section should contain phrases like:

"Upon receipt of payment"
"Conditioned on payment of"
"Effective only when payment has been received and deposited"
"This waiver is conditional upon the maker's receipt of payment"

Red flags:

Document title says "conditional" but the body contains unconditional release language
No reference to payment as a condition
Language says "hereby waives" without any condition attached
The form is an unconditional progress or unconditional final waiver

Pass/Fail: If the waiver doesn't contain clear conditioning language, reject it. Do not accept a waiver based on its title alone.

Check 2: Confirm the Waiver Type Matches the Payment Stage

What to check: Is this a progress waiver or a final waiver? Does it match where the project stands?

Project Stage	Correct Waiver Type
During construction (monthly billing)	Conditional Progress
At project completion (final billing)	Conditional Final
Retention release	Conditional Final

Red flags:

A conditional final waiver submitted during active construction
A conditional progress waiver submitted at project completion
A conditional final waiver that doesn't include retention amounts

Check 3: Match the Dollar Amount to the Pay Application

What to check: The conditional waiver amount must match the corresponding pay application amount exactly.

How to check: Compare the waiver amount against:

The net payment amount on the pay application (gross billing minus retention)
Any adjustments for disputed items
Any credits or backcharges applied

Pass/Fail criteria:

Comparison	Result
Waiver = Net pay app amount	Pass
Waiver > Net pay app amount	Fail -- sub is waiving too much
Waiver < Net pay app amount	Fail -- coverage gap
Waiver = Gross pay app (ignoring retention)	Fail -- retention shouldn't be included

Check 4: Verify the Through-Date

What to check: The through-date on the conditional waiver must match the billing period end date on the pay application.

How to check: Find the through-date on the waiver (sometimes labeled "for work through" or "covering the period through"). Compare it to the billing period on the pay app.

Red flags:

Through-date is the date the waiver was signed (common error)
Through-date is earlier than the billing period end date (creates a gap)
Through-date is later than the billing period end date (covers unbilled work)
Through-date is blank

A through-date error of even one day can create a gap in waiver coverage.

Check 5: Confirm Party Names Are Correct

What to check: All parties must be correctly identified.

Required parties on most conditional waivers:

Claimant: The party waiving lien rights (sub, supplier)
Customer: The party the claimant contracted with (GC, or higher-tier sub)
Owner: The property owner
Direct contractor: The GC (if different from the customer)

Red flags:

DBA name used instead of legal entity name
Old entity name (company changed names or restructured)
Wrong owner name (common on projects that have been sold)
Missing party fields

Check 6: Verify Project Identification

What to check: The waiver must clearly identify the project.

Required project information:

Project name
Project address (street, city, state)
Project number (if applicable)
Contract number or purchase order number

Red flags:

Generic project description that could apply to multiple projects
Wrong project address
Missing project number on a project that uses numbered identification

A waiver with vague project identification can be challenged as not applying to the specific project in question.

Check 7: Check for Proper Exception Language

What to check: If there are disputed amounts, pending change orders, or other exclusions, they should be explicitly stated.

Acceptable exception language: "This conditional waiver specifically excludes and reserves all rights related to [specific description] in the amount of [$X]."

Unacceptable approaches:

Including disputed amounts in the waiver without exception language
Vague references to "all disputes" without specifics
Exception language that's buried in fine print or handwritten margins

Check 8: Obtain Required Signatures

What to check: The waiver must be signed by an authorized representative of the claimant.

Verification steps:

Confirm the signer is authorized to bind the company
Verify the signer's name and title are printed or typed below the signature
Check the date of signature
If notarization is required (by state law or contract), confirm notarization is complete

Red flags:

Signature without printed name or title
Signed by someone other than an officer, manager, or authorized agent
Unsigned waiver (surprisingly common)
Signature date that predates the billing period

Check 9: Verify Statutory Compliance (Statutory States Only)

What to check: In the 12 statutory states, the waiver must conform to the state-mandated form.

Verification approach for statutory states:

Item	Check
Form matches statutory template	Compare word-for-word against state statute
Required notices included	Some states require specific warning language
No unauthorized additions	Added language can void the form
No unauthorized deletions	Removed language can void the form
Correct form version	Legislatures update forms; ensure current version

Check 10: Track the Conditional Status

What to check: Log the conditional waiver in your tracking system and set a follow-up for unconditional conversion.

Required tracking data:

Date conditional waiver received
Sub/supplier name
Pay app number and amount
Through-date
Expected payment date
Deadline for unconditional waiver follow-up (typically 30 days after expected payment)

The tracking entry isn't complete until a follow-up date is set. Without a trigger to chase the unconditional conversion, the conditional waiver sits in limbo indefinitely.

Check 11: Confirm Lower-Tier Coverage

What to check: If you're the GC, confirm that the sub has collected conditional waivers from their sub-subcontractors and material suppliers.

How to check:

Request a list of all lower-tier parties who provided labor or materials during the billing period
Cross-reference against submitted conditional waivers
Flag any lower-tier party who performed work but hasn't submitted a waiver

Common gaps:

Material suppliers who delivered but aren't tracked in the waiver system
Equipment rental companies
Sub-subcontractors who worked only a few days during the billing period
Temp labor agencies

Check 12: File and Store Properly

What to check: The signed conditional waiver is stored in an accessible, organized system with backup.

Storage requirements:

Filed by project, then by sub, then by billing period
Easily retrievable for lender draw packages
Retained for the statutory period (typically 6-10 years post-completion)
Backed up digitally if originals are on paper

Organization matters. When a lender requests the complete waiver package for a $15 million project, you need to produce it within hours, not weeks.

Monthly Compliance Audit

In addition to the per-waiver checklist above, run a monthly audit across all projects:

Audit Item	Action
Conditional waivers older than 45 days without unconditional conversion	Follow up on payment status
Subs who performed work but have no conditional waiver on file	Contact sub immediately
Through-date gaps between consecutive billing periods	Request corrected waivers
Amount mismatches between waivers and pay apps	Reconcile and correct
Statutory form compliance (for projects in statutory states)	Re-verify form type
Lower-tier waiver coverage	Cross-reference against active sub-tier lists

Frequently Asked Questions

How long should the 12-point review take per waiver? With practice, 3-5 minutes per waiver. Initial reviews take longer as you build familiarity with forms and requirements. With 20 subs on a project, budget 60-90 minutes per billing cycle for waiver review.

Who should be responsible for the checklist review? Typically the project engineer or project manager. On larger projects, the project accountant or a dedicated compliance coordinator handles waiver review. The key is assigning a single responsible person.

What if a sub submits a non-compliant waiver right at the deadline? Reject it and request immediate correction. Don't submit a non-compliant waiver to keep the billing on schedule. A non-compliant waiver is worse than a missing waiver because it creates a false sense of coverage.

Should I keep this checklist as a physical document or digital? Digital is strongly preferred. A digital checklist can be integrated with your project management software, auto-populated with project data, and audited across multiple projects simultaneously.

How do I handle a sub who consistently submits defective waivers? Schedule a waiver training session with the sub's accounting team. Provide them with blank forms and completed examples. If problems persist, consider pre-filling the waiver and sending it to the sub for signature only.

Does this checklist apply to both waivers I issue and waivers I receive? Yes. Apply the same standards to your own conditional waivers that you apply to waivers you receive from subs. Your owner and lender are running the same checks on your waivers.

Automate the Checklist

Running 12 checks on 25 waivers every month is a significant administrative burden. SubcontractorAudit automates every check on this list -- from form type verification to amount matching to statutory compliance -- and flags non-compliant waivers before they enter your system.

See automated waiver compliance in action ->