Your No-Fault-Found Rate Is an Information Problem, Not a Personnel Problem
The industry average for “No Fault Found” on returned field equipment sits somewhere between 20% and 40%, depending on which study you read and which vertical you’re in. That means at minimum one in five pieces of equipment making the round trip through your depot — pulled by a field tech, shipped, received, tested, cleared, and shipped back — was working fine the entire time.
That’s not a small inefficiency. In field service, a high No Fault Found rate is a structural leak — and one of the most persistent, underdiagnosed cost problems in the industry.
The cost isn’t just shipping and depot labor, though those numbers hurt. There’s the customer downtime while the replacement is sourced. The replacement unit sits in parts inventory instead of serving a backup purpose. Consider the field tech’s time on-site. And then there’s the credibility hit when the “faulty” unit powers on immediately at the customer’s next visit.
So what’s actually going on? The common response is: “Our techs need better training.” That’s the wrong diagnosis.
The Tech Isn’t Guessing — They’re Protecting Themselves
Put yourself, for a moment, in the field tech’s position. They’re standing in front of a piece of industrial equipment that the customer says is misbehaving. They can’t reproduce the fault reliably. They run through their checklist. Nothing definitive.
Now they’re on the phone with a senior engineer back at the depot. They’re trying to describe what they’re seeing — an intermittent vibration, a pressure reading that’s within spec but feels off, a noise that started two weeks ago but isn’t happening now. The engineer on the other end is working from a diagram and a description. Neither of them can prove the unit is faulty. Neither can prove it’s fine.
In that situation, the field tech does the rational thing: they swap it. Not because they’re lazy or undertrained. Because swapping it is the only move that closes the loop. It solves the customer’s complaint. It removes the ambiguity. And if they don’t swap it and the problem recurs, they’re the one who signed off on a unit they should have pulled.
The return isn’t a mistake. It’s a hedge. And it’s rational given the information available.
No Fault Found Field Service Diagnosis: The Information Problem
Here’s the non-obvious insight: this isn’t about training — it’s about visibility.
When a field tech and a remote engineer are diagnosing together over a voice call, one of them is flying blind. The engineer has the expertise but can’t see the equipment. The tech can see the equipment but may not have the expertise to know what they’re looking at. The verbal handoff between those two positions is where the diagnosis breaks down.
For instance, the tech says “the seal looks a little worn.” Is that a failed seal or normal wear? “The motor is running a bit loud.” How loud? Compared to what? These aren’t questions that can be resolved by better training. They’re questions that require shared observation.
When the engineer can actually see what the tech is seeing — live, in context, on the actual equipment — the dynamic changes completely. They can direct the camera and ask the tech to move to a specific component. They can watch the behavior in real time. More importantly, they can compare what they’re seeing against their own experience with hundreds of similar units — and make a call with actual evidence behind it.
That’s what Viewabo is built for. It’s live video for field service — the tech streams what they’re seeing, the remote expert observes and guides, and the decision gets made with the full picture available. Not a description of the picture. The picture.
What Changes When You Add Visual Evidence
When a remote engineer can observe the fault (or the absence of one) directly, a few things happen.
First, the threshold for “let’s pull it” rises. It’s a lot harder to approve a return on a unit that you just watched run through its operational sequence without incident. The engineer’s sign-off carries weight — and they’re not going to sign off on a return they can’t justify.
Second, the tech stops being alone in the decision. This matters more than it sounds. A field tech who says “I pulled it, I wasn’t sure, I called it in” is in a completely different position than one who says “I pulled it because the engineer on the live call confirmed the fault.” The shared visibility creates shared accountability, and that actually makes techs more willing to leave a questionable unit in place when there’s no evidence to pull it.
Third, you get documentation. A recorded visual inspection isn’t just useful for the return decision — it’s also valuable if the unit does fail later, for warranty claims, for root cause analysis, for pattern recognition across a fleet.
The Policy Lever You Didn’t Know You Had
Most service operations trying to reduce no fault found returns in field service reach for one of two levers: add a depot test requirement (which just shifts costs downstream) or implement a second-approval process (which adds friction without adding information). Neither addresses the root cause. The economics are detailed in the hidden cost of field service misdiagnosis.
Instead, the actual lever is simpler: give the tech and the remote expert shared visibility before the return decision gets made.
You don’t need a new approval workflow. You need the engineer to be able to see what the tech sees. When that’s possible, the approval workflow you already have works — because it’s finally operating on real information.
Indeed, organizations that have implemented visual remote support for field diagnosis consistently report meaningful reductions in No Fault Found rates. Not because they changed the rules, but because they changed what the decision-maker could see.
No Fault Found in Field Service Is Expensive Every Time
Specifically, each no fault found return in field service costs somewhere between $300 and $1,500 per unit in depot test, clear, and reship — depending on your logistics network and equipment category. Multiply by your annual return volume. Multiply by your NFF rate. That’s the number sitting on the table.
The fix isn’t more process. It’s more visibility. Your field team isn’t approving bad returns because they’re making bad decisions — they’re making rational decisions with insufficient information. Change the information available and the decisions change with it.
That’s how you reduce unnecessary RMAs in field service. Not by adding checkboxes. By giving your people the ability to actually show each other what they’re looking at. The first-time fix rate math shows how fast those savings compound.
Viewabo is a live video platform built for field service teams. If your NFF rate is higher than you’d like, let’s talk.