Skip to main content
TemplateFREE⏱️ 15 minutes

Blocked Items Tracker Template for Agile Teams

A template for tracking and resolving blocked work items with escalation paths, root cause tags, and resolution timelines to keep delivery on track.

Updated 2026-03-05
Blocked Items Tracker
#1
140
#2
98
#3
84
#4
75
#5
75

Edit the values above to try it with your own data. Your changes are saved locally.

Get this template

Choose your preferred format. Google Sheets and Notion are free, no account needed.

Frequently Asked Questions

How many blockers per sprint is normal?+
For a team of 5-7 engineers, 2-5 blockers per two-week sprint is typical. More than 5 suggests systemic issues with dependencies, unclear requirements, or insufficient [backlog refinement](/templates/backlog-grooming-template). Zero blockers usually means the team is not surfacing problems.
Should we track blockers in Jira/Linear or in a separate document?+
Both. Flag the blocked item in your project management tool so it is visible on the board. Use this template as a summary view for standups, retrospectives, and escalation meetings. The tool flag keeps the board accurate. The tracker adds context, owners, and resolution timelines.
When should we escalate a blocker?+
Escalate when a blocker has been open longer than its target resolution date or when the assigned owner does not have the authority to resolve it. The escalation path should be clear before the blocker is logged: if the owner cannot fix it by [date], it goes to [manager/VP/stakeholder].
What is the difference between a blocker and a risk?+
A blocker is stopping work right now. A risk is something that might stop work in the future. Blockers go on this tracker. Risks go in the risk register or sprint planning notes. When a risk materializes, it becomes a blocker.

Related Tools

Explore More Templates

Browse our full library of PM templates, or generate a custom version with AI.