Home services and trades
Technician job notes: how to write them so they are useful to you and to AI
By SourceX Editorial · Updated
Short answer
Technician job notes are useful when someone who was not on the job can tell what the customer reported, what the technician found, the cause, what was done and whether the fix worked. Use that five-part structure on every call and keep gate codes and personal comments out. Consistent notes help callbacks, warranty disputes, training and AI alike.
Key takeaways
- A useful note answers five questions: what was reported, what was found, the cause, what was done, and the result with any next step.
- Notes written on site before the next call are more accurate than notes written from memory at the end of the day.
- Gate codes, alarm codes, health details and opinions about customers belong outside free-text notes.
- Pick-lists for cause and repair, plus a short free-text explanation, give both consistency and detail.
- Never rewrite old notes to tidy them; original records keep their value only while they stay original.
What a useful technician note does#
A useful technician note lets a person who was not there understand the visit well enough to act on it: the next technician on a callback, the office handling a warranty claim, a service manager reviewing a dispute. If a note cannot support those uses, it will not support anything more ambitious either.
Notes are also the most detailed record a trades company keeps of real diagnostic work. Invoices show what was charged and job types show the category, but only the note explains why a technician replaced one part rather than another.
A five-part note template#
The five-part template covers what was reported, what was found, the cause, what was done, and the result with any next step. It works for HVAC, plumbing and electrical calls, and it maps onto the custom job forms most field service platforms let you build.
Keep each part short. The goal is completeness, not length, and a sentence or two per part is usually enough on a routine call.
| Part | What to write | Prompt for the technician |
|---|---|---|
| Reported | The customer's complaint in their own words, and when it started | What did the customer say was wrong? |
| Found | Observations, readings and equipment details | What did you see, measure and test? |
| Cause | The diagnosis and how you confirmed it | Why did it happen, and how do you know? |
| Done | Repair, parts used and anything left unfinished | What did you replace, adjust or clean? |
| Result and next | Test after the repair, options offered, follow-up needed | Does it work now, and what should happen next? |
Illustrative: a poor note and a strong note for the same call#
Illustrative: the same fictional no-cooling call, written two ways, shows the difference the template makes. Both versions describe one visit by one technician to a two-story house.
The strong note lets the next technician start where this one stopped. It also records an unsold recommendation, which matters if the same system fails again next summer. A tool learning from many notes like the strong one can link symptoms to causes; from the poor one it can learn nothing.
| Part | Poor note | Strong note |
|---|---|---|
| Reported | No AC | Upstairs not cooling since last night; downstairs fine |
| Found | Checked unit | Outdoor unit not running; contactor pitted; capacitor reading below its rating |
| Cause | Left blank | Failed capacitor; contactor wear consistent with short cycling |
| Done | Fixed | Replaced capacitor and contactor from truck stock |
| Result and next | Customer happy | Cooling restored and checked at the supply registers; recommended a thermostat and airflow check for short cycling; customer declined for now |
What the found part should capture in each trade#
The found part of a note carries the most diagnostic detail, and what belongs in it differs by trade. A short trade-specific prompt on the job form reminds technicians which details the next person will need, without turning the form into a long checklist.
| Trade | Details worth recording | Often missing |
|---|---|---|
| HVAC | Equipment make, model and serial; refrigerant type; pressures, temperatures and airflow readings; filter and coil condition | Readings taken but not written down |
| Plumbing | Fixture or line affected; pipe material; water heater make and age; camera inspection findings and where in the line they sit | Location of the problem in the line |
| Electrical | Panel make and condition; circuit affected; voltage and load readings; wiring type; code issues observed | Code issues noted verbally but not recorded |
Habits that make notes less useful#
Most weak notes come from a handful of habits, not from careless technicians. Each habit has a simple fix that a service manager can coach on a ride-along or in a toolbox talk.
- Canned text pasted on every job, which buries the one detail that mattered.
- Personal abbreviations that only one technician understands.
- Notes written from memory at the end of the day, after several other calls.
- Findings texted to the dispatcher instead of entered on the job.
- Photos with no caption saying what they show or why they were taken.
- Price talk and opinions about the customer mixed in with technical findings.
- Callbacks logged as new jobs with no reference to the original visit.
What to keep out of job notes#
Job notes should hold technical facts, not access codes or personal details about customers. Free-text notes are copied into reports, printed on some invoices, pulled into exports and read by far more people than technicians expect.
Gate codes, alarm codes, lockbox combinations and key locations belong in a restricted access field, if your platform has one, not in the note. Health details, such as a customer's oxygen equipment or mobility needs, should be recorded only where safety requires it and in a field with limited visibility. Opinions about a customer's character never belong in a business record.
The rule pays off later. Notes free of personal details are easier to share with a warranty administrator or a buyer in diligence, and they need less removal work before any outside use.
How to get technicians to write better notes#
Technicians write better notes when the job form does part of the work and the feedback comes from their own jobs. Mandating longer notes rarely helps on its own and usually produces more canned text.
- Turn the five parts into required fields on the job form in ServiceTitan, Housecall Pro, Jobber or whichever platform you use.
- Add pick-lists for common causes and repairs, with free text for the explanation.
- Allow voice dictation, with a quick read-through before the job is closed.
- Require the note before a job can be marked complete, while the technician is still on site.
- Review a few notes with each technician regularly, using their own jobs as examples.
- Use callbacks as the teaching moment: compare the first note with what the second visit found.
Why consistent notes raise the value of your records#
Consistent notes raise the value of a company's records because they turn individual visits into a history that can be searched, compared and learned from. Inside the business that means faster callbacks, better training and stronger evidence in warranty disputes.
Consistency is what turns notes into data. When every technician records the cause in the same field from the same short list of cause codes, the company can answer questions it could not before: which installs fail early, which parts come back and which technicians fix the problem on the first visit.
Outside the business, AI developers building diagnostic and field service tools look for real sequences of reported problem, finding, cause, repair and outcome. Those records can be licensed, not sold, and the company keeps ownership. The SourceX Enterprise Data Value Framework counts domain expertise, human-generated signal and data cleanliness among the drivers that increase value, and notes kept free of personal details lower the privacy burden and the work in the Preparation step of the SourceX five-step transaction.
Frequently asked questions
How long should a technician note be?
Long enough to cover the five parts and no longer. On a simple maintenance visit that may be a few lines; on a difficult diagnosis it may be a short paragraph per part. Completeness and clarity matter more than word count.
Are voice-to-text notes good enough?
They can be, if the technician reads them before closing the job. Dictation is faster in the field and often captures more detail than typing on a phone, but it mishears model numbers and trade terms, so a quick check is needed every time.
Should we go back and fix old notes?
No. Editing historical notes changes the record of what was known at the time and weakens it as evidence. Improve notes from now on, and if old cause codes are inconsistent, build a separate mapping table rather than changing the originals.
Do customers see technician notes?
Sometimes. Many field service platforms can print selected fields on invoices or include them in customer summaries. Check which fields are customer-facing in your settings, and keep internal observations in fields that stay internal.
Should notes mention the price discussion?
Record what was offered and what the customer chose, ideally linked to the estimate, but keep sales commentary out of the technical note. Separating the two keeps the diagnostic record clean and the sales record easy to find.
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.