Lien waiver tracking means knowing, for every payment on every job, which waiver you asked for, which one you received, from whom, for which period and amount, and whether the money has actually cleared. The table below is a tracking template organized by waiver type: conditional or unconditional, progress or final. Copy it into a spreadsheet.
Lien law is state by state, so we opened the statutes for California, Texas and Florida and report only what those pages say. Then we describe how a waiver log can be automated with n8n or Make and Claude, with a person approving every exception, and when software you buy is the better answer. This is general information, not legal advice: confirm every form and deadline with your attorney. To discuss a build, describe the job and your budget range in the contact form.
Lien waiver tracking template by waiver type
Two choices define every waiver: whether it is conditional (effective only when payment is received) or unconditional (effective on signing, usually stating that payment has been received), and whether it covers a progress payment or the final payment. That gives four waiver types. A tracker needs one row per waiver per pay period per party.
| Waiver type | When it is typically used | What to track before you pay | Main risk if mishandled |
|---|---|---|---|
| Conditional, progress | Sent with the pay application, before the check is issued | Received before payment released, signed, correct through date, amount, project, party name | Effective only when the stated payment clears, so file the check or payment reference against it |
| Unconditional, progress | Collected after the payment has been made and received | Evidence the payment cleared, signed after receipt, same through date and amount | Signing before the money arrives gives up lien rights without payment (the signer's problem, but also a dispute source for you) |
| Conditional, final | With the final pay application, for work through the final date | Final amount, retention included or excluded as the form says, all lower-tier parties covered | Missing lower-tier waivers leave claims open against the job |
| Unconditional, final | After final payment clears | Cleared payment, signed and dated after receipt, final through date | Closing out a job without it leaves the file incomplete |
Beyond the four types, these are the columns we would put in the sheet. Every column answers a question someone will ask when a dispute or a closeout happens:
| Column | What to enter |
|---|---|
| Project and contract number | Your reference and the owner's, if different |
| Party | Subcontractor, supplier or lower-tier name exactly as on the subcontract |
| Tier | Prime sub, sub-sub, supplier |
| Pay application number and period | Which application this waiver supports |
| Waiver type | One of the four above, from a drop-down |
| Through date | The date the waiver says it covers work through |
| Amount on the waiver | Number as written; compare to the pay application |
| Form used | The statutory form for that state, or an exception note if something else was accepted |
| Date requested, date received, date signed | Three separate dates. Request-to-receipt time shows who is slow |
| Payment reference and cleared date | Check or ACH reference and the date funds cleared |
| Status | Requested, Received, Wrong form, Amount mismatch, Held, Cleared, Exception approved |
| Release rule | A line you can test: "payment is not released until a valid conditional waiver for this period is on file" |
The last row is the control. A tracker that only records what arrived does not stop a payment. A rule that ties payment release to a status does. The mistake that costs money, covered below, is what happens when the rule exists on paper but not in the process.
What three state statutes say (California, Texas, Florida)
We opened the statute pages below on 2026-11-11. For California and Texas we could not reach the official legislature sites from our tools, so we read the public.law mirrors of the code text; the Florida page is on the Florida Senate site. The mirrors show verification dates of 9 Nov 2026 (California) and 26 May 2025 (Texas); the Florida page is the official 2025 statute. Law changes, so treat this as a map for questions to put to your attorney, not as the current text.
| State | What the page says | What to put in the tracker |
|---|---|---|
| California (Civil Code 8132, 8122) | A conditional waiver and release on progress payment, where the claimant is required to sign to receive or induce payment, is "null, void, and unenforceable unless it is in substantially the following form". The form takes effect only when the claimant receives payment on the identified check, and sets out items it excludes, such as retentions and unpaid extras (Civil Code 8132). A contract term that waives or impairs a claimant's rights is void unless the claimant signs and delivers a waiver and release under that article (Civil Code 8122) | A "form used" check: statutory form, or flagged. A through date, a payment identification, and the excluded items on every conditional progress waiver |
| Texas (Property Code 53.284, 53.283) | A waiver and release is "unenforceable unless it substantially complies with the applicable form". There are four forms: conditional and unconditional, each for progress and final payment. Unconditional forms must open with a bold notice stating the document waives rights unconditionally and that the signer has been paid (Property Code 53.284). A person may not require an unconditional waiver unless the claimant has already received payment in that amount in good and sufficient funds (Property Code 53.283) | A hard rule that unconditional waivers are requested only after payment clears, and a check that the right one of four forms was used |
| Florida (Statutes 713.20) | A lien right cannot be waived in advance of work: such a waiver is unenforceable. There are statutory forms for progress and final payment, and a person may not require a lienor to furnish a waiver in a different form. The page's subsection (8) says a waiver not substantially similar to the statutory forms is enforceable under its own terms (Florida Statutes 713.20) | Reject any waiver that covers work not yet done, and record the form used |
Notice that the states differ on the same question. The California page (conditional progress waiver) and the Texas page say a non-conforming form is unenforceable; the Florida page says a non-conforming waiver is enforceable under its own terms. A tracker that applies one state's assumption to every job will get some wrong. That is the case for putting the job's state on every row and having a person who knows the law set the form rules for each state you work in.
We did not open anything for other states, and we did not open California sections 8134, 8136 and 8138, which cover the other statutory forms. We are not saying what those say. Do not use this page to decide your forms. Ask your attorney for the forms and rules for each state where you work.
The mistake that costs money: paying against the wrong waiver
The costly mistake is paying against a waiver that does not do what everyone assumed. Four versions of it recur, and each is traceable to the statute differences above and to how a sheet is used:
- An unconditional waiver collected before the money has arrived. Texas 53.283 as we read it prohibits requiring that before the claimant has received payment in that amount in good and sufficient funds. Even where it is not required, it is a risk to the party signing and a dispute magnet for you.
- The wrong form for the state or the wrong type. Where the statute says a non-conforming waiver is unenforceable, you may find you are relying on a document that does not protect the owner or contractor who asked for it. Where the statute says it is enforceable on its own terms, you still need to know what those terms say.
- The through date or amount does not match the pay application. The form can be signed and filed and still not cover what you paid for. Nobody caught it because the sheet recorded "received", not "matches".
- A waiver before work is done. Florida's page says an advance waiver is unenforceable, so a file full of them proves less than it appears to.
We will not attach a dollar figure to this. We did not find a statistic we could open and verify, and the exposure depends on the job and the state. What we can say is the process failure behind all four: the sheet records that a document arrived, and nothing compares it to the pay application, the form rule and the payment status before money moves.
How to automate lien waiver tracking, step by step
The automation target is narrow: stop payment from being released until a valid waiver is matched to the pay application, and chase the missing ones. This is a design we would propose. It is not a product on a shelf, and we have no construction client result to cite. Tools: n8n or Make for the workflow, Claude to read documents, or custom code where your accounting system or portal needs it.
| Step | What runs | Who decides |
|---|---|---|
| 1. Trigger on the pay application | When a pay application is entered or approved, the workflow creates the required waiver rows for each party and period, with the state's form rule attached | Nobody, it follows your sheet or accounting export |
| 2. Request the right waiver | An email or portal message goes to each party with the correct form for the job's state and waiver type, and the through date and amount filled in | A person approves the template for each state once |
| 3. Intake | Signed PDFs arrive by email or upload and are filed against the project, party and period | Nobody |
| 4. Read the document | Claude extracts signer, party, project, through date, amount, form title, conditional or unconditional, signature present. Its documentation says PDFs are read page by page as images and its text is also extracted and provided alongside and that encrypted PDFs are not accepted (Claude PDF support documentation) | Nobody, but results are checked next |
| 5. Compare by rules | Plain rules compare the extracted fields to the pay application and the state form rule: amount equals, through date equals, type matches the request, signature present, unconditional only after cleared payment | Rules decide pass or exception |
| 6. Approve exceptions | The accounts or project person sees the PDF beside the extracted fields and approves, rejects or sends it back. A workflow can pause until a form is submitted or a webhook is called (n8n Wait node documentation) | A person, always |
| 7. Release gate | The payment run list shows only items with a matched waiver, and held items with the reason. Money release stays a person's action in your accounting system | A person |
| 8. Closeout | On final payment the workflow requests the unconditional waivers, compares them, and produces a closeout list of what is outstanding by party | A person signs off |
Two design rules keep this safe. The model reads; rules judge. And a blank or doubtful field is never a pass: it goes to a person. We would also keep the form rules per state in a table that your attorney reviews, so that a change in a state's law is a table edit and not a rebuild.
What the automation will not do
What this will not do:
- Give legal advice. It cannot tell you which form is valid for your project, whether a waiver is enforceable, or what a deadline is. Your attorney provides that.
- Replace the form library. Statutory forms and their notices must come from your attorney or the statute. We would load them as templates, not write them.
- Authenticate signatures. It can see that a signature appears. It cannot confirm who signed or that the signer had authority.
- Verify that money cleared. That fact comes from your bank or accounting system, which the workflow can read, but your team confirms it.
- Cover every state automatically. Each state you work in needs its own rule row, built and reviewed.
When to buy software or use your platform instead
Be honest about the alternatives before building:
| Your situation | Better choice | Why |
|---|---|---|
| You already run a project or payments platform with lien waiver handling | Use it. Check what your plan includes | We did not open any platform's feature page for this article, so we make no claim about what any product does. Confirm with the vendor |
| You collect waivers through a portal your subs already use | A waiver or compliance platform | A portal changes the sub's behavior; a workflow built on email does not |
| A handful of jobs and a few parties | The spreadsheet above | Simple beats a build |
| Many states, many forms, high volume | A platform with maintained state forms, plus counsel | Maintained forms are a product feature, not a workflow |
| Waivers are one part of a bigger paperwork chain in email and spreadsheets | A custom workflow | The value is joining waivers, pay applications, certificates and payments |
Procore users sometimes search for "Procore lien waiver tracking". If you run Procore, ask Procore or your account team what your plan covers before commissioning anything. Our construction automation overview explains where its native agents make more sense than a custom workflow and where they do not reach.
Next step
The first call covers your states, how you collect waivers today, where pay applications are kept, who releases payments and how many parties you handle per month. We tell you plainly if a template or a platform is enough.
Describe the job and your budget range in the contact form. We quote to scope in writing after a short call, and meetings are online. Related jobs: the certificate of insurance tracking and subcontractor compliance tracker pages, and the certified payroll guide. Larger contractors with job costing and billing in one system can also look at construction software.
Sources
- california.public.law/codes/ca_civ_code_section_8132
- california.public.law/codes/ca_civ_code_section_8122
- texas.public.law/statutes/tex._prop._code_section_53.284
- texas.public.law/statutes/tex._prop._code_section_53.283
- www.flsenate.gov/Laws/Statutes/2025/713.20
- platform.claude.com/docs/en/build-with-claude/pdf-support
- docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.wait/