The dispute doesn’t arrive as a conversation. It arrives as an email.
The GC’s project manager writes to say that the payment application for October is being held. The rough-in on Floors 4–6 doesn’t appear to be complete per the GC’s inspection on the 22nd, and they’re not releasing the milestone until they have a completion date. Or the GC writes to say that the conduit reroute at grid line C4 was in-scope — the design was clear and the sub should have bid the conflict — and they’re not approving the change order. Or the GC sends a punch list with 14 items and one of them is a drywall gouge in the Floor 3 corridor that they’re attributing to the electrical sub’s crew.
The specialty sub now has three options: respond with documentation, respond without documentation, or escalate.
Responding without documentation means the dispute is the sub’s word against the GC’s. The GC has a project manager, a superintendent, and a punchout list generated from a formal walkthrough. The sub has a foreman who says he didn’t cause that damage and a PM who says the rough-in was done on the 19th, not the 22nd.
The sub’s documentation — or its absence — determines what happens next.
What “Documentation” Means When a Dispute Arrives
The word gets used loosely on a job site. A GC asking for documentation of the rough-in completion wants something specific: a dated record, generated at or near the time of the event, that shows what was done, by whom, and when. Not a summary prepared for the dispute. Not the foreman’s recollection of what happened. A contemporaneous record.
Three types of documentation do the work in the three most common specialty sub disputes:
The daily log. A daily log entry from October 19th showing Floor 4–6 rough-in complete, with the inspector’s name and the pass result, is evidence. The same information, emailed to the GC’s PM on November 3rd because the dispute arrived, is not. The record has to exist from the day it happened.
The inspection record. Construction site inspections — the rough-in inspection, the above-ceiling inspection, the final — leave a paper trail if the foreman documented them at the gate. Inspector name, time, areas inspected, pass or fail, correction if required. That record, timestamped to the inspection date, establishes completion as a fact that predates any dispute.
The photo record. A photo of the Floor 3 corridor showing the drywall gouge, timestamped to the day the drywall finishers were on that floor and before the electrical crew arrived, establishes that the damage predates the electrical sub’s work. The same photo, taken after the GC sends the punch list, establishes nothing.
The pattern is the same in each case: the record has to be created at the time of the event. A dispute that arrives six weeks later is resolved by documentation from six weeks ago, not by documentation created in response to the dispute.
The Three Disputes and What Each One Requires
Progress Payment Dispute
The GC withholds a payment milestone claiming work isn’t complete. The specialty sub’s position is that the milestone work is complete — rough-in on Floors 1–4 is done, the inspection passed, and the milestone is triggered.
What the sub needs:
- Inspection record showing floor-by-floor rough-in completion with inspector, date, and pass result. This is the most authoritative record — a passed inspection is a third-party confirmation of completion.
- Daily log entries from the days rough-in was completed, showing foreman, crew, and areas finished. The log covers what the inspection record doesn’t — completion of work that doesn’t have an inspection gate.
- Task completion records showing each rough-in zone marked complete with a completion timestamp. Task-level records fill in the granularity between daily log entries.
The GC’s PM reviewing a payment dispute wants a clear answer to one question: was this work done, and when? The daily log, inspection record, and task records together answer that question with dates, names, and areas. Without them, the answer is “yes, we’re pretty sure it was done by the 19th.”
The daily report that generates automatically from daily log entries becomes the artifact the PM submits — a formatted PDF showing the completion entries, dated, sent to the GC on the day it was generated. The GC’s PM already has it in his inbox. He received it the day the rough-in was completed. The dispute becomes much harder to sustain.
Change Order Dispute
The GC disputes a change order, claiming the work was in-scope. The sub’s position is that the work — typically a field condition that wasn’t in the contract documents — is additional scope warranting additional compensation.
The documentation that supports a change order claim has to establish three things:
-
The condition wasn’t visible in the contract documents. The RFI submitted when the condition was discovered, referencing the specific plan sheet and detail that didn’t show the conflict, is the baseline record. No RFI means no contemporaneous record that the sub identified it as a field condition rather than a bid oversight.
-
The condition was discovered and flagged before the work was done. A daily log entry from the day the conflict was found — “encountered existing [condition] at grid line C4, not shown on E-Series drawings, flagged to GC superintendent, RFI submitted same day” — establishes the sequence. The sub flagged it, submitted the RFI, and waited for direction rather than proceeding and billing later.
-
The work to address the condition is documented separately. Daily log entries from the days the reroute was performed, showing hours and crew, establish the cost basis for the change order. If the foreman tracked those hours to a separate cost code for the reroute, the payroll records support the change order amount.
What’s missing in most change order disputes: the daily log entry from the day the condition was discovered. The RFI exists — most subs know to submit an RFI. But the daily log entry that ties the RFI to the field condition at a specific grid line, on a specific date, by the foreman who found it — that’s the record that’s usually absent. Without it, the RFI looks like paperwork submitted after the fact rather than a field condition flagged in real time.
Punch List Damage Dispute
The GC’s punchout walk identifies damage in a finished space and attributes it to the specialty sub — typically the last trade to work in that space before the finishers. The sub’s position is that the damage was pre-existing.
This dispute is won or lost entirely on photo documentation. The question is whether a timestamped photo of the damage exists from before the specialty sub’s crew entered the space.
The photo documentation habit that protects the specialty sub here is specific: the foreman photographs the condition of a space when his crew enters, not when they leave. A photo of the Floor 3 corridor taken by the electrical foreman when his crew arrived, showing the drywall gouge already present, is the record. A photo taken after the GC sends the punch list is not.
The foreman who receives the punchout list needs to review each disputed item against his own photo record before responding. Items that appear in dated photos taken before his crew’s work began are not his sub’s responsibility. Items that appear in dated photos taken after his crew’s work began require investigation — but at least he knows the sequence.
What the Documentation Needs to Look Like When It’s Submitted
The form of the documentation matters. There is a significant difference between these two responses to a payment dispute:
“Our foreman says Floors 4–6 rough-in was complete by October 19th. We can have him write up what he remembers.”
“Attached is the daily report from October 19th, which was generated automatically and sent to your project manager’s email address at 6:30 PM that day. Pages 2–3 show the rough-in completion entries for Floors 4, 5, and 6, with the inspector’s name and pass result. The inspection record is attached separately.”
The second response isn’t better because it’s more polite. It’s better because it can’t be disputed. The report was in the GC’s PM’s inbox before the dispute existed. The date isn’t a claim — it’s a timestamp on an email the GC already received.
The daily reporting system that generates and emails the report automatically means every day’s log entries become a dated artifact in the GC’s inbox. When a dispute arrives six weeks later, the PM pulls the report from the date in question and attaches it to the response. The record was created at the time of the event and delivered to the GC in real time. The dispute is responding to documentation that predates it.
The Gap Between “We Captured It” and “We Can Submit It”
Most specialty subs capture some version of the field record — the foreman logs something at end of day, photos get taken when there’s time, the inspection gets noted if anyone remembers. The problem isn’t always the absence of documentation. It’s the form.
A photo in the foreman’s camera roll with no location, no project reference, and a timestamp that shows it was taken at 7 PM after the crew left doesn’t establish when the condition existed. A note in a text thread between the foreman and the PM about the conflict at grid C4 isn’t an RFI. An end-of-day log written from memory about what happened that morning is a reconstruction, not a contemporaneous record.
The documentation that holds up in a dispute has three properties: it was created at the time of the event, it was generated by a system rather than reconstructed from memory, and it was delivered to someone other than the sub — the GC, the inspector, or an automated report recipient — on the day it was created.
That’s what the foreman is building every time he logs an inspection result at the inspection, not at the end of the day. Every time he photographs a space when his crew enters, not after the punch list arrives. Every time the daily report goes out automatically at 6:30 PM and lands in the GC’s inbox.
The record isn’t for the dispute. The record is for the job. When the dispute arrives, the record is already there.
See how LogLoon’s field reporting creates dated, deliverable documentation from the foreman’s daily log, or check the pricing — it’s on the website.