“I’m blocked” alerts a colleague to a problem, but it does not yet show how to help. A useful blocker message explains the obstacle and identifies the smallest input or decision needed to continue.
Describe the effect on the task
State which part cannot proceed and which part can still move. For a fictional example, a draft may be ready except for a confirmed publication date. That is different from being unable to start the entire piece.
Include the relevant deadline and when the missing input is needed. Avoid creating false urgency by using “ASAP” where a specific time would be clearer.
Show the checks, briefly
Name the sources or people you have already consulted, without recounting every minute of the attempt. This helps the recipient avoid suggesting a step you have just completed.
Do not hide uncertainty behind a diagnosis. “The shared folder returns an access message” is an observation. “The system is broken” is a broader claim that may not be established.
Ask for one next action
Request access, a choice between options or confirmation of an assumption. If several people could respond, identify the owner through the team’s normal process so the message does not become everyone’s and nobody’s responsibility.
Keep a record of the response in the task notes. Our guide to clear work updates can help you report progress alongside the blocker, showing both what is done and what remains dependent on someone else.

