Job handovers between techs: notes that stop rework

The question appears in every field-service community sooner or later: "Tech A roughed it in Tuesday, Tech B finishes Thursday, and B walked in blind. Customer had to explain the job to my own company. How do you hand over?" The cost of bad handovers hides in rework, second site visits and the credibility hit when your business looks like two strangers. Fixing it is not about writing more; it is about writing four specific things in a place the next person cannot miss. Here is the system, plus the photo habits that make notes half as necessary.

The four-line handover standard

A usable handover answers exactly four questions. What did I do? What is left? What will surprise you? What did I promise the customer? Four lines, written at clock-off while the job is fresh, beats a paragraph written from memory that night. Make the four prompts part of the job completion flow so they are asked, not remembered.

The "surprises" line earns its keep: the isolator that does not isolate, the dog that bites, the ceiling with no crawl space. It is the line that saves the second tech an hour and the business a callback.

Photos are handover notes that cannot lie

Before-you-leave photos of the work state, the parts left on site and anything opened up cost thirty seconds and answer questions no prose can. The pattern that works: wide shot of the area, close-up of the stopping point, photo of any label or model plate involved. With a field app that attaches photos to the job automatically, the next tech scrolls the story on the drive over instead of ringing the last one mid-job.

Notes live on the job, or they do not exist

The forum horror stories share one root cause: the handover existed, in a text thread, a voicemail, a whiteboard. If notes are not attached to the job record itself, they are unavailable at the only moment they matter, on site, next visit. One home per job, everything attached, searchable later. This is also your evidence trail when a warranty callback or dispute surfaces months after everyone forgot the details.

Checklists carry the technical handover

For staged work, rough-in, fit-off, commission, a shared checklist on the job does the heavy lifting: B sees precisely which items A ticked. Checklists also survive personnel surprises, sickness, resignations, the apprentice sent alone, because the job explains itself. Pair them with the safety forms already on the job so the handover includes hazards, not just tasks, in line with guidance from bodies like the UK Health and Safety Executive on communicating site risks between workers.

Make it culture: the two-minute rule

The system fails only when writing it feels optional. The rule that sticks: no clock-off without the four lines and three photos, two minutes, every job, including your own as the owner. Review handovers in toolbox talks occasionally, praising the note that saved a visit. Within a month the crew writes them for each other rather than for you, which is the point: the business stops depending on any single memory, including yours.

Frequently asked questions

What should a job handover note contain?

Four lines: what was done, what remains, what will surprise the next person, and what was promised to the customer. Written at clock-off while it is fresh, plus three photos of the stopping point. That standard covers the overwhelming majority of handover failures without asking anyone to write essays.

Where should handover notes live?

On the job record itself, full stop. Notes in text threads, voicemails or whiteboards are unavailable at the only moment that matters: on site, at the next visit. If your crew works from a field app, the note is already in the right place the moment it is typed.

How do I get techs to actually write them?

Make the four prompts part of clock-off so they are asked rather than remembered, and enforce one rule: no clock-off without the note and photos. Then spotlight the saves in toolbox talks, the note that prevented a second visit. Habits stick when the crew sees the note saving them, not the boss.

The bottom line

The pattern across every topic on this blog repeats here: the businesses that win are not working harder, they are keeping better records and letting systems carry the routine. Start with one change this week, measure it for a month, and let the results argue for the next one. And if you want the whole loop, scheduling, field app, safety and invoicing in one place, start a free SKEDS trial and test it on a real week of your own jobs.