Guide
Callbacks: How to Cut Rework with Better Job Notes
Set a simple standard: 3 photos (before, during, after), 3 bullets on work performed, one line on next step, and one line on any scope change plus customer agreement. Require notes and photos before closeout so they can't skip. When notes and photos live in one place tied to the job, callbacks turn from guesswork into proof. When you're ready for software, look for notes and photos tied to each job and easy mobile entry so techs complete on-site.
For teams with repeat visits and rework where no one can see what was done or approved.
Next: Roll out the 3-photo and 3-bullet standard on 10 jobs; then check whether notes and proof are still getting lost between field and office.
The situation
A customer calls back with a problem. No one can see what was done or approved, so you send a tech again or argue without proof.
Callbacks eat margin and trust. Good notes and photos turn “we never said that” into “here’s what we did and what you agreed to.”
Set a simple standard: three photos (before, during, after), three bullets on work performed, one line on next step, and one line on any scope change plus customer agreement. Require it before closeout so techs can't skip. When notes and photos live in one place tied to the job, the office and the next tech see the same thing.
What strong job notes include
- Before and after photos—so you can see condition and what changed.
- What was repaired or replaced—specific enough that the next person (or the customer) understands.
- Any customer approvals or changes—especially scope or price changes so there’s no “I didn’t agree to that” later.
- One line on what was recommended next (e.g. filter change in 3 months, or follow-up visit).
A simple standard
- Three photos minimum: before, during, after. Same angle so comparison is easy.
- Three bullets on work performed—not an essay, just enough to close the loop.
- One line on the next recommended step so the customer and the office know what’s coming.
- If the scope changed, one line on what changed and that the customer agreed (or a photo of the signed change).
When tools help
Once photos, approvals, and notes live in different places, callbacks turn into guesswork. Tools that tie everything to the job fix that.
- Notes and photos tied to the job so the office and the next tech see the same thing.
- Easy access for office follow-up so you’re not digging through texts or paper.
- Customer history in one place so repeat visits don’t start from zero.
- Optional: customer-facing link so they can see what was done and what’s recommended.
Optional: Browse the FSM category page for more examples.
Mistakes to avoid
- Using only text with no photos—when there’s a dispute, photos win.
- Leaving notes on personal phones—they don’t help the office or the next tech.
- Skipping customer sign-off on changes—get a quick “yes” or a note so scope creep doesn’t become a callback.
Quick win (no new tool)
Small steps you can do today before trying a new app.
- Take before / after photos on every job.
- Write three bullets on work performed (parts + steps + issue found).
- Get customer sign-off on changes (text or initials).
Take the FSM quick check
Quick checkSee if Field Service Management tools are right for your team.
Take the FSM quick checkRelated guides
If this helped, you might also want to check out:
Related templates
Copy-paste scripts and checklists for this pain: