When a customer asks for a delivery date

Estimate is not a commitment

The planning note contains a month, a condition and a review requirement. It does not say that the integration for this customer will be ready on the first day of that month. In this scenario, neither repeating the date nor adding "probably" resolves the missing agreement.

A fictional response could be: "I can record 1 December as your required date. We need to confirm the integration scope and delivery plan before committing to it." That acknowledges the requirement of the customer without presenting the planning note as an authorized promise.

Record which kind of date you are looking at

• Customer requirement: when the customer needs the result. Preserve it as their requirement, not your acceptance.
• Internal estimate: a planning expectation with assumptions. Keep those assumptions attached when checking it with the responsible owner.
• Authorized commitment: a date agreed through the normal approval process of your company for the actual scope and customer. Check the applicable record rather than substituting a general roadmap.

For this rehearsal, use a paper card or a fictional file to record the date, its type, the work it covers, its conditions and who needs to confirm it. These are suggested fields for a team exercise; EvidCue does not claim to store or enforce them today.

Keep the answer label visible

An approved card might provide the prewritten response of your team to requests for an unconfirmed date. Approval of that response does not approve the underlying delivery date. A retrieved source passage can show what a planning document actually says, but it is still evidence rather than automatically approved wording.

An AI draft requires human review. If a draft says "We should be able to meet your deadline," compare it with the fictional source above: the draft has converted an internal target into a customer-specific assurance. Remove that assurance unless the responsible owner has confirmed it through the normal process. Plausible wording cannot supply missing authority.

Make the follow-up narrow enough to resolve

After the call, send the responsible owner a precise manual question through your normal company channel: "The customer requires integration readiness by 1 December. The planning note targets December subject to discovery. Can we confirm a date for their stated scope, and what dependencies remain?" Do not send real company documents or customer details to this preview.

Record what you actually told the customer alongside what still needs confirmation. If the eventual answer differs from the date the customer requested, say so directly. A phone cue should not conceal that gap.

1. Give a colleague the fictional laptop question and phone passage.
2. Ask them to separate the requirement of the customer from the internal estimate before drafting a response.
3. Have a second colleague add an unconfirmed dependency, such as an external connector review. Check whether the response still implies a promise.
4. Record the exact wording used and the unresolved question for the delivery owner.

This is a practice exercise, not completed user research. Human comprehension remains untested until consenting participants describe the experience without prompting. No improvement in response speed, follow-up volume or sales-cycle length has been measured here.

Explore the simultaneous laptop-meeting and separate-phone illustration. Related exercises cover checking the actual scope the customer asked for and reviewing a draft before speaking.