# How $50M GCs Get Lien Waivers in 48 Hours, Not Two Weeks Canonical: https://granular.to/blog/get-lien-waivers-48-hours-not-two-weeks Published: 2026-06-16 Updated: 2026-06-16 Author: Trey Category: Playbook Tags: general-contracting, automation, operations > A step-by-step workflow for mid-market general contractors to compress lien waiver chase from 6-10 business days to 48 hours per pay app, covering state-specific template management, payment gates, and automated reminder cadences. > **TL;DR.** Mid-market GCs lose 6 to 10 business days every pay app chasing lien waivers. The cost is not just admin time. Construction DSO sits at a median of 83 days, and missing waivers are the single most cited reason draws stall at the owner or lender. The fix is not a better email template. It is three things: pre-loaded state-specific templates at sub onboarding, automated reminder cadence at 24/48/72 hours, and a hard payment gate at the AP level so no check leaves until the waiver is in. You ran your last pay app on the 5th. By the 12th, your project accountant is on her third round of follow-up emails to the same six subs. By the 15th, two of those subs sent back the wrong waiver type. By the 17th, the draw is late and your lender is asking questions. This is the lien waiver chase, and at a $50M GC it eats one full week of every pay app cycle. It is the most expensive paperwork problem in mid-market construction, and almost nobody talks about it because it does not show up on the P&L as a line item. It shows up as cash that has not arrived yet. ## Why this stalls every month at $50M GCs A $20M commercial job running through monthly pay apps generates 60 to 200+ waiver documents per cycle. Fifteen to thirty first-tier subs, two to four sub-tier vendors and suppliers per sub, and both conditional and unconditional waivers per party per pay period. At $50M in revenue with 8 to 15 active projects, your project accountants are tracking several hundred waivers per month. Manually. In a spreadsheet that lives on someone's desktop, with email follow-ups that get buried by Friday lunch. The chase typically runs **6 to 10 business days** per cycle. That is one full week of every month where a meaningful chunk of your monthly billing is sitting at "submitted, awaiting waiver clearance" status with your lender or owner. The downstream math is brutal. According to the [DocJoist 2024 Construction Payment Statistics Report](https://www.docjoist.com/reports/construction-payment-statistics), median construction DSO sits at **83 days**, among the highest of any industry. Eighty-two percent of contractors wait more than 30 days for payment. The [Rabbet 2024 Construction Payments Report](https://www.docjoist.com/reports/construction-payment-statistics) attributes a meaningful slice of that to administrative friction, with waiver management cited as a primary driver. For a mid-market GC running $50M, every 19 days of DSO reduction is roughly $2.6M in freed working capital. The lien waiver workflow is the single most concentrated lever you have to move that number. ![Mid-market commercial GC project accountant working through a stack of subcontractor lien waiver packets at a multi-monitor workstation with a pay application aging dashboard](/images/blog/get-lien-waivers-48-hours-not-two-weeks-pay-app-volume.jpg) ## The four waiver types and where they trip you up You know there are four types. Your project accountants know there are four types. Your subs sort of know. The trouble is the four types map to the billing cycle in a way that gets muddled fast under volume. - **Conditional progress waiver.** Submitted with the pay app. Effective only when payment clears. The "I promise to release my lien rights when you pay" version. - **Unconditional progress waiver.** Submitted after payment clears. The "you paid, my lien rights through this date are released" version. - **Conditional final waiver.** Submitted with the last pay app. Effective on final payment including retainage. - **Unconditional final waiver.** Executed after full payment. Closes out all lien rights entirely on the project. The Construction Financial Management Association (CFMA) maintains a [detailed primer on lien waiver essentials](https://cfma.org/articles/lien-waiver-essentials-types-timing-and-best-practices-for-subcontractors) that is worth handing to every new project accountant. Common waiver mistakes (wrong type submitted at the wrong stage, dollar amounts mismatched to the pay app, through-dates that do not match) are catalogued in CFMA's [companion piece on common mistakes](https://cfma.org/articles/common-lien-waiver-mistakes-and-how-subcontractors-can-avoid-them). ### The state-form trap The bigger problem is statutory forms. Twelve states require statutory language for lien waivers, and any deviation from the exact statutory language can void the waiver entirely. Arizona, California, Florida, Georgia, Massachusetts, Michigan, Mississippi, Missouri, Nevada, Texas, Utah, and Wyoming. If you are running jobs in TX, CA, and FL simultaneously, you need at least 12 statutory-compliant template variants just to cover the four waiver types per state. Nevada and Wyoming add notarization requirements on top. What this means in practice: the "one template fits all" approach your project accountant has been quietly maintaining is legally defective in three of your biggest markets. When a sub returns the wrong form, that is not the sub being lazy. That is your template library failing. ## The 48-hour workflow The most documented compression we have seen comes from a residential GC profiled by CountBricks: a draw that previously took 6 to 7 days got down to 48 hours. The workflow logic is identical for commercial mid-market. ![Mid-market construction office with an AP coordinator and project accountant reviewing an ERP payment-gate dashboard showing subcontractor lien waiver status and automated reminder cadence](/images/blog/get-lien-waivers-48-hours-not-two-weeks-payment-gate-workflow.jpg) Three changes did it. ### 1. Pre-load state-specific templates at sub onboarding The single biggest unlock. Stop picking the template at billing time. Pick it at sub onboarding time. When a sub gets onboarded to a project, your project accountant assigns the correct state-specific template variant (conditional progress, unconditional progress, conditional final, unconditional final) once. Forever after, when that sub bills on that job, the system serves them the right form. They cannot pick the wrong one. This kills 60% of the chase before it starts. The waivers that come back are the right type, with the right statutory language, on the first round. ### 2. Automate reminder cadence at 24, 48, 72 hours Your project accountant chasing waivers by email is the wrong unit of work. She is checking who has not returned a form, looking up email addresses, drafting a follow-up, attaching the template again, hitting send. Three days a week. The reminder cadence should be automated. At 24 hours after pay app submission, an unsigned waiver triggers a reminder email to the sub. At 48 hours, a second reminder plus a copy to the sub's AR contact. At 72 hours, an escalation to the sub's executive contact and a flag in your project accountant's queue. That is a workflow rule, not a person. The person reviews the flagged exceptions, not the routine reminders. ### 3. Gate payment release at the AP system level This is the discipline most $50M GCs do not have. The waiver is required to release payment, but the gate is enforced manually. Someone in AP confirms before cutting the check. In a 48-hour workflow, that gate moves out of the AP person's head and into the ERP. No waiver of the correct type with matching dollar amount and through-date, no check. Period. The system blocks it. This sounds harsh until you realize the alternative is a check going out to a sub who has not returned an unconditional waiver, and you are now holding lien exposure on a paid invoice. That is the failure mode every GC's lawyer wants to prevent and almost nobody actually prevents. ## The tools landscape Most $50M GCs are using one of five things to manage waivers right now. Here is the honest take on each. | Tool | What it does | Pain point | |------|-------------|------------| | **Levelset** (Procore) | State-specific waiver generation, digital signatures, statutory compliance tracking | Tightly coupled to Procore. Limited payment-hold enforcement if you run Sage 100/300, Foundation, or Viewpoint. | | **GCPay** (Autodesk) | End-to-end sub pay apps, waivers, compliance docs, ACH | Implementation curve is steep. Overkill for GCs under $30M. | | **Oracle Textura** | Pay app and waiver exchange for large projects, integrates with Vista, Yardi, Sage 300 | Designed for enterprise. Pricing is opaque. Subs often charged to participate. | | **Procore Pay** | Embedded payment and waiver release inside Procore PM | Fragmented across Procore modules. Still relies on the Levelset add-on for actual waiver lifecycle. | | **hh2 Document Flow** | AP automation and document routing for Sage 100/300, Vista, Foundation | Not a dedicated waiver tool. Document storage only, no waiver lifecycle management. | | **Manual email + PDF** | Free. Universal. | Breaks at five active jobs. No audit trail, wrong templates picked, amount mismatches add days to DSO. | The pattern: the best-in-class tools are either married to a specific PM platform (Procore plus Levelset) or built for enterprise (Textura, GCPay). The $50M GC running Sage 100 Contractor with eight active projects ends up cobbling together hh2 plus manual email plus a shared spreadsheet. That is where the chase lives. [GCPay's recent overview of waiver management software](https://ww3.gcpay.com/blog/best-lien-waiver-software/) walks through the tradeoffs at more length, and [Levelset's own playbook on tracking waivers](https://www.levelset.com/blog/tracking-lien-waivers/) is a fair primer even if you do not adopt their product. ## What to do this month Three actions, in order. None of them require buying software in the next 30 days. **Audit your last pay app cycle.** How many waivers were required? How many came back on the first round? How many days from pay app submission to all waivers cleared? Get the numbers. Most $50M GCs have never measured this. **Inventory your statutory templates.** For every state you have an active project in, do you have a current statutory-compliant template for each of the four waiver types? If you are running jobs in TX, CA, and FL, you should have 12 templates minimum. If you have one Word doc that says "Lien Waiver," you have a problem. **Get the payment gate in writing.** Talk to your CFO. The rule should be: no check leaves AP without the correct waiver type with matching dollar amount on file. Get someone in AP to enforce it manually for the next two pay app cycles before you automate it. You will find the workflow gaps fast. These three actions get you 60% of the way to the 48-hour cycle without buying anything. The remaining 40% is automating reminders and gating at the ERP level, which is where a tool conversation makes sense. ## FAQ **How many statutory-form states are there?** Twelve as of 2026: Arizona, California, Florida, Georgia, Massachusetts, Michigan, Mississippi, Missouri, Nevada, Texas, Utah, and Wyoming. Nevada and Wyoming add notarization on top of statutory form requirements. **Can we use one waiver template across all jobs?** Not if you have active jobs in any of the 12 statutory states. Any deviation from the statutory language can void the waiver entirely, which means your "one template" is legally unenforceable in those states. The downstream risk is that you pay a sub, the sub goes under, and a sub-sub or supplier files a lien against the property anyway because your waiver was defective. **What is realistic compression from 6-10 days to 48 hours?** Most $50M GCs we have seen can get to 3-4 days within one quarter without buying software, just by enforcing the payment gate and pre-loading templates at sub onboarding. Getting to 48 hours typically requires automating the reminder cadence, which means a dedicated tool or a custom workflow on top of your ERP. **Do we need to switch ERPs?** Almost never. The bottleneck is not your ERP, it is the workflow around your ERP. Most $50M GCs running Sage 100 Contractor, Sage 300 CRE, Viewpoint Vista, or Foundation already have the AP gating capability. It just is not turned on or enforced. **What about subs who refuse to use a portal?** You will have 10 to 20% of your subs who will not adopt any platform you put in front of them. That is fine. The chase compression still works for the 80 to 90% who will, and your project accountants get to focus their manual effort on the holdouts instead of everyone. ## The bottom line Lien waivers are the highest-leverage paperwork problem in mid-market construction. The chase eats one full week of every pay app cycle, drives your DSO past 80 days, and lives entirely on your project accountants' personal email and one shared spreadsheet. The 48-hour workflow is not magic. It is three disciplined changes: pre-load templates at sub onboarding, automate reminders, gate payment at AP. If this sounds like your Tuesday and you want help wiring the workflow into your ERP without ripping anything out, [book 30 minutes with us](/). We have done this work at GCs running Sage 100, Sage 300 CRE, and Viewpoint Vista, and we ship in four weeks. Fixed price. --- ## Keep Reading - **[How $50M GCs Close Out Construction Jobs in 30 Days](/blog/close-construction-jobs-30-days-not-90)**. The other place mid-market GCs lose cash velocity. Project closeout typically runs 60-90 days. Here is the workflow that cuts it to 30. - **[Where $50M GCs Lose $80K a Year on Equipment Rentals](/blog/where-gcs-lose-money-equipment-rentals)**. Another operational gap where money sits trapped because nobody is measuring the cycle. Same pattern, different paperwork.