Record why a task was cancelled instead of completed

Where the extra work starts

Record the cancellation reason so your reports do not claim progress for a task the team no longer needed to do.

For invoice preparation, ParseMill combines PDF extraction, source review and Excel export in one workspace. Test whether the downloaded workbook gives the receiving colleague what they need. The plan has one account owner; shared team seats and automatic posting to accounting systems are not included.

A terminal state is an administrative classification, not a way to hide a missed commitment. If the underlying requirement still exists elsewhere, retain its active reference.

A practical way to get it right

Define the terminal categories and who may apply them. Completed requires the agreed outcome and evidence. Cancelled requires an authorized withdrawal or changed requirement. Duplicate requires a link to the surviving action. Out of scope requires a recorded scope decision and any necessary routing.

When closing a record, capture the reason, decision source, actor and date. Check for reminders, assignments or downstream tasks that need updating. A duplicate record should stop generating duplicate work while the surviving action continues normally.

Report completed outcomes separately from other terminal states. For queue reconciliation, all terminal records may reduce the open count, but that does not mean they represent productive completions. Keep both the movement explanation and the outcome classification visible.

Microsoft: Set and update task progress lists Planner’s broad progress states. If they cannot represent cancellation separately, preserve the terminal reason explicitly and use it in reporting.

What this looks like on a real task

Synthetic example. The people, references and figures below are invented to demonstrate the method.

Only A311 counts as a completed outcome in this example. A313's closure does not complete A309, and A314 creates a separate referral action. Copy the reason and evidence columns and reconcile any resulting work. Four closed records therefore do not equal four completed client requirements.

Catch the cases that create rework

If the tracker offers only a broad Completed state, maintain the terminal reason in a defined field or linked register and ensure reports use it. Do not rely on a free-text note that reporting ignores. If a cancelled task later becomes necessary again, create a linked reopening or new occurrence with the current scope.

Avoid deleting duplicate records before preserving the evidence and surviving reference; deletion can remove the explanation for a changed queue total.

Microsoft: Apply data validation to cells supports controlled value lists. A defined terminal-reason field helps prevent “done,” “cancelled” and “duplicate” from becoming interchangeable labels.

Decide whether the change is worth keeping

Sample terminal records and verify that their reason matches the evidence. Reconcile opening work, arrivals, completions, cancellations and reopenings in the period report. A clear distinction lets the team understand whether the queue shrank because work was delivered, scope changed or duplicate tracking was cleaned up.

The workflow audit checklist can help record the observed friction before considering a change.