Managing Interruptions on a Job
Why this matters
Interruptions are the hidden drain on a field day. The chatty customer, the dispatch call, the "while you're here" request, the phone buzzing in your pocket. Each one feels small, but together they break concentration, stretch every job, and are how a tech who is technically fast still finishes late. The skill is not refusing interruptions. It is handling each one in a way that protects the work without making the customer feel brushed off.
Know which interruptions are which
Not every interruption deserves the same response. Sort them fast.
- Urgent and relevant (a real safety issue, a dispatch emergency, the customer pointing out something that changes the job): stop and deal with it. This is not a distraction; it is the work.
- Relevant but not urgent (a new request, a question about a second issue): acknowledge it, park it, and return to it at a natural break. Do not let it derail the current task mid-step.
- Not relevant (social chatter, a personal call, a notification): defer it. Be polite, but keep your hands and your head on the job.
Handle the chatty customer without being rude
A friendly customer is good for business; a constant conversation is bad for your timeline. You can have both manners and momentum.
- Engage at the right moments, not during precision work. A few words during setup or cleanup is fine. Mid-measurement is not.
- Use honest, friendly redirects. "Let me get through this part and I'll explain what I'm finding" keeps them warm and buys you focus.
- Give them a job if they want to help or hover: clearing access, deciding on an option, getting out of the work zone. It satisfies the urge to be involved without crowding you.
The goal is a customer who feels attended to and a tech who still gets to concentrate.
Protect concentration during the critical steps
Some moments cannot absorb an interruption without a mistake or a redo.
- Diagnosis, live measurement, and anything safety-critical are heads-down. Finish the step before you look up.
- If you must pause mid-step, mark your place: note where you stopped, what is apart, what comes next. Resuming blind is how a fastener gets missed or a wire gets crossed.
- Silence the avoidable. Put the personal phone on do-not-disturb during focused work. Most buzzes are not the job.
Manage the "while you're here" without losing the day
The added request is the most common scope interruption. Handle it cleanly.
- Trivial and adjacent: a quick courtesy, within reason, is fine.
- A second real job: acknowledge it warmly, then treat it as its own job with its own write-up and estimate. Folding free work into the current call is how techs run chronically behind. See related: The Five-Minute Job That Takes an Hour.
Interruption playbook
| Interruption | Response |
|---|---|
| Real safety or dispatch emergency | Stop, handle it, then resume |
| New request or question | Acknowledge, park, return at a break |
| Chatty customer mid-precision-work | Friendly redirect, engage at setup or cleanup |
| Personal phone notification | Do-not-disturb during focused work |
| "While you're here" second job | Treat as a separate job, write it up |
Get back on track fast
The cost of an interruption is not just the interruption. It is the time to find your place again afterward. Minimize it.
- Before you turn away, freeze the state in your head or in a quick note: where you stopped, what is open.
- After the interruption, take five seconds to re-orient before acting, instead of charging back in and missing a step.
- If interruptions are piling up and the job is slipping, name it: "I want to give this the attention it needs, so let me focus and I'll catch you up in a few minutes." Honest beats flustered.
A tech who manages interruptions well looks unhurried because nothing knocks them off their line. See related: Setting Up the Work Area for Speed.
References
- See related: The Five-Minute Job That Takes an Hour
- See related: Setting Up the Work Area for Speed
- See related: The Efficient Diagnosis vs the Rabbit Hole
- Trade-standard practice: scope and quote added requests as separate work rather than bundling unbilled