ZEBSOFT VIDEO TRAINING
Contingency plans and testing
02:21 · English · Anonymised demonstration · Transcript below
What this training covers
Define contingency plans, connect risks and ZAP workflows, and retain test results and review evidence.
Terminology, available options and workflows may differ with your configuration and permissions.
Video chapter guide
- 00:00 — Find the plans that need attention
- 00:11 — Define ownership and scope
- 00:29 — Explain the response
- 00:46 — Connect the supporting controls
- 01:02 — Open the linked workflow
- 01:17 — Review the workflow evidence
- 01:33 — Record a test or analysis
- 01:51 — Check the status against the evidence
- 02:05 — Keep the response current
Browse all video demonstrations
Video transcript
Open Contingency plans under Risk. Use the summary cards to find untested plans and plans due for review. Search for the event or equipment concerned, then open the relevant plan.
Use Add a contingency plan for a new scenario, or Edit an existing plan. Define its title, site, responsible job role, affected activities and location. Set validity and review dates, and link a controlled document where detailed instructions are held.
In Plan and links, explain the requirement, disruption and mitigation. Describe a practical response, including limitations. State who tells affected customers, what triggers communication and which channel to use, or explain why there is no customer impact.
Link the relevant risks, ZAP workflows and equipment. Choose workflows that support invoking or testing the plan. This demonstration uses an existing workflow to show the connection; select a workflow suited to your own contingency scenario.
The plan displays its related risks, workflows and equipment. Start opens a linked workflow for completion, while View results opens its existing completions. Review the associations so they support the intended response.
The workflow results page links back to the contingency plans it supports. Use the filters to find relevant completions and open the evidence or report. Check the completion status and what was actually tested; a score alone does not establish readiness.
On the plan, choose Record a test. Select Test or Analysis, identify who carried it out and enter the date and next test date. Record the result and notes clearly enough to explain the scenario, evidence, limitations and follow-up. Save to log retains the entry.
Review the test log alongside the plan status. This older example is marked Tested but has no logged tests, and its dates have expired. Check the supporting evidence and current dates before relying on a plan.
Return to Due for review to prioritise updates. Assign follow-up through Tasks where needed, revise the plan and supporting workflows after changes, and test again. Keep the response instructions, retained evidence and review dates aligned.