Every trade has callbacks — a tap that weeps a week after the fit, a hairline crack in a patch of plaster, a socket that trips under load. Fixing it under warranty is simply the cost of standing behind the work. What's easy to miss is that it's still a cost, and if it's not tracked against the original job, that job's real margin is quietly better on paper than it actually was.

Why a callback disappears from the numbers

The original job gets invoiced, paid, and closed. The callback happens weeks or months later, off the clock as far as the books are concerned, with no invoice attached to remind anyone it happened. Unless the fuel, materials and time for that morning get logged somewhere, the job's final margin — the number used to decide whether it's worth quoting similar work again — never accounts for it.

What actually needs logging on a callback

  • Travel — a callback is rarely on the way to anything else; it's usually a dedicated trip.
  • Materials used to fix it — even a small part replaced under warranty is a real cost, paid by you, not the customer.
  • Labour time — an hour or two that isn't billable, but is still an hour or two not spent on paid work.
  • The reason — a quick note on what actually went wrong. A pattern of callbacks for the same cause is worth knowing about; a one-off is worth knowing was a one-off.

Tag it to the original job, not a general "callbacks" bucket

A generic callbacks category tells you comebacks cost money in general. Tagging each one back to the specific job it relates to tells you something far more useful: whether a particular job, client, or type of work is generating more comebacks than the rest. That's the number that should actually change how similar jobs get quoted or built next time — not a vague sense that "callbacks happen sometimes."

A worked example

Say a job was quoted with a healthy margin and invoiced accordingly. A callback six weeks later costs a morning's travel, a replacement part, and two hours on site — none of it billed, none of it currently attached to the job anywhere. Logged against the original job, the real margin is now visibly a little thinner than the invoice suggested. Left untracked, the job simply looks more profitable than it was, and the next quote for similar work is built on a number that was never quite true.

When a pattern is the real finding

One callback on one job is normal — trades involve materials and installs that occasionally fail regardless of how carefully the work was done. Three callbacks in a year for the same type of fault, on jobs that otherwise looked fine, is a different story: a materials supplier worth reconsidering, a step in the process worth changing, or a specific sub-contractor's work worth checking more closely before it's signed off. None of that pattern is visible unless each callback is logged with enough detail to compare them later.

How Site Wallet handles this

A callback's fuel, materials and cash costs can be logged straight back onto the original job's record — even weeks or months after it's closed — so the job's true margin stays accurate rather than frozen at the invoice date. A short note on the cause makes it easy to spot a pattern across jobs later, without digging back through old paperwork to remember what actually happened.

FAQ

Should I track a callback even if it only took twenty minutes?

Individually it barely moves the needle — but callbacks that seem trivial one at a time can add up to a meaningful chunk of unbilled time across a year, and the pattern is only visible if they're logged consistently, not just the big ones.

What if the callback isn't really my fault — a product failed, not my work?

Still worth logging against the job for the same reason: it's still a real cost to you, and it's useful evidence if you ever need to push back on a supplier or manufacturer over a recurring product fault.

Does this change how I should price future jobs?

Only if a pattern shows up. A single unlucky callback doesn't mean the pricing was wrong. A trade or job type that consistently generates callbacks is a signal that either the price, the process, or the materials need a second look.