Search “construction progress tracking” and you’ll find Procore, Buildertrend, and PlanGrid — tools that help a general contractor track progress across an entire project. All trades, all phases, one dashboard. The GC sees where every sub stands. Milestones update. The schedule adjusts.
That’s a real tool. It’s the GC’s tool.
A specialty subcontractor has a different problem. He needs to track his own progress — not for the GC’s dashboard, but for his own protection. The GC’s system shows what the GC’s team observed, when they walked the floor, on the dates they chose. The sub’s system should show what actually happened: which zones were complete, at what time, with what inspection status, as of any specific date the GC’s project manager asks about.
When the GC’s observation and the sub’s record describe the same phase differently, the sub with a timestamped completion record is in a better position than the sub who relies on the GC’s walkthrough. The GC controls when the walkthrough happens. The sub controls when his crew logs a task complete.
The Two Progress Records Problem
On a commercial job, two progress records exist simultaneously:
The GC’s record. The GC’s super or project engineer walks the floors on a schedule — weekly, bi-weekly, whatever the GC’s process requires. He notes what he sees. His system updates to reflect it. His record is accurate as of the time he walked the floor.
The sub’s record. The foreman logs task completions as they happen. Zones marked done, inspections passed, deviations noted. The sub’s record reflects what the crew actually completed, at the time it was completed.
These two records should tell the same story. On a well-run job, they usually do. But they diverge in ways that matter when money is at stake:
-
The GC’s walkthrough happens on the 16th. The sub’s foreman marked Floor 3 rough-in complete on the 14th. The GC’s system shows completion as of the 16th. The sub’s system shows completion as of the 14th. For a milestone payment tied to the 15th, the 14th matters.
-
The GC’s super walks Floor 4 on a Tuesday and sees incomplete work. The sub’s foreman marked that zone complete the prior Thursday — and the GC’s concrete crew worked in the space over the weekend and damaged the rough-in. The sub’s completion record with a photo from Thursday is evidence. Without it, the sub is explaining damage, not proving it.
-
The sub’s crew reaches substantial completion on a floor before the GC’s punch list walk. The GC’s record dates substantial completion from the walk. The sub’s completion log dates it from the foreman’s entries. The retention clock starts from the GC’s date unless the sub has a record that establishes an earlier date.
The sub’s timestamped field record is the instrument that resolves these divergences — not in the sub’s favor automatically, but with actual evidence rather than recollection.
What Progress Tracking Actually Means for a Specialty Sub
For a GC, progress tracking is a project management function — are we on schedule, where are the critical path items, what’s the percent complete by trade.
For a specialty sub, progress tracking is both a management function and a protection function.
Management: The PM needs to know where the crew is in the phase sequence, whether the phase is running on the estimate, and what’s coming up in the next two weeks. That’s internal — it informs staffing decisions, material orders, and inspection scheduling.
Protection: The sub needs a record that answers the question “what was complete as of [date]” with enough specificity to survive a payment dispute, a change order negotiation, or a punch list review. That’s external — it’s the record the sub shows the GC when the GC’s record tells a different story.
Most progress tracking tools are built for the first function. The second requires something different: timestamped entries at the zone level, not just percent-complete by phase.
Percent Complete by Phase
Phase-level progress — rough-in is 65% complete, wire pull is 20% complete, panel is not started — tells the PM whether the job is tracking to schedule. The foreman marking zones complete in real time as he moves through the building produces this number automatically. The PM doesn’t need a weekly walkthrough to know that rough-in is 65% complete if the foreman’s task completions add up to 65%.
This is also the number the GC’s project manager asks for in weekly progress meetings. The sub who can say “rough-in is 67% complete — Floor 3 East and West done, Floor 4 East done, Floor 4 West in progress, estimated completion Thursday” isn’t guessing. He’s reading from his task completion log.
Zone-Level Completion with Timestamps
Phase-level progress is useful. Zone-level completion with timestamps is what protects the sub in a dispute.
“Rough-in is 65% complete” doesn’t tell the GC whether Floor 3 East was done before or after the 15th. “Floor 3 East rough-in complete, Tuesday the 14th at 10:15 AM” is a record.
The zone-level completion entry captures what the percent-complete number doesn’t: when the specific zone was done, who logged it, and what the inspection status was at that time. When a milestone payment dispute asks whether Floor 3 was complete by the 15th, the zone-level log answers it. The percent-complete number doesn’t.
Inspection Status as Progress Evidence
For specialty subcontractors, inspection results are progress milestones — not administrative events. A passed rough-in inspection is proof that the work was complete and code-compliant at a specific time, signed off by an authority independent of both the sub and the GC.
The foreman who logs “pre-rough-in inspection, Floor 3, Inspector Garcia, passed, 11:45 AM” at the time of the inspection has a record with three independent data points: the date, the inspector’s name, and a pass result. That record is stronger than a zone completion entry alone, because it introduces an independent authority.
The sub’s progress record that includes inspection results — pass, fail, deficiency noted, corrected, re-inspected, passed — is a complete picture of what happened on that floor in sequence. When the GC’s payment application dispute asks whether Floor 3 was ready for wall close by the 15th, the inspection log answers it.
Three Situations Where the Sub’s Progress Record Determines the Outcome
Payment application. The sub submits a payment application showing 65% completion and bills accordingly. The GC disputes it — his walkthrough shows 55% complete. The sub’s zone-level completion log shows exactly which zones are done and when they were completed. If the GC’s walkthrough was on a date when he didn’t walk every floor, or walked after some damage occurred, the sub’s log establishes the completion state he billed for. Without it, the dispute is a percentage argument. With it, it’s a zone-by-zone comparison.
Retention release. The sub reaches substantial completion and requests retention release. The GC dates substantial completion from his punch list walk. The sub has zone completion entries and inspection records that establish substantial completion on an earlier date. The retention clock — and the interest on it — runs from the actual completion date if the sub can document it. Every week the punch list stays open is another week the sub finances the GC’s project out of retained money. A completion record that establishes the actual date moves the clock.
Punch list damage. The GC’s punch list attributes finish damage in the Floor 4 corridor to the electrical crew. The sub’s progress log shows Floor 4 East rough-in complete on Thursday with entry-condition photos taken when the crew accessed the floor. The photos document that the damage wasn’t there when the crew arrived. The completion log establishes when the crew was in the space and when they left. Without that record, the sub is arguing. With it, the sub has a timeline.
What a Progress Tracking Tool Needs to Do
Zone-level task completions, not just phase percentages. The PM needs phase-level rollup. The PM’s payment application needs zone-level entries with timestamps. Both come from the same foreman logging tasks complete as they happen — if the tool captures zone and timestamp.
Inspection results tied to zones. A passed inspection is the strongest progress entry a sub can have. The tool that captures inspector name, date, and result at the zone level creates a record that’s almost impossible to dispute.
Reports that generate from field entries, not from a separate form. The weekly progress report the GC asks for should compile from the foreman’s task completions, not from a separate Friday afternoon exercise. If the foreman’s entries generate the report, the report reflects what actually happened. If the report is a separate task, it reflects what the PM thinks happened.
For commercial electrical jobs in particular: progress tracking needs to map to the inspection gate structure — rough-in by zone, above-ceiling by zone, final by zone. The GC’s drywall schedule, wire pull crew scheduling, and punch list walk all sequence around those gates. The sub who can show inspection status by zone, by date, doesn’t need a weekly meeting to explain where the job stands.
The Record Nobody Disputes
The sub’s progress record — zone-level completions, timestamped by the foreman at the point of work, with inspection results attached — is the record nobody disputes, not because it’s formal, but because it’s contemporaneous.
A reconstruction prepared in response to a dispute is an argument. A record built as the job runs is evidence. The difference isn’t in the content — it’s in when it was created.
See how LogLoon’s task management and reporting work for specialty sub progress tracking, or check the pricing — it’s on the website.