Published November 3, 2026

Question and scope

This protocol asks how long a cross-team dependency stays open before someone reviews it, escalates it, or closes it. The scope is the operating record in one operations coordination function during a defined period. The measure matters because an aging dependency can block a dated commitment while looking like a normal item on a project board. The protocol does not assign fault to a team or decide whether a dependency should have existed. It describes the age of open items and the stage where time accumulates. The operations lead keeps the decision about priorities, escalation, and resourcing.

Population and unit of analysis

The unit is one dependency, from the date it was requested through the date it was closed or escalated. A dependency with several deliverables should be split into separate units when each deliverable has its own owner and needed-by date. If the team tracked it as one item, keep it as one unit and note the reduced precision. Start with a dated export from the dependency list or project tracker. Record the requester, the provider, the needed-by date, the status, and the last update. Include items that were closed during the window so the review can compare open and closed aging. Exclude items that were never accepted as dependencies and items that belong to a different operating cycle. Record the exclusions with reasons so the denominator is reproducible.

Definitions and measures

A dependency begins when the requester records a specific need and a named provider. A dependency closes when the requester accepts the artifact or decision, or when an authorized owner cancels it. A status change without an acceptance is not a close. Compute age in whole days from the request date to the review date for open items, and from request to close for closed items. Report the median, the 75th percentile, and age bands such as under three days, three to seven days, seven to fourteen days, and over fourteen days. Split the age into acknowledgment wait, delivery wait, and acceptance wait. Acknowledgment wait is the time before the provider confirms the request. Delivery wait is the time before the artifact arrives. Acceptance wait is the time before the requester confirms it is usable. The split shows whether the problem is responsiveness, production, or review.

Evidence standard

Each dependency needs the request date, the need, the provider, the needed-by date, the status, and the close evidence. If the request was made verbally and recorded later, mark the date as reconstructed and note who recorded it. A reconstructed date is weaker evidence than a system timestamp. Preserve status changes and owner changes. An item that was reassigned three times has a different history from one that sat with the same owner for the same number of days. Record the handoffs rather than overwriting the owner field. Keep sensitive operational detail in the approved system. The analysis file should use a dependency reference rather than copying customer data, contract terms, or internal access information into a separate spreadsheet.

Sampling and collection

When the list is small, review every dependency in the window. When it is large, use a documented sample and add a targeted sample of items past their needed-by date, items with no named owner, and items that changed owner more than once. Freeze the sample before collection. Have a second reviewer check a small subsample and record disagreements. Most disagreements come from an unclear request date or from treating a delivery as a close. Resolve those definitions before reporting the full result.

Analysis and reporting

Report open items separately from closed items. Show the oldest open dependency, the number past its needed-by date, and the share with no named owner. Pair the age measure with a short review of close evidence, because a fast close without acceptance may hide an unresolved need. Avoid ranking providers by average age. Request quality, lead time, and the complexity of the artifact all affect how long a dependency takes. The useful management question is whether the request and escalation process gives both sides a fair chance to act.

Limits and sources of error

The cited public sources frame operating records, privacy, security, and internal-control practice in general terms; they do not provide a local result or a management conclusion for a specific team. A short age does not prove that the dependency was well managed, and a long age does not prove that the provider was careless. The measure also depends on how the team defines a dependency. A broad definition can turn ordinary collaboration into a queue item, while a narrow definition can miss real blocks. State the definition and keep it stable across periods.

Review cadence

Review the result on a fixed date and end with one process change, one owner, and one check date. A repeated defect should change the request template or the escalation rule before it changes coaching. Archive the export, the coding sheet, and the notes so the measurement can be repeated. That record is what lets the next reviewer compare the result without rebuilding the sample from memory.

Sources