Why Some Faults Are Safe to Tolerate and Some Aren't
Why this matters
Not every fault demands an immediate, full repair, and pretending otherwise makes you the tech who scares customers into unnecessary spending. But some faults look small and are not, and treating those the same as a cosmetic annoyance is how a minor-looking issue becomes an emergency call. The skill is knowing which category a given fault falls into, and explaining that distinction to a customer in a way that builds trust instead of sounding like a sales pitch either direction.
The real question is not severity, it is failure mode
The instinct is to rank faults by how bad they look right now. The better question is: what does this fault do if it is left exactly as it is? A fault that stays flat, self-limits, or only affects comfort or convenience is a different risk than one that compounds, cascades, or removes a safety margin. Ask three things about any tolerable-looking fault before you decide it is actually tolerable.
Question 1: Does the fault involve a genuine hazard category
If the fault touches gas, stored pressure, stored energy, height, structural integrity, or electrical combined with water, it is never in the "safe to tolerate" category, regardless of how minor it currently looks. A small gas smell, a slightly bulging pressure vessel, a breaker that trips only occasionally under a specific load: these get treated as real until disproven, and the safety action comes first, before any further diagnosis or discussion of tolerating it. This is not a judgment call to weigh against convenience; it is a category exclusion.
For everything outside that hazard category, continue to the next two questions.
Question 2: Does it get worse on its own, or does it stay flat
A fault that is self-limiting, meaning the same trigger produces the same result every time with no escalation, is a fundamentally different risk than one that compounds:
- Self-limiting example: a cosmetic rattle that has been present and unchanged for a long time, with no effect on function.
- Compounding example: a small vibration that is wearing a mounting point, which will loosen further, which increases the vibration, which accelerates the wear. Each cycle makes the next cycle worse.
If the fault is genuinely flat over a meaningful observation period, tolerating it with monitoring is reasonable. If the fault is on a compounding path, even a small current impact, tolerating it means accepting a worse and more expensive failure later, on a schedule you do not control.
Question 3: Does it consume a safety or capacity margin that protects against something else
Some faults do not look dangerous on their own because something else is still covering for them. A backup or redundant system quietly compensating for a failed primary is the clearest version: everything still works, so it looks tolerable, right up until the backup is also needed and is not there, or the backup itself fails next and there is nothing left standing behind it.
If tolerating the fault means you are now running on a margin that used to be a backup, that is not a tolerable fault, it is a ticking one. Flag it plainly: "this still works today because something else is compensating for it, and that only holds until that other thing is also under load or also fails."
Field key
| Category | Tolerate with monitoring | Do not tolerate |
|---|---|---|
| Hazard type (gas, pressure, stored energy, electrical + water) | Never | Always act first, diagnose second |
| Trend | Flat, self-limiting, unchanged over an observed period | Compounding, worsening, escalating |
| Margin | No dependency on a backup or redundant system | Consuming a safety margin or backup capacity that was meant for something else |
| Function impact | Cosmetic or convenience only | Function-critical or safety-critical |
How to have the customer conversation either way
- Tolerable: "This is a real finding, it is not urgent, and here is specifically what would change that." Naming the specific trigger that would escalate it (a certain symptom, a certain time frame) gives the customer something concrete to watch for, instead of a vague reassurance.
- Not tolerable: show the evidence for why, using the framework above, rather than a bare assertion of urgency. "This looks minor today, but it is on a path that gets worse each cycle, and here is why" lands as a genuine finding, not a scare tactic.
The credibility comes from applying the same three questions consistently, every time, regardless of whether the honest answer that day is "this can wait" or "this cannot."
References
- OSHA general industry guidance on hazard categorization and immediate-action triggers
- Trade-standard practice for risk-based maintenance prioritization
- See related: Chase the Nuisance Fault or Let It Go Decision Tree; Neglect or Defect, Who Bears the Cost Decision Tree