Backcharges on Finish Work: Where They Start and What Stops Them

A Backcharge Is a Documentation Failure Before It Is a Money Problem

When a backcharge holds up, it is because someone can show what the condition was, when it changed, and who was on site. When it falls apart, it is because two parties are describing the same wall from memory, four months later, with a payment application in between.

That is the real test. Not whether the work was wrong, but whether anyone can prove what it looked like before. On finish work this matters more than on any other trade, because the finish sub arrives last and inherits every condition the previous eleven trades left behind.

The Three Situations That Produce Most of Them

The first is damage. Trim goes in clean on Tuesday. On Thursday a mechanical crew runs a lift down the corridor and takes a chunk out of a casing. Nobody photographed the corridor on Wednesday. The backcharge lands on the finish sub because they were the last name in that room.

• Damage after acceptance, with no dated record of the condition at handoff
• Rework caused by an upstream trade, priced as if it were a defect
• Scope the GC assumed was included and the sub assumed was excluded

Rework That Belongs to Someone Else

The second situation is upstream. A door will not close because the rough opening moved, or a wall is out of plumb by half an inch and the crown reads crooked to the eye. The finish crew can fix it, and often does, but the hours belong to the framing condition, not to the trim.

The moment that work happens without a written note, it becomes invisible labor. Nobody bills it, so nobody remembers it, and when the punch list arrives the same item shows up again as a quality complaint against the finish scope.

Scope Both Sides Assumed Differently

The third is the quietest. Closet shelving, hardware installation, caulking and paint prep, adjusting doors after the paint cures. Every one of those sits on a boundary. A GC reads them as part of finish carpentry. A sub reads them as a separate line. Neither one is being unreasonable.

You settle that at the bid, not at closeout. A scope document that names what is included and what is not turns a future argument into a two minute conversation before the first purchase order.

What a GC Can Require Before the Work Starts

None of this requires a new process. It requires four things to exist in writing, and a sub who produces them without being chased.

• A written scope that lists inclusions and exclusions by name, not by category
• Dated photos of conditions at the start of each area, before any material goes up
• A record of anything the crew fixed that was not their scope, sent the same week
• Sign-off by area, so completed work stops being open indefinitely

When the Backcharge Is Still the Right Call

Sometimes the work is genuinely wrong and the fix belongs to the sub. That happens, and a GC should not hesitate. The difference is that with a record in place the conversation takes ten minutes, the sub agrees, and the number moves through the pay application without a dispute.

That is the version worth building toward. Not a project with no problems, but a project where problems are cheap to resolve because everybody is looking at the same file.