Before you use it
- Use when
- The receiver may face a predictable branch after the sender is unavailable.
Keep this limit in mind
- Contingency planning should cover plausible high-impact branches, not produce an unreadable tree of remote possibilities.
Why it matters
For the important next action, include the most plausible failure or change in conditions and the prepared response. Name the trigger, not just the fallback. This prevents the receiver from having to rediscover the sender's risk reasoning at the exact moment the plan starts failing.
Steps
- The receiver knows both the normal next step and the response to at least one material foreseeable branch.
An example
'Run batch 3. If replication backlog exceeds 20 minutes, stop the batch and notify the interface lead.'
Check your result
The receiver knows both the normal next step and the response to at least one material foreseeable branch.
An idea to explore.
Try this idea.
Inspect the example, try the idea in your situation, then check your next move.
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Connected ideas
You are readingHand off the contingency with the task
Ideas that link here
These ideas link to this one. Check their conditions and limits before use.
Useful with this ideaHand off the uncertainty, not just the status
Evidence and sources
AHRQ's I-PASS structure includes situation awareness and contingency planning so the receiver knows what may happen and what to do next.
Contingencies should cover plausible high-impact branches, not every imaginable scenario.
Tool: I-PASS · Situation Awareness & Contingency Planning
All sources (1)
Edition and review
Version 0.1.0
No review details are supplied for this edition.
