Every subcontractor lien release form that crosses your desk deserves the same scrutiny you give a pay application. A release with a wrong date, a missing signature, or non-statutory language in a statutory state is not documentation. It is a liability masquerading as compliance.

This checklist provides the 12 verification points that separate enforceable releases from paper decoration. Use it for every release on every pay cycle. Print it. Pin it to the wall above your project accountant's desk. Build it into your review workflow.

The Pre-Check: Is This the Right Form?

Before examining any data on the form itself, answer one question: is this the correct form type for this project's state?

Project State	Required Form Source	Action if Wrong Form Received
Arizona, California, Michigan, Nevada, Utah	State statutory form (4 types)	Reject and reissue correct form
Florida	State statutory form (partial/final)	Reject and reissue correct form
Georgia	State statutory form (progress/final)	Reject and reissue correct form
Mississippi	Sworn statement with notarization	Reject and request notarized form
Missouri, Wisconsin, Wyoming	State-mandated language	Verify language compliance
Texas	State statutory form (notarized for final)	Reject if final is not notarized
All other states	Contract-specified or company form	Verify against contract requirements

If the form is wrong, stop. Do not verify anything else. Send it back and provide the correct form. No amount of accurate data rescues a non-statutory form in a statutory state.

Checkpoint 1: Correct Form Type for Payment Stage

The form type must match the payment stage. There are four possible types:

Conditional Progress -- Used with current pay application while payment is pending
Unconditional Progress -- Used for prior period after payment has cleared
Conditional Final -- Used with final pay application while final payment is pending
Unconditional Final -- Used after final payment has cleared and been confirmed

Red flag: An unconditional release submitted with a current pay application (before payment). This means the sub is waiving rights before receiving money. Send it back and request a conditional release instead.

Red flag: A progress release submitted with the final pay application. If this is the last payment, the release should be a final release covering all remaining rights.

Checkpoint 2: Proper Party Names

The lien waiver identifies the property owner by legal name
The general contractor is named correctly (matching the prime contract)
The subcontractor's legal entity name matches the subcontract exactly
The project name or description matches contract documents

Common error: The release names "Smith Electrical" but the subcontract is with "Smith Electrical Services, LLC." These are legally distinct entities. A release from an entity not party to the subcontract does not waive lien rights of the contracting entity.

Verification method: Keep a master list of every sub's legal entity name as stated in their executed subcontract. Cross-reference every release against this list.

Checkpoint 3: Matching Payment Amounts

The release amount matches the approved pay application amount for this period
The amount is stated in both numbers and words (if the form requires both)
If amounts differ between numbers and words, flag for correction
The amount reflects any GC adjustments to the original pay app submission

How to verify: Pull the approved pay application for the same period. Compare the approved amount (not the submitted amount) against the release amount. They must match to the penny.

Scenario	Release Amount	Payment Amount	Status
Perfect match	$87,450.00	$87,450.00	Accept
Release exceeds payment	$90,000.00	$87,450.00	Reject -- sub waiving too much
Payment exceeds release	$87,450.00	$90,000.00	Reject -- $2,550 unwaived
Rounded amount	$87,000.00	$87,450.00	Reject -- $450 unwaived

Checkpoint 4: Correct Through-Dates

The release specifies the exact period it covers (start date and end date or "through" date)
The through-date matches the pay application billing period
There are no gaps between the prior release's through-date and this release's start date
For final releases, the through-date covers through substantial completion or the final day of work

Common error: The January release covers work through December 31. The February release covers work through February 28. January 1 through January 31 is unwaived. One full month of work has no release coverage.

Verification method: Maintain a timeline for each sub showing covered periods. Each new release should begin the day after the previous release's through-date.

Checkpoint 5: Conditional vs. Unconditional Language

Conditional releases include explicit language: "effective upon receipt of payment" or equivalent
Unconditional releases include explicit language: "effective immediately" or equivalent
In statutory states, the exact statutory language is used without modification
The conditional/unconditional status matches the payment status (conditional for pending, unconditional for received)

Why it matters: A release that uses ambiguous language (neither clearly conditional nor unconditional) creates uncertainty about when lien rights are waived. If a dispute arises, ambiguity favors the party who did not draft the form, which is usually the sub.

Checkpoint 6: Valid Signature

The release is signed (not blank in the signature field)
The signer's name is legible or printed below the signature
The signer's title is indicated (officer, managing member, authorized agent)
The signer has documented authority to bind the subcontractor entity

Verification method: During sub onboarding, collect a list of authorized signers with their titles. Before accepting any release, confirm the signer appears on the authorized list.

Edge case: A release signed by a project superintendent who is an employee but not an officer. Unless the sub has provided a specific authorization letter granting signing authority to the superintendent, this release is potentially voidable.

Checkpoint 7: Notarization (Where Required)

For Mississippi projects: release is notarized
For Texas projects: final releases are notarized
Notary seal is current (not expired)
Notary jurisdiction covers the state where the document was executed
If using remote online notarization (RON), the state accepts RON for lien documents

States requiring notarization:

State	Notarization Required For
Mississippi	All lien waivers/releases
Texas	Final waivers/releases
All other statutory states	Not required

Checkpoint 8: Lower-Tier Release Collection

The sub has submitted releases from their Tier 2 suppliers and subcontractors
Lower-tier release amounts correspond to the sub's payments to those parties
Cross-reference against preliminary notices filed on the project
Any party that filed a preliminary notice has a corresponding release
Flag any preliminary notice filer without a release

Minimum standard: Collect Tier 2 releases for every sub on every pay cycle. On projects over $5M, consider requiring Tier 3 releases as well.

How to cross-reference: Maintain a list of all preliminary notice filers on the project. For each pay period, every active filer should have a release. If a supplier filed a preliminary notice in month 2 and has not submitted a release in months 3 through 6, investigate.

Checkpoint 9: Project Description Accuracy

The property address matches the project address
The legal description (if included) matches the recorded property description
On multi-phase projects, the correct phase or parcel is identified
The project name matches contract documents

Why it matters: A release for "123 Main Street, Phase 1" does not cover work performed on Phase 2 of the same property. On multi-parcel developments, a release referencing the wrong parcel number provides no protection for the correct parcel.

Checkpoint 10: Change Order Inclusion

If change orders were billed in this period, the release amount includes change order amounts
The release does not exclude change order work through limiting language
The total matches base contract billing plus approved change order billing

Common error: The sub submits a release for $50,000 covering base contract work. They also billed $8,000 in approved change orders. The release should be for $58,000. The $8,000 in change order work is currently unwaived.

Checkpoint 11: Retainage Treatment

Progress releases clearly state whether retainage is included or excluded
If retainage is excluded, confirm the release amount equals the net payment (billed minus retainage)
Final releases include retainage amounts
The retainage treatment matches your subcontract terms

Standard approach: Progress releases cover the net amount paid (after retainage withholding). The final release covers the total remaining balance including released retainage.

Checkpoint 12: Filing and Storage

The release has been digitally scanned or electronically captured
The file is named per your naming convention (Project_Sub_Period_Type)
The release is stored in the project's compliance folder
The tracking system/spreadsheet has been updated to show receipt
A backup copy exists in a separate location or cloud system

Quick Reference: The 60-Second Review

For experienced project accountants who process dozens of releases weekly, here is the abbreviated version:

Right form for state? Yes/No
Right form type for payment stage? Yes/No
Names match subcontract? Yes/No
Amount matches approved pay app? Yes/No
Through-date matches billing period? Yes/No
Authorized signer? Yes/No
Notarized (if required)? Yes/No/N/A
Lower-tier releases included? Yes/No

If any answer is "No," stop processing and request correction.

Frequently Asked Questions

How long should the verification process take per release? For an experienced reviewer with a standardized form and a master sub list, 3-5 minutes per release. On a project with 20 subs, that is 60-100 minutes per pay cycle for Tier 1 alone. Add lower-tier reviews and the time doubles.

Should I verify releases before or after issuing payment? Before. Always verify before releasing payment. The verified release package (current conditional + prior unconditional + lower-tier releases) should be complete and approved before the payment is processed.

What if a release passes 11 of 12 checkpoints? One failure is enough to compromise the release. If the amount is wrong, the release does not cover the correct payment. If the signer is unauthorized, the release may be voidable. Fix the failing checkpoint before accepting the release.

Can I delegate release verification to a junior staff member? Yes, for the data-matching checkpoints (amounts, dates, names). The form type determination and signature authority verification should be handled by someone with construction administration experience or reviewed by a senior team member.

What if a sub consistently submits defective releases? Address it during the next project meeting. Provide the correct forms pre-populated with project data. Consider using a compliance platform that generates the correct forms automatically and guides the sub through completion.

How does this checklist change for final releases vs. progress releases? Final releases require extra scrutiny on three points: the amount should cover all remaining balances including retainage, the through-date should extend through the final day of the sub's work, and the release type should be "final" rather than "progress." All other checkpoints apply equally.

Build this checklist into your workflow automatically. SubcontractorAudit verifies every data point on every release and flags discrepancies before payment is processed.

Automate release verification