A customer decides not to continue with a proposed direction. At the next review, the project still appears as progressing: someone prepares samples while another person waits for feedback. The decision has changed, but the team’s actions have not followed it.

The question I take from the review is how to hand over a cancellation accurately. The underlying record does not support a full account of the cancellation; this note offers checks for the next similar situation.

Establish the scope of cancellation

Has the customer stopped one structural option, a development route or the entire project? If one option has been dropped, are alternatives still under assessment? Return to explicit evidence instead of expanding “not this one” into a decision that all work is over.

Pause, awaiting response and cancellation also need different states. Silence is not cancellation. Conversely, an explicit cancellation should not remain indefinitely in progress while someone waits for a response no longer needed.

Update actions as well as the label

A short exit record can contain:

  • Cancelled scope and corresponding revision.
  • Decision evidence and confirming role.
  • Work to stop or change, and who acknowledges the notice.
  • Remaining issues and their owners.
  • Conditions requiring fresh confirmation if the work restarts.

If samples, materials or external work may already exist, first check for remaining issues and route them to the responsible people. Changing a status does not establish that no obligations remain. Equally, a method article should not invent costs or disposal events absent from the evidence.

Make the boundary clear to the next colleague

The confirmed stop applies to the listed option. Other work retains its own status. Please acknowledge the corresponding action changes. Remaining issues have separate owners; any restart will require a fresh check of demand, revision and resources.

This reduces unnecessary chasing without turning a local cancellation into a statement that the whole customer relationship has ended. A project table should explain what happens next, including what no longer needs to happen.

For training, use entirely fictional replies and ask a colleague to distinguish a cancelled direction, a paused project and an unresolved decision. Closing an item accurately is part of making room for useful work.

Related: A follow-up email needs a decision point.


Drawn from questions raised in a periodic work review. Identities, business figures and project details have been removed. Checklists and sample wording are for similar situations; they do not establish a completed outcome.