# Handovers And Exceptions

Release r-3c7687664372c00d · https://mirrorfirm.com/knowledge/handovers-and-exceptions

## Why build tasks around exceptions?

The interesting work often begins when the standard path breaks.

The interesting work often begins when the standard path breaks. Use observed exception patterns to shape generated tasks.

Limitation: an exception task is only as useful as its stated expected action. Define what a correct response is before using it as an evaluation.

_Status: positioning · editorial · revision 1_

## Why do handovers matter in generated scenarios?

Context, dependencies and responsibility move with the work.

Work changes hands. Generated scenarios can preserve the context, dependencies and responsibility that move with it.

Scenario: in the fictional Aster Financial example an application moves from origination to credit. Check that the record passed on identifies who now holds the next action.

_Status: positioning · editorial · revision 1_

## How are workflows that cross departments represented?

Shared context is retained across departments.

A workflow can cross departments before it is complete. Retain that shared context when creating generated training material.

Scenario: the fictional Aster Financial map connects Origination, Credit, Servicing and Collections through shared business state, so a later team can trace back to the original application.

_Status: positioning · editorial · revision 1_