Create intermediate Works with: Any AI

Contingency Plan for a Critical Deliverable

Decision tree Has example

Prepare an alternative route.

The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.

Create a contingency plan. The critical deliverable and its dependencies: [DELIVERABLE_DEPENDENCIES]. What could prevent it: [THREATS]. Deadline and consequences of missing it: [DEADLINE_CONSEQUENCES].

For each threat define an early warning indicator, a trigger point, and a response. Build alternatives: reduced scope version, manual workaround, additional resources, alternate supplier. Estimate cost and time of each in ranges using my inputs only. Provide a decision tree with the trigger date for committing to the contingency. Include a communication plan and a rehearsal. Mark unknown costs [TO_CONFIRM]. Close with a one-page summary for the sponsor.

Add a section on the cost of waiting, showing how each day of delay narrows options, and a rehearsal script for a 30-minute tabletop test of the plan. Include a list of the people who must be told when the contingency is triggered and a template for recording what was done, so that lessons can be captured afterwards.

Add a worked trigger table for an invented deliverable (a regulatory submission due on 30 June): early warning indicator, trigger date, trigger condition, response, owner and cost range, for three threats (key reviewer unavailable, data not ready, supplier failure). Show the decision tree with the final date on which the contingency can still be activated. Label it an illustration. Add a cost-of-waiting table showing which options disappear as each week passes. Provide a rehearsal exercise: a thirty-minute walk-through in which the team pretends one trigger has occurred, with prompts for the facilitator and a form to record gaps found. Include a closing checklist after the deliverable ships: what was triggered, what it cost, and which part of the plan should change. End with a one-paragraph statement of the minimum acceptable version of the deliverable, agreed in advance with the sponsor, so the team knows what good enough looks like when the contingency starts.

Fill in before use

Optional: type your details and the prompt above updates. Nothing is saved or sent.

Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.

Deliverable: data migration before the 1 September contract end.
Threat: vendor export delayed. Early warning: no sample file by 10 August. Trigger: 15 August.
Response options: manual export of the top 100 customers (cost 3 days of 2 people); extend the old contract by one month (cost to confirm); reduce scope to active customers only.
Decision tree: if no sample file by 10 August, escalate; if none by 15 August, start the manual export.
Communication: sponsor on 10 August; customers if a delay is likely.
Costs unknown: [TO_CONFIRM].

• risk