This contingency plan template prepares a specific alternate route, its activation conditions, and the evidence needed for a real decision. The orientation example separates an unknown trigger, an unready fallback, and supplied model prerequisites without activating anything.
Define the ordinary disruption and the alternative
The original fictional plan concerns delivery of a volunteer orientation, not emergency response or equipment repair. The normal route presents an approved slide deck on a local projector. The first session is planned for 14:00, with a proposed decision checkpoint at 13:40. No actual date, venue, contact details, or authorized person is supplied.
Asana's contingency-plan template describes planning an alternative in advance and defining the conditions for using it. Apply that principle to a bounded situation where the team can specify what must be true before deciding to change route.
Here is the complete teaching decision card:
| Field | Proposed arrangement |
|---|---|
| Normal route | Approved slide deck presented on the local projector. |
| Checkpoint | 13:40 for the planned 14:00 first session. Actual date and local arrangements remain to confirm. |
| Trigger | Equipment owner actually confirms that the deck cannot be presented for this session. A missing reply does not establish that condition. |
| Fallback | Approved printed facilitator notes and participant agenda, with required copies, accessible formats, and facilitator coverage checked. |
| Decision owner | Responsible orientation lead; actual authority, person, and contact route must be confirmed. |
| If prerequisites are incomplete | Bring the gap to the lead for an actual decision, which may require another arrangement or postponement. Do not pretend the fallback is ready. |
| Return to normal | At a later agreed break, after an equipment check and the lead's decision; no automatic mid-instruction switch. |
Keep the trigger precise enough that someone can ask for evidence. “Projector might be a problem” identifies a concern. “The equipment owner confirms the deck cannot be presented for this session” defines the proposed decision condition.
Read three different cases
All records below are invented teaching inputs. They are not an actual equipment report, approved operating plan, or authorization to change a session.
| Case | Supplied input | Decision-card reading |
|---|---|---|
| A · Fallback proof missing | Equipment owner confirms the deck cannot be presented. Printed-copy readiness and facilitator coverage are unconfirmed. | Trigger met in this model; fallback prerequisites unresolved. Ask the lead to resolve the gap or choose another arrangement. |
| B · Model prerequisites supplied | Same equipment confirmation. Fictional record N1 identifies approved facilitator notes FN1 and agenda PA1, confirms required copies/access formats checked, and confirms facilitator-role coverage. | Trigger met and fallback prerequisites supplied in this model. An actual authorized lead must still decide whether to use it. |
| C · Trigger unknown | No equipment-owner confirmation is supplied. | Trigger unknown. Do not switch merely because confirmation has not arrived. |
Choose Case A to inspect the two separate conditions. The projector confirmation does not provide printed materials. Choose Case B to see what N1 adds: specified fallback resources and coverage. It does not add the missing actual decision.
The example always shows Actual decision still needed separately. Selecting a model case cannot approve a real fallback, send a notice, print a document, or establish who will facilitate.
Prepare the sequence before the checkpoint
- Obtain the equipment owner's actual status through the agreed contact route.
- Compare that status with the trigger. If it remains unknown, obtain the information rather than treating silence as confirmation.
- If the trigger is met, check the fallback's material versions, approval basis, copies, access format, and facilitator coverage.
- Present the trigger and prerequisite evidence to the authorized lead. Record the real decision and any conditions through the organization's normal process.
- Follow the agreed delivery and communication arrangement. If the normal route becomes available later, wait for the planned break and an actual review before changing it.
Check the alternative with the facilitator in advance. Can the approved notes and agenda support the intended session in the available format? What would still depend on projected content? Resolve that question before the checkpoint instead of assuming a stack of pages is a workable replacement.
A review copy in your NOS workspace can put the trigger and fallback requirements together for that conversation. Clarify an ambiguous static phrase such as “If unavailable” to state whose confirmation is needed and for which session. Keep the actual approved plan, local materials, and contact procedure accessible through the team's agreed arrangement; an online review page should not be the only place the fallback exists.
Keep return conditions in the plan
A projector becoming available does not automatically make a switch during instruction useful. The example's return rule uses a later agreed break, a check that the normal route works, and the lead's decision. It preserves the delivery arrangement until that review point.
For your own plan, specify the disruption, the alternative's limits, the decision authority, and what ends the alternate arrangement. Use actual resource and access checks; do not fill a readiness field with a proposed plan to obtain the resource later.
Copy a prompt for the decision card and case review
Create one complete HTML contingency-plan review page.
Bounded ordinary work and normal route: [PASTE]
Actual trigger, evidence source and decision checkpoint: [PASTE]
Fallback materials/resources, approval and access prerequisites: [PASTE]
Actual decision authority, contact route and record process: [PASTE]
Decision sequence and return-to-normal condition: [PASTE]
Separate trigger state, fallback readiness, and actual decision.
Do not infer a trigger from silence or treat a planned fallback as
ready without prerequisite evidence. No invented contacts, approval,
dates or resources.
Include this original fictional volunteer-orientation plan:
Normal: approved slide deck on local projector; first session 14:00.
Proposed checkpoint 13:40. Actual date/person/contact route unspecified.
Trigger: equipment owner confirms deck cannot be presented for this
session. Fallback: approved printed facilitator notes and participant
agenda, checked required copies/access format and facilitator coverage.
Decision: actual authorized orientation lead, still to confirm.
Case A: equipment owner confirms unavailability; copy readiness and
facilitator coverage unconfirmed. Trigger met; fallback unresolved;
lead must resolve/choose another arrangement or postponement.
Case B: same equipment confirmation plus fictional N1:
approved facilitator notes FN1 and agenda PA1, required copies/access
formats checked, facilitator-role coverage confirmed. Model prerequisites
supplied, not an actual lead approval or activated fallback.
Case C: no equipment-owner confirmation. Trigger Unknown; no default
switch. Retain actual decision still needed in every case.
Sequence: obtain actual status via agreed route; check trigger;
check fallback versions/approval/copies/access/coverage; present
evidence to lead; record real decision and follow agreed delivery.
Return only at a later agreed break after equipment check and lead
decision, not automatically mid-instruction when projector returns.
All cases invented; no actual session or completed action represented.
Provide complete decision card, Case A/B/C selection and separate
Trigger/Fallback prerequisites/Actual decision still needed output.
Show exact source inputs beside interpretation. No Activate/Send/
Print/Approve controls or incident-control-console appearance.
Add a blank plan scaffold and temporary review notes; preserve
typing across views and confirm reset. No employee assessment,
emergency guidance, live equipment control or integration.
Use at least 16px text, native labeled controls, visible focus, stacked
records at 360px without overflow. Inline CSS/JavaScript, no external
assets, network or storage. Return full HTML and unresolved decisions.
Check the generated Case B carefully: N1 can make the modeled resource checks explicit, but the actual decision must remain separate. In Case A, leave the missing copy and coverage evidence unresolved.
Put the evidence at the decision point
Before the agreed checkpoint in your actual session plan, establish where the equipment confirmation and fallback checks will be recorded, and who can make the decision. Verify that the facilitator can obtain the materials in the agreed form.
At the checkpoint, ask two concrete questions: what establishes the trigger for this session, and what establishes that the alternative can actually be delivered? Give the decision owner those records, including any remaining gap.