Cross-Team Dependency Negotiation Template

Every cross-team dependency tracker ranking for this query records the same three things on each row: a status of on track, at risk or blocked, a provider-stated confidence or risk score, and an owner on each side. None of them check that confidence against anything. The UK government's own reference-class-forecasting research draws exactly the line these trackers miss. An inside view, built from the specifics of one commitment, is where the optimism comes from. Only an outside view, built from a comparable track record, actually corrects it.

This pack builds that outside view for every provider team it tracks. Past commitments get bucketed by the confidence a team stated at the time, the same check forecasters run on their own published probabilities. A stated 70 percent should hold about 70 percent of the time, measured across many claims made at that level. At Thornwood Systems, a fictional healthcare scheduling software company, Identity's stated 90 percent confidence has held on 3 of its last 12 commitments at that level, 25.0 percent, its worst-calibrated band of the three it uses.

Across all three of Thornwood's provider teams, 120 recorded commitments held on time 69.2 percent of the time, a figure no single dependency row would surface. Slip history by team reads as uncomfortable, and it is exactly what tells a requesting team which commitments to plan around rather than believe. Built for the lead negotiating a date out of a team they do not manage. The technical program plan tracks the same handoffs at the programme level, and the capacity forecast checks a provider's own backlog before it commits to anything.