Source: [Original HTML page](https://stolenorbit.com/en/templates/exception-register/)

Language: English

FREE TEMPLATE · FILL IN, DOWNLOAD, REUSE

# Automation exception register

Give cases that leave the standard flow a defined path. The register should help restore work with a verifiable outcome, rather than merely collect error messages.

[By Stolen Orbit](https://stolenorbit.com/en/about/) Revision 2026-09-24

## When to use it and what to produce

[Source for this section](https://stolenorbit.com/en/templates/exception-register/#template-purpose)

During pilots and ongoing operation, when work gets paused, records are incomplete or outcomes between systems are uncertain.

An exception queue with status, priority, ownership and closure evidence; repeated issues become inputs to workflow improvements.

Fill in the fields below and download your document. The website does not send or save answers: closing the page may lose them. Examples are illustrative and should be replaced with your process data.

[Download the complete blank template (.md)](https://stolenorbit.com/downloads/exception-register-en.md)

Without JavaScript, download the full template above and complete it in your editor.

## 1\. Identify the case

[Source for this section](https://stolenorbit.com/en/templates/exception-register/#capture)

Capture enough context to find the operation without unnecessarily copying confidential data. One exception should not create several disconnected records.

**See a worked example**

Illustrative example: ORD-042 is paused after an ERP timeout. Its email was read, but it is not yet clear whether the order draft was created.

**Reference, time and step**

Record case identifier, workflow version and the last step known to have completed.

**Observed issue and evidence**

Describe the visible symptom, link accessible logs and distinguish facts from suspected causes.

**State in connected systems**

Check which writes happened and which remain uncertain before another attempt.

## 2\. Assign priority and action

[Source for this section](https://stolenorbit.com/en/templates/exception-register/#triage)

Priority follows the effect on operations, not the length of a technical error. Distinguish an isolated case from a failure affecting the whole queue.

**See a worked example**

Illustrative example: pause ORD-042, search for its reference in the ERP and let other cases continue if no related failures appear.

**Impact and urgency**

Record affected cases, operational deadlines and possible effects on customers or records.

**Owner and next update**

Assign a person or staffed role, a backup and the time of the next update.

**Containment and fallback**

Describe what stops, which cases may continue and how work can temporarily proceed manually.

## 3\. Verify before closing

[Source for this section](https://stolenorbit.com/en/templates/exception-register/#resolution)

A successful retry is insufficient if duplicates or partial effects remain. Connect the fix to the business outcome and to lasting prevention.

**See a worked example**

Illustrative example: the draft already existed. Link it to the case, avoid creating another and add a reference lookup after timeouts to the workflow.

**Recovery action**

Record checks performed, manual changes and the exact point from which work resumes.

**Closure evidence**

Confirm the correct outcome, absence of duplicates and notification of the case owner.

**Cause and preventive change**

Record category, similar cases, proposed change and a test to add before the next release.

## Pitfalls to avoid

[Source for this section](https://stolenorbit.com/en/templates/exception-register/#template-pitfalls)

-   Closing the technical issue while leaving the business case incomplete.
-   Repeating the whole process manually after some effects already occurred.
-   Leaving the exception queue without an owner or regular review.

[Turn documents into usable data, with checks at every handoff.](https://stolenorbit.com/en/services/ai-document-data-extraction/)

[Keep your CRM connected to the work happening around it.](https://stolenorbit.com/en/services/crm-automation-ai-integration/)

[Evaluate an AI system by what must succeed and what must never happen.](https://stolenorbit.com/en/resources/evaluating-ai-reliability/)

[Human review of AI: a control should help someone make a decision.](https://stolenorbit.com/en/resources/human-review-for-ai/)

[Reliable automation knows what to do when the outcome is uncertain.](https://stolenorbit.com/en/resources/automation-failures-and-duplicates/)

[All templates and tools](https://stolenorbit.com/en/tools/)

[All guides](https://stolenorbit.com/en/resources/)

## Take the next step together.

Use this document to start a discussion about scope, evaluation and project ownership.

Review the text before sending. Only your email is needed alongside the message; other details are optional.

[Contact us](/en/contact/)

## Turn the question into a next step.

-   [Evaluating AI reliability](https://stolenorbit.com/en/resources/evaluating-ai-reliability/)
-   [Evaluation lab](https://stolenorbit.com/en/tools/ai-extraction-evaluation/)
-   [AI evaluation dataset](https://stolenorbit.com/en/templates/ai-evaluation-dataset/)