Stop losing retention to missed lien waivers
By The SubTools team
Retention can be five to ten percent of a job, held for months after you finish. For a busy sub running dozens of jobs at once, that is a large, quiet pile of money sitting on someone else's books. Ask most subcontractors where their profit went last year and a surprising amount of it is still in retention that never got released — not because the work was bad, but because a piece of paper was missing.
The single most common reason retention slips is a missing or late lien waiver. It is the most avoidable one, too.
The waiver problem in plain terms
There are two kinds of lien waiver, and mixing them up is where subs get burned. A conditional waiver says "I waive my lien rights for this amount once I actually get paid." It's safe to send with a pay application. An unconditional waiver says "I've been paid, and I waive my rights" — it should only go out after the money lands. Sign an unconditional waiver before you're paid and you've given up leverage on money you don't have yet.
Now multiply that by every job, every draw, and every tier above you. On a single project you might owe a conditional waiver with each monthly pay app and an unconditional one each time a payment clears — and the GC often wants waivers from your lower-tier suppliers too before they'll release anything to you.
- Waivers are tied to a pay app, but usually tracked in a separate spreadsheet.
- The correct waiver type depends on whether you've been paid yet — a moving target.
- The GC won't remind you to send them. They'll just quietly hold your money.
- Lower-tier waivers you owe can block your own payment upstream.
Why the spreadsheet always loses
A waiver log in a spreadsheet is a snapshot that's wrong the moment a payment posts. Someone has to remember to open it, find the right row, generate the right document, send it to the right contact, and mark it done. On a busy month with a dozen active jobs, that is dozens of small manual steps — and the one that gets skipped is invariably the one holding up a retention check.
“We didn't have a lien-waiver problem. We had a 'nobody had time to send the lien waiver' problem.”
Make the waiver ride with the money
The fix isn't discipline — it's tying the document to the event that requires it. In SubTools, every pay application carries its conditional waiver. When you send the pay app, the conditional waiver goes with it, pre-filled with the right amounts and job details. There's no separate step to forget.
When a payment posts, the agent drafts the matching unconditional waiver, flags it for a quick review, and reminds you to send it. The document is generated from the same numbers you invoiced, so there's nothing to re-key and nothing to reconcile later.
- Conditional waiver auto-attached to every pay app you send.
- Unconditional waiver drafted the moment payment clears.
- A running view of every waiver owed, by job and by builder.
- Lower-tier waivers tracked alongside yours so nothing blocks a release.
What changes when it's automatic
No job reaches closeout with an open waiver. Retention gets released on schedule because the paperwork was never the holdup. And when a GC's accounting team emails asking for "the final unconditional on job 8905," you already sent it — with the backup attached.
Retention is money you already earned. The waiver is the only thing standing between you and it. Stop letting a document you could automate keep your profit on someone else's balance sheet.