Pause before you promise
A request can sound small when it arrives as a message between meetings. “Could you take a quick look?” may mean five minutes, or it may involve research, revisions, and a decision from someone else. If your day is already full, an immediate yes can create two problems: the new task may get more attention than it needs, and work you have already promised may quietly slip.
A brief acknowledgment gives you room to assess the request without ignoring it. You might say, “I’ve seen this. I’m checking today’s commitments and will let you know what I can do.” If the person is waiting for an urgent decision, say when you can respond. The aim is not to delay everything; it is to replace an automatic promise with an informed one.
Find out what the request actually requires
Before moving tasks around, clarify the result the person needs. Ask what they want delivered, when it will be useful, and whether they need a finished piece of work or a first pass. If “today” is the deadline, ask what happens if they receive it tomorrow. This is a practical question, not a challenge to the person making the request. It helps distinguish a fixed deadline from a preference.
Estimate the effort in broad terms rather than pretending you can predict every minute. Consider preparation, coordination, review, and the time it takes to return to your existing work afterward. Also check whether someone else has information or approval you would need. A request you cannot complete independently may need a different plan from one you can finish in a single sitting.
Compare it with commitments already on your list
Look at the work you planned to finish, not just the open space on your calendar. Meetings, focused work, follow-ups, and deadlines all use time. Identify which commitments are fixed and which could move. It may help to write a quick three-line snapshot: what must be done today, what can reasonably wait, and what depends on someone else. This makes the trade-off visible before you change your plan.
The question is not simply, “Can I fit this in?” It is, “What would I delay or reduce to fit this in?” If the answer is a deadline or a promise to another person, bring that consequence into the conversation. When priorities are set by a manager or team lead, ask them to help choose rather than making the choice silently and hoping no one notices.
Offer a concrete option
A useful response states what you can do and what it affects. For example: “I can send a first pass by 3 p.m., but the report I planned to finish today would move to tomorrow. Which should take priority?” Another option is to offer a narrower contribution: “I can review the main question today and do a detailed edit later.” Specific options make it easier for the requester to decide whether speed, scope, or another task matters most.
Sometimes you need to decline the requested timing. Keep the response direct and courteous: “I can’t complete this today alongside the two items due this afternoon. I can start tomorrow morning, or we can discuss which deadline to change.” You do not need to justify every hour of your schedule. Give enough context to support a decision, and avoid promising an evening or weekend fix that you cannot reliably provide.
Update the plan and close the loop
Once a priority is agreed, put the new request in the same system you use for other work. Note the deliverable, the next action, the agreed timing, and any task that has moved. Tell affected people about changed expectations before their deadlines pass. Even a short update is better than leaving them to assume the original plan is still intact.
If new requests repeatedly overwhelm the day, look for a pattern rather than treating each one as a personal planning failure. You may need more room in your schedule for incoming work, a clearer process for deciding priorities, or a regular check-in about workload. The goal is not to create a perfectly interruption-free day. It is to make each new commitment a deliberate choice that you and others can understand.
