How to send a lien waiver to a subcontractor in two minutes

You don't need an account from your subcontractor. You don't need to email them a PDF. You don't need to chase a wet signature for five days.

Send a link. Watch them sign. Release the payment.

Here's the loop, step by step.

Step 1: Pick the project

Open your dashboard. Pick the project the payment belongs to. Every waiver is tied to a project so the audit trail stays clean later.

If the project doesn't exist yet, add it. Project name, address, owner. Done.

Step 2: Pick the subcontractor

Pick the sub from your list. If they're new, add them: company name, contact name, email. That's all you need for them to sign.

You don't need their EIN, their license number, or their bank info to send a waiver. Just an email address.

Step 3: Pick the waiver type, amount, and date

Four types cover almost every situation:

• Conditional progress payment. You're paying for work done so far on the current pay period. The waiver releases lien rights through that date, but only once the payment actually clears.
• Unconditional progress payment. Same scope, but the release is final the moment the sub signs. Use this only when the payment has already cleared.
• Conditional final payment. Last payment of the job. Releases lien rights for everything, conditional on the payment clearing.
• Unconditional final payment. Last payment, fully released. Use only after the money has moved.

Pick the type, type the amount, type the through-date. The form fills itself with the right statutory language for the state.

Step 4: Hit send

The sub gets an email. The email leads with your company name and a single button: review and sign.

They click. They land on a clean signing page. They review the waiver, sign on phone or laptop, and submit. The signed PDF lands in your dashboard with a timestamp.

That's it. Four steps, two minutes from your end.

What the subcontractor sees

This part matters more than most GCs realize. The signing experience is what your subs associate with you, not with us.

When your sub opens the email, the first line says "Acme Construction sent you a lien waiver." Not "LienDone sent you a lien waiver." The signing page shows your company name above the form. The PDF they download carries your job number and address.

To them, the whole thing looks like Acme Construction runs a tight, modern operation. They sign in two minutes and go back to work. You look like the kind of GC people want to work with.

What you see in your dashboard

The waiver status moves through three states:

1. PENDING. Sent, not yet signed.
2. SIGNED. Done. PDF available.
3. OVERDUE. Seven days passed without a signature. Token voided. Send a fresh one.

You can filter by project, by sub, by status. You can pull a CSV of every signed waiver for an audit.

Why two minutes (not two hours)

Most lien waiver workflows still look like this:

1. GC writes an email.
2. GC attaches a PDF template.
3. Sub prints, signs, scans.
4. Sub emails it back.
5. GC saves the PDF to a folder no one can find later.

That loop takes anywhere from a single day to two weeks, depending on how busy the sub is. The sub forgets. The PDF sits in a Gmail thread. The compliance person on the GC side has to remember to chase.

A signed link removes every step that involves one human waiting on another. The sub gets one email, signs once, and the PDF lands in the right folder automatically.

If you want a deeper read on the four waiver types, conditional vs unconditional waivers covers when each one fits.

Common mistakes to avoid

Three patterns we see GCs trip on:

• Sending unconditional before the money clears. If the sub signs unconditional and the check bounces, you have a problem. Send conditional first, unconditional after.
• Picking the wrong state form. California's statutory language is not Texas's. Texas's is not Florida's. Pick the state in the form picker, don't paste a generic template. The California requirements guide walks through the four statutory forms.
• Letting the sub sign on a stale link. Tokens expire after seven days. If a sub clicks a 30-day-old email, they see "this link has expired." Send a fresh one instead of arguing about the old one.

Try it on your next pay period

Pick one project, one sub, one waiver. Send it. Time it.

If your subs are signing in under two minutes, you've cut your compliance overhead from days to seconds. If they're not signing at all, why subcontractors don't sign lien waivers is the next read.

FAQ

Does the subcontractor need an account?

No. They click a link, review the waiver, sign on phone or laptop, and submit. The PDF lands in your dashboard the moment they click submit.

Which forms can I send?

Conditional progress, unconditional progress, conditional final, and unconditional final. California, Texas, Florida, and the other 47 state forms are built in.

How long is the signing link valid?

Seven days. After that, the token is voided. Send a fresh one and the sub gets a new email.

What if the sub signs the wrong form?

Void the request and send a new one. The original PDF stays in your dashboard for the audit trail.