> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# How to design a process for the exceptions
- URL: https://blog.jestor.com/design-a-process-for-the-exceptions/
- Published: 2026-09-16T18:55:31.000Z
- Updated: 2026-09-16T18:55:31.000Z
- Author: Bruno Bannach

Learning to **design for exceptions** is what separates a process people follow from one they work around. The happy path is easy and rarely the problem. What determines adoption is whether the process has a path for the cases that do not fit.

## Why workarounds appear immediately

A process built only for the standard case leaves everyone facing an unusual situation with two options: force it into a shape that does not fit, or bypass the process.

Both corrupt the data, and the second one spreads, because once bypassing is normal it extends to cases the process handled perfectly well.

Exceptions that always exist:

- The urgent case that cannot wait for approval
- The record missing information that is genuinely unavailable
- The decision that needs reversing after approval
- The request that belongs to no category
- The case requiring an authority nobody was given

## Designing each exception

| Exception           | Path to provide          | Control               |
| ------------------- | ------------------------ | --------------------- |
| Urgency             | An expedited route       | Retrospective review  |
| Missing information | Provisional record       | Completion deadline   |
| Reversal            | Explicit reversal action | Approval and reason   |
| Uncategorized       | An open category         | Reviewed periodically |
| Beyond authority    | Escalation path          | Recorded decision     |

## Step by step to build them

1. **Ask what happens when this does not fit**, for each stage.
2. **Provide an expedited route**, with review afterwards rather than a block.
3. **Allow provisional records**, with a deadline to complete them.
4. **Build reversal explicitly**, since it will be needed.
5. **Keep an open category**, and review what lands in it.
6. **Define escalation** for cases beyond anyone's authority.
7. **Monitor exception volume**, since a rising rate means the design is wrong.

## Why exception volume is a design metric

A process where one in twenty cases takes an exception path is working. One where a third do is telling you the standard path does not match reality. That ratio is the most useful signal you will get about whether a process fits the work.

## Why choose Jestor

In **Jestor**, exception paths are conditional routes rather than separate processes, provisional records can carry required completion deadlines, reversal can be an action with its own approval and justification, and the volume taking each path is measurable on the same data.

## Frequently Asked Questions

### Why do people bypass internal processes?

Because the process has no path for the case they are facing. See [jestor.com](https://www.jestor.com/?ref=blog.jestor.com).

### Should urgent cases be blocked?

No. Provide an expedited route with review afterwards, or it will be bypassed.

### What does a high exception rate mean?

That the standard path does not match how the work actually happens.

## Video Tutorial: Step by Step

With **Jestor**, you can automate workflows, connect teams, and build internal systems your way, all without code and powered by **AI**. Discover Jestor at [jestor.com](https://www.jestor.com/?ref=blog.jestor.com) and see how to take your company's operations to a new level of efficiency and control.