Your Job Notes Are Garbage — And It's Costing You

Last year I pulled twenty return visit records out of Jobber on a Friday afternoon. I wanted to know how much re-diagnosis time we were running. I expected a minor annoyance. It wasn't.

Fourteen of those twenty jobs had original notes that were useless. Two sentences, no panel condition, no photos, no deferred work, nothing about what the customer had actually described. The techs had logged that a job happened. They had not logged what they found. The second tech walked in cold every time.

What a Job Note Actually Costs You (When It's Wrong)

I'm obsessive about attribution. Every marketing channel at Reeves Electric has a tracking number. Every ad has a UTM tag. I can tell you the booking rate on LSA calls versus organic, the average ticket by source, what the truck wrap on the 2023 Transit is actually producing. I do that because you can't improve what you don't record.

Shallow job notes are the same problem, applied to the field. The chain breaks at the job site. You see it on the return visit invoice. You hear it when your tech asks a customer to re-explain something they described in detail eight months ago.

Here's what it costs on a five-truck shop. A return visit where the second tech re-diagnoses from zero runs 30 to 45 minutes longer than one where they had real notes. Multiply that across fourteen of twenty return visits. It adds up fast — not catastrophic per job, but consistent, and invisible because nobody's counting.

That's before the upsell you missed. When the original tech doesn't note that the panel is a 1990s Zinsco with breakers failing to trip on overcurrent, the second tech doesn't know to bring it up either. The customer never gets the conversation they needed. The job that should have turned into a panel replacement stays a service call until the panel fails and they call someone else.

And before the review. Customers remember what they told you. Every single time.

The Lie Techs Tell Themselves When They Close a Job

In month two of Reeves Electric — February 2022 — my NPS was a 4. Out of 100. Work was getting done, invoices were getting paid, and I had no idea the experience was that broken. I started answering every call myself, reviewing every interaction. The patterns were obvious once I was actually looking. The problem wasn't the work. It was the intake, the communication, the follow-through — everything I couldn't see because I hadn't been recording it.

Shallow job notes are the same failure mode. The tech finishes the work, the work is good, and they close the job with three sentences because the job is done in their head. The note is an afterthought. Most owners let it happen because the invoice went out and nothing visibly broke.

What I do now with call recordings: every week, my dispatcher and I pull four calls — two that booked, two that didn't — and tag what went right and what went wrong. That practice more than anything else got our NPS to 81 by month nine. Note quality fails the same way intake fails. You don't review it because everything felt fine. But "felt fine" is not the same as "was documented."

Techs tell themselves they'll remember. They won't. The next tech definitely won't. The customer absolutely will.

The Note Schema That Fixed It (Five Fields, No Exceptions)

I built this on a whiteboard with my techs in early 2023, after a return visit I'll describe in a minute. It lives inside the job record in Jobber. The tech cannot mark the job complete without filling it out. The software doesn't enforce quality — nothing does that except you — but it blocks the shortcut of closing with an empty field.

Five fields. No exceptions before close.

1. Condition of equipment at time of visit. Not "panel okay." The actual condition. Breakers original or replaced? Signs of heat damage, corrosion, double-tapping? Age of panel if visible on label? Federal Pacific or Zinsco gets noted explicitly, every time, regardless of what the primary complaint was.

2. Deferred work the customer declined. If the tech identified a problem and the customer said "not today," it goes here — with the approximate scope and price discussed. When that customer calls back in six months, whoever picks it up sees the conversation we already had. We're not starting over.

3. Photos attached. Minimum two — one of the primary work location before, one after. More on anything with visible damage, anything unusual, anything that becomes a dispute later. Photos are not a substitute for the written note. They're the exhibit the written note refers to.

4. Next recommended service window. What should we follow up on, and when? If there's no follow-up warranted, the tech writes "no follow-up indicated." The field can't be blank. "No follow-up indicated" is a legitimate answer. Blank is not.

5. What was not checked and why. This is the one most shops don't have. If the tech couldn't access the subpanel because the homeowner had furniture in front of it, that goes here. If the customer declined the full inspection, that goes here. It protects you legally. It tells the next tech where the gaps are before they walk in.

A tech who fills out five fields in four minutes is giving you a job record worth reading. A tech who writes "all good" in 20 seconds is giving you a liability waiver that protects nobody.

Enforcement in dispatch is simple. Before a job gets marked complete, my dispatcher does a 30-second scan on the close. Not reading every word — just checking that all five fields exist and aren't single-sentence placeholders. If they're empty or clearly phoned-in, the tech gets a message before they drive to the next job. "Hey, field two is blank on the Elmwood job — did the customer decline anything?" That prompt alone changed behavior faster than any training I ran.

Better Software Will Not Save You

When shops have bad note quality, the instinct is to look at the tool. I've watched shops buy a third software layer on top of an existing stack to "fix documentation," and what they end up with is expensive garbage where they used to have cheap garbage.

The right core stack for a five-truck residential service shop is Jobber or Service Fusion. Both have note fields that do the job. Both let you attach photos. Both let you build custom fields if you want the schema enforced at the form level rather than by dispatcher review. Neither one will make your techs write better notes. That's a training and accountability problem, and no software subscription fixes that.

The shops buying new tools to fix this usually haven't done the diagnosis first. They've gotten a bad return visit or two, had a customer complaint, and reached for something visible to do. But they haven't pulled 40 return visits, read the original notes cold, and counted how many would have helped a different tech walk in prepared.

Do the audit first. Pull your last 20 return visits. Read the original notes — not the return visit notes, the notes from the first time you were at that address. Ask one question for each one: could a different tech have walked in cold and known exactly what they were dealing with?

My bet is fewer than 4 of 20 pass. If I'm wrong, you're ahead of almost every shop I've seen. If I'm right, you have your scope. Then decide if you need new software. You probably don't.

The Return Visit That Changed How I Train Techs

Late 2022. We went back to a house in East Austin we'd been to six months earlier. Older home, 1960s original panel, customer had called about flickering lights in one part of the house. First visit: loose lug on a double-pole breaker, tightened it, tested the circuit, closed the job.

The note from that visit: "Found loose connection in panel. Tightened and tested. All circuits functioning normally."

Three sentences. No mention of the panel's age. No note that it was a 60-amp sub with original breakers that were well past their service life and already showing heat marks on two lugs. No deferred work field because we didn't have one yet. No photo of the panel interior.

Six months later, customer calls back. Different tech responds. No useful information from the first visit, so he asks the customer to describe the problem from the beginning. She explains it. Then says — and I know this because I listened back to the call recording — "I feel like I already explained all of this to the guy who came last time."

That line showed up in the review that night. "Nice guys, good work, but felt like they didn't have any record of what we talked about last time." Four stars. I pulled the job record and found the three sentences. Listened to the original intake call, which actually had good detail — the customer had mentioned the age of the panel, the specific room, that she'd had this problem once before. The tech heard it. None of it made it into the notes.

That Friday I sat down with my crew, wrote five fields on a whiteboard, and told them this was a hard close requirement starting Monday. No new software. One whiteboard session, one new dispatcher checkpoint, one week to get used to it. A month later the notes were unrecognizable — we went from most records having two or three lines to most records having panel condition, deferred work, photos, and a follow-up note. I could actually read them cold.

What to Do Monday Morning

Pull your last 20 return visits out of Jobber or Service Fusion. Read the original job notes. Ask one question per record: could a different tech have walked in cold and known exactly what they were dealing with?

From there, three moves:

Draft your schema this week. The five fields I use are a starting point. Adjust for your trade, your call types, your most common return-visit failures. Keep it at five fields or fewer — more than six and techs start treating it like a form to defeat.

Add the close checkpoint in dispatch. Whoever marks jobs complete adds a 30-second scan to that step. Are the fields there? More than one sentence each? If not, message the tech before they leave the driveway.

Add note quality to your weekly review. Same session where you review call recordings and booking rates — pull five closed jobs every Friday, read the notes, flag anyone still writing "checked panel, all good." Make it consistent. That's what actually moves the number.

The note problem is not complicated. It's invisible — until the return visit invoice hits, or the four-star review lands from a customer who remembers the conversation your notes forgot.

---

FAQ

If my techs are already slammed between jobs, how do I get them to fill out five fields without it blowing up their schedule?

A tech with a clear schema fills out five fields in three to four minutes. The time problem is usually a training problem — techs without a defined structure spend longer staring at a blank text box than techs who have five specific questions in front of them. Build the fields into the job record as explicit prompts, not an open note box. If a tech is genuinely running four calls a day with no buffer, the notes aren't your only scheduling problem.

We use Housecall Pro and the note field is just a text box — do I need a different tool to enforce a schema?

No. Paste the five field labels into a note template inside Housecall Pro and tell techs to fill it out before close. It won't auto-enforce — your dispatcher still has to check — but it puts the structure in front of the tech every time they open the close screen. That's enough. I built our schema inside Jobber the same way before I added any custom fields.

How do I handle notes on jobs where the tech found nothing wrong?

"Could not reproduce" is a legitimate finding, but it needs context. What did the tech check? What conditions were present? What did the customer describe, and how does that compare to what the tech observed? "Could not reproduce — customer reported intermittent trip on kitchen circuit, tested under load for 15 minutes, GFCI and breaker both held, panel shows no signs of heat damage, recommend monitoring and callback if it trips again" is a useful record. "Could not reproduce" alone is almost worthless on a return visit. Same conclusion, completely different record.

My best tech has been with me six years and writes the worst notes on the crew — how do I have that conversation without losing him?

Directly, and without making it personal. Not "your notes are bad" — "here's the standard we're running, here's why it exists, here's what I need from every tech including you." Show him the return visit where bad notes created a problem. The pattern is the point, not the blame. When I had this conversation with one of my six-year guys in early 2023, I walked him through the East Austin job. He didn't push back. He just hadn't known it mattered to me. If a tech genuinely pushes back after you've explained it clearly, that's a different conversation about what kind of shop you're running.

Is there a liability angle to this?

Yes, and it cuts both ways. Detailed notes that describe what you found, what you recommended, and what the customer declined are generally protective — they show you did a professional assessment and documented it. The "what was not checked and why" field exists partly for this reason. Sparse notes leave you with nothing to point to when someone disputes scope. Talk to your insurance carrier if you want a formal opinion. My read: document thoroughly, you're in a better position. Document poorly, you're not.

How do photos fit into this — substitute for written notes or supplement?

Supplement. Always. A photo of a panel interior shows what it looked like. It does not tell the next tech which breaker was running hot, what the customer said about the problem, or what work was declined. Photos are exhibits. Written notes are the record. Both fields are required in our schema. Neither one satisfies the other.