Progress billing is slow because percent complete gets reconstructed at month end instead of recorded as the work happens. The project manager walks the site on the 25th, looks at the framing, remembers roughly when the electrician started and writes down a number. The owner's rep looks at the same wall and writes down a different one. The fix is not a better pay app template. It is recording installed quantities against each schedule of values line in the daily log, so that by the 25th the percentage is a sum, not a guess.

Why the month-end scramble happens

Most of what gets written about progress billing construction teams run focuses on the form — the AIA G702 summary sheet and the G703 continuation sheet. The form is not the bottleneck. The bottleneck is the input. Each line on the continuation sheet asks for work completed this period, and on most jobs nobody wrote that down during the period.

So the PM rebuilds it. The sequence looks the same on most jobs:

  1. Billing cutoff arrives. The office asks PMs for percentages on every active job.
  2. The PM drives each site, or calls the superintendent, or scrolls back through photos and texts to figure out what went in since last month.
  3. Percentages get estimated line by line, usually rounded to the nearest 5 or 10.
  4. The pay app goes to the owner, architect or lender's inspector, who walks the job with their own eyes and their own rounding.
  5. Lines get disputed. The app comes back marked up. The PM revises and resubmits.
  6. The payment clock restarts from the resubmission date, not the original one.

Every step after the third one is a consequence of the third one. A percentage that was estimated can be argued with. A quantity that was recorded on a dated daily log, with a photo, mostly cannot.

Turn every schedule of values line into something countable

Percent complete only becomes recordable if each line on the schedule of values has a unit that can be counted on the day the work goes in. That decision gets made when the schedule of values is built, not at billing time. A line that reads "Electrical — $84,000" has no unit. Someone will have to eyeball it every month for the life of the job.

Break lines down until each one has either a quantity or a defined milestone:

  • Drywall hang — square feet hung against total square feet on the takeoff
  • Underground plumbing — linear feet installed and inspected against total linear feet
  • Concrete footings — cubic yards placed against total cubic yards
  • Plumbing fixtures — fixtures set against fixture count
  • Rough electrical — split into milestones: rough-in started, rough-in complete, rough inspection passed, each worth a fixed share of the line
  • General conditions — billed on time elapsed, not work in place, which the owner usually expects anyway

The takeoff already has most of these quantities. That is the point of building the schedule of values from the estimate rather than typing it fresh into a spreadsheet — the units on the bid are the units on the bill. Lines that genuinely cannot be counted, like a design-build engineering fee, get milestones agreed with the owner up front, in writing, before the first draw.

Record the quantity in the daily log, the day it happens

Once lines have units, the daily log becomes the billing record. The superintendent already writes down who was on site, what the weather was and what got done. Adding "1,200 sf drywall hung, level 2, east wing" against the drywall line takes seconds. Doing it 22 working days in a row means the monthly total is already sitting there on the 25th.

Three habits make this hold up when an owner's rep pushes back:

  • Quantities, not percentages — the super records what went in; the percentage is calculated from the total, never typed in by hand
  • A dated photo on the entries that matter most — the lines with the largest scheduled value, or the ones this owner has disputed before
  • Inspections logged against the line they release — a passed rough inspection is the cleanest evidence a milestone was reached

This is the same record that protects the job in other disputes. A daily log written the day of the work is a contemporaneous record. A percentage rebuilt three weeks later is a recollection, and it will be treated as one.

Change orders have to reach the schedule of values first

Extra work cannot be billed until it is a line on the schedule of values, and it cannot be a line on the schedule of values until the change order is signed. On jobs where change orders run on handshakes, this is where the month-end scramble gets worst. The PM knows the crew did the added work. The owner has no signed document saying they agreed to pay for it. The line either gets left off the pay app — deferring cash the job already spent — or gets added anyway, and the app comes back.

The fix sits upstream, at the point the work is requested. The mechanics of why undocumented changes fail are covered in why verbal change orders fail on memory. For billing purposes the rule is simpler: a change order that is approved before the work starts is a billable line by the next draw. One that is approved after the fact is an argument.

Putting unsigned change order work on a pay app, or claiming a percentage the inspector cannot see on site, rarely gets that one line cut. More often the entire application is returned for revision. Most contracts start the payment clock when a complete, approvable application is received — so a returned app does not lose the disputed line, it delays every line, including the ones nobody questioned. Bill only signed scope and only what the log can show.

Front-loading shows up on the WIP report

The other way the reconstruction habit hurts is in what it encourages. When percentages are estimates anyway, there is a pull toward rounding up — or toward building the schedule of values with heavy values on early lines like mobilization and site work so the first draws carry more cash. It feels like managing cash flow. It is borrowing from the back half of the job.

Two things happen. First, the gap between billings and costs grows, and that gap appears as overbilling on the construction WIP report, which a surety or lender will read. Second, owners and lender inspectors who catch a front-loaded schedule early tend to scrutinize every later draw more closely. Recorded quantities remove the temptation because the number is not a judgment call. Billing tracks work in place, and the job ends with retainage left to collect instead of a final draw that does not cover the last month of labor.

What month-end looks like when the record already exists

With quantities in the daily logs and change orders signed before the work, the billing close becomes a review rather than a reconstruction. The order of work changes:

  1. Pull the period's quantities per schedule of values line from the daily logs. This is a report, not a site walk.
  2. Check the calculated percent complete against cost to date on each line. A line that is 70% billed and 30% spent, or the reverse, is the one to look at before anyone else does.
  3. Confirm every approved change order since the last draw has been added as a line, and that nothing unsigned has crept in.
  4. Add stored materials only where the contract allows it and the supplier invoice and storage location are documented.
  5. Calculate retainage per the contract — and note any lines where retainage drops after a milestone.
  6. Attach backup: the log entries and photos for the largest lines, plus conditional lien waivers from the subs and suppliers being paid from this draw.
  7. Submit. Walk the job with the inspector holding the same log, not a different memory.

Step 2 is the one that catches problems while they are still cheap. It depends on cost being current, which is why job costing has to run on a weekly rhythm rather than catching up at month end — the same reconstruction problem applies to cost as to billing.

Where BuilderSolve fits, and where it does not

On the software side, the estimate becomes the schedule, and daily logs record what happened on site against that job. Change orders carry an audit trail from request to approval, and the budget vs. actual view puts billed, spent and remaining side by side per line, which is the check in step 2 above. The AI assistant can draft a daily log entry or a change order from field notes; a person approves or rejects it before it counts for anything. It does not decide percent complete.

What it does not do, stated plainly: BuilderSolve reads QuickBooks one way. QuickBooks stays the book of record for invoices, receivables and retainage held. Purchase orders are in development and not shipped, so supplier commitments for stored materials still need to be tracked wherever they are tracked today.

For builders who are short of hands rather than short of software, the construction back-office team includes finance staff who prepare pay applications, chase lien waivers, process change orders and keep AR current in QuickBooks. They can only bill what the field recorded, which is the whole argument of this piece — the record has to exist before anyone can bill from it.

What to do this month

Do not try to fix every active job at once. Pick the one with the largest contract value and the most disputed pay apps. Rebuild its schedule of values so every line has a unit or a written milestone, get the owner to accept the revised breakdown and have the superintendent log quantities against those lines starting Monday. Run one billing cycle from the log instead of from a site walk. Compare how long the close took and how many lines came back. Then do the next job.

Common questions

how is percent complete calculated for progress billing

Percent complete for each schedule of values line is work in place divided by total scope for that line. It is most defensible when calculated from recorded quantities — square feet hung, linear feet installed, fixtures set — rather than estimated by eye. Lines that cannot be counted should use milestones agreed with the owner in writing, each worth a fixed share of the line's scheduled value.

why do construction pay applications get rejected

Pay applications most often come back because a claimed percentage does not match what the owner's rep or lender inspector sees on site, or because unsigned change order work was billed. Missing lien waivers and stored materials without documentation are other common causes. Under most contracts a returned application restarts the payment clock for every line, not just the disputed one.

can you bill for a change order before it is signed

Generally no. Extra work becomes billable once the change order is signed and added as a line on the schedule of values. Billing unsigned work usually gets the whole pay application returned rather than just that line removed. The practical fix is getting change orders approved before the work starts, so the added scope is a billable line by the next draw.

what is front-loading in progress billing

Front-loading means assigning inflated values to early schedule of values lines, such as mobilization or site work, so the first draws bring in more cash than the work in place justifies. It shows up as overbilling on the WIP report, draws closer scrutiny from owners and lenders on later draws and can leave the final draws too small to cover the remaining labor and materials.