This tool helps continuity planners estimate whether a proposed minimum staffing level is credible during disruption. It is most useful after BIA workshops, when teams know the minimum service level but have not yet tested whether the available people and role coverage can actually sustain it.
What this tool is designed to decide
Use current role coverage, shift design, cross-training and workload evidence rather than the normal headcount. Minimum staffing is the number and mix of people needed to sustain the minimum service level during disruption, not simply a percentage of the department.
The result is a planning challenge, not permission to reduce staffing. Check whether the remaining people have the required authority, access, location, skills and fatigue tolerance, and whether several critical activities compete for the same specialists.
Assess Minimum Resource Staffing Planner
Rerun the assessment after organization changes, outsourcing, automation, seasonal demand, new locations or material changes in the BIA. Staffing assumptions are especially sensitive to turnover and changes in single-person knowledge dependencies.
Typical people required in normal operation.
People expected to sustain the minimum acceptable service.
Planning assumption for unavailable staff.
Count of key roles with no trained backup.
Percentage of minimum staff realistically able to work from alternate arrangements.
How to interpret the result
A high score means the proposed minimum headcount is numerically achievable under the absenteeism assumption and is not heavily undermined by single-person roles or weak alternate-work readiness. A medium score indicates the headcount may be available but the staffing model is fragile. A low score means the minimum service is likely to fail because there are too few available people, too many single-person dependencies or insufficient alternate-working capability.
Retain the service level, required roles, shift assumption, cross-training evidence, maximum sustainable duration and fallback arrangement. Where a critical role has no substitute, document the exposure and the approved treatment rather than hiding it in a total headcount.
Recommended corrective actions
- Cross-train at least two people for each role required in the minimum operating model.
- Document authority to temporarily combine, defer or suspend non-critical duties.
- Verify remote access, credentials, equipment and communications for minimum staff.
- Create call-in and escalation rules for prolonged disruption and shift handover.
- Test minimum staffing during an exercise rather than validating only the full team.
Challenge the plan with simultaneous absence and extended duration. A team that can cover one shift may fail on day two because the same specialists are required for recovery, operations and management reporting.
Governance and assurance
- Business owners should approve the minimum service and staffing assumptions.
- HR and workforce planning should validate absenteeism and availability assumptions.
- BCM should challenge single-person dependencies and ensure they become tracked actions.
Use realistic availability values and test the minimum service workload. The browser calculation is a starting point; it does not validate labour rules, health and safety limits, competence or local emergency staffing requirements.
Common mistakes to avoid
Do not allow arithmetic to average away key-person risk. Ten available generalists do not replace one unavailable administrator, approver, engineer or licensed specialist when that role is a hard dependency.
Actions should address the actual constraint: cross-training, delegated authority, documented procedures, remote access, alternate location, supplier support or additional on-call coverage. Verify the change through an exercise or operational test.
Evidence to retain
Align thresholds with the BIA's minimum business continuity objective and recovery duration. The tool should support a conversation between service owner, HR, operations and BCM rather than produce an isolated staffing number.
Worked staffing example
Assume a service normally operates with 24 people across several roles but the BIA states that a minimum 40 percent service level must be sustained for three days. A simple headcount calculation might suggest that ten people are sufficient. The planner should go further: two of the ten must be authorized approvers, one must administer a critical system, at least two shifts are required, and the same system administrator is also assigned to technology recovery. If only one trained approver is available on the second shift, the apparent minimum headcount is not credible. The corrective action may be cross-training, delegated authority, changed shift design or a different minimum service model.
Staffing evidence to retain
- Minimum service volume and duration from the BIA.
- Role-by-role skill and authority requirements.
- Shift, fatigue and handover assumptions.
- Known single-person or scarce-skill dependencies.
- Remote-work, access and location constraints.
- Exercise or operational evidence demonstrating the proposed staffing model.
Related BCM.Center knowledge
Availability and productive capacity are different. A person may be reachable but unable to work because of caring responsibilities, transport, device, access, site or network constraints; model those limitations explicitly.
Shift, fatigue and duration considerations
Minimum staffing is not a single-shift calculation. A service that can operate with six people for four hours may require a materially larger continuity pool for forty-eight hours because rest periods, handovers, travel, welfare, specialist availability and management supervision become limiting factors. Consider the duration of disruption, number of shifts, maximum safe working hours, weekend and overnight coverage, transport constraints, family-care impacts and the availability of supervisors. Where staff are expected to cover unfamiliar duties, include time for briefing and quality checking. Long-duration continuity plans should identify a sustainable staffing model rather than assuming the same minimum team can work indefinitely. Exercise the handover between minimum teams because loss of situational awareness during rotation is a common source of operational error.