Report a blocker without drama: impact, what you tried, the exact ask, who can unblock, and your next step while waiting.
Status update
Keep it answerable: what changed, what you need, and when you check in next.
Runs in your browser. Auto-saves on this device. Nothing is uploaded.
Your draft
Live
When the draft is ready, paste it into Today’s end-of-day fields.
Open Work Dashboard
Blank, example, and short versions
Blank status update
Date:
Project / ticket:
Blocked on:
Impact (what cannot move):
What I already tried:
What I need (exact ask):
Who can unblock:
Deadline / risk if still blocked:
My next step while waiting:
Realistic status example
Date: 2026-09-13
Project / ticket: INV-214: invoice PDF export
Blocked on: Access to production S3 bucket `invoices-prod` (read-only is enough)
Impact (what cannot move):
Cannot verify PDF upload path on real data. Staging uses a stub bucket.
What I already tried:
- Confirmed IAM role on staging works
- Reproduced with fixture PDFs locally
- Asked #platform at 11:40; no reply yet
What I need (exact ask):
Grant my IAM user `s3:GetObject` on `invoices-prod/exports/*` for 48 hours, or pair for 15 minutes.
Who can unblock:
DevOps on-call (or Mira if she is online)
Deadline / risk if still blocked:
Client demo Thursday 10:00. If still blocked by EOD Wednesday, demo uses staged fixtures only.
My next step while waiting:
Finish error-state UI and write the rollback note.
Shorter version
Blocked on:
Impact:
Exact ask:
Who can unblock:
Next step while waiting:
About this template
What this is for
Surface a blocker so someone can unblock you. Keep impact, ask, and owner obvious.
When should you use it?
Use when you are stuck longer than one focus block, or when a dependency is about to slip a deadline.
When should you skip it?
Do not use this for a vague feeling of being busy, or for work you have not tried for even one focused attempt. If the reader is an external client who only needs a status pulse, use the client status update. If you are transferring ownership at shutdown, use the end-of-day handoff.
Why this example works
The ask is specific (permission, scope, duration). Impact and deadline are clear. Waiting work is named so you are not idle-looking.
Job this solves
A good blocker update turns “I am stuck” into an actionable packet: impact, evidence of effort, one exact ask, one owner, and what you will do while waiting.
How to fill it
Name the blocked outcome in one line before any story.
State impact in plain words: what slips if this stays blocked.
List what you already tried so nobody restarts at zero.
Write one clear ask with a single unblock owner.
Say what you will do while waiting, then send once.
Soft nudge vs blocker
If the ask already exists and you only need a polite bump, keep it to two lines. Promote to this full template when the wait now threatens a date or another person’s work.
Common mistakes
Describing feelings (“stuck”) without an outcome or owner
Asking a whole channel instead of one person
Hiding the ask at the bottom of a long narrative
Skipping the already-tried list, which invites duplicate advice