What a Partial Fix Obliges You to Say

Why this matters

A customer does not experience a partial fix. They experience the truck leaving and the problem being better. Whatever the tech said in the driveway, what survives is the invoice, and if the invoice says "repaired" then in ninety days the customer is not calling about an unfinished job, they are calling about a failed one. The shop that eats that visit is not being generous, it is paying for a sentence it did not write. Every partial fix carries an obligation to say what you did not fix, and the only version of it that survives is the one on the document the customer keeps. Treat that as your standard regardless of what the law in your state requires, because the written record is what the argument runs on either way.

Three things get called a partial fix, and they owe different sentences

Sort which one you are in before you write anything, because the obligation is different in each.

Function restored, known residual left in place. The complaint is gone and something you found is still wrong: a worn part still in service, a marginal condition you did not correct, a root cause you chose not to chase because the customer declined the access. What you owe here is the residual named, its consequence, and whether your warranty covers it.

A stop-gap holding until a part or a return visit. Nothing is finished. The equipment is running on an interim arrangement that is expected to be removed. What you owe here is a date, the interim's limits, and what the customer should do if it does not hold.

One of several causes corrected. The symptom had more than one contributor and you addressed some of them. This is the one that produces the most disputes, because the symptom improves, which reads to everyone as success. What you owe here is the number: how much of the symptom you expected to remove, how much is left, and which cause owns the remainder.

The three sentences

Whatever the flavour, a partial fix ships with three sentences on the customer's copy.

1. What is still wrong. Named, located, and observable, so a different tech can confirm it.
2. What happens if it is not addressed. The consequence in the customer's terms - it comes back, it damages something else, it gets more expensive, it becomes a safety issue.
3. What the clock is. A return date, a re-check interval, or an expiry on the interim arrangement. A partial fix with no clock has no end, and something with no end is a permanent condition you installed.

Then one more line that is not a sentence to the customer but a decision inside your own paperwork: what your warranty covers here. If your standard labor term applies to everything on the invoice, and the invoice includes a partial fix, the customer will read the term as covering both, and you will be arguing about the wording of your own document.

When it should not leave the site as a partial fix at all

There is a gate above all of this. If the interim state is not safe unattended, it is not a partial fix, it is an out-of-service condition, and the equipment gets taken out of service rather than left running with a note. That includes anything where a protective or relief function has been bypassed, jumpered, or is in an unknown state, anything venting products of combustion into occupied space, and anything where a fault path could become energized while nobody is watching.

Taking it out of service means physically preventing operation, not asking. Where that means opening and securing an electrical disconnect, de-energize, lock and tag, and prove dead before contact under 29 CFR 1910.333(b)(2), and leave the isolation in place. Where it means isolating stored mechanical or pressure energy - a spring, an accumulator, a pressurized vessel - isolate and release the stored energy under 29 CFR 1910.147, which covers mechanical and stored energy and expressly excludes electrical utilization work at (a)(1)(ii)(C). Then tell the occupant, in writing, that the equipment is out of service and why. A life-safety finding is not a negotiating position and it is not softened by the customer's schedule.

The case: 75% better, and a warranty claim anyway

A shop is called on an intermittent fault the customer logs at about four events a week. The tech finds two contributing causes: one correctable on the spot in about 2.5 hours, one requiring a part with a lead time of six working days and about 4.0 hours to install.

The tech does the 2.5 hours, orders the part, and explains in the driveway that this is roughly three quarters of the problem and the rest needs the second visit. The invoice, written on the tablet at the curb, says: "Diagnosed intermittent fault. Repaired. 2.5 hours."

Over the next fortnight the customer's log runs at about one event a week. That is down from four, which is a 75% reduction against the original four-a-week base. Read that number carefully, because the customer read it wrong and so did the shop's own service manager: the remaining one event a week is not a residual of the repair that was done, it is the second cause running on its own. The first cause is gone. The improvement is not a partial success at one job, it is a complete success at half the job.

The part arrives on day six. The shop calls to schedule and the customer, now down to one event a week and busy, defers. Nobody re-sends anything in writing.

At week twelve, day eighty-four, the second fault escalates and takes the equipment down. The customer calls it a callback on a repair that is eighty-four days old, inside the shop's ninety-day labor term.

Here the shop's paperwork works against it three times. The invoice says "repaired," with no residual named. The warranty term is written to cover the invoice, and the invoice does not distinguish the cause corrected from the cause outstanding. And the deferral of the second visit exists only as a phone call. The shop absorbed the recovery, which ran about 9.0 hours.

Compare that against the 4.0 hours the second visit would have taken, but compare it as a direction rather than a ratio: the 4.0 hours were hours the customer would have bought, and the 9.0 hours were hours the shop ate. One is price and one is cost, and they are not the same currency. What is fair to say is that a job the customer had already agreed in principle to pay for turned into a larger job the shop paid for, and the mechanism was a one-word invoice line.

What would have prevented all of it, at a cost of roughly three minutes at the curb:

Corrected cause 1 (2.5 hours). Cause 2 remains: part on order, six working days, approximately 4.0 hours to install. Expect roughly one event a week until cause 2 is corrected. This invoice warrants the work performed on cause 1 only. Cause 2 is outstanding and is not covered.

Every clause there is something the tech already knew standing at the truck. The consequence line, the clock, and the warranty scope are the three that changed the outcome.

What flips the answer

If the second cause is genuinely unknown rather than identified. Then you do not have a partial fix, you have an unresolved diagnosis, and the honest line says the complaint may recur and the next step is further diagnosis, not a scheduled repair. Do not describe an unknown as an outstanding item with hours attached; the customer will hold you to those hours, and the record will read as a commitment you made.

If the customer is the one deferring. The record shifts from a partial-fix disclosure to a declined recommendation, and it needs the decline fields: who declined, when, by what channel, and delivered in writing that day. See related: How to Document a Recommendation That Was Declined. In the case above, the deferral at day six was exactly this moment and nobody treated it as one.

If the partial fix is a stop-gap you installed rather than a condition you left. Then you own the interim itself, and the clock is not advisory. State what the interim will and will not tolerate, and set the return date rather than leaving it to a call-back-when-convenient. An interim arrangement that quietly becomes permanent is your workmanship, not the customer's decision.

Where the sentence has to live

Not in the tech's notes. Not in the internal job record. On the document the customer keeps, which for most shops is the invoice, and in the same message that delivers it. A shop with a well-run internal system and a two-word invoice line has documented nothing that matters, because the only file anyone reads during a dispute is the one the customer already has.

If your invoicing template does not have a field for outstanding work and warranty scope, that is the change to make, not a reminder to techs to write more. A field gets filled. A reminder gets remembered on good days.

Verifying a partial fix before you leave

Read your own invoice line as if you were the customer, three months from now, on the day it comes back:

• Does it say what is still wrong, in a way that names a location or a component?
• Does it say what happens if that is not addressed?
• Does it carry a date, an interval, or an expiry?
• Does it say which part of the work your warranty covers, and by implication which part it does not?
• If a stop-gap is in place, does the customer know it is a stop-gap from the paperwork alone, without relying on the driveway conversation?
• Would a service manager reading only this invoice know whether an incoming call is a callback or a scheduled second visit?

The last one is the useful test, because that is the exact question somebody will have to answer under time pressure, using nothing but this document.

References

• 29 CFR 1910.147, the control of hazardous energy, for isolation of mechanical and stored energy, including the electrical utilization carve-out at (a)(1)(ii)(C)
• 29 CFR 1910.333(b)(2), safety-related work practices for work on or near energized electrical parts, general industry
• See related: How to Document a Recommendation That Was Declined; What You Owe When You Find Something Dangerous; The Temporary Fix Someone Left in Place; How to Tell Partial Progress From a Moved Symptom
• Whether a disclosure obligation attaches to particular work, and what satisfies it, is set by state law and can differ for consumer and commercial customers; have your own attorney review your invoice language once