It's Wednesday afternoon, and you have an hour reserved to finish a client presentation. There is just one problem: the figures you need are still waiting for approval. Instead of refreshing your inbox, treat the missing reply as a separate task, give it a follow-up date, and move the parts you can control forward.
Waiting on someone else is not the same as having nothing to do. Yet when an important project is held up by an email, a signature, or a colleague's decision, it's easy to let the whole afternoon feel suspended. A better plan makes the handoff visible and gives the waiting period a purpose.
Name the missing handoff instead of calling the whole project stuck
Picture a freelance designer who has drafted a website but needs a customer's final photographs. Her to-do list says 'Finish website.' Every morning she sees it, feels behind, and checks for an email. That single line hides two very different things: designing the pages is her work; supplying the photographs belongs to somebody else.
Try replacing that broad task with a small chain: 'Receive approved photos' → 'Place photos in layout' → 'Check mobile pages' → 'Send final preview.' Put the person's name beside the first step. Now you can see exactly what is blocked and what is not. The same technique works for a manager awaiting a budget sign-off, a student awaiting feedback, or a household waiting for a contractor's measurement.
Project-management guides call these relationships task dependencies: one piece of work needs another piece to happen first. Atlassian describes dependencies as information, outputs, and handoffs that determine the order of work; Asana likewise distinguishes a task that is 'blocked by' another from one that is ready to proceed. You don't need either app. A note, a simple table, or a line in your calendar can capture the relationship.
Before leaving the task, ask: What exact item am I waiting for? Who can provide it? What becomes possible the moment it arrives? If you can't answer, the next move is not more waiting; it's clarifying the request.
Keep a waiting list that tells you when to act
A normal to-do list is full of commands addressed to you: write, review, send, revise. A waiting list is different. It stores commitments that require someone else's move. Mixing the two means that every scan of your tasks reopens the same uncertainty, even when there is no productive action available.
For each waiting item, jot down four pieces of information: the deliverable you need, the person who owes the next response, the date you requested it, and the next date you will check. Add the project deadline only when it matters to the handoff. For example: 'Revised event poster — Mina — requested Tuesday — follow up Thursday noon — print cutoff Friday.' The entry is not a judgment about Mina; it's a reminder of the workflow.
Choose a checking rhythm that matches the stakes. A same-day launch might justify a short check-in within a few hours. A nonurgent suggestion for next month's newsletter may only need a reminder next week. One planned review beats leaving an inbox open all day. And if a colleague has agreed to a specific reply time, use that agreement rather than an arbitrary rule.
The goal isn't to create a larger productivity system. It's to make sure 'I should probably ask again' doesn't follow you around while you're trying to concentrate on something else.
Ask for a decision someone can actually give
Sometimes a reply is late because the original request made the next action too vague. 'Could you take a look?' may mean anything from catching typos to reconsidering the entire approach. A clearer message helps the other person see what is needed without hunting through a thread.
Instead of writing 'Any updates?', try: 'Could you approve option A or tell me what needs changing by Thursday at 2 p.m.? I need to send the final file to print on Friday.' Attach the specific file or link and keep the request focused on one decision. When a date is flexible, say so. When it's a genuine cutoff, explain what it affects.
If you need several approvals, do not assume they can happen in parallel. One manager's decision may change what the next reviewer needs to inspect. Sketch the sequence on paper and ask whether parts can be reviewed early. That small conversation can reveal a bottleneck before the afternoon you had reserved for 'finishing everything.'
A follow-up can be kind and precise at the same time. It isn't about sending louder messages. It is about giving the recipient enough context to respond and giving yourself a clear moment to move on if the answer doesn't come.
Build two plans: work that is ready and work that needs a green light
Suppose the presentation needs approved sales numbers, but the speaker notes, slide order, and visual cleanup do not. Put the first group in a 'waiting' column and the second in a 'ready' column. Then schedule an actual block to work on the ready items. You are not pretending the missing numbers don't matter; you're refusing to let them freeze unrelated work.
Be careful about fake progress, though. Polishing a layout that will change completely after the decision may create rework. Prefer reversible tasks: outlining, gathering background material, checking sources, drafting alternative headings, or preparing a template. If the decision could invalidate almost everything, switch to a separate project with a real deadline instead.
Make the switch rule explicit. For example: 'If finance hasn't approved the figures by 11 a.m., I will spend 45 minutes on the speaker notes, then move to the newsletter draft.' A rule like this is especially useful when waiting feels urgent but no new information is arriving. It keeps the next hour from being decided by the next notification.
Asana's guidance on blocked tasks makes a related distinction: work with a dependency should start when the prerequisite is complete, not merely because it appears on the schedule. The everyday version is simple: save your most constrained step for when its input is truly available.
Protect the deadline with an early decision point
Let's say the campaign email must go out Friday morning. Legal review is due Wednesday, and a designer is waiting for that approval to finalize the image. Writing 'Launch Friday' in the calendar doesn't show that Wednesday's handoff controls the rest of the sequence. Put the internal decision point on your calendar as prominently as the public deadline.
Work backward from what must be delivered. What is the latest useful time to receive the approval, allow for revisions, and still complete the remaining work? A practical plan might be: legal reply by Wednesday noon, image finalized Thursday morning, test email Thursday afternoon, send Friday. Those are example dates, not magic durations; use your own team's turnaround time.
Then decide in advance what happens if the reply doesn't arrive. Can you use a previously approved image? Reduce the scope? Ask the project owner to choose between delaying the launch and using a simpler version? Identify who can make that call before the schedule is already slipping. Don't silently invent someone else's consent.
For one week, try this tiny experiment: keep a separate waiting list; choose a follow-up time for each item; and put one fallback task beside your most important dependency. On Friday, notice which blocks were real and which were just a lack of a next action. You may still have to wait for people, but you won't have to give every delay your entire day.
You cannot make another person's inbox move faster on command. You can make your part of the project easier to understand: name the handoff, ask for a clear response, keep a follow-up date, and work on what is genuinely ready. Good time management is not only deciding when to work. Sometimes it means knowing when a task is waiting—and refusing to confuse waiting with falling behind.