Why blocked work disappears from the queue
A blocked item often looks healthy in a tracker because it has an owner, a status, and a due date. The work is not moving, but it still counts toward workload and still appears in the weekly report. Without a review that isolates blocked items, the first clear signal is usually a missed delivery that surprises everyone. A short weekly review makes the dependency visible while there is still time to act.
This is not a general status meeting. It looks only at work that cannot proceed without another team's action, decision, or artifact. That narrow scope keeps the conversation short and gives every item a specific resolution path. Coordinators who run the review consistently tend to find that a small number of dependencies cause most of the delay, which makes the list easier to manage each week.
Separate blocked work from ordinary waiting
Waiting is a normal part of coordination and does not always require escalation. Treat work as blocked only when the next step belongs to someone outside the owning team and no useful workaround exists. A request awaiting a routine reply is not blocked if the team can continue another part of the deliverable. This distinction matters because a queue full of vague waiting labels can hide the few items that are genuinely stuck.
Write the test down so two coordinators apply it the same way. A useful prompt is to ask what the team would do next if the other party did not respond for three days. If the answer is nothing, the item is blocked. If the answer is a partial draft, a test, or a parallel task, the item is waiting and belongs in normal follow-up.
Write one blocking record per dependency
Each blocked item needs one record that names the deliverable, the owning team, the blocking team, and the person who can resolve the block. Add the date the dependency was requested, the date the next step is needed, and the impact if it slips. Keep the record short enough to read aloud in a meeting. Link to the original message or ticket so the history is not reconstructed from memory.
Update the record in place instead of adding a new comment every week. A single current field for the next checkpoint is more useful than a long thread that no one rereads. When the dependency changes hands, record the new resolver and the date of the handover. That small discipline prevents a block from being quietly reassigned to a team that never accepted it.
Name the person who can resolve it
A team name is not a resolver. The record needs a person who has the authority to approve the dependency, release the artifact, or make the decision. If that person is unavailable, name a fallback with the same authority rather than routing the request back to a shared inbox. The coordinator should confirm that the named person accepts the role before the item enters the review.
Authority and capacity are separate questions. A manager may be authorized to approve a dependency but too overloaded to act this week. Record both the authority and the realistic date, then decide whether the item needs a different resolver. This prevents the review from producing names that look accountable but cannot actually move the work before the deadline.
Run a thirty-minute weekly review
Prepare the list before the meeting and sort it by the date the next step is needed. Open with new blocks, then review aging blocks, then finish with items that can be closed. Give each item a short time box and stop the discussion when it turns into a general update. The coordinator records decisions live so no one has to reconstruct them later.
Invite the resolvers for the items on the list rather than every stakeholder. Attendance should follow the dependency, not the org chart. If a resolver cannot attend, the coordinator should still present the recorded next step and follow up in writing. A review that waits for perfect attendance will lose the weekly rhythm that makes it useful over time and across teams.
Decide to unblock, renegotiate, or close
Every item should leave the review with one of three outcomes. Unblock means a named person commits to a specific action by a specific date. Renegotiate means the receiving team accepts a new delivery date or a reduced scope. Close means the work is no longer needed or the dependency has been removed. An item that leaves with none of these outcomes has not been reviewed.
Record the outcome and tell the receiving team in the same channel where the commitment was made. A decision that lives only in the meeting notes is not visible to the people planning around it. When the outcome is a renegotiation, capture the new commitment in the cross-team commitment log rather than leaving the old date in place. That keeps the review connected to the record the rest of the team uses.
Measure whether the review changes anything
Track the number of blocked items, their median age, and the share that have a named resolver. Add the share closed by the promised checkpoint and the number that missed their original due date. These measures show whether the review is producing decisions or just collecting problems. A falling count can be good, but only if the work is actually moving.
Compare several weeks before drawing a conclusion, because a single quiet week may reflect a holiday or an unusual project mix. Look for repeat blockers by team and by dependency type. If one team blocks the same kind of work every month, the fix may belong in planning or intake rather than in the weekly meeting. The review of broken commitments offers a useful second view of the same pattern.
Keep the review from becoming a status meeting
Protect the format with three rules. Only blocked items appear on the agenda, updates are written in the record before the meeting, and every decision is captured while the right people are present. A coordinator who allows general status updates will soon need a second meeting to discuss the actual blocks. The constraint is what makes the review useful and keeps it short enough to repeat.
Rotate the facilitator occasionally so the process does not depend on one person. Keep the log in a shared system and audit a sample of closed items each month to confirm the resolution was real. Share the aggregate pattern with the teams that block and unblock the most work. The goal is a shorter dependency list and a clearer promise to the receiving team, not a longer meeting.
Sources
- U.S. Government Accountability Office, Standards for Internal Control in the Federal Government, reviewed November 9, 2026.
- U.S. Bureau of Labor Statistics, Occupational Outlook Handbook: Project Management Specialists, reviewed November 9, 2026.
