- Published on
How to Respond to an Unexpected Task Without Dropping Everything
- Authors

- Name
- Valo Focus editorial team
An unexpected task can arrive with language that makes it sound automatically urgent: "quick," "ASAP," or "can you just." Sometimes it genuinely is urgent. Often it is important to the requester but not more important than the work already on your plate. The useful skill is not refusing every interruption. It is making the trade-off visible before you abandon a commitment that someone else also depends on.
Pause long enough to understand the request
Before switching tasks, identify the outcome, deadline, audience, and consequence of delay. "Can you look at this?" may mean a two-minute check, a detailed review, or a decision that requires information you do not have. Ask what must be true when the task is complete and when it is needed.
If the request is genuinely time-sensitive, say what you will do first. If it is not, offer a specific review time rather than a vague promise. "I can look at the draft after the 2 p.m. meeting and send comments by 4" is more dependable than "I'll try to get to it."
Compare it to the work already promised
Name the task it will displace. You may be able to fit a small request into a planned buffer, but larger work needs a conscious choice. Tell the requester or your manager: "I can take this today, but the supplier summary will move to tomorrow. Is that the right trade-off?" This is not a complaint. It gives the person setting priorities the information needed to decide.
Avoid the tempting response of doing both by working invisibly later. That habit hides capacity problems, makes future requests seem costless, and eventually reduces the quality of all the work.
Choose an appropriate response path
There are usually four options: do it now, schedule it, delegate it, or clarify that it belongs elsewhere. Use the smallest path that meets the real need. A colleague may only need a link, not a full analysis. A recurring request may need a shared template or an owner, not another ad hoc rescue.
When you cannot help, give useful direction. Point to the right person, relevant documentation, or the information needed for a decision. A clear handoff is more respectful than accepting work you cannot complete well.
Confirm who can authorize the change
The requester may not own the commitment you would displace. If a colleague asks for a detailed review today but your manager has promised a customer delivery, explain the conflict to the person who can set the priority. Offer a bounded alternative while that decision is pending: "I can check the two assumptions in ten minutes; the full review needs an hour and would move the customer summary."
For a real emergency, follow the established response process first. For ordinary requests, avoid treating a missed reply as approval to drop other work. Write down the agreed outcome, owner, and timing so the interruption does not create two incompatible expectations.
Close the loop deliberately
After handling the interruption, update your task list and calendar. Record the new commitment and any displaced work. Take one minute to write the next step of the task you paused; this reduces the mental cost of returning to it later.
If unexpected tasks repeatedly come from the same source, look for a pattern. Perhaps a deadline is unclear, a team lacks a shared intake process, or a responsibility is missing. Bring the pattern to a planning conversation with examples rather than waiting until frustration makes the issue feel personal.
Final takeaway
Unexpected work deserves a response, not automatic surrender of the day. Clarify the outcome and deadline, state the trade-off, choose the smallest useful path, and update the plan you interrupted. This keeps you responsive while protecting the commitments that already matter.