Records, Handover & Close-out

The repair fixes today. The record is what is left afterwards, and it is the only part of the visit that is still working in six months.

Chapter 15 made this the ninth step of the method and called it the one with no immediate payoff and the largest compound return. This chapter is what actually goes in it, and why so much of what gets written is worthless.

Why records are bad: three readers, one paragraph

Naming them separately is what makes the problem tractable:

• The next technician — very often you, months later, on the same machine. Wants the diagnostic path: what the symptom was, what got ruled out, what turned it, and under what conditions it was tested.
• The customer — and specifically whoever runs the machine at night, not whoever signed your worksheet. Wants what was wrong, what you did, what to watch for, and what is still outstanding.
• The business — contract, warranty, stores, planning. Wants time, parts, the facts that decide chargeability, and compliance values.

None of those is optional and none of them is served by "replaced sensor, tested OK".

What a close-out is actually for

Six lines cover nearly every job:

1. Reported — the symptom in the customer's words, including the pattern. "Stops mid-cycle, six to eight times a shift, since Monday."
2. Found — the root cause, not the failed part.
3. Ruled out — the eliminations. This is the line that saves the next visit and the one that is always missing.
4. Did — the work, and the part numbers actually fitted.
5. Outstanding — anything you have not done, including things you noticed and did not act on.
6. Conditions — what the machine was doing when you proved it: load, rate, temperature, duration.

The eliminations and the conditions are the two lines that turn a receipt into evidence, and they are the two that get dropped when somebody is writing this in a van at the end of a long day.

Time, parts, and the part you took off

Accuracy here matters well beyond the invoice. Labor hours by asset are how a plant finds out which machines are eating the maintenance budget. Parts consumption is how stores decide what to hold, and a technician who records "seal kit" instead of the part number is why the van does not have one next time. Failure records are how anybody ever calculates a mean time between failures.

Three specific habits:

• Record the part you fitted, by number, not by description.
• Record what you took off separately — fitted, ordered and removed are three different facts and the last one is routinely lost.
• Keep the failed part. Tag it, photograph it in place before removal wherever you can. Chapter 12's argument — that the worn part is a written record of the conditions that killed it — does not stop being true when the part reaches the van. On a warranty claim it is the only evidence there is.

Chargeability, and the words that decide it

This is the field-service part that nobody teaches and that costs real money.

Your report frequently decides whether a job is warranty, contract or chargeable. That decision is not yours to make on site, and you should not try — but the language you use will make it for you whether you intend it or not.

Wear and tear, misuse, abuse, customer damage, fair wear: these are contractual terms with defined meanings, and writing one down is closer to a legal opinion than to a description. Written casually they either hand away a valid claim or accuse a customer of something in a document they will read.

Describe the mechanism instead — exactly as Chapter 16 recommends for delivering the same news out loud:

"Filter last changed four months ago against a three-monthly schedule. Silencer blocked with carried-over debris."

That is accurate, it is neutral, it is checkable, and it lets the people whose job it is decide what it means commercially. It is also the version you would be comfortable reading out later, which is a useful test.

Compliance records

Some records are not notes, they are proof that work was done to a standard, and they have retention periods and legal weight:

• Insulation resistance results and calibration certificates (Chapter 4)
• Refrigerant handling records (Chapter 11)
• Permits and isolation certificates (Chapter 2)
• Pressure systems, lifting equipment, safety-system proof tests

For all of these, the value without its conditions is nearly worthless — the same point Chapter 4 made about thermal surveys and Chapter 13 about vibration. An insulation reading with no temperature, humidity or test voltage cannot be compared with the next one, and comparison is the entire reason it was taken.

Red-lining

Chapter 14's point, restated because this is the chapter where it gets skipped: if you found the drawing wrong, mark it and return the marked copy. The correction is worth more than the repair, because the repair fixes today and the correction fixes every visit after it.

Handover

Two kinds, and the second is the one that goes wrong.

Finished work hands over to the person who will still be there — what was wrong, what you did, what to watch for, what is outstanding. Chapter 16 covers the conversation.

Unfinished work is harder and more important. Anything half-done must exist as a physical, visible state and a written note, never as something you meant to mention: a lock still applied, a guard removed, a fuse pulled and in your pocket, a machine that will run but should not. Chapter 2's transfer of isolation is the formal version of this.

And when you hand over an unfinished diagnosis, hand over the evidence rather than the symptom: what you checked, what it ruled out, and what you would do next. That is worth far more than a description of the fault, and it is the same structure as a Fault Log entry — which is not a coincidence.

Closing a job out.

1. Write it before you leave, not later

   In the van outside is fine; three days later is not. The eliminations and the conditions are the first things memory loses and the two things the record exists for.

2. Write the six lines

   Reported, found, ruled out, did, outstanding, conditions. If a line is genuinely empty say so rather than omitting it — "nothing outstanding" is a fact, and a blank is ambiguous.

3. Record the root cause, not the part

   "Fitted seal kit" is what you did. "Seal hardened and dragging when warm, shortening the stroke" is what was wrong. The second one is what makes the entry usable when the same symptom appears on head 2 next year.

4. Record parts by number, and separate fitted from removed

   Fitted, ordered and removed are three different facts. Descriptions instead of numbers are why the van does not carry the right part next time.

5. Keep and photograph the failed component

   Tagged, and photographed in place before removal where you can. It is the only physical evidence of what happened, it exists once, and both the warranty claim and the next diagnosis may need it.

6. Describe mechanisms, never contractual conclusions

   No "wear and tear", "misuse" or "abuse". State what you observed and what it did. The commercial decision belongs to people whose job that is, and your neutral description is what lets them make it correctly.

7. Record compliance values with their conditions

   Safety

   Temperature, humidity, test voltage, speed, load, duration — whatever the measurement depends on. A value that cannot be compared with the next one has not been recorded, it has been written down.

8. Close permits and hand over unfinished work physically

   Safety

   Every permit closed or formally transferred, every isolation either removed or handed over with its record. Anything half-done must be a visible state and a written note, never a thing you meant to mention.

9. Hand over the evidence, not the symptom

   For anything unresolved: what you checked, what it ruled out, what you would do next. That is worth more than a description of the fault to whoever picks it up, and it is the same structure a Fault Log entry uses.

• Writing the report for whoever signs it

  Why

  The person holding the worksheet is standing in front of you and everybody else is abstract, so the report drifts toward what satisfies them — which is usually the shortest version. The reader who needed the detail is not in the room and will not complain for eight months.

• Leaving it until later

  Why

  There is always a next call, and writing it up properly at the end of the week feels like the same job done in one sitting. It is not the same job: the eliminations and the conditions are gone within hours, and what gets written is a summary of the outcome rather than a record of the reasoning.

• Closing with 'no fault found'

  Why

  It is honest and it feels like the only available answer when the machine ran perfectly for ninety minutes. But on its own it tells the next person nothing, and it invites the assumption that the customer imagined it. The same visit with its eliminations attached is a genuinely useful record.

• Deciding chargeability on site

  Why

  You have the most information and it feels efficient to reach the conclusion while you are there. But it is a contractual judgment rather than a technical one, and writing "misuse" in a report is not a description — it is a position, recorded in a document the customer will read.

• Recording the value and not the conditions

  Why

  The number is the thing you measured, so the number gets written down. Without the load, the temperature or the test voltage it cannot be compared with the previous one — and comparison is the entire reason insulation, vibration and thermal readings are taken at all.

• Binning the failed part

  Why

  The machine is running, the job is done, and the old part is rubbish in your hand. It is also the only physical evidence of what happened, it exists exactly once, and the claim or the repeat failure that needs it turns up after it has gone.

Six questions. Each is about what a record has to do for somebody who is not in the room, which is the whole reason it exists.