Technician Running Late

The operating outcome

Use this playbook to keep technician running late consistent, visible, and owned. The office should finish with a reliable job record, a realistic customer promise, and a clear next action.

Before acting

Confirm the customer, location, requested work, urgency, history, access, commercial terms, and the person authorized to make decisions. Do not turn a customer description into an unverified technical diagnosis.

Key checkpoints

• Confirm the technician’s safe estimated completion and travel time.
• Contact the affected customer before the promised window expires.
• Offer a revised window, another qualified technician, or a reschedule based on policy.
• Update the board and downstream customers, not only the next stop.

Office workflow

• Review the information already available before contacting the customer again.
• Resolve missing facts that affect safety, qualification, access, timing, material, or price disclosure.
• Set the job status, priority, assigned owner, customer communication promise, and escalation path.
• Update every downstream appointment or team member affected by the decision.
• Close the loop in the job record instead of relying on chat or memory.

Record and handoff

• Keep the original customer wording, confirmed facts, warnings, commitments, and accepted timing.
• Make the next owner, due time, and unresolved exception easy to see.
• Review repeated exceptions for training, staffing, routing, or policy improvement.