Question and scope

This protocol tests how often a cross-team deadline changes without a recorded reason and a named approver. A moved date can be a legitimate response to new information, or it can be a quiet way to avoid a hard conversation about capacity. The measure separates those cases by looking for the reason, the approver, and the replacement commitment. It does not judge whether the new date was realistic, because that requires evidence the record may not contain.

Scope is one coordination queue and one defined period, such as the most recent quarter or the last twenty cross-team commitments that reached their original due date. Include deadlines that were moved before the due date and deadlines that were missed and then reset. Exclude internal task dates that were never shared with another team. State the queue and the period so the boundary can be checked.

Population and unit of analysis

The unit is one commitment with one original due date, one owning team, and one receiving team. A commitment that covers several deliverables should be split when each deliverable has its own date and owner. If the team recorded one combined date, keep one unit and note that the date was shared. Use the commitment as it was first communicated, not a cleaned version created after the fact. Record each one in a commitment log before testing the change history.

Include commitments that were cancelled, because cancellation is a change in the promise even when no new date is set. Include commitments that moved more than once and record each move as a separate event under the same unit. Exclude duplicates and commitments that were created only for a rehearsal or a test. Record the reason for every exclusion so the denominator can be defended.

Definitions and measures

A recorded reason is a short explanation that names the condition that changed, such as a late dependency, a scope change, or a resourcing decision. A generic note that says "timeline updated" is not a recorded reason. A named approver is the person who accepted the new date on behalf of the receiving team, not the person who edited the record. Both fields are required for a move to count as explained.

Report four shares: moves with a reason and an approver, moves with a reason only, moves with an approver only, and moves with neither. Also report the median number of days between the original date and the replacement date. Show the count behind each share and the number of commitments that moved more than once. A percentage from five moves should be presented as a count, not a rate.

Evidence and data dictionary

Each commitment needs an identifier, the original due date, the current due date, the owning team, the receiving team, and the date the change was recorded. Add the reason text, the approver, and a link to the message or meeting note where the change was agreed. If the change was agreed verbally, record the date it was written down and who wrote it. The evidence should let a reviewer reconstruct the sequence without interviewing the team.

Define moved, missed, reset, cancelled, and unchanged before coding begins. Define whether a date change within the same day counts as a move, and whether a public holiday shift counts. Include one example of an explained move and one example of an unexplained move in the dictionary. A short shared vocabulary prevents two reviewers from counting the same event differently.

Sampling and test design

Use a census for a small commitment log and a documented random sample for a large one. The sample should include each receiving team and at least one commitment that moved close to its due date. Freeze the sample before reading the reasons so the reviewer cannot select the most dramatic examples. Keep the original export and the coded sheet together.

Have a second reviewer recode at least ten commitments and compare the four shares. Resolve disagreements by returning to the source record rather than by voting. A written reconciliation note is enough. If the disagreement rate is high, revise the definition of a recorded reason and recode the full sample. A measure that depends on the reviewer's intuition will not survive a change of reviewer.

Decision rules before the test

Decide before coding how to treat a date that moved because the receiving team requested a later date. That move may have an approver but no written reason, and the rule must say whether it counts as explained. Decide whether a move approved in a meeting counts when the minutes are published later. Write both rules down and apply them to every row.

Agree on the action that follows a high unexplained rate. One option is to require a reason and an approver before a date can be edited in the tracker. Another is to review all moves at the weekly coordination meeting and close the ones without a replacement commitment. Avoid a blanket rule that no date may change, because that encourages teams to hide risk instead of reporting it.

Analysis and reporting

Report the share of moves with both fields, the share with neither, and the median slip in days. Break the result down by receiving team and by the stage at which the change occurred. Show the oldest unexplained move and the commitment it affects. Pair the count with a review of whether the receiving team was told before the original date passed.

Look for patterns rather than a single bad month. A cluster of moves near quarter end may point to a planning calendar that overloads the same week. A cluster of moves without an approver may point to a tracker that anyone can edit. Report the pattern with the count and one example, then name the process change the team will test next.

Reporting template

Use a one-page template with blocks for scope, explained share, unexplained share, median slip, oldest unexplained move, and the action agreed at review. Put counts beside every percentage and record the source of each date. Add a short note for every exclusion and every change to the definition. Keep the template short enough to complete in the review meeting. Name the person who will maintain it.

Store the template with the commitment export and the coding sheet. A later reviewer should be able to reproduce the headline share without asking for context. Mark the final version clearly. If the tracker changes or the definition of a commitment changes, start a new series and mark the break. A clean comparison is more useful than a long trend built on inconsistent records.

Limits and sources of error

The cited public sources describe records, internal control, and project practice in general terms; they do not provide a local rate for a specific queue. A recorded reason can be thin or inaccurate, and an unrecorded reason can still be known to the people involved. The measure also depends on whether the tracker keeps date-change history. A system that overwrites the old date will undercount moves.

Edited records and reconstructed timelines are common sources of error. Check a sample against the original messages and mark any date that was entered after the fact. Use the version participants actually saw. Exclude a commitment when the original date cannot be verified, but report the exclusion count. A clear caveat is more useful than a precise number that cannot be traced.

Review cadence

Review the result at a fixed date and end with one change, one owner, and one check date. Repeat the test after two full cycles before setting a target, because a single quarter may reflect an unusual project mix. Keep the definition and the sample method with the result so the next reviewer can compare like periods. Mark any process change on the same timeline as the data.

Retire the measure if it stops informing a decision. If the team keeps it, publish the unexplained share and the oldest open commitment together so silence and delay are visible at the same time. A metric that no one acts on is overhead. The purpose is a date that someone can trust, not a perfect record. Stop when the team can show that outcome consistently.

Sources