Published November 3, 2026.
Why the weekly review needs a dependency check
A weekly operations review often becomes a status meeting where each team reports what it finished. The harder question is what cannot finish because another team owes an input, an approval, or a decision. A dependency check answers that question before the meeting, so the review spends its time on the blocked work instead of on a recital of activity. The check is a short, dated list of cross-team dependencies with one owner on each side. It is not a project plan and it does not replace the teams' own trackers. Its purpose is to give the operations coordinator a reliable view of where work is waiting and which conversation needs to happen next.
List the dependencies that actually block work
Start with the commitments already made in the current operating cycle. For each one, ask what input must arrive from another team before the next step can happen. Record the requesting team, the providing team, the specific artifact or decision needed, and the date it is needed. Avoid listing every collaboration as a dependency. A dependency exists only when the next step cannot proceed without the other team's output. If the work can continue with an assumption, record the assumption and the date it must be confirmed instead of treating it as a hard block.
Name one owner on each side
Every dependency needs a requester and a provider, each named as a person. A team name is not an owner, because nobody can follow up with a department. The requester owns the follow-up and the date; the provider owns the delivery and the confirmation that the artifact is ready. When the provider changes, record the handoff rather than replacing the original name. That history matters when a deadline slips, because it shows whether the request was reassigned or simply forgotten. A backup owner should be named for critical dependencies so the work does not stop during a single absence.
Set a needed-by date and a follow-up date
The needed-by date is driven by the downstream commitment, not by convenience. Work backward from the review or delivery date and record the latest moment the input can arrive without forcing a change to the plan. If that date has already passed, mark the dependency as overdue rather than moving the date silently. The follow-up date is the next time the requester will check in. It should be earlier than the needed-by date and specific enough to act on. A follow-up without a date is only an intention, and an intention is what the dependency check is meant to replace.
Keep status separate from opinion
Use a small status set: requested, acknowledged, in progress, delivered, accepted, blocked, and cancelled. Each status should have a date and an owner. A dependency is not delivered because someone said it was coming; it is delivered when the requester can see the artifact and confirm it meets the stated need. Record the acceptance step separately from delivery. The provider may send a draft that is not yet usable, and marking it delivered too early hides the remaining work. If the requester accepts a partial artifact, record what was accepted and what remains open.
Review the list before the meeting
The coordinator should review the dependency list the day before the operations review. Sort by needed-by date and look for items that are overdue, unacknowledged, or missing an owner. Send the short list to the meeting participants so the discussion starts with the blocked items rather than the completed ones. During the review, ask one question for each blocked item: what decision or artifact will unblock it, who owns that action, and when will it arrive. Record the answer in the same list so the next review can see whether the commitment moved. Do not reopen items that were closed with evidence unless a new fact changes the situation.
Close dependencies with evidence
A dependency closes when the requester confirms the artifact or decision is usable, or when the work is formally cancelled with an owner's approval. Record the close date, the person who accepted it, and the evidence link. If the dependency changed the plan, note the change so the downstream schedule remains explainable. At the end of the cycle, review the closed items for patterns. A provider that repeatedly delivers late may need a different request lead time, while a requester that repeatedly changes the need may need a clearer brief. The pattern is more useful than a single late item.
Keep the check short enough to maintain
The dependency list should be small enough to read in a few minutes and specific enough to act on. If it grows into a second project plan, the team will stop maintaining it. Keep only the cross-team items that block a dated commitment, and move the rest into the owning team's normal tracker. A good dependency check does not eliminate delays. It makes them visible early, assigns the next conversation to a person, and gives the operations review a concrete agenda. That is a better use of the meeting than a round of status updates that nobody can act on.
