HomeResources

How Daily Reports Win (or Lose) Back-Charge Disputes

A back charge holds up when the daily reports show the problem on the day it happened: what was wrong, where, whose work it was, who was notified, the chance given to fix it, and the labor, equipment and material spent fixing it. Subs fight back charges the same way, with their own daily reports showing what they did, when, and what direction they were given. Whoever has the better same-day record usually wins.

Back charges are one of the fastest ways for a general contractor and a sub to end up in a fight over money. Usually both sides believe they are right, and the dispute turns on whose records are better. This guide covers what to record so the paperwork supports you, whichever side of the back charge you are on.

What a back charge needs to stand on

Subcontracts usually set the rules: notice, an opportunity to cure, and documentation of cost. Read yours. In practice, a back charge that survives review typically has:

  1. Notice. The sub was told in writing about the problem.
  2. Opportunity to cure. The sub had a reasonable chance to fix it, unless the contract or an emergency allowed otherwise.
  3. Proof of responsibility. Records showing it was that sub's work or damage.
  4. Proof of cost. Itemized labor, equipment and material used to fix it, recorded when it happened.

Law firms that advise on these disputes stress the same points. See, for example, McDonald Hopkins on proper back charges. The daily report is where items 3 and 4 usually live.

What general contractors should record

The day the problem is found:

  • What is wrong, in plain words, with location
  • Whose work it is, and how you know (installed by whom, on which date per the earlier daily report)
  • Photos with captions and time
  • Who from the sub was told, how, and when

The days the sub is given to fix it:

  • Whether the sub showed up, with headcount
  • What they did, or that they did not respond

The days your forces or another sub fix it:

  • Company, headcount and hours spent on the fix, separate from other work
  • Equipment used and hours
  • Material used, with tickets
  • Photos before, during and after

The key is separating the fix work from everything else in the daily report. A line like "General contractor labor 3 workers, 6 hrs, general cleanup and drywall repair" makes the cost impossible to prove. Compare it with this entry:

General contractor labor 2 workers, 4 hrs each, patch and finish 3 drywall penetrations, Level 3 rooms 312 to 314, left open by plumbing sub. Plumbing foreman notified by text 10/06 7:40 AM, no response by 10/08. See photos 7 to 12.

What subs should record

Subs often learn about a back charge weeks later on a pay app deduction. Your own daily reports are your best defense:

  • What you installed, where, and when, with photos when complete
  • Who accepted it or inspected it, if anyone did
  • Damage you found from other trades, logged when you found it
  • Direction you received, with the person's name and time
  • Notices you received, and your response
  • Times you were blocked from returning to fix something

If you receive a back charge, respond in writing quickly, ask for itemized backup, and compare it to your own daily reports and time records. Without your own records, it is your word against theirs. For more on what your foremen should capture, see the foreman daily report guide.

The cleanup back charge

Shared cleanup charges are a classic fight. The general contractor charges every sub on the floor for a dumpster and labor because nobody claims the mess. Records that help:

  • Which trades were working in the area that day (from manpower by sub)
  • Photos of the debris showing what it is (drywall scraps, conduit ends, packaging)
  • The cleanup notice and the deadline given
  • Hours and equipment for the cleanup itself

Manpower by sub and location is what turns a guess into an allocation. See construction manpower tracking for how to keep that record daily.

Damage by another trade

When one sub damages another sub's finished work, the general contractor sits in the middle. The damaged sub wants to be paid to repair it, and the general contractor wants to pass the cost to whoever caused it. The record that settles it usually has three parts:

  • The damaged sub's report showing the work complete and undamaged, with photos, on an earlier date
  • The report on the day the damage was found, with photos and the trades working in that area since the last clean record
  • The repair entry, with hours and material kept separate

Without the "before" photo, every trade in the area can deny it.

Back-charge documentation checklist

  • Problem recorded in the daily report the day it was found
  • Location, description and photos with captions
  • Responsible party identified with supporting record (earlier daily report, install date)
  • Written notice sent; date, method and recipient logged
  • Opportunity to cure given and logged (response or no response)
  • Fix work recorded separately: company, headcount, hours
  • Equipment and material for the fix with tickets
  • Before, during and after photos
  • Cost summary ties back to specific daily report entries
  • Subcontract clause for back charges checked

Make the records easy to capture

Most back-charge records never get written because the person who saw the problem had no easy way to log it in the moment. A foreman who snaps a photo and texts "found 3 open penetrations L3 312 to 314, not ours" creates a timestamped record that settles a lot of arguments. See construction photo documentation and subcontractor daily report requirements for how to set this up on your jobs, and daily reports for change orders for the other side of the money: getting extra work paid.

How Cascade keeps the record

Cascade Technology is SMS-first field intelligence for general contractors and subcontractors. Superintendents and foremen text in their day, along with their subs, and Cascade turns those texts into daily reports with photos, locations and manpower and hours by sub. When a dispute comes up, the PM can ask in plain English, "who worked on Level 3 rooms 312 to 314 between October 1 and 10?" and see the answer with the source reports. Scope: Daily reports, manpower and hours by sub, photos, toolbox talks, pre-task plans (JHA), safety incidents and corrective actions, project + schedule planning, automatic sub reminders, analytics and plain-English answers.

Subcontractor access is free, so subs get their own record too, and general contractors using Cascade see 95%+ sub daily report compliance. Onboarding and integration are free, and the general contractor plan starts with a one-month pilot with no contract lock-in. We beat Raken, Procore, and ACC on price, guaranteed. See the daily report template or why Cascade.

Request Access

Frequently asked questions

What documentation do I need for a back charge?

Typically written notice to the sub, a record of the opportunity to cure, proof the issue was that sub's responsibility, and itemized labor, equipment and material costs for the fix. Check your subcontract for the exact requirements.

How can a subcontractor dispute a back charge?

Respond in writing promptly, ask for itemized backup, and compare it with your own daily reports, photos and time records. Point to specific entries that show what you installed, when, and any direction you received.

Why do back charges get rejected?

Common reasons are no written notice, no chance to cure, no proof of who caused the problem, and fix costs mixed in with other work so they cannot be verified.

Should fix work be separated in the daily report?

Yes. Record the labor, hours, equipment and material for the fix on their own lines, with the location and photos. Mixed entries make the cost hard to prove.

Request Access

RESOURCES

See how your team reports by text.

Free onboarding and integration, a one-month pilot and no contract lock-in. Tell us about your jobsites.

EARLY ACCESS FOR PUGET SOUND GCS · SET UP IN DAYS · YOUR DATA STAYS YOURS