The GC withholds 20% of a progress payment claiming the electrical rough-in on floors 3 and 4 isn’t complete. The electrical sub says it is. Neither of them has a zone-by-zone completion record. The argument runs three weeks, the sub floats payroll twice, and eventually the GC releases 85% of the withheld amount as a compromise.
The sub accepted a loss on a dispute he likely would have won — because he couldn’t prove completion at the time of the draw, only assert it.
The progress payment application is the specialty sub’s regular financial exposure point. Most subs know how to fill out an AIA G702. Fewer have built the field documentation record that makes each line item in the schedule of values defensible before the GC’s project engineer reviews it.
This is what that record looks like.
What the GC’s Project Engineer Is Checking
When the specialty sub submits a progress payment application, the GC’s project engineer reviews it against what he’s observed on site. The PE isn’t always wrong when he marks something incomplete — but he’s often working from a site walk, a weekly report, or a vague memory of what the sub’s crew was doing last Tuesday.
The sub who submits a draw with nothing behind it is asking the PE to trust his percentage estimate. The sub who submits a draw with a zone-level completion record behind it is giving the PE something to verify against.
There are three things that make a progress payment application hard to dispute.
Three Records That Make a Draw Undisputable
Zone-Level Task Completion Tied to the Schedule of Values
The schedule of values on a commercial specialty sub’s contract breaks the scope into line items — rough-in, wire pull, panels, trim-out, startup. Each line item has a contract value and a percent-complete estimate on each draw.
The percent-complete number is an assertion. It’s defensible if there’s a field record behind it showing which zones are complete, which are in progress, and which haven’t started — updated as the work happened, not estimated in the office when the draw is being prepared.
For an electrical sub on a six-floor building, zone-level completion means: Floor 1 rough-in complete (all zones), Floor 2 rough-in complete (zones A through D), Floor 3 rough-in in progress (zones A and B complete, C and D started). That breakdown maps directly to the schedule of values line item. The rough-in line at 40% complete isn’t an estimate — it’s four floors out of ten with a zone-by-zone record behind it.
The GC’s PE who disputes 40% rough-in complete on a ten-floor building when floors 1 and 2 are fully closed and floors 3 and 4 are visible is making a judgment call against a documented record. The GC’s PE who disputes it when the sub’s only backup is “we’re about 40% done” is disputing an assertion.
Stored Material Documentation
Most specialty sub contracts allow billing for materials delivered to the jobsite but not yet installed — stored materials on the AIA G702 line item. The GC’s PE who approves stored material billing wants confirmation that the material is actually on site, identified, and protected.
Stored material documentation is a photo and a delivery record. The conduit delivered to Floor 4 last Tuesday — date of delivery, quantity, where it’s staged, photo of the material in place. The panelboard delivered to the electrical room — date, panel tag, photo showing it’s on site. Without the documentation, the stored material line item is a billing claim the GC can’t verify and will often reject or reduce.
The sub who photographs material deliveries as they arrive — date-stamped, location-tagged — has the stored material backup in the draw package before the PE asks for it. The sub who assembles it from memory when the draw is disputed is trying to reconstruct what was delivered three weeks ago.
The Daily Report Archive for the Billing Period
The progress payment application covers a billing period — typically monthly. The daily report archive for that period is the contemporaneous record of what work was completed, on which dates, by which crew.
A daily report that the GC received in his email at 6:30 PM on the day it was generated is a record that predates the draw. The GC’s PE can’t dispute a zone completion that appeared in a daily report he received on the day of completion, two weeks before the draw was submitted. He received it. It’s dated. It was in his inbox before anyone knew there would be a dispute.
The daily report reconstructed Friday from memory is a document the GC’s PE can question. “Your report says Floor 3 rough-in was complete on the 14th — but I was on site on the 15th and it wasn’t done.” If the daily report was generated from the foreman’s field entries on the 14th and delivered that evening, the sub has a timestamped record to point to. If it was written Friday from memory, he has a document.
The daily report archive for a billing period also establishes the work rhythm. A sub billing 30% complete on a line item has daily reports showing crew deployment, zone completions, and inspection clearances across the billing period. The PE reviewing the draw can see the work happening day by day. That’s a different conversation than a percent estimate with nothing behind it.
Building the Record Before the Draw, Not During It
The common mistake is treating progress payment documentation as something assembled at draw time. The sub prepares the G702, realizes he needs backup for the stored material line and the completion percentages, and spends two days pulling together photos and task lists from memory.
That approach produces incomplete backup, creates disputes that delay payment, and gives the GC negotiating room that shouldn’t exist.
The record that makes a draw undisputable is built as the work runs. Zone completions logged by the foreman at the time of completion. Material deliveries photographed as they arrive. Daily reports generated from field entries and delivered to the GC’s email the evening of each workday. When the draw is prepared, the documentation already exists — it’s a selection from a complete archive, not an assembly under deadline pressure.
The specialty sub who has that record submits a draw application with a zone-completion attachment, a stored material photo log, and three weeks of daily reports the GC already received. The PE reviews it against what he knows and what he already has in his own inbox. The disputes narrow to genuine disagreements about scope, not arguments about whether work happened.
What the Documentation Looks Like at Draw Time
For each schedule of values line item:
- Zone-level completion breakdown (which zones complete, in progress, not started) with dates from the task log
- For stored materials: delivery date, quantity, photo of material on site
For the billing period overall:
- Daily report archive from day one to the draw cutoff date — already delivered to the GC, now referenced in the draw package
- Any inspection clearances during the period (inspection date, inspector, result) — documented at the time of inspection, not reconstructed
For change order work billed in the draw:
- The same-day log entry and photo documentation from when the change was encountered or directed — establishing that the additional scope happened, was outside the original contract, and was documented at the time
The PM who has this documentation assembled before draw day submits applications that get approved on schedule. The PM who assembles it under pressure submits applications that generate questions, get partially withheld, and require follow-up that delays payment by weeks.
For how the zone-level task completion record connects to progress payment backup, see subcontractor progress tracking. For the daily report structure that makes the archive defensible, see subcontractor communication. For how the same zone-level completion record and entry-condition photos protect the sub when the GC’s punch list attributes items that aren’t his, see construction punch list for specialty subcontractors.
See how LogLoon’s reporting generates the draw backup from the foreman’s field entries, or check the pricing — it’s on the website.