Subcontractor Delay Documentation: How to Protect Against Back-Charges

March 31, 2026 · 9 min read

Subcontractor delays are the most common source of construction disputes — and the hardest to prove after the fact. When a sub no-shows, undermans, or delivers defective work, your daily log is the only evidence that matters 60 days later when the back-charge dispute hits.

This guide covers exactly what to document, when, and how to build evidence packages that hold up in disputes.

Why Subcontractor Delay Claims Fail

Most subcontractor delay claims fail for three reasons:

1. No contemporaneous records. Waiting until the end of the week to document a Monday no-show destroys credibility. Arbitrators and judges want same-day documentation.
2. Vague descriptions. "Sub was slow today" means nothing. "ABC Concrete arrived with 4 of 8 scheduled workers at 9:45am, 1hr 45min late. Poured 2 of 5 planned footings" is evidence.
3. No photographic proof. A daily log entry without photos is your word against theirs. GPS-tagged, timestamped photos of empty work areas, insufficient crews, or defective work are decisive.

What Your Subcontract Says About Delays

Notice Requirements

Most subcontracts require written notice within 48-72 hours of a delay event. Your daily log is that notice — but only if it's specific enough and timestamped. Check your subcontract for: notice period, required format (written vs. email), who must receive notice, and whether you need to quantify the impact.

Back-Charge Provisions

Standard AIA A401 and ConsensusDocs 750 allow back-charges for: failure to perform work on schedule, failure to provide adequate workforce, defective work requiring correction, and failure to maintain safe work conditions. Each of these requires documentation at the time of occurrence — not weeks later.

Liquidated Damages

If your prime contract has LDs and a sub causes the delay, flow-down clauses let you pass the cost through — but only with documented proof of which sub caused which delay on which days.

The Subcontractor Delay Documentation Checklist

Record these items in your daily log every day a subcontractor issue occurs:

1. Date and time of observation — exact time you noticed the issue, not end of day
2. Subcontractor name and trade — "ABC Concrete, footings" not just "the concrete sub"
3. Scheduled vs. actual workforce — "8 workers scheduled per Tuesday planning meeting, 4 arrived"
4. Scheduled vs. actual work — "5 footings planned per baseline schedule, 2 completed"
5. Impact on other trades — "Framing crew (XYZ Carpentry, 6 workers) stood down from 10am-2pm waiting on footing completion"
6. GPS-tagged photos — empty work areas, insufficient crews, defective work, idle equipment
7. Weather conditions — rule out weather as the cause of the delay
8. Communication record — "Called sub foreman John Smith at 8:15am re: missing workers. He said crew was reassigned to another project."

Building the Subcontractor Delay Evidence Package

When a back-charge dispute reaches mediation or arbitration, you need a structured package:

1. Timeline of delay events. A chronological table: date, what was scheduled, what happened, impact. Pull this directly from your daily logs.
2. Baseline schedule vs. actual. Show the original schedule and where the sub fell behind.
3. Daily log excerpts. The relevant entries for each delay day, with timestamps and GPS coordinates proving you were on site when you documented it.
4. Photo evidence. GPS-tagged, timestamped photos from each delay day. Organize by date.
5. Cost impact calculation. Quantify: idle labor hours × rate, extended general conditions, acceleration costs if you brought in another sub.

Common Mistakes in Subcontractor Delay Documentation

Documenting too late

End-of-week batch documentation is the #1 killer of back-charge claims. If your log entry timestamp says Friday at 5pm but you're describing Monday's events, opposing counsel will highlight the gap.

Being vague about impact

"Sub delay impacted schedule" is useless. "ABC Concrete's 4-day delay on Building A footings pushed framing start from March 15 to March 19, causing XYZ Carpentry crew of 6 to stand down for 4 days at $480/day = $11,520 idle labor cost" is evidence.

Not documenting good days

If you only log problems, opposing counsel argues you were looking for issues. Document normal days too — "ABC Concrete: full crew of 8, completed 5 footings as scheduled." This establishes a baseline that makes delay days stand out.

Failing to flag reports as claim-relevant

When you need to compile evidence 3 months later, searching through hundreds of daily logs is painful. Flag delay-related reports as "claim relevant" with the "subcontractor delay" category at the time you write them.

Frequently Asked Questions

How quickly should I document a subcontractor delay?

Same day, ideally within hours of the observation. Contemporaneous documentation (recorded at the time of the event) carries far more weight in disputes than after-the-fact summaries. Use voice dictation on site to capture details in real time.

What if the subcontractor disputes my documentation?

This is exactly why timestamps, GPS coordinates, and tamper-evident integrity matter. A daily log with a SHA-256 hash, GPS proof you were on site, and a submission timestamp is much harder to dispute than a spreadsheet someone could have edited after the fact.

Should I notify the subcontractor in writing about delays?

Yes — check your subcontract for the required notice period (typically 48-72 hours). Send written notice referencing your daily log entry. Your daily log serves as the contemporaneous record; the formal notice is the contractual step.

Can I use daily logs as evidence in arbitration?

Yes. Daily logs are one of the most commonly cited forms of evidence in construction arbitration. Arbitrators look for: contemporaneous creation (same day), specificity (names, numbers, times), consistency (documented every day, not just problem days), and integrity (not edited after the fact).

How does BuildLog help with subcontractor delay documentation?

BuildLog lets you flag daily reports as "claim relevant" with the "subcontractor delay" category. When you need to build your evidence package, filter by delay category and date range, then export a Delay Defense Pack — a structured PDF with timeline, weather records, GPS-tagged photos, and tamper-evident integrity verification for each report.