In short

  1. 1. Turn the date into dependenciesList the critical dependencies: customer data, access, security approvals, third parties, specialist resources, integration work and customer decision points. A date without dependency ownership is a target, not a commitment.
  2. 2. Separate internal and customer-controlled workIf the timeline depends on customer action, state that explicitly. Otherwise the supplier carries timing risk it cannot fully control.
  3. 3. Use base rates where possibleCompare the proposed timeline with similar implementations. If the new promise is materially faster, identify what is actually different this time rather than assuming optimism will close the gap.
  4. 4. Repair before escalationThe smallest repair may be sequencing, a phased launch, narrower initial scope, a customer dependency clause or more time. A good review should create options, not just objections.

Turn the date into dependencies

List the critical dependencies: customer data, access, security approvals, third parties, specialist resources, integration work and customer decision points. A date without dependency ownership is a target, not a commitment.

Separate internal and customer-controlled work

If the timeline depends on customer action, state that explicitly. Otherwise the supplier carries timing risk it cannot fully control.

Use base rates where possible

Compare the proposed timeline with similar implementations. If the new promise is materially faster, identify what is actually different this time rather than assuming optimism will close the gap.

Repair before escalation

The smallest repair may be sequencing, a phased launch, narrower initial scope, a customer dependency clause or more time. A good review should create options, not just objections.

A date becomes safer when every dependency has an owner, evidence and a consequence if it moves.