Datacat

Insights

2026-10-15 · 6 min

The same fault, the third callout — how multi-site teams stop paying for repeat jobs

The cool room alarm trips again and a new tech has no idea what was done last time. How multi-site teams link repeat jobs to history and stop paying for rework.

The cool room alarm at one of your sites goes off on a Saturday night. A refrigeration tech attends, resets a controller, and closes the job. Three weeks later it happens again. A different tech from the same company turns up, has no idea anyone was there before, and replaces a fan motor. A month after that, the alarm trips a third time and the store loses a night's stock.

Each invoice looked reasonable on its own. Together they paid for the same fault three times, plus the stock, and nobody in ops saw the pattern until the regional manager asked why one site keeps showing up in the spend report.

Repeat callouts are one of the most expensive leaks in multi-site maintenance, and one of the least visible. The jobs get done. They just don't stay done.

Why the same job keeps coming back

  • Every callout starts from zero. A new work order goes out with "cool room alarm" and nothing else. The contractor can't see what was tried last time, so the second visit repeats the first.
  • Close-out notes say "fixed", not why. Without a recorded cause, there is no way to tell a reset from a real repair, or to know whether the fault was found at all.
  • Rework gets invoiced like new work. If the same contractor returns for the same fault a fortnight later, that should usually be on them. Without the history in front of you, it goes through accounts payable as a fresh job.
  • Repair versus replace never gets asked. A unit that has been patched five times in a year is costing more than a new one, but nobody adds it up because the jobs live in five separate threads.
  • Sites stop reporting the small stuff. Staff learn the fault "always comes back" and work around it, so the next failure is bigger and arrives on a weekend.

What good looks like

Stopping repeat jobs is not about a tougher contractor or a longer contract. It is about making the history impossible to miss, at the moment someone raises the next job.

New jobs show what happened last time. When a site raises a fault, ops can see recent work at that site for the same trade or equipment before the work order goes out. The contractor gets the history with the job, so the second visit starts where the first one finished.

Close-out records the cause, not just the outcome. A job is not complete until the contractor says what they found, what they did, and attaches the photos to prove it. "Reset and tested" and "replaced failed fan motor" are very different answers, and you need to know which one you paid for. This is the same discipline as work-order proof leadership can trust.

Rework is flagged before it is paid. When the same contractor is called back for the same fault within an agreed window, the job is marked as a return visit. Your team decides whether it is billable with the history in hand, not after the money has gone.

Repeat faults surface on their own. A short weekly view of sites and equipment with more than one callout for the same issue tells you where to look. Two visits might be bad luck. Three is a conversation about root cause or replacement.

Repair versus replace has a number. Add up the callouts, parts, and downtime for a problem unit over the last year and put it next to a replacement quote. That turns a gut feeling into a capital request finance can approve.

The right contractor gets the hard ones. If a fault keeps beating your first-choice trade, send the next attempt to whoever on your approved list has actually fixed it before, rather than whoever is next in rotation. Going to quote stays a last resort, as in RFQ overflow when the preferred book is full.

Signals you are paying for the same job twice

  • Nobody can say, without searching emails, how many times a given site has called out the same trade this quarter.
  • Close-out notes are a word or two, or blank.
  • Return visits from the same contractor are invoiced at full rate without anyone checking.
  • The same handful of sites keep topping the maintenance spend report, and the explanation is "old building".
  • Site staff have a workaround for a fault that was "fixed" last month.

One of those is normal wear and tear. Three or more means your maintenance budget is quietly funding the same repair over and over.

What changes after the first quarter

  • Every new work order carries the recent history for that site and trade, so contractors arrive informed.
  • Close-outs record cause and evidence, so you know what you paid for.
  • Return visits are caught before invoices are approved, and rework conversations happen with facts.
  • Repeat-fault sites and units show up in a weekly list, with a clear repair-or-replace case for the worst offenders.
  • Your preferred contractors are judged on jobs that stay fixed, not just jobs that get closed, across every site in one queue.

We built OpsChase for exactly this kind of multi-site repair work. It sends jobs to the contractors you already trust first, keeps response and attendance visible on every work order, and will not let a job be marked complete until the close-out pack of photos, checklists and signatures matches your template, so the record of what was actually done is there when a fault comes back. See how it fits on the OpsChase product page.

Need repeat-fault reporting, rework rules, or asset history tied into a larger CRM or finance setup? We build preferred contractor and work order systems, vendor and contractor portals, and ops workflow automation around the way your operation actually runs. Browse selected work, book paid strategy and discovery if you are still scoping, or talk to Datacat.