A good handoff answers four questions: What is the job? Who owns it? What does the next person need? What happens afterward? Use these checks to keep those answers visible throughout the day.

This is a workflow aid for your team. It does not replace technical procedures or update any jobs in your workspace.

0 of 12 checkedCheck off as you review. Refreshing starts a new checklist.

Before the first call

Give the day a workable plan.

Start with today’s commitments and the people available to keep them. A full calendar still needs room for an unexpected diagnosis or a delayed arrival.

Confirm who is available.Review technician availability, relevant skills, and any job that needs a second person. Identify who can make reassignment decisions.Check the promises already made.Review arrival windows, urgent calls, callbacks, and visits waiting on parts. Flag a commitment that the current schedule cannot meet.Review geography and realistic travel time.Look at service addresses together. Account for travel between visits, access restrictions, and the expected length of each job.Choose how the office will handle a delay.Agree who updates the schedule and who contacts the customer. Keep an owner on the change until the new plan is confirmed.

Before each visit

Send context with the technician.

The next person should be able to understand the job without reconstructing a conversation. Keep the handoff short, specific, and attached to the right record.

Match the customer, contact, and service address.Check the actual visit location, unit or suite, contact number, and access instructions. A billing address is not always the service address.Describe the reason for the visit.Record the customer’s concern, the system involved, and the agreed scope. Separate an observed symptom from an unconfirmed diagnosis.Make the relevant history easy to find.Connect prior notes, equipment details, open proposals, and any known parts requirement. Confirm coverage details before presenting them as a promise.Confirm the assignment and customer update.Make sure the technician has the job details. Check whether the expected arrival message was sent through the configured channel; follow up on delivery problems.

After the visit—and before the day ends

Leave an owner on the next step.

A technician leaving the property and a job being fully resolved are different events. Review what happened and make the remaining work visible.

Capture what was completed and what remains.Review the work notes, recorded parts and time, and any unfinished checklist items. Keep a return visit or unresolved issue clear in the job record.Review the invoice or proposal that follows.Check the scope, customer, amounts, and supporting details. Assign who will prepare or send the document when another person needs to finish it.Put a name and a date on follow-up.For parts, a return visit, an unanswered proposal, or another customer commitment, record a responsible person and the next review date.Check the exceptions together.Review unassigned work, delayed arrivals, incomplete jobs, and failed customer updates. Carry forward an explicit next action instead of relying on memory.

Try it with the team

Review the friction.
Keep what helps.

After a week, ask the office and field team which information they still had to chase. Review a few delayed jobs and unfinished follow-ups together. Improve the handoff that caused the confusion, then run the checklist again.

Start small: fewer clarification calls, clearer ownership, and fewer jobs waiting without a next action. Compare similar work over a consistent period before treating a change as a trend.

Give the day a workable plan.

Send context with the technician.

Leave an owner on the next step.

Review the friction.Keep what helps.

Review the friction.
Keep what helps.