The Second Call on the Same Furnace

"No heat" comes in on a Tuesday. A tech gets dispatched, pulls up, opens the panel, and starts working the problem from the top — checks the thermostat, checks the flame sensor, works down the list the way you're trained to.

Six weeks earlier, a different tech was at that same furnace for the exact same complaint. Replaced a capacitor, and flagged the ignitor as marginal — probably fine for now, worth watching. None of that made it to today's tech. So today's tech finds the same marginal ignitor, on their own, the slow way, and the customer's first question is "didn't someone already look at this?"

Where this actually comes from

It's not that the first tech didn't write anything down. Most do — a note on the invoice, a line in a paper ticket, something scribbled before they left. The problem is where that note ends up. It's attached to that job, not to the furnace. Once the job is closed, the note is closed with it, filed away in whatever last month's paperwork became.

The next tech dispatched to that address doesn't get a furnace's history — they get a fresh work order with a customer name and an address on it, same as any other call. Whatever happened last visit, and the one before that, exists somewhere, technically, but not anywhere the person standing in front of the unit can see it before they start.

So every visit defaults to starting from zero. Not because anyone's careless — because the system in most shops is built to remember jobs, and nobody built it to remember equipment.

Why it costs more than one redundant diagnosis

A repeated ten minutes of diagnosis is the smallest version of this. The more expensive version is the miss: a tech who doesn't know an ignitor was already flagged as marginal has no reason to replace it proactively — they just confirm it still technically works and move on, and the customer's back on the schedule for "no heat" again in another six weeks. That's two truck rolls and two trip charges for a problem that a visible history would have closed on the first one.

It also shows up as a trust problem, and that one's harder to fix than the furnace. A customer who has to re-explain what happened last time, to a tech who clearly doesn't know, starts to wonder what else the shop isn't keeping track of — whether the maintenance plan they're paying for is actually watching their equipment, or just showing up on a schedule.

What actually closes the gap

The fix isn't better notes. Techs are already writing things down — the problem is where those notes live. If a note is attached to the equipment instead of the job, it's still there the next time anyone — any tech, any visit, any reason — shows up at that address. A capacitor replacement, a flagged part, a "customer mentioned a rattling noise" aside: all of it sits on the unit's own record, not buried in a closed-out job from last month.

That's the model TradeVan's work orders are actually built around — equipment, not just jobs, as the thing being tracked. A tech pulling up to a service call sees that furnace's history before they open the panel: what was replaced, what was flagged, what the last visit's notes said. The second call starts where the first one left off, instead of starting over.

If this hasn't bitten you yet

At low job volume, with a small, steady customer list, this mostly doesn't show up — the same one or two techs remember most of what happened, because they were probably there for it. It starts showing up once there's enough volume that the tech on today's call wasn't the one on last month's, or enough time between visits that even a good memory doesn't hold it. That's usually a maintenance-plan shop's whole customer base, most of the time — worth having an answer for before a customer gives you the "didn't you already look at this?" question in front of you.

---

Part of our "Problems and Solutions" series — see also the invoice that sits for three days, why the whiteboard breaks at 5 techs, and the double-booked tech. If there's an operational problem you'd like us to cover, let us know.