Practical guide

Teach exceptions without inventing authority

Last materially reviewed 2026-10-02

Quick answerTeach people to recognize the boundary and find the right owner; do not turn every exception into an automatic answer.
What to know

Look for the missing branch

A procedure often explains the normal path more fully than the exception. Ask what happens when a required field is absent, two requests conflict or the expected tool is unavailable. Mark branches that have a documented answer separately from branches that require judgment. In the fictional room-booking case, an urgent request is not automatically authorized to override an existing reservation.

What to know

Make stopping an explicit option

A useful practice question can end with “pause and ask the booking owner,” provided that is what the source actually requires. Include the information the learner should gather before escalating and a clear indication that no confirmation has yet been issued. Avoid vague advice to “use common sense” when the point of the procedure is to define responsibility.

What to know

Do not create policy in feedback

Generated feedback may invent a grace period, priority order or exception approval. Compare every such detail with the source. If the rule is missing, leave the answer unresolved and seek an authorized decision in your real workflow. Our fictional examples illustrate this distinction; they are not operational instructions for a particular business and should not be copied into safety-critical or regulated procedures.

What to know

Maintain the branch separately

Record the source step, escalation role and lesson elements that depend on each exception. When the owner or process changes, update the route and verify that old links do not still point to the wrong person. Continue to the source-approval review before publishing a confident lesson. A shorter lesson is not better if the one boundary that prevents a wrong action has been removed.

What to know

Three fields for an escalation

State the condition that triggers the stop, the role that can resolve it and the information needed for that review. Leave the final decision open when the learner is not authorized to make it. This keeps recognition and approval visibly separate.

Continue when useful

Next: Resolve source conflicts

Do not let a course generator choose between inconsistent procedures; identify the authoritative owner and version first.

Open Resolve source conflicts →

Sources used for this page

These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.

  1. CDC Quality Training Standards — Standards and certification reference · cdc.gov · Publisher independence not verified · checked 2026-10-02