Define an exception operationally
An exception is any item the standard path cannot complete safely. It may be bad input, an ambiguous decision, a system failure or a business case that requires different authority.
Use categories the operation can act on. ‘AI failed’ is not useful. ‘Purchase order total does not match its line items’ tells the reviewer what evidence is in conflict and where to begin.
Input exception
A required field is missing, unreadable, duplicated or inconsistent.
Rule exception
The item falls outside an approved threshold or matches conflicting rules.
System exception
An integration is unavailable, times out or rejects the requested change.
Business exception
The request is valid but unusual enough to require judgment or authority.
Detect early and contain the impact
Validate required information before changing downstream systems. When confidence or completeness is insufficient, hold the item with its original source and the reason it stopped.
Containment means an uncertain run cannot silently create duplicate records, send an incorrect commitment or disappear. Use idempotent operations where possible so a retry does not repeat a completed action.
Thresholds
Define when uncertainty becomes a review instead of pretending every result is certain.
Holding state
Keep unresolved items visible in a queue with age, owner and status.
Source preservation
Retain the message, document and values used during the attempted run.
Safe retry
Make repeated execution recognizable so it cannot double-send or double-post.
Route the exception with decision-ready context
A human review queue should reduce work, not reproduce the entire manual process. Show the extracted values, the relevant source, the failed rule and the available approved actions together.
Route by decision authority. A data-entry correction may belong to operations; a pricing override may require sales leadership; a privacy or contractual issue may require a designated specialist.
Reason
State precisely why the standard path stopped.
Evidence
Present the original source and the values or rules in conflict.
Owner
Assign the role authorized to resolve this category.
Next action
Offer clear approved actions such as correct, approve, reject, retry or escalate.
Use exception data to improve the workflow
Track exceptions by category, source, age and resolution. A growing queue may indicate a changed source format, a broken integration or a business rule that no longer reflects reality.
Do not automate every recurring exception immediately. Confirm that the resolution is consistent, approved and safe. Some categories should remain human because the value of judgment is greater than the cost of review.
Exception rate
Percentage of total runs leaving the standard path, separated by category.
Time to resolve
Elapsed time from detection to an approved outcome.
Repeat cause
Sources or conditions responsible for recurring preventable exceptions.
Recovery success
Whether corrected or retried items complete without duplicate side effects.