Prevent
Threat: connectivity failure.
Maintain an independent backup connection and test failover. Assign an owner and record test evidence.
FICTIONAL EXAMPLE ยท SAMPLE WALKTHROUGH
Keep customer support running.
Explore how one critical activity connects to its threats, preventive measures and recovery arrangements. These are illustrative choices, not recommendations for your organisation.
1. What matters most?
Service: Customer support. Activity: Respond to urgent customer requests.
Consider who depends on this activity and how harm increases while it is unavailable. The example team proposes a four-hour recovery target, subject to business impact assessment and testing.
2. What could interrupt it?
A loss of connectivity could prevent the team from accessing its support system. Record the evidence behind likelihood, the severity of disruption and uncertainty before ranking this against other threats.
3. Build the bow tie
Loss of control
The team cannot access the support system.
Define a clear trigger for invoking the response arrangements.
Mitigate and recover
Consequence: urgent requests are delayed.
Use an agreed alternative contact channel, triage urgent requests and reconcile records when service returns. Test the workaround's capacity.
4. Check whether the arrangements work
Exercise the connectivity loss scenario. Measure the time to restore a minimum service, identify gaps and give each improvement an owner and due date.
This walkthrough contains no editable plan or downloads. The desktop edition will provide the full planning workspace.
You have completed the sample. The desktop edition adds your own activities, guided entries, saved plans and exports. Paid downloads are still being prepared.