Progress Billing vs. Milestone Billing: Which Structure Fits the Project
Construction contracts generally use one of two billing methods — or a hybrid of the two. Progress billing invoices based on work completed to date, typically calculated as a percentage of completion against each line item on a schedule of values. Milestone billing invoices at pre-defined project stages, each with a specific dollar amount payable on completion of the milestone. The choice between them affects cash flow, the administrative cost of running the billing, and the kinds of disputes that arise.
Neither method is universally better. A residential renovation with a $100K contract and four-month duration probably doesn't need the overhead of a full AIA schedule of values with monthly pay applications. A $30M school construction project almost certainly does. Picking the right method for the project is part of setting up the contract correctly; converting between methods mid-project is hard.
In progress billing, the total contract value is broken down into a schedule of values — individual line items each with a dollar allocation. On each pay application (typically monthly), the contractor reports the percentage complete for each line item. The percentage complete times the line's allocated value gives the "earned to date" for that line. Summing the earned values and subtracting previously-billed amounts gives the current invoice amount.
A concrete example: the schedule of values has a line for "Foundation — $500,000." The contractor reports 40% complete. The earned value is $200,000. If previous pay applications billed $120,000 against this line, the current pay application bills $80,000 for foundation. Repeat this calculation for every line on the schedule, sum, apply retention, and arrive at the net payment amount.
Progress billing smooths cash flow over the project duration. Revenue comes in monthly, tied to actual work performed. The contractor's cash in and cash out roughly match, with retention holding back a portion for later. The owner pays for work actually completed, with the architect's certification protecting against overstatement.
In milestone billing, the contract defines specific project stages, each with a predetermined payment amount. Payment is triggered when the milestone is achieved — no proration, no percentage complete. The contractor either completes the milestone and bills the associated amount, or the milestone isn't done and no payment is due.
A small project example: a $200K custom home renovation with milestones of $40K at contract signing (mobilization), $50K at demolition complete, $60K at rough-in complete, $30K at drywall complete, $20K at punch list resolution. Each milestone either happens or it doesn't; there's no partial payment for partial milestone completion.
Milestone billing is simpler administratively. There's no monthly calculation of percentage complete, no schedule of values maintenance, no debate over whether a line item is 45% or 50% done. Either the milestone is reached or it isn't. The simplicity comes at the cost of cash-flow lumpiness — long gaps between milestones can stretch the contractor's working capital.
Progress billing produces steady monthly cash flow for the contractor. Every month of active work generates an invoice and, after the payment terms pass, a cash receipt. The contractor's cost outflows (labor weekly, materials as delivered, sub pay-apps monthly) roughly sync with the cash inflows, with the main gap being retention held at the project's end.
Milestone billing produces lumpy cash flow. If a project has a milestone at month 2 and the next one at month 6, the contractor is funding four months of costs on their own capital between milestones. For a sub with steady payroll and material costs, this can be hard to carry. Some milestone-based contracts include a mobilization milestone up front ($40K or similar) to partly address this, but the contractor is still carrying working capital between milestones.
The mismatch between milestone timing and cost timing is one of the main reasons progress billing dominates larger projects. Working capital requirements on a $30M project with milestone billing could easily be $3M-$5M. Progress billing's steady cash flow keeps that requirement low.
Progress billing requires ongoing administrative effort. Every month: prepare the pay application, walk the project, assess percentage complete for each line, assemble backup, submit for architect review, respond to questions, and wait for certification. On a large project with 100+ schedule-of-values lines, the monthly effort is significant — a pay-app team of multiple people is typical on jumbo projects.
Milestone billing reduces the administrative overhead during the project. The billing effort is concentrated at each milestone — verify the milestone is met, submit the invoice, collect. Between milestones, there's no billing cycle. For small projects, this saves meaningful time.
For the owner's side, progress billing requires active review each month — the architect or owner's rep has to certify each pay application. Milestone billing concentrates the review effort at each milestone but reduces the month-to-month cost of management.
On projects that don't have the administrative structure to support monthly pay applications — owners without in-house architects or project managers, small GCs without dedicated pay-app staff — milestone billing can actually produce better outcomes. The simpler structure matches the simpler administrative capacity.
Progress billing creates percentage-complete disputes. The contractor reports 55% complete on a line; the architect thinks it's 45%. The difference is $40K on this pay application. Multiply by multiple line items and the monthly dispute surface is large. These disputes usually get negotiated quickly ("Fine, we'll accept 50% this month and true up next month"), but they're friction.
Get AP insights in your inbox
A short monthly roundup of construction AP + accounting posts. No spam, ever.
No spam. Unsubscribe anytime.
Milestone billing creates milestone-definition disputes. The contract says "demolition complete" triggers a $50K payment. Is demolition complete when all the walls are down, or only after the debris is hauled off? Is the foundation milestone reached when concrete is poured, or when it's cured and inspected? The ambiguity at the milestone boundary is the dispute.
Well-drafted milestone contracts specify the milestone completion criteria precisely — "demolition complete, defined as (a) removal of all walls, fixtures, and finishes identified for demolition; (b) site free of debris; (c) inspection sign-off by owner's representative." Vague milestones create disputes.
Some contracts use both methods. A common hybrid: progress billing against a schedule of values for most of the work, with milestones triggering certain payments. For example, the bulk of the contract might bill through standard progress billing, but a specific milestone payment ($200K at substantial completion) replaces what would otherwise be a retention-release payment tied to percentage complete.
Another common hybrid: milestone billing for design or soft-cost phases, progress billing for construction. A design-build project might bill the design phase in three milestones (conceptual design, design development, construction documents) and then switch to progress billing once construction starts. The hybrid matches each phase's natural billing rhythm.
Under progress billing, retention is typically held as a percentage of each pay application (5%-10% common) until substantial completion, then released with a smaller portion held against punch list through final completion. The retention mechanic is built into the pay application calculation.
Under milestone billing, retention can be held a few ways: as a percentage of each milestone payment, as a dollar amount reserved for post-substantial-completion release, or as a separate final milestone tied to project closeout. The choice depends on the contract drafting. Some milestone-billing contracts hold no retention at all, with the final milestone serving as the effective retention piece — payment only flows once the project is truly done.
General rules of thumb, with exceptions:
When progress billing is the right fit
- Large projects with long duration (6+ months)
- Complex scope with many trades and line items
- Owners with in-house architects or project managers who can review monthly
- Contractors whose working capital would be strained by lumpy milestone cash flow
- Public work where progress billing is the standard (and often required by specification)
When milestone billing is the right fit
- Smaller projects with short duration (a few months)
- Well-defined scope where milestone completion is objective
- Owners without administrative infrastructure for monthly pay-app review
- Design phases, soft-cost phases, or specific deliverable-based scopes
- Contracts where the contractor has enough working capital to fund inter-milestone activity
Progress billing and milestone billing are both valid construction billing structures, but they fit different projects. Progress billing provides steady cash flow and handles complex scope but requires monthly administrative effort. Milestone billing is simpler to administer but concentrates cash flow around discrete events. The right choice depends on project size, duration, complexity, and the administrative capacity of both parties. Picking the wrong structure for the project creates either avoidable administrative burden or avoidable cash-flow strain, both of which surface as friction during the job.
Written by
Marcus Reyes
Construction Industry Lead
Spent twelve years running AP at a $120M general contractor before joining Covinly. Lives in the world of AIA G702/G703, retainage schedules, and lien waiver deadlines. Writes about the construction-specific workflows that generic AP tools get wrong.
View all posts