Write exactly what you need, who can provide it and when it affects the plan. Request the information clearly and schedule an appropriate follow-up. Work on independent steps likely to remain useful; mark the blocked part as waiting until the answer arrives.
Your next step depends on a reply, a document or permission from someone else. The whole project stays on the list as something you should be doing, even though you cannot complete the blocked part today.
Write down exactly what you are waiting for and who can provide it. Send a clear request with the date that matters. Decide when to follow up, considering any response arrangement already in place.
Look for useful independent work
Check whether another part can move without the answer. You may be able to gather your own documents or draft a question. Avoid doing work that will probably be discarded if the missing decision goes another way.
If no useful independent step exists, mark the project as waiting and move it out of today's active tasks. Keep the follow-up date visible so it does not disappear. When the answer arrives, revise the plan using the actual information rather than automatically continuing the assumptions you wrote while you were waiting.
Waiting for venue confirmation
An illustrative exampleSuppose you are arranging a workshop and need confirmation that a room is available. You can draft the outline and materials list while waiting. Printing invitations with an unconfirmed address would create rework. Send a request naming the preferred slot and when you need the answer. Keep the request and follow-up together in a waiting note. If there is no reply, follow the provider's contact process or consider another venue. Once the answer arrives, update the plan using the confirmed room size and access arrangements. The preparation you kept was independent of the details you had yet to learn, so it can still serve the event.
Make the dependency visible
Tick the steps as you work through them.
0 of 5 steps checked
When the answer stays unavailable
Use the timeline in your request and any stated response arrangements. A brief follow-up can repeat the question without inventing urgency. If the deadline passes, decide which alternative is available and what it changes. Repeated messages cannot create access or approval on their own. Tell whoever owns the wider deadline which dependency remains unresolved and what that means for the output. Where nothing useful can proceed, keep the project in a waiting list with the next check visible.
Write a waiting note
Your notes stay in this page. Copy them before leaving; they are not saved or sent to us.
