Why subcontractors don't sign lien waivers (and how to fix it)
The five real reasons your subs ignore your waiver requests, and the five fixes that get them signing in two minutes instead of two weeks.
If your subs don't sign your waiver requests, the problem is rarely the sub.
It's almost always one of five specific things on your end. Fix those, and the signatures come back the same day.
Reason 1: You sent unconditional before the check cleared
This is the most common one and the easiest to fix.
If a sub sees an unconditional waiver in their inbox before they've been paid, they're going to do one of three things: ignore it, refuse it, or escalate to their lawyer. All three protect them.
The unconditional waiver releases their lien rights the moment they sign. If they sign before the payment clears and your check bounces, they have no recourse. Most state statutes write a bold warning into the unconditional form for exactly this reason. California Civil Code §8134 and Texas Property Code §53.284(c) both make the protection explicit.
The fix: send conditional before the payment clears. Send unconditional after. Conditional vs unconditional lien waivers covers the four-type framework in detail.
Reason 2: You sent the wrong state's form
Twelve U.S. states (California, Texas, Florida, Nevada, Arizona, Georgia, Mississippi, Missouri, Wyoming, Utah, Massachusetts, Michigan) require specific statutory language. A generic waiver in those states is void on its face.
If you sent a Texas sub a California-style waiver, they may sign it anyway. But the savvy ones won't. They know that an unenforceable waiver is exactly the same as no waiver, so signing it costs them effort and gives you nothing legally binding.
The fix: use the right statutory form for the project's state. The California guide and Texas guide cover the two biggest markets in detail. For the rest, pick the state in the form selector and the right language fills itself.
Reason 3: Your signing link doesn't work on a phone
Subs sign waivers on the job site. The job site has a phone, not a desktop.
If your e-signature platform asks subs to:
- Create an account before signing
- Enter a code from a separate email
- Download a PDF, sign in Adobe, and re-upload it
- Wait for a desktop because the form doesn't render on mobile
…then your signing rate drops by 60–80%, depending on how many of those steps your platform requires. Each extra step is a 10–20% drop-off in our category, broadly consistent with what e-signature platforms publish about consumer signing flows.
The fix: use a signing experience that takes the sub from the email to a signed PDF in under two minutes, on a phone, with no account required. How to send a lien waiver in two minutes walks through what that looks like end-to-end.
Reason 4: The amount or the through-date doesn't match the pay app
Subs read the amount and the through-date first. If those numbers don't match the pay app they submitted, they pause.
A waiver that says "$45,200 through April 30" when the sub's pay app said "$45,250 through April 30" is going to sit in their inbox until someone explains the $50 difference. Multiply that across 40 waivers a month and you've got a permanent backlog.
The fix: pull the amount and through-date directly from the pay app. Don't retype them. Most lien waiver delays we see are reconciliation delays, not signature delays.
Reason 5: You don't have a reminder cadence
Subs are busy. They forget. They don't sit by their inbox waiting for waiver requests.
If you don't have a structured reminder cadence, your average waiver sits unsigned for 8 to 14 days. If you do, it sits for 2 to 4.
The fix: automatic reminders at day 2 and day 4. After day 7, the token expires; send a fresh request instead of re-sending the old link. The sub who clicks a 30-day-old email and sees "expired" is the sub who never replies.
What good looks like
When the five reasons are fixed, the typical sequence looks like this:
- You cut a pay app on Monday morning.
- The system sends a conditional progress waiver to the sub.
- The sub gets a one-line email with your company name and a single button.
- The sub clicks, reviews the waiver on their phone, signs, and submits.
- The signed PDF lands in your dashboard before lunch.
- You release the payment.
The whole loop takes the GC about two minutes and the sub about two minutes. The compliance person on your end never has to chase.
What bad looks like
When one of the five reasons is broken, the loop looks like this:
- You cut a pay app on Monday morning.
- Your AP person emails the sub a generic PDF template.
- The sub opens the email on Wednesday, can't sign on their phone, decides to deal with it later.
- Your AP person emails again on Friday. Still nothing.
- AP calls on Monday. Sub says they'll get to it.
- The sub signs on Wednesday. Scans on Friday.
- AP files the PDF in a folder no one can find later.
That loop took 11 calendar days, four touch points from AP, and produces a PDF that's hard to find in an audit.
The diagnostic
If your subs aren't signing, walk through the five reasons in order:
- Did you send unconditional before the payment cleared? Switch to conditional.
- Did you send the right state's statutory form? Pick the state in the form selector.
- Does the signing link work on a phone? Test it yourself before sending.
- Does the amount and through-date match the pay app? Pull them straight, don't retype.
- Do you have a reminder cadence? Set it once, let it run.
Most GCs we work with have one of these broken. Fix the broken one and your signing rate jumps in the next pay period.
FAQ
How long should I wait before sending a reminder?
Two business days for the first reminder, four for the second. After seven days the token expires.
Should I withhold payment until the waiver is signed?
For conditional, yes (the conditional form releases lien rights only when the payment clears, so it's safe to require it before cutting the check). For unconditional, no.
What's the best email language?
Lead with the GC's company name, the project, and the dollar amount. Two sentences. One button.
Can I require waivers in the sub contract?
In most states, yes. In Texas, no, because §53.286 voids contractual waivers of future lien rights.
How do I handle a sub who refuses outright?
Confirm you sent the right form for the right phase. If you sent unconditional before payment, send conditional. If they still refuse, treat it as a contract dispute and document the refusal in writing.
Send your next waiver in two minutes.
Pick the project, pick the sub, hit send. The signed PDF lands in your dashboard.
Get startedSee pricing