Job Handoff Between Techs SOP

Purpose

A job handoff happens whenever one tech finishes part of a job and a different tech picks it up: a multi-day install, a return visit, a shift change, or a callout that reassigns the work. Done poorly, the second tech walks in blind, repeats diagnostics, misses what the first tech already found, or contradicts what the customer was told. Done well, the customer never feels the seam. This SOP defines the minimum information that must travel with a job so the next tech starts where the last one stopped.

Scope

Applies any time a job moves from one tech to another before it is complete. Covers planned handoffs (multi-visit jobs, scheduled return trips) and unplanned ones (a tech called out, a job reassigned mid-day). Covers what the outgoing tech records, what the incoming tech reviews, and what the dispatcher confirms in the middle.

Roles and responsibilities

Procedure

1. Outgoing tech records the job state before leaving

The moment a job is going to pass to someone else, the outgoing tech documents where it stands, while it is fresh. The handoff record must carry:

• What was done so far, in plain detail.
• What is left to do, with enough specifics that a stranger could pick it up.
• What was found (diagnostics, root cause, surprises) so the next tech does not re-diagnose.
• Parts used, ordered, and still needed.
• Access and site notes (where the shutoff is, gate code, dog, parking).
• What the customer was told and any commitment made on timing or price.

The last item is the one most often dropped and the one that burns you. If the first tech promised a return by a certain day or a certain fix, the second tech must know it or the customer catches you contradicting yourself.

2. Capture it where the next tech will look

The handoff lives on the job record, not in a text the next tech will never find. Photos of the in-progress state, notes on the job, parts marked. If it is buried in one person's phone, it did not transfer. Put it where the work happens so the incoming tech sees it without asking.

3. Dispatcher confirms the record is complete before reassigning

Before the job is handed to the next tech, the dispatcher or lead checks the handoff record is actually usable. An empty or vague record gets sent back. This is the gate that prevents a tech from arriving to a blank job. Thirty seconds of checking saves the second tech a wasted trip.

4. Incoming tech reviews the handoff before arriving

The incoming tech reads the record before they show up, not in the driveway. They confirm:

• They understand the scope and what is left.
• They have or can get the parts needed.
• They know what the customer was promised, so they reinforce it instead of contradicting it.

If the handoff is unclear, the incoming tech raises it with the dispatcher or the outgoing tech before driving out, not after.

5. Direct contact for anything the record cannot carry

For complex jobs, a thirty-second call between the two techs beats any written note. Some context (a hunch about what is really wrong, a customer's mood, a tricky workaround) is faster spoken. The written record is the baseline; a quick call fills the gaps on the hard ones.

6. Incoming tech confirms continuity with the customer

On arrival, the incoming tech signals continuity: they know who the customer is, what was done, and what comes next. The customer should feel like one company is handling their job, not two strangers. "I see the previous visit found the issue and ordered the part; I am here to finish it" turns a worrying seam into confidence.

Watch out for

• No record of what the customer was promised. The single most common handoff failure. Always carry the commitments.
• Handoff notes in a private text thread. If it is not on the job record, the next tech cannot find it. Put it where the work is.
• Re-diagnosing from scratch. When findings do not transfer, the second tech wastes time and the customer pays twice in patience. Record the diagnosis.
• Silent reassignment. Moving a job without a complete handoff sends a tech in blind. The dispatcher gates this.

References

• See related: Morning Dispatch Huddle SOP
• See related: End of Day Closeout Routine SOP
• See related: Capture Tribal Knowledge Before a Key Tech Leaves
• Trade-standard practice for field-service job continuity and shift handoffs