Technician Notes That Are Worth Reading Next Time

A useful technician note contains 4 things and most notes contain only 1 of them. The most valuable of the 4 is what you ruled out, and it is almost never written down because eliminating a cause does not feel like work that was done.

The short version

Notes get written to close a job. "Attended, carried out repair, tested OK" satisfies the form and tells the next person nothing.

The next person is a different technician, eight months later, at seven in the evening, standing in front of the same piece of equipment with a customer waiting.

Writing for that reader rather than for the form is the whole difference, and it takes about the same number of words.

The 4 things a note should contain

What	Why the next visit needs it
What you found	The cause, not the task. "Blocked drain" beats "cleared drain"
What you ruled out	Saves the next technician repeating your diagnosis
What you would check first next time	Your judgment, which is the part nobody else has
What you could not do, and why	Access, parts, authorization. It explains the gap

Row two is the one that is missing almost everywhere, and it is worth more than the other three together on any intermittent fault.

What you ruled out is the valuable half

And it feels like nothing, which is why it goes unrecorded.

A technician spends forty minutes on a unit that is cycling short. They check the charge, the airflow, the door seals and the defrost, find nothing wrong with any of them, and eventually replace a thermostat.

The note says the thermostat was replaced. Forty minutes of elimination has disappeared.

When the same symptom returns in March, the next technician checks the charge, the airflow, the door seals and the defrost again, because nothing told them not to.

Two lines would have prevented it: charge and airflow checked and correct, seals good, defrost operating.

Record the cause, not the task

Because the task is already on the invoice.

"Replaced contactor" is what was done. "Contactor burned, pitting on both poles, unit had been short cycling for some time" is what was found, and it points at something upstream that may still be there.

The second version is what makes a pattern visible across visits. A piece of equipment with three burned contactors in two years has a problem that is not the contactor.

Roopairs holds equipment asset records with job history attached to the equipment, which is what puts those three notes in one place rather than in three separate jobs nobody reads together.

The note is not a legal document

Which is why length is the wrong target.

Three specific sentences beat a paragraph of careful phrasing. A technician standing at a piece of equipment will read three lines and skim anything longer.

What matters is that the words are concrete. "Some corrosion" is unusable and "corrosion on the evaporator, worst at the return bend" is a place to look.

Avoid the two habits that make notes unreadable: abbreviations only the writer uses, and part numbers with no description. A number that has been superseded means nothing to somebody reading it a year later.

Write it at the equipment

Because detail decays within the hour.

A note written in the van forty minutes later contains what the technician remembers, which is the outcome and not the observations that led to it.

The elimination detail, the readings, the thing that looked slightly wrong and turned out to be irrelevant, all of that is gone by the time the next job starts.

Which makes this a capture problem as much as a writing one. A notes field that is quick to reach on a phone gets used at the equipment, and one that requires closing several screens gets used in the van.

Photographs carry what words cannot

Three worth taking every time.

The nameplate, which settles the model question permanently. The fault, which shows condition better than any description. And the installation, which is what explains recurring problems at a site.

A photograph of a condenser installed against a wall with no clearance explains four years of failures in a way a note never will.

They are also faster than typing, which matters more than anything else about them.

Test your own notes

1. Take 10 of your own from a year ago on equipment you have not attended since
2. Ask what you would do differently at that equipment today because of them
3. Count how many gave you anything beyond what the invoice already said

Most service companies running this find the number is low, and it is not a criticism of the technicians. Nobody was ever told who the reader was.

What to change on Monday

One sentence added to the form, and one instruction.

Add a prompt rather than a blank box: what did you find, what did you rule out, what would you check first next time.

And tell people who the reader is. A technician writing for a colleague at seven in the evening writes differently from one filling in a field, and the instruction costs nothing.

The pain starts around your third or fourth technician, which is where the next visit is nearly always somebody else, and the note becomes the only handover there is.

Roopairs runs a product tour where you can see per-equipment records with the full visit history attached.

What service companies in the trade say

“The usability of the platform is another standout feature. It's user-friendly, easy to train new staff on, and integrates seamlessly with our existing systems. The learning curve was minimal.” — Joshua Bennett, Branch Manager

Also worth reading

• Credit Notes and Customer Credits, Kept Straight
• Handing Off an Account: What the Next Tech Needs
• Why field service technician productivity starts on the job site

Frequently asked questions

What makes a technician note useful?

Four things: what you found rather than what you did, what you ruled out, what you would check first next time, and what you could not do and why. Most notes contain only the first.

Why does "what you ruled out" matter most?

Because it saves the next technician repeating the diagnosis. Forty minutes of elimination disappears when the note records only the part that was replaced, and the next visit checks all of it again.

What is wrong with recording the task?

The task is already on the invoice. "Replaced contactor" is what was done, and "contactor burned, pitting on both poles, unit short cycling" points at something upstream that may still be there.

How long should a note be?

Three specific sentences. A technician at a piece of equipment reads three lines and skims anything longer, so concrete words matter more than length or careful phrasing.

When should it be written?

At the equipment. A note written in the van forty minutes later contains the outcome rather than the observations that led to it, and the elimination detail is already gone.

What should be photographed?

The nameplate, the fault, and the installation. A condenser installed against a wall with no clearance explains four years of failures in a way no note will, and photographs are faster than typing.