Treat the request as a starting point, not a task
A message such as “Can you put together a summary?” describes an intention, but it may not describe a schedulable piece of work. The summary could be a few notes for one colleague or a polished document for a group. Putting “write summary” on the calendar immediately creates an appearance of commitment without resolving that difference.
Before assigning time, restate the request in your own words. Identify the intended result, who will use it, and what decision or activity it supports. If you cannot describe the finished work in a sentence, keep it in an intake list rather than placing it among confirmed tasks. This is not a way to delay the work; it is a way to avoid scheduling the wrong version of it.
Ask for the details that change the work
A short scope check usually needs five answers: What is the deliverable? Who is the audience? What material should it include or exclude? When is it needed, and why then? Who will decide that it is complete? These questions help distinguish a quick draft from a larger assignment with research, revisions, or approval steps.
You do not need to send a long questionnaire for every request. Ask only about uncertainties that would change your estimate or approach. For example: “Is this a one-page recap for the team, or a presentation for the client?” If the requester is unsure, offer two workable options with different levels of effort. Concrete choices can be easier to respond to than an open-ended request for more detail.
Clarify whether a stated date is the final handoff or an intermediate review. A review date may require a draft well beforehand, while a final deadline may leave room for a simpler process. Avoid treating either interpretation as settled until you have checked.
Look for hidden steps and dependencies
Once the output is clear, sketch the steps between the request and completion. Gathering inputs, making decisions, drafting, checking details, and incorporating feedback may all take time. You do not need a detailed project plan, but you should know which steps require your attention and which depend on someone else.
Note any missing access, files, decisions, or approvals. A task that takes an hour of hands-on work might still span several days if you must wait for source material or a review. Mark those dependencies explicitly rather than filling your calendar with uninterrupted work time and hoping everything arrives.
It can help to separate your estimate from the lead time. Your estimate covers the effort you expect to spend; lead time includes waiting and handoffs. Both matter when deciding whether a requested date is workable.
Compare the request with existing priorities
Scope alone does not determine where a request belongs. Before accepting a date, look at work you have already committed to and at the space your week needs for routine responsibilities and interruptions. Ask whether this request is more important than something already planned or whether it can follow that work.
If the requester wants it sooner than your capacity allows, make the trade-off visible. You might propose a narrower first version, a later delivery, or a pause on another task if the relevant people agree. “I can deliver a brief outline on Thursday, or a fuller draft next week” is more useful than a vague promise to fit it in. When priorities conflict, seek a decision from the person who can make that trade-off rather than silently absorbing it.
Confirm the agreement, then schedule the next action
Close the scope check with a brief written summary: the deliverable, its boundaries, the date, any input you are waiting for, and who will review it. For example: “I’ll prepare a one-page internal recap using the notes you send by Tuesday. I’ll share a draft on Friday for your review; recommendations are outside this version.” This gives everyone a chance to correct a mismatch while it is still easy to change.
Then schedule the next action you can actually take. That might be requesting a missing document, reviewing source notes, or drafting an outline. If a dependency blocks progress, record a follow-up date instead of reserving a large block of work that cannot yet begin.
New information may change the scope later. When it does, revisit the time and priority rather than treating the original schedule as fixed. A clear initial agreement will not prevent every change, but it gives you a shared reference for deciding what needs to move.
