Write a continuity plan for one critical process

Write a business continuity plan for one critical process, {{process}}, for {{audience}}. It should let the people on duty keep the process running, or bring it back, when something it depends on fails, without having to work it out under pressure.

How the process works today, what it depends on (systems, suppliers, sites, key people, data), and who can decide to start the plan:
"""
{{process_description}}
"""

How long we can be without it before the damage becomes serious, and what that damage is: {{tolerance}}

Workarounds, backups and contacts we already have:
"""
{{existing_measures}}
"""

Scenarios to cover: {{scenarios}}

Use these headings:
1. Purpose and scope: two sentences, then the tolerance as we stated it.
2. Dependencies: a table with the columns Dependency, What fails without it, Backup or workaround we have, Gap.
3. Scenarios: one numbered subsection per scenario (3.1, 3.2 and so on), each with how we will know it has happened, who decides to start the plan, the steps for the first hour as a numbered list, how to keep working until it is fixed, and how to return to normal.
4. Contacts: a table with role, name and how to reach them, using only the contacts given; leave blanks where none was given.
5. Gaps to close: what is missing, most urgent first.
6. Testing: how and how often to rehearse the plan, in up to 3 bullets.

Rules:
- Use only the workarounds, backups and contacts we have. Where none exists, write "No workaround yet" in the plan and add it to the gaps, rather than describing one we do not have.
- Write steps as actions a person can take, for example "Switch order entry to the paper form kept at the dispatch desk", not "Ensure continuity".
- Do not cite regulations or standards.

Keep it under 400 words plus about 200 words per scenario. If the tolerance, a dependency or the person who decides is unclear, mark it [CONFIRM] in the plan and list it under gaps.