It's Thursday afternoon. Your bid is due at 8 a.m. Friday. You've got three subcontractors who submitted pay applications with line items that don't match their scope, one mechanical sub threatening to walk because he says he's owed for stored materials you never approved, and your project manager is asking whether you've collected lien waivers from last month's draw. You haven't.

This is what a broken subcontractor payment schedule construction process actually looks like — not a spreadsheet problem, but a project on the edge. Payment schedules that are vague, disconnected from the subcontract, or built on unclear scope don't just slow cash flow. They create the conditions for liens, defaults, and relationships that don't survive the next project.

This guide is built for GCs who want to fix that — not with theory, but with structure you can use on your next contract.

What a Subcontractor Payment Schedule Actually Controls (It's More Than Dates)

A payment schedule isn't an administrative form — it's the operational backbone of every subcontract you sign.

Procore's coverage of payment schedules does a reasonable job explaining why they matter in general terms. But it stops short of showing GCs how the schedule functions as a control mechanism across cash flow sequencing, lien exposure, default triggers, and negotiating leverage. Those four things are what you're actually managing every time a pay application hits your desk.

When a sub submits a draw, your payment schedule should tell you exactly what milestone was supposed to be complete, what retention is being held, whether a conditional lien waiver is attached, and what happens if the work isn't in place. Without that structure, every pay application becomes a negotiation instead of a verification.

The Difference Between a Payment Clause and a Payment Schedule

A payment clause in a subcontractor contract template construction document tells you *when* payment is due — typically within a set number of days after the GC receives payment from the owner. That's a timing mechanism. It's necessary, but it's not a schedule.

A payment schedule maps every milestone, the dollar amount tied to it, the retention percentage being withheld, and the condition precedents that must be satisfied before payment releases — across the full project lifecycle. It's the difference between a sentence and a spreadsheet. One tells you the rule; the other runs the project.

Why GCs and Subs Read the Same Schedule Differently

Every payment schedule has adversarial tension baked into it, and pretending otherwise is how disputes start.

The GC is using the schedule to protect margin, control cash flow, and ensure work is in place before money moves. The sub is using it to cover labor costs, float materials, and stay solvent between draws. These are not the same goals. A mechanical sub with $80,000 in equipment on order needs that stored materials draw approved. You need proof the equipment is on-site and properly stored before you cut the check.

Understanding both perspectives doesn't mean you give ground — it means you write a schedule specific enough that there's no room for either side to reinterpret it.

The Four Payment Structures GCs Actually Use in the Field

The Reddit threads on contractor payment schedules are full of homeowner horror stories, but the structures GCs use on commercial and multi-family work are more specific — and the risks are different depending on which model you choose.

There are four dominant subcontractor payment schedule construction models in active use: milestone-based, percentage-of-completion, stored materials draws, and time-and-material billing cycles. Each fits different trade types and project conditions. Using the wrong one for a given scope is how you end up overpaying a sub who's three weeks behind schedule.

Milestone-Based Schedules: Best for Defined-Scope Trades

Milestone payments work best for trades with clear, inspectable deliverables — electrical, plumbing, HVAC rough-in, framing. You tie each payment to a discrete event: rough-in complete, inspection passed, final trim installed, punch list cleared. When you build these milestones directly into your subcontractor scope of work template, you eliminate the most common source of scope creep disputes — the sub who claims a line item was "implied" in the original contract.

The risk is milestone definition. If "rough-in complete" isn't defined in writing — does that include pressure testing? does it require inspection sign-off? — you'll have the argument anyway. Be specific. One sentence of clarity in the contract saves three weeks of dispute.

Percentage-of-Completion: The GC's Default — and Its Blind Spots

Percentage-of-completion is the most common billing structure on commercial projects, and it's also the one most frequently gamed.

The model works by tying each draw to a verified percentage of the subcontract value completed. On a $400,000 drywall subcontract, a 25% draw means $100,000 of work is in place. The problem is that "in place" is only as reliable as your verification process. Subs who front-load their schedule of values — assigning disproportionate value to early-stage line items like mobilization and material delivery — can collect 40% of the contract value while completing 20% of the work.

According to the Construction Financial Management Association (CFMA), overbilling is one of the top three causes of GC cash flow shortfalls on projects over $5M. Review every schedule of values before you approve it, not after the first draw is submitted. Understanding construction markup vs margin also helps you spot when a sub's pricing structure is designed to front-load cash rather than reflect actual work progression.

Stored Materials Draws and T&M Billing Cycles

Stored materials draws exist because long-lead items — structural steel, MEP equipment, custom glazing — require subs to commit capital before installation. A stored materials draw lets the sub get paid for materials on-site or in bonded storage before they're installed. The documentation requirement is non-negotiable: you need a bill of sale, proof of insurance, and confirmation the materials are properly stored and identified as project-specific.

T&M billing cycles apply to open-scope work where the final quantity isn't known upfront — demolition, remediation, certain sitework conditions. The risk here is invoice inflation. Require daily field reports, signed by your superintendent, that match the labor hours and equipment hours on every T&M invoice. Without that paper trail, you're approving numbers you can't verify.

Building Your Subcontractor Agreement Template Around the Payment Schedule

The payment schedule only works if it's structurally embedded in the subcontract — not attached as an exhibit that nobody reads after signing.

A GC we spoke with on a $9M medical office build in Nashville put it plainly: *"We had a solid payment schedule, but it was in Exhibit C and the subcontract body didn't reference it. When we had a dispute with our framing sub, his attorney argued the exhibit wasn't binding because the main contract language contradicted it. We settled for more than we should have."* That's a drafting problem, not a project problem — and it's more common than most GCs admit.

Your subcontractor agreement template needs to treat the payment schedule as a referenced, integrated document — not an afterthought.

The Five Clauses Every Subcontract Must Link to the Payment Schedule

Schedule of values approval must require the sub to submit a schedule of values within a defined window (typically 10 days of contract execution) and make GC approval a condition of the first draw. Without this, you're approving a pay app against a schedule you never formally accepted.

Application for payment deadlines should specify the submission cutoff — typically the 25th of each month — and state that late submissions roll to the next billing cycle. This protects your upstream billing schedule with the owner.

Retention percentage and release conditions must state the exact percentage (10% is standard; 5% is increasingly common on public work), the conditions for reduction, and the specific trigger for final retention release — typically final inspection, punch list completion, and receipt of all closeout documents.

Pay-when-paid language needs to be explicit about the timing mechanism: the GC's obligation to pay the sub is conditioned on receipt of payment from the owner, but payment must still occur within a defined outside date (often 7 days after owner payment, or no later than 60 days from invoice submission).

Dispute resolution tied to payment should specify that payment disputes go to a defined process — mediation, then arbitration — and that the sub cannot stop work pending resolution unless payment is more than 30 days past the outside date. This clause alone prevents most work stoppages.

Pay-When-Paid vs. Pay-If-Paid: What Your State Actually Allows

These two clauses sound similar. They are legally opposite. Pay-when-paid is a timing mechanism — the GC pays the sub after the owner pays the GC, but the GC's obligation to pay eventually exists regardless. Pay-if-paid is a risk transfer — if the owner never pays, the sub never gets paid. Courts treat them very differently.

California, New York, Texas, and several other states have either banned pay-if-paid clauses outright or severely restricted their enforceability in construction contracts. In California, Civil Code Section 8122 effectively prohibits pay-if-paid language in most private construction contracts. If your subcontractor contract template construction uses pay-if-paid language in a state where it's unenforceable, you've lost that protection — and potentially created ambiguity about your entire payment obligation.

Know your state's statute before you copy-paste a contract template from another project or another state.

Retention: How Much, When to Release, and How to Use It as Leverage

Retention is the GC's most direct financial tool for managing subcontractor performance — and most GCs underuse it.

The standard is 10% withheld on each draw until substantial completion. The trend on public projects, driven by prompt payment legislation in states like California and Florida, is moving toward 5% after a sub reaches 50% completion. Conditional retention release — tied to specific deliverables like closeout documents, as-builts, and O&M manuals — gives you leverage at the end of the project when subs are least motivated to finish punch list items.

Retention also connects directly to subcontractor default construction risk. If a sub defaults at 80% completion and you've been holding 10% retention, you have a financial buffer to cover completion costs. If you've already released retention early without those conditions being met, that buffer is gone. Understanding job costing for construction helps you calculate what that completion cost buffer actually needs to be based on your real project margins.

Lien Waivers: The Payment Schedule's Enforcement Layer

Every payment event in your schedule should have a corresponding lien waiver requirement — and the sequencing of those waivers matters as much as the payment itself.

This is where a lot of GCs leave themselves exposed. They collect waivers inconsistently, accept the wrong type at the wrong stage, or — worst of all — collect unconditional waivers before funds have actually cleared. A solid lien waiver construction guide isn't about the paperwork; it's about the sequence.

Conditional vs. Unconditional Waivers: Sequence Them Wrong and You Lose Your Lien Rights

There are four standard lien waiver types, codified by the AIA and recognized in most states: conditional waiver on progress payment, unconditional waiver on progress payment, conditional waiver on final payment, and unconditional waiver on final payment. The conditional waiver is effective only when payment actually clears. The unconditional waiver releases lien rights regardless of whether payment has been received.

The most common GC mistake: collecting an unconditional progress payment waiver before the check has cleared the sub's account. If your payment is later reversed, stopped, or disputed, the sub has already waived their lien rights — but so have you potentially waived your documentation of what was paid and when. Collect conditional waivers at the time of payment, and unconditional waivers only after you've confirmed funds have cleared.

How to Build Lien Waiver Collection into Your Payment Schedule Workflow

The workflow is straightforward, but it requires discipline. The sub submits a pay application by the cutoff date. You issue a conditional lien waiver for the sub to sign before payment releases. Payment goes out. Within 10 days of confirmed receipt, you collect the unconditional waiver for that draw before the next pay application is accepted. No unconditional waiver, no next draw.

Procore and Buildertrend both have lien waiver tracking built into their payment workflows, which helps on larger projects with multiple subs. The breakdown happens on smaller projects managed through email and spreadsheets, where waiver collection is manual and easy to skip under deadline pressure. Build the requirement into your subcontract so it's contractual, not optional.

How to Manage Subcontractors When the Payment Schedule Goes Off the Rails

Payment schedules don't fail because of bad math — they fail because of bad documentation, unclear scope, and GCs who approve draws without verifying work in place.

How to manage subcontractors on construction projects means having a defined response for each breakdown scenario before it happens. Improvising mid-project costs more than the original dispute.

Overbilling and Front-Loaded Schedules of Values: Catch It Before You Pay It

Front-loading is a standard sub tactic on percentage-of-completion contracts. The sub assigns inflated values to early line items — mobilization, material procurement, site prep — to collect more cash in the first two draws than the work warrants. By draw three, they're technically "ahead" on billing but behind on installation.

Review every schedule of values against the actual scope before approving it. Mobilization should represent no more than 2–5% of the subcontract value on most trades. General conditions line items should reflect actual project duration. If a $300,000 electrical sub is claiming $60,000 in mobilization, push back before the first invoice — not after you've paid it.

Subcontractor Default: What Your Payment Schedule Should Trigger Automatically

Default provisions tied to the payment schedule are your contractual safety net — but only if they're specific.

Your subcontract should define payment-related default triggers: failure to pay lower-tier subs or suppliers within a defined period, a lien filed by a sub-sub against the project, failure to complete a milestone within a defined number of days of the scheduled date, or submission of a fraudulent pay application. Each trigger should require written notice and a cure period — typically 48 to 72 hours for payment-related defaults — before the GC can terminate or take over the work.

Without these triggers written into the contract, you're relying on common law remedies that are slower, more expensive, and less certain. The AGC's standard subcontract language includes default provisions, but they're often generic — customize them to your project conditions.

Using a Subcontractor Performance Scorecard to Flag Payment Risk Early

A subcontractor performance scorecard isn't just a post-project evaluation tool — it's a real-time risk flag. Track four metrics on every active sub: invoice accuracy (does the pay app match the approved schedule of values?), on-time submission rate, lien waiver compliance, and milestone completion rate against schedule.

A sub who's consistently submitting late pay apps, missing milestones, and slow on lien waiver returns is showing you the pattern before the default happens. Score your subs monthly. If a sub drops below your threshold on two consecutive scoring periods, increase your verification frequency and tighten your draw approvals. You're not punishing them — you're protecting the project.

Frequently Asked Questions

What should a subcontractor payment schedule include?

A complete subcontractor payment schedule construction document should include every payment milestone or billing period, the dollar amount or percentage of contract value tied to each event, the retention percentage being withheld, the condition precedents required before payment releases (work in place, inspection sign-off, lien waiver submission), and the application for payment deadline. It should be referenced explicitly in the body of the subcontract — not just attached as an exhibit — and signed by both parties as part of contract execution.

How does retention work in subcontractor agreements?

Retention is a percentage of each progress payment — typically 10%, though 5% is increasingly common on public projects — withheld by the GC until the sub meets defined completion conditions. Retention is released either at substantial completion, final completion, or in stages tied to specific milestones depending on your subcontractor agreement template. Some states have prompt payment laws that limit how long retention can be held after a sub completes their scope, so check your state's statute before setting retention release terms.

What is pay-when-paid in construction?

Pay-when-paid is a contract clause that conditions the timing of the GC's payment to a sub on the GC first receiving payment from the owner. It's a timing mechanism, not a risk transfer — the GC still owes the sub payment eventually, even if the owner is slow to pay. It differs from pay-if-paid, which transfers the risk of owner non-payment entirely to the sub. Pay-if-paid clauses are unenforceable in several states including California, New York, and Texas, so verify what your state allows before using either clause in a subcontractor contract template construction document.

How do lien waivers connect to payment schedules?

Every payment event in your schedule should have a corresponding lien waiver requirement. The correct sequence is: sub submits pay application, GC collects a conditional lien waiver before releasing payment, payment clears, GC collects unconditional waiver before accepting the next pay application. Collecting waivers out of sequence — particularly collecting unconditional waivers before payment clears — can leave the GC exposed if a payment dispute arises later. Treating lien waiver collection as an integrated part of the payment workflow, not a separate administrative task, is the core of any practical lien waiver construction guide.

What happens when a subcontractor misses a payment milestone?

If a sub misses a milestone tied to a payment event, the GC should not release that draw until the work is in place and verified. The subcontract should specify a cure period — typically 5 to 10 business days — within which the sub must complete the milestone before the GC can declare a default or redirect resources. Persistent milestone failures, especially when combined with signs of financial distress (unpaid sub-subs, supplier liens), are early indicators of subcontractor default construction risk and should trigger your performance review process immediately.

How often should a subcontractor submit a pay application?

On most commercial projects, pay applications are submitted monthly — typically on a fixed cutoff date, such as the 25th of each month, to align with the GC's upstream billing cycle to the owner. On fast-track projects or large subcontracts with significant material costs, bi-weekly billing may be appropriate. Whatever the frequency, it should be defined in the subcontract and tied to the payment schedule so both parties know the submission window, the review period, and the expected payment date.

The Faster Way to Structure Subcontractor Bids and Payment Terms from Day One

Most payment disputes don't start at the invoice stage — they start at the bid stage, when scope is unclear and the payment schedule is built on assumptions instead of facts.

When a sub bids a project without a clearly defined scope of work, they build contingency into their number — and they build ambiguity into every future pay application. When you receive three bids with different scope interpretations, the payment schedule you build from the lowest number is already wrong. The sub who wins on price is often the one who excluded the most scope, and you won't find out until the first draw dispute.

This is where upstream bid management directly determines downstream payment schedule accuracy. A construction estimate checklist with a defined subcontractor scope of work template, a clear invitation to bid, and a leveled comparison of what each sub actually included means your payment schedule is built on a real scope, not a best guess.

Bidi is built for exactly this stage of the process. It helps GCs run structured subcontractor bids with clear scope definitions, so when you build your payment schedule, you're working from verified numbers and aligned expectations — not chasing clarifications after the contract is signed.

See how Bidi works at bidicontracting.com and build your next subcontract on a foundation that holds up from the first invoice to the last lien waiver.

A subcontractor payment schedule is only as strong as the bid, scope, and contract it's built on. Get those three things right — with structured bids, a tight subcontractor agreement template, and a payment schedule that's integrated into every clause — and you spend less time managing disputes and more time running projects. Get them wrong, and it's Thursday afternoon all over again.

*Reviewed by Weston Burnett, Co-Founder and CTO of Bidi Contracting.*