This tool evaluates communication resilience rather than message quality. It is designed to expose cases where a crisis plan lists several channels but they all depend on the same identity provider, network, device estate, directory, cloud tenant or telecom provider.
What this tool is designed to decide
This interactive BCM.Center tool is intended to support structured professional judgement, not replace it. The result should be used as a documented discussion aid during business impact analysis, recovery strategy design, continuity planning, exercise preparation, incident governance or assurance. The strongest use of the tool is to make assumptions visible, create a repeatable scoring conversation, and expose where evidence is weak or conflicting.
Use current, organization-specific inputs wherever possible. Avoid treating a single numeric result as an approval decision. A mature continuity program should retain the underlying evidence, record who supplied the inputs, identify the review date, and document any management override. Where an input is uncertain, use the more conservative value and record the uncertainty for follow-up.
Interactive assessment
Enter the current values, then calculate. All processing happens in your browser; this tool does not save the values to BCM.Center.
Count only channels with meaningfully different failure dependencies.
How confident you are that priority contact information is current and reachable.
Availability of contact lists, templates and procedures without normal systems.
Ability to use channels if primary SSO/identity services fail.
Percentage of priority recipients successfully reached in the most recent representative test.
How to interpret the result
A high score means the organization has multiple genuinely independent ways to reach priority stakeholders and can access critical communication information during technology disruption. A medium score often indicates that several channels exist but share hidden dependencies. A low score means a compound outage could disable both the communication platform and the information needed to use the fallback.
The numerical output is only useful when the scoring basis is consistent. Re-run the assessment when assumptions, suppliers, staffing, technology, incident conditions, regulatory expectations or recovery dependencies change. If two business owners produce materially different scores for the same scenario, treat the disagreement as a governance issue that needs evidence and facilitation rather than averaging the numbers without discussion.
Recommended corrective actions
- Maintain an offline or separately hosted copy of priority contact data and templates.
- Test at least one fallback that does not rely on the primary identity provider or corporate network.
- Measure actual reach rates and acknowledgement, not only message dispatch success.
- Define communication priorities for staff, customers, regulators, suppliers and media.
- Include contact-data maintenance and fallback-channel testing in the BCM assurance calendar.
Corrective actions should be owned, dated and traceable. High-priority actions should connect to the continuity improvement backlog, risk register, exercise program or recovery strategy decision record. Closure should require evidence, not only a status change. Examples of evidence include approved procedures, tested alternate arrangements, supplier commitments, technical recovery results, call-tree tests, staffing rosters and exercise observations.
Governance and assurance
- Communications owns message governance; BCM owns continuity requirements for the communication capability.
- Technology should document shared dependencies across channels, including identity and network services.
- Privacy and data-protection controls should apply to offline contact lists and alternate platforms.
Review the assessment at least when the related process, service, dependency or recovery strategy changes. For critical services, consider independent challenge by the BCM function, risk function, technology recovery lead, supplier manager, facilities lead or crisis management team as appropriate. The review should confirm that the inputs remain current and that the resulting treatment is proportionate to the operational consequence.
Common mistakes to avoid
Do not use the tool as a substitute for a BIA, risk assessment, recovery plan or exercise. Do not inflate scores to justify a preferred investment and do not suppress scores to avoid remediation. Avoid combining unrelated services into one assessment because different dependencies and recovery objectives can disappear inside an average. Do not assume that a documented workaround is effective until it has been demonstrated under realistic conditions.
Another common mistake is to confuse availability with recoverability. A supplier, application or facility may be available most of the time but still have weak recovery capability after a severe disruption. Likewise, a plan may exist but depend on unavailable people, inaccessible credentials, untested data restoration or a single communication channel. The assessment should focus on the ability to sustain or recover the required business outcome.
Evidence to retain
Retain the completed assessment, input source, decision owner, review date, supporting evidence and resulting actions. Where the score is used to support funding or acceptance of residual risk, retain the approval and rationale. During an audit or post-incident review, this evidence is more valuable than the score itself because it demonstrates that the organization understood the assumptions and made a deliberate decision.
Related BCM.Center knowledge
- Crisis Communications Plan
- Mass Notification for Business Continuity
- Media and Spokesperson Crisis Preparedness
BCM.Center tools are educational practitioner aids. Adapt thresholds, scoring scales and decision rights to your organization's risk appetite, regulatory obligations, sector, operating model and approved business continuity management system.
Separate channel availability from message governance
Communication resilience depends on both technology and operating discipline. A fallback platform is not useful if nobody has access, contact groups are outdated, approval rules are unclear or staff do not know when to switch channels. Define who can authorize emergency messaging, who maintains recipient data, who approves external statements, how acknowledgements are monitored and how failed deliveries are escalated. Establish a minimum offline communications pack containing priority contacts, message templates, regulatory notification references, spokesperson details and channel activation instructions. Test the pack without access to the normal corporate network. The test should measure successful receipt and acknowledgement by representative stakeholders, not simply whether the platform reported that a message was sent.