Everybody in flooring knows what a go-back is. Hardly anybody knows what one actually costs.
Ask an owner and they'll shrug: "Couple hours, little bit of material, no big deal." That's the number they feel. The real number is two or three times that, and it comes straight off a job they already counted as profitable.
Let's actually add it up.
The real math on one go-back
Say a seam lifts on a job you finished three weeks ago. Here's what the return trip really costs:
- Drive time — an hour each way, two installers in the van. That's four paid man-hours before anyone touches the floor.
- The fix itself — two hours on site, two men. Four more man-hours.
- Material — adhesive, a little replacement product, maybe a transition. Call it small but not zero.
- The job you bumped — those installers were supposed to be somewhere else. Now that job slips, or you pay overtime to catch up.
So your "couple hours" go-back is really eight-plus paid man-hours, some material, and a scheduling ripple that pushes another job. On a job that already closed, that's not a small ding — it can erase the entire margin you made on it.
And none of that includes the part that doesn't show up on a timesheet: the customer who was thrilled at the final walkthrough and is now annoyed, leaving a lukewarm review instead of a great one.
Why go-backs don't show up in your numbers
Here's the sneaky part. Almost nobody logs go-backs against the original job. The install closed out weeks ago. The return trip gets buried in "general labor" or just disappears into the crew's week.
So your reporting still shows that job at a healthy produced margin, when in reality it went negative the day someone drove back out. If you've read the sold vs. produced margin breakdown, this is one of the biggest reasons the two numbers drift apart.
You can't manage a cost you can't see. And go-backs are practically invisible by default.
How to actually drive the number down
Go-backs are never going to hit zero — flooring is a hands-on trade and stuff happens. But most shops could cut theirs in half just by making them visible and tying them to a person.
1. Log every go-back against its job and its installer. Not in a notebook. Somewhere it rolls up. When you can see that Crew A has half the go-back rate of Crew B on the same product, you've found real money — and a training opportunity.
2. Tie it to the scorecard, not to blame. This isn't about chewing somebody out. It's about patterns. If one installer's go-backs cluster around a specific product or substrate, that's fixable with training, not punishment. Tracking installer performance the right way is how you do this without turning the shop toxic.
3. Separate installer-fault from everyone-else's-fault. A go-back because the installer rushed a seam is a different problem than a go-back because the material shipped defective or the customer's subfloor moved. Lumping them together hides the real cause. Track them apart.
4. Catch it at final walkthrough, not three weeks later. A defect caught the day of install costs a fraction of one caught after the customer's been living on it. A solid walkthrough with photos closes the gap.
The bottom line
A go-back isn't a two-hour favor. It's eight paid man-hours, some material, a bumped job, and a dinged reputation — landing on a job you already booked as a win. The shops that take rework seriously don't do it to punish installers. They do it because cutting their go-back rate is one of the cheapest margin improvements available, and it's hiding in plain sight.
FloorStrategy logs go-backs against the job and the installer automatically — including a client-facing claims tracker so warranty issues don't turn into bad reviews. Free until July 22.
FAQ
What does a flooring go-back actually cost? Far more than the on-site fix. Add drive time, a full crew's man-hours both directions, material, and the cost of bumping another job. It's often enough to wipe out the original job's profit entirely.
How do I reduce go-backs without micromanaging my installers? Track them by installer and by product to find patterns, then use training where the patterns point. It's about fixing causes, not assigning blame.
Should every callback count as a go-back? Separate installer-fault rework from material defects, subfloor movement, and customer-caused issues. They're different problems with different fixes, and lumping them together hides what's actually going wrong.