Insights · Business continuity · 5 minute read

Who Can Act When Your Systems and Leaders Are Unavailable?

Give the people on duty the authority, tools, and verified contacts they need to act when the usual systems or leaders cannot be reached. Then test the handoff.

By Vitaver Staffing ·

This guide draws on the Vitaver Playbook’s practice of naming the decision owner and confirming the handoff. Give the deputy the tools to act before the primary owner is unavailable.

Decide who can act without waiting for a meeting

Imagine that the finance platform and Microsoft Teams are unavailable while a payment batch is in an uncertain state. The people on duty need a way to reach each other, a trusted record of who can pause processing, and a way to verify the status of the batch. Put those decisions in an approved continuity policy and a short procedure the deputy can open outside the usual collaboration tool. The operational objective is to act within authority and retain a record the next shift can trust.

FEMA’s Continuity Guidance Circular discusses succession, delegations of authority, and resilient communications. Apply the concepts to the work the organization has designated essential. Name the person filling each role, who acts when that person is absent, which decisions the delegation covers, and when it starts and ends. Keep current contact details in a controlled directory with an alternate copy accessible to authorized responders.

Separate the decisions that have different owners

Make trusted access and communications independent

Choose an alternate communication path that remains usable if the usual identity provider, collaboration service, or network is involved in the incident. Test the actual sign-in path and who can reach it from each recovery location. Provide a pre-verified callback procedure for unexpected requests to change routing, payment instructions, credentials, or authority. Have a second designated person verify high-impact requests using an approved contact record. Log the decision through a channel the incident team has already authorized.

Maintain emergency access for the specific systems responders may need, such as the backup vault, domain management, or a recovery console. Microsoft’s Entra emergency access guidance is a product-specific example of thinking through independent authentication dependencies, designated secure workstations, and monitoring emergency account use. Have the system owner validate the approved emergency route for your system. Use designated accounts and devices, protect the credentials, monitor their use, and document how access will be reviewed after activation.

Prove the deputy can take the next shift

Give the deputy a procedure that fits the first hour. It should show the activation trigger, identity verification method, decision limits, trusted systems, alternate contact paths, and where to record decisions. Test it with the primary owner and normal collaboration tool treated as unavailable. Ask the deputy to reach the alternate team, find the authority to pause an at-risk process, record an update, and hand over the incident log to the next shift.

The continuity owner should review the procedure after changes in staffing, authentication, vendors, or contact channels. Archive superseded versions and keep an approved copy where the deputy can reach it during an outage. Accept the change when the alternate operator can find the current procedure, demonstrate the decision path, and state when authority returns to the normal owner.

← All Insights