Blockers

When To Use A Blocker

Use a blocker when work cannot move forward because something required is missing, delayed, or unresolved.

Examples:

• Waiting for client assets
• Missing footage or files
• Need clarification
• Talent unavailable
• Approval pending
• Dependency on another task
• Required information is missing

A blocker should represent something that genuinely prevents or significantly delays progress.

What Happens Next

When work is marked as blocked, AGENCIE makes that state visible in the workflow so the team can identify work that needs attention.

This helps managers and other responsible team members understand where production is stuck without repeatedly asking for updates in chat.

Good Blocker Notes

A useful blocker explains both what is preventing progress and what is needed to continue.

Instead of:

> Waiting.

Write:

> Waiting for the client to provide the final product images before editing can begin.

Clear blocker notes make it easier for someone else to understand the problem and help resolve it.

When The Blocker Is Resolved

Once the dependency or issue has been resolved, the work should no longer remain blocked.

Continue the workflow from the appropriate production stage so the current status reflects what is actually happening.

Blockers vs Delays

Not every delay needs to become a blocker.

Use a blocker when progress cannot reasonably continue without an external action, missing input, decision, or dependency.

If work can still continue normally, keep its regular workflow status instead.

Visibility

Blocker visibility follows the user's access to the underlying work.

Internal team members only see blockers for work they are authorized to access.