The Inner Steady

Work Waiting on Someone Else? What to Do Next

By The Inner Steady Editorial Team

·

6–9 minutes
Two people work side by side at computer desks in a shared workspace.

You have written a report as far as you can. The next section depends on numbers a colleague promised to send, or a decision from a manager who has not replied. You open your inbox again, wonder whether to start guessing, and feel as though the whole task is still yours to carry.

When work is waiting on someone else, the useful question is not only “How do I stay productive?” It is: “What exactly is missing, what can I do without it, and when will I decide what happens if it does not arrive?”

Key Takeaways

  • Name the missing item, who can provide it, which part is blocked, and when the answer matters.
  • Continue only work that remains useful without the missing input; label approved assumptions and agree on a fallback instead of guessing.

Name the dependency precisely

Write one sentence that describes what is missing. “I’m waiting for Sam” is less useful than “I need Sam to confirm which figures to use in the Q3 table.” A specific dependency helps you see whether the whole task is blocked or only one part of it.

Note four details:

  • The missing item: a file, number, approval, answer, or decision.
  • Who can provide or confirm it.
  • Which part of the task cannot proceed without it.
  • When the missing item becomes important for the deadline or someone else’s work.

A short line in the task or project thread may be enough: “Waiting for the approved rate from Maya; needed before I can finalize the quote; follow up Thursday at 11.” You do not need to create a new tracking system for one blocked task.

Separate blocked work from work that can continue

Do not fill in unknown details just to feel that the task is moving. If a decision could change the result, pause that part and wait for the answer. Then check whether another part can be completed without making assumptions.

For a report, you may be able to format the confirmed sections while waiting for a figure. For a proposal, you might prepare the outline without choosing a price. For a plan that depends on a decision, you could draft the parts that work under either answer.

Ask yourself:

If…Then…
You can finish work that remains useful regardless of the answer.Continue that independent part.
You would have to guess and might need to redo the work.Hold the affected step and identify what input is missing.
Someone with authority approved a provisional assumption.Label it clearly and record its scope.

If only one step is blocked, move it out of your active “do now” list and choose a useful independent task. If the whole task depends on the answer, mark it as waiting and decide when you will check again. You are responsible for making the dependency visible; you are not responsible for inventing the missing input.

Send a request someone can answer

If you have not clearly asked for the information, send a concise request. Include the item, the decision you need, when you need it, and what part of the work depends on it.

“Could you confirm which rate I should use for the quote by Thursday at noon? I can prepare the rest now, but I can’t finalize the total without that number. If Thursday isn’t possible, please let me know who can confirm it.”

If there is no firm deadline, explain the consequence without manufacturing urgency:

“I’m waiting for the approved wording before I send the page for review. Do you know when it will be available? I can work on the other sections in the meantime.”

A broad “Any update?” may leave the recipient to reconstruct the request. A subject, link, or one-line reminder can make the question easier to answer. If you already sent a clear request, repeating it immediately may not add anything; use the follow-up point you agreed on or the norms of your workplace.

Set a follow-up point instead of checking repeatedly

Decide when you will look for the answer again. The timing should fit the actual deadline and your workplace’s communication norms; there is no one interval that works for every team.

Put the next step somewhere visible. You might make a calendar reminder, add a short “waiting for” note to the task, or record the follow-up in your project thread. Then return to the independent task you chose. The point is not to forget the dependency; it is to stop re-deciding what to do every few minutes.

If the answer arrives early, pick up the blocked part. If it does not, follow the plan you set: send the agreed reminder, contact the alternate owner, or tell the person responsible for the deadline that the missing input has become a risk.

Agree on a fallback before the last minute

For work with a meaningful deadline, ask what should happen if the input does not arrive. A fallback might be a shorter deliverable, a later date, another person who can decide, or a clear note that the work cannot be finalized without the missing information.

You could ask the person responsible for the deadline:

“If I don’t have the figures by Thursday, should I send the sections that are confirmed, wait for the full report, or use another source? I don’t want to estimate the missing values without approval.”

This puts the decision with someone who can authorize it. Do not present a guess as confirmed information just because a reply is late.

Raise a delivery risk with facts

If the deadline is at risk, tell the relevant person while there is still time to choose among options. State what is missing, when you requested it, which work is affected, and what decision you need. Avoid guessing why the other person has not replied.

For example:

“The quote is due Friday, and I still need the approved rate to finalize the total. I requested it Tuesday. I can send the confirmed sections now, but I can’t complete the price without that approval. Should we ask the backup owner or move the delivery date?”

If the dependency repeats across projects, describe the pattern and its effect rather than diagnosing a coworker’s motives:

“The last two releases waited on the same approval, and I didn’t know who could decide when the approver was unavailable. Could we agree on a backup owner or cutoff time for the next release?”

A factual summary makes the coordination problem visible and gives the team something specific to resolve.

Keep responsibility and authority clear

You may be responsible for delivering the work, but not for supplying a decision that belongs to someone else. Record what you requested and when, share the current status with the people who need it, and ask who owns the next decision.

If the work follows a required approval, safety, or client process, use that process. A personal follow-up routine does not authorize you to bypass a required review. If the person who owns the deadline asks you to accept a provisional assumption, label it clearly and confirm the plan in the usual channel.

Frequently asked questions

Should I follow up if I have already sent a message?

If the timing matters, a follow-up can be appropriate. Refer to the original request, state what is still missing, and explain the next deadline or decision. Use your workplace’s communication norms and avoid repeated pings that do not clarify what has changed.

Can I continue using my best guess?

Only if the appropriate person has authorized a provisional assumption and you can label it clearly. If the unknown could change the result or create risk, do not present a guess as confirmed information. Ask who can make the decision or agree on a fallback.

What if the whole task is blocked?

Mark it as waiting, record who owns the missing input and when you will follow up, then move to another useful task. If nothing else can proceed or a deadline is at risk, tell the person responsible for prioritizing the work and ask what should change.

Is this the same as starting a task with unclear instructions?

Not quite. If you do not know what the task requires, our guide to starting a task when work instructions are vague can help you clarify the assignment. This guide is for a task where you know what is needed but are waiting for a specific input or decision.

When work depends on someone else, keep the missing decision visible without carrying it in your attention all day. Name the dependency, continue only where it is safe, and agree when you will follow up or change the plan. For related planning questions, see what to do when you get a task with no deadline or browse Habits and Decisions.

✎ Write