Review exceptions

The skill and its purpose

An exception is a useful signal when it states what differs from the accepted plan and what happens next. It can involve a missing component, incorrect variant, delayed access, disputed quantity or incomplete evidence. A general red status is less useful than a precise record. The exception should preserve the original requirement while showing the observed difference and responsible decision.

Work through the decision

Identify the affected site, asset, file or task and the baseline it differs from. Record the actual observation, source and time, then assign the next action and decision owner. Separate urgent operational response from later root-cause improvement. Review dependent milestones and any required variation. Close the exception only when the relevant evidence supports the resolution, retaining the history for the programme review.

Practical exercise — fictional

A fictional branch receives the correct quantity but the wrong language variant. Create an exception linked to the site allocation and released file reference. Identify the immediate correction decision, the provider’s actual response and the later packing-control review. Explain why changing the received variant label without a real replacement would be misleading.

Take it to the next job

• Identify the baseline and observed difference.
• Assign next action and decision authority.
• Review affected dependencies and variations.
• Close with evidence while retaining history.