How to Write a ‘Waiting on Someone’ Update

“Still waiting on Sam” tells readers who to blame but not what the project needs. A professional dependency update describes the transfer of work, not the character of the person holding it.

Name The Missing Input

Write what you requested and when:

Waiting for finance to confirm the 2027 budget ceiling. The request was sent Tuesday, with a response requested by Friday at noon.

This is more useful than “finance has not replied.” It gives the team an auditable state.

Explain The Effect

Say what can and cannot continue:

We can finish the vendor comparison meanwhile. Final selection and contract review depend on the budget ceiling.

The reader can now judge urgency without you adding emotional pressure.

Schedule The Next Move

Every waiting state needs a review point:

I will follow up Friday morning. If there is no answer by noon, I will ask the finance lead to nominate a decision-maker.

Tools can help keep that promise visible. Axtio lets you place delegated work under the person you are waiting on, then move the next follow-up into view instead of relying on memory.

For a frustrated draft, use this Wrivio Context:

Rewrite this as a factual dependency update. State the missing input, current owner, request date, impact, and next follow-up. Remove blame, sarcasm, and speculation. Preserve all dates and names.

This approach is firm because it exposes the state and the consequence. It is fair because it does not pretend to know why the response is late.

For more on the next message, see how to write a follow-up email that gets a reply.