Who keeps the service moving when a system stops?

What we found in the news

NIST’s 2024 small-business guide to its Cybersecurity Framework (opens in a new tab) includes a useful instruction about recovery:

“Understand who within and outside your business has recovery responsibilities.”

— National Institute of Standards and Technology, February 26, 2024

The guide addresses cybersecurity risk. The question it raises for our purposes is operational: when a system becomes unavailable, do the people running the service know who can decide what happens next?

Technical recovery belongs with the appropriate specialists. A service team also needs to understand its own decisions, communication responsibilities, and approved continuity arrangements.

Why this matters to us

Imagine the booking system is unavailable as colleagues arrive for a morning program. The reception team wants to know which arrivals can be confirmed. A manager is trying to contact the technology provider. Someone is already asking whether to call participants.

Each person has a sensible concern. Without agreed responsibilities, several people may make overlapping calls while another necessary decision waits.

At genus, we are interested in the connections between these pieces of work. The people restoring a system and the people welcoming participants need different information. They also need a dependable way to keep their decisions aligned.

Separate the decisions that need making

Work through a short, ordinary interruption with the colleagues who would actually be present. Who assesses whether the planned service can continue? Who decides that an activity must change? Who can authorize additional help?

Then ask who contacts staff, participants, relevant partners, and the technology provider. Identify cover for each responsibility. A plan built around one person answering their phone immediately is a useful place to start improving.

Record how the team will find approved instructions when the usual system cannot be reached. Use the organization’s established arrangements for information security, privacy, and professional oversight. An improvised shared spreadsheet or personal messaging account should not become the default home for care information.

The aim is to make decisions possible within appropriate boundaries.

Prepare an explanation people can act on

A participant may not need a technical account of the interruption. They do need to know whether their arrangements have changed, what the organization can confirm, and where to ask a question.

Prepare a simple structure for updates. Explain the practical effect, the available options, and when another update is expected. Avoid guessing a restoration time or saying everything is normal before the relevant checks are complete.

Consider different communication needs. A notice on a website will not reach everyone who is already travelling. A telephone message may be inaccessible to someone who uses a different contact method.

Agree who keeps the explanation current so that colleagues do not give conflicting answers in good faith.

Plan the return to ordinary work

Recovery has another operational step: reconciling what happened during the interruption.

Which changes were agreed through an approved alternative process? Who checks them against the restored system? How will the team avoid repeating a request, overlooking an arrangement, or treating an incomplete record as final?

Give that work time and an owner. A screen returning to normal does not tell a manager that every service commitment has been checked.

After the event or rehearsal, ask colleagues where the plan became difficult to use. Look for missing contacts, unclear authority, or information that could not be found. Assign the necessary changes and arrange a later check that they have been made.

What this means for the people you serve

People should be able to understand the options affecting their day. Invite them to explain practical consequences before assuming an alternative arrangement will work. A changed time may affect transport, employment, or support from another person. Keep those choices visible while the organization resolves the interruption.

The genus connection

Today, configured genus staff workspaces support operational records and workflows according to the modules and permissions in use. Organizations still need continuity arrangements appropriate to their service.

This article does not claim offline capability, automatic recovery, or uninterrupted availability. It asks leaders to plan the human decisions around the technology and to test the arrangements they actually have.

One question for your next team meeting

If our usual system stopped tomorrow morning, which service decision would be waiting for an owner?