How to Write a Job Note That Protects Both Sides

Why this matters

Two bad notes get written for opposite reasons and they cost the same. One overstates: it calls a finding a violation, a hazard, or a failure without saying what was measured, and a year later the shop is defending a determination it never actually made. The other understates: it buries a real warning inside a soft sentence, so the customer never registers that they were told, and when the thing fails the shop has a note proving it knew. The note that protects both sides is the one that keeps three kinds of sentence separate, so a reader can tell what you saw, what you concluded, and what you told them to do.

The three registers, and what blending them costs

• Observation is what an instrument or your own eyes recorded, with the conditions it was recorded under. It is the only part of a note that is not arguable.
• Inference is what you concluded from the observation, along with its basis and how confident you are. It is arguable by design, and marking it as inference is what makes it defensible rather than reckless.
• Instruction is what you recommended, by when, and what happens if it is not done. This is the part the customer acts on, and the part that has to be plain enough to survive being skimmed.

Blend them and both failure modes appear in one sentence. "Compressor is drawing way over and is going to fail" reads as an observation, is actually an inference, and carries a prediction with no time frame. If it fails next week the shop looks prescient and unhelpful. If it runs for three more years the shop looks like it was selling something.

Step 1: Write the observation with the condition it was taken under

Every measured value carries the state of the system when it was taken. A current reading at start-up, at steady state, and on a hot afternoon are three different numbers off one machine, and a number without its condition can be argued into meaning almost anything.

Say the instrument, the value, the moment, and the ambient or operating state in the same sentence. If you did not measure something and are reporting it visually, say that too. "Pitting visible on the contact faces, no measurement taken" is a complete and honest observation. "Contacts are burnt up" is a conclusion wearing an observation's clothes.

Skipping this step is what makes a note unusable to the next tech, who has no way to tell whether your reading was comparable to the one he just took.

Step 2: Mark the inference as an inference, with its basis

Use words that show the reasoning is yours: most likely, consistent with, my read is, I would expect. Then give the basis and the gap. "Most likely a failing contactor rather than a compressor problem, based on the pitting and the current settling to normal after a manual start. I did not check the capacitor, so this is a working read and not a confirmed diagnosis."

That sentence does two jobs at once. It gives the customer something real to act on, and it fixes the limit of what you claimed, so nobody can later say you diagnosed something you did not.

Step 3: Make the instruction specific and time-bounded

A recommendation with no time frame is not a recommendation, it is an observation with a suggestion attached, and customers treat it as optional forever. Name the action, the window, and the consequence: what to do, by when, and what happens if it is not done.

Where the answer genuinely is "this can wait," say that too. A note that flags everything as urgent teaches the customer to discount all of it, which is the mechanism by which a real warning gets ignored six months later.

Step 4: Record what you did not check, and why

This is the line most techs skip and the one that most often decides a dispute. A note that lists findings implies the rest was looked at and was fine. If you could not open a section, could not reach a component, or were asked not to move something, write it down with the reason.

"Did not open the indoor section; the access panel is behind stored material the customer asked me not to move" costs eight seconds and removes an entire category of future argument about what you should have found.

Step 5: Write the customer's decision in their words

Summarizing a customer's decision in your own words is where notes turn adversarial. "Customer refused the repair" and "customer said they want to wait until after the holidays and will call in January" are the same fact and they read completely differently to the customer standing in front of them a year later.

Quote them briefly, name the date, and note the channel. If they were shown something before deciding, say what they were shown. A decision line is the one part of the note the customer is most likely to eventually read.

Step 6: Use the heavy words only when you mean them, and mean them fully

Unsafe, hazardous, failed, code violation. These carry weight, and both misuses are expensive.

Used loosely, they are determinations you are not necessarily the one to make. Whether something violates code is decided by the authority having jurisdiction under whatever edition of the applicable code that jurisdiction has adopted, not by a tech in a crawlspace. "Does not appear to meet current requirements, worth having the inspecting authority confirm" says the useful thing without asserting the finding.

Used correctly, they carry a duty that the note alone does not discharge. A note calling a condition unsafe, written by a tech who left the equipment energized and running and said nothing out loud, is a contradiction that will be read back to you. If it is unsafe, act like it in the same visit: shut it down at its disconnect and prove dead with a tester checked on a known live source before and after the reading before tagging it out of service, per NFPA 70E-2021 section 120.5 for the proving sequence and 29 CFR 1910.333(b)(2) for the work practice on electric utilization equipment. For a gas odor, everyone leaves the area immediately, no switches or lights are touched, no phone is used inside, and the utility is called from outside; the note gets written after, from outside. The written notice still goes to the customer the same day, plainly, and a life-safety finding is never softened to protect a sale.

The same visit, written twice

Version one, as it usually gets typed at the end of a long day:

"Unit is shot, way overdue for replacement. Told the customer it is basically a fire hazard at this point. They do not want to spend the money. Not on us if it goes."

Four sentences. Zero observations. Three inferences stated as fact, including an age judgment nothing in the note supports. One heavy word used with no basis and no corresponding action, since the unit was left running. One characterization of the customer that reads as contempt. Nothing about what was measured, nothing about what was not checked, no time frame, and no evidence linked. Every sentence in it is a liability in a different direction: the fire-hazard line exposes the shop for leaving it energized, and the "not on us" line is the sentence a reader remembers.

Version two, same visit, same findings:

"At 2:05 p.m., ambient near 90 F, unit at steady state after about 20 minutes of run time, measured running current on the compressor circuit at roughly 1.15 times the nameplate rated load current. Pitting and arc marks visible on the contact faces; no measurement taken on the contacts. Voltage at the disconnect within the range on the nameplate.

Most likely the contactor rather than the compressor itself, based on the pitting plus current settling toward normal after a manual restart. I did not test the run capacitor, so this is a working read, not a confirmed diagnosis.

Recommend replacing the contactor and re-measuring running current at steady state afterward, before the next stretch of hot weather. If it is not replaced, the likely path is the contacts welding closed or failing to pull in, which shows up as a unit that will not start or will not stop.

Did not open the indoor section: the access panel is behind stored material the customer asked me not to move.

Advised the above on site at 2:20 p.m., quoted at an additional half hour of labor plus the part. Customer said: 'Let's do it, but I want to wait until my tenant is out next Tuesday.' Confirmed by text at 2:31 p.m., thread attached. Photos of the contact faces and the meter reading attached."

Twelve sentences: three observation, two inference and both marked as such, two instruction, one on what was not checked, and four recording the decision and the evidence attached to it. It took maybe ninety seconds longer to write than version one.

Read them against the two failure modes. Version one overstates and under-protects at the same time: it makes a hazard claim with no basis and no action, and it gives the customer nothing they could act on if they wanted to. Version two gives the customer a specific thing to do with a window on it, and gives the shop a fixed boundary around what was and was not examined. Neither party is worse off for it, which is the actual definition of a note that protects both sides.

How to check a note before you post it

• Underline every sentence and label it O, I, or A. Any sentence carrying two labels gets split. Any note with no O at all is a set of opinions.
• Find the heavy words. For each one, ask what you measured that supports it and what you did about it on the visit. If either answer is empty, the word comes out or the action goes in.
• Read the decision line as the customer. If it would make them defensive, rewrite it as a quote and a date.
• Check for the not-checked line. If the note has no boundary, it implicitly claims the whole system was assessed.
• Ask whether the next tech could act on it cold. A note whose readings carry no conditions cannot be compared to anything, which means it will be re-measured from scratch and the visit taught nobody anything.

References

• Whether a condition violates code is a determination for the authority having jurisdiction under the code edition that jurisdiction has adopted; a tech's note can describe what was observed and route it to the inspecting authority
• NFPA 70E-2021, section 120.5, for the live-dead-live proving sequence, which binds through your employer's electrical safety program and through 29 CFR 1910.333(b)(2) for electric utilization equipment
• See related: Writing a Clear Customer-Facing Service Note, How to Write Field Notes the Office Can Actually Use, The Record That Survives a Year of Memory