Handing a Job Over Between Technicians: The Checklist

Handing a job over between technicians works when you transfer state, not stories. The outgoing tech leaves the site in a defined, documented condition; the incoming tech reads a written 60-second brief attached to the job before they get out of the van. That brief needs four things and no more: what is done, what is not done, what is unsafe or energised right now, and what the next decision is. Everything else (photos, test results, materials, customer quirks) lives on the job record where both people can find it without asking. If your handover happens on a phone call, you do not have a handover. You have a rumour with a two-person labour cost attached.

Why handover is where the rework starts

One tech, one job, one day is a self-cleaning system: the person who made the mess remembers the mess. Once a job spans two people or two days, that memory stops being free. It gets written down or it evaporates.

Rework on multi-tech jobs almost never comes from bad workmanship. It comes from three gaps:

• Duplicated work. Tech B redoes something Tech A finished, because nothing said it was finished. Cheap in minutes, expensive in margin.
• Assumed work. Tech B assumes something is done because it looks done. A circuit that looks terminated, a joint that looks made off, a first fix that looks complete behind a board. This is the one that costs real money.
• Lost decisions. The customer agreed to move the socket 400 mm left. Tech A knows. Tech A is now on another site. Tech B installs it where the drawing says.

All three are state-transfer failures. None of them are fixed by trying harder.

The 60-second brief: what the next tech needs before they open the van door

The incoming tech gets one screen. If it takes longer than a minute to read, it will not be read. Keep it to five lines:

1. Status in one sentence. First fix complete on ground floor, kitchen ring pulled but not terminated at the board.
2. Safety state. What is live, what is isolated, where the lock-off is, who holds the key. Say it explicitly even when the answer is: everything dead, board off, lock on, key in van 3.
3. The next action. One thing, not a list of five. Terminate kitchen ring, test, then second fix upstairs if time.
4. Blockers. Missing materials, waiting on the plasterer, customer working from home in the back bedroom until 14:00.
5. Customer context. The one thing that will cause a complaint if it is not known. Dog in the utility room. Do not park on the gravel. Call before you drill.

That is the whole brief. Everything deeper hangs off the job record underneath it.

Write it at the end of the job, not the start of the next

The handover note is the last ten minutes of the outgoing tech's day, on site, before they pack the van. Written the next morning from memory, it is fiction. Written from the driveway, it is accurate. This is the single highest-leverage rule in this article and it is the one most firms skip.

The site-state checklist: what condition you leave the job in

A handover is a physical thing before it is a paperwork thing. Agree one standard for the whole firm so nobody has to guess what left it tidy means for that particular colleague.

• Nothing energised that is not labelled. Live is labelled live. Dead is labelled dead and locked off. No exceptions for I will be back tomorrow anyway.
• Nothing half-terminated without a physical marker. Tape, a tag, a cap, a label. An unterminated conductor that looks tidy is a trap for the next person.
• Cables labelled at both ends before the ceiling closes. The plasterer does not care about your memory.
• No open holes, no exposed conductors, no unsupported tray. The customer lives here between your two visits.
• Materials for tomorrow staged where the next tech will look — and listed in the note, because in the van is useless if it is a different van.
• Photos taken before anything gets covered. More on this below.
• Test results recorded now, not reconstructed at certification time.

The safety handover is not optional and it is not verbal

Electrical isolation between shifts is the one part of a handover with a legal shape rather than a cultural one. In the UK, safe isolation under the Electricity at Work Regulations means proved dead with an approved voltage indicator to HSE guidance note GS38, locked off, key held, and a caution notice fitted. In Sweden the same duty sits under Elsäkerhetsverket's electrical safety rules plus Arbetsmiljöverket's workplace requirements. In Australia and New Zealand it is AS/NZS 4836 and the equivalent lock-out/tag-out practice.

The detail differs by country. The principle does not: the person who applied the lock is the person who removes it. If a shift change means someone else has to work on that installation, the incoming tech proves dead again and applies their own lock. You do not inherit somebody else's isolation on the strength of a text message. Write down which locks are on, which are yours, and where the keys are.

Where photos and notes should live (and where they must not)

One place, attached to the job, visible to whoever holds the job next. Not the group chat. Not the tech's camera roll. Not an email thread the office started.

Group chats fail as a record for a structural reason: they are ordered by time, not by job. Three weeks and four jobs later, the photo of the wall before the plasterboard went on is 900 messages up, in a thread about a different address, on a phone that may have left the company. The photo exists. It is not findable. For record-keeping, unfindable and non-existent are the same thing.

What earns its keep on a handover:

• Before-cover photos. Every wall, floor or ceiling void, photographed with something in frame for scale and position, immediately before it is closed. These pay for themselves the first time somebody drills into a cable run or a customer disputes a route.
• The board, wide and close. Whole board plus a readable shot of the schedule and any temporary labelling.
• Anything you are unsure about. Photograph the confusion. Tech B will resolve in ten seconds what would otherwise cost you a phone call.
• Test values as data, not as a photo of a scribbled pad. A number in a field can be searched, checked and pulled into certification. A photo of handwriting cannot.
• Voice notes are fine for capture, useless as a record. Nobody scrubs four minutes of audio to find one sentence. Transcribe it onto the job.

Why a phone call is the most expensive handover method there is

Everyone defends the call because it feels fast. Do the arithmetic on one handover.

The call costs roughly double the labour of the note and produces nothing. Ten to twenty minutes of combined tech time, gone, with no artefact at the end. Then it happens again next Tuesday, because there is still no record. Then again when the customer queries the invoice and nobody can say what was done on which day. The note costs one person three minutes and answers every future question for free.

The deeper problem is that a call is synchronous. It only works when both people are free at the same moment, which on a working site is almost never. So the call slips: it happens at 19:40 from a sofa, half-remembered, and the important detail is the one left out. A written handover gets read at 07:15 by someone standing on the drive, which is exactly when it is useful.

Keep the call for the decision, not the record. Do we run it through the joist or box it in is a call. First fix is done is a note.

Multi-day and multi-tech are two different failures

They need the same note but they break differently, so know which one you are managing.

• Multi-day, same tech. The enemy is your own memory plus the site changing overnight: other trades move your materials, the plasterer covers your first fix. Fix it with photos before cover and a written next action.
• Multi-tech, same day. The enemy is two people working on the same installation with different pictures of it. Fix it with explicit ownership: who owns which circuits, which rooms, which locks. Two techs on one board without split ownership is a near miss waiting to happen.

Three or more people across a week is both at once. At that scale the job card is not admin. It is the only shared source of truth you have.

Making it stick when nobody likes writing things down

Handover discipline dies from friction. Three fixes, in order of effect:

• Make the note a set of fields, not a blank box. Five prompts beat one empty text area every time. People will fill in fields they would never write a paragraph into.
• Make it work with no signal. Plant rooms, basements, lift shafts and half-built houses have no coverage. If the note needs bars to save, it does not get written. An offline-first field app that queues the note and photos on the device and replays them when signal returns removes the excuse — that is one of the things OdinTask is built around, with handover notes, photos, test records and the day's checklist all hanging off the same job card instead of living in someone's phone.
• Make reading it the incoming tech's first action. If the brief is the first thing on the job card, it gets read. If it is three taps deep, it does not.

One habit worth the effort: at the end of a multi-day job, read your own handover notes back. They are a free audit of how the job actually ran, and day two is usually where the estimate went wrong.

If you want handover notes, before-cover photos, test records, assignments and the customer's history on one job card that works without signal, start a free trial of OdinTask and run a single multi-day job through it. That is enough to tell you whether it beats the phone call. More field workflow guides are on the blog.