The next technician should arrive knowing what happened last time. A practical guide to job notes that help your crew prepare and keep customers informed.
In this guide
Picture a homeowner who calls your office about a problem that has returned. She explains what happened, mentions the technician who visited last month, and asks whether someone can come back.
Your office books the appointment. The next technician arrives and asks, “So, what seems to be the problem?”
There may be a perfectly reasonable explanation. A different technician handled the first visit. The office was busy. The original notes only say “checked system.”
But the customer hears something else: nobody passed along what she already told you.
Good job notes help prevent that conversation. They give the next person enough information to pick up where the last person left off.
Write for the person who wasn’t there
The technician who completed a job usually remembers the details that afternoon. A month later, with dozens of service calls in between, memory becomes a poor filing system.
Notes should make sense to someone who has never visited the property.
“Unit acting up again” tells that person very little.
A more useful note would be:
Customer reports the upstairs system stops cooling during the late afternoon. It was operating when I arrived. Completed today’s inspection and recorded findings in the equipment record. Asked the customer to note the time and thermostat reading if the problem returns. Office to call Thursday to check whether it happened again.
That note separates what the customer reported from what the technician observed. It also identifies the next step.
You do not need polished prose. You need a record someone else can act on.
Capture what happened, including what remains unfinished
A useful service record explains the customer’s concern, the work performed, and the outcome. If something remains unresolved, say so plainly.
Consider this hypothetical plumbing visit:
Customer reported a slow drip beneath the kitchen sink. Found moisture at the supply connection. Replaced the connection component and checked for leakage afterward; none observed during the check. Customer also asked about replacing the faucet. Replacement was not included in today’s work. Office to prepare a separate estimate.
The final sentences matter. Without them, the customer may expect a faucet estimate while the office has no idea one was requested.
Make room for the details that affect the next visit: which equipment was serviced, relevant model information, parts used, and where supporting photos or measurements are stored.
Avoid turning every note into a long report. A straightforward job may need only a short paragraph. An unresolved problem deserves enough detail to explain what was checked and what still needs investigation.
Keep customer requests separate from commitments
“The customer wants us back Friday” and “We confirmed a Friday appointment” are different statements.
When notes blur that distinction, the office can inherit a promise nobody actually made.
Use direct language:
Customer requested Friday morning. Appointment has not been confirmed. Office will contact the customer with availability.
Apply the same care to pricing and additional work. If an estimate is needed, record that it is needed. If the customer approved a specific scope, record the approval through your normal process.
A job note should help explain the record. It should not leave the next employee guessing whether a conversation amounted to authorization.
Leave a clear handoff
“Follow up” is easy to write and easy to overlook.
A useful handoff names the person or role responsible and gives a reasonable time frame:
Office: contact the customer by Thursday afternoon about the requested faucet estimate.
Or:
Returning technician: review the previous visit’s findings before attending and confirm the required part is available.
The owner should not have to discover unfinished work by reading every note at the end of the week. Put the next action into whatever task or scheduling process your business actually uses.
The note supplies context. The assigned task makes the next step visible.
Before closing a job, ask: Does anybody still owe this customer something?
If the answer is yes, make that responsibility clear.
Write professionally, even when the visit was difficult
Job notes should describe facts and relevant requests.
“Customer was difficult” does little to help the next employee. It can also encourage someone to arrive expecting an argument.
A useful alternative is:
Customer questioned the diagnostic charge. Explained the quoted fee and requested that the office call to discuss the remaining billing concern.
That tells the office what happened and what needs attention without making a judgment about the person.
Record only the personal information needed to perform the service. Follow your business’s approved process for sensitive access information rather than placing door codes or similar details in broadly visible notes.
Make reviewing notes part of the next visit
Writing better notes accomplishes little if nobody reads them.
Give technicians a chance to review the previous service record before arriving. The office should check outstanding commitments when a returning customer calls.
A prepared greeting can be simple:
“I reviewed the notes from the last visit. Has the same problem continued, or has anything changed?”
The customer can then explain what is new instead of rebuilding the entire history.
Start with five recently completed jobs. Ask whether another employee could understand what happened and identify anything still owed to the customer. Where the record falls short, improve the process rather than expecting everyone to remember more.
If you’re looking for a more organized way to manage customer records and daily service work, explore Service Command HQ.
Your next technician should arrive with the benefit of the last technician’s work. Clear notes make that possible.