Support & operations · Practice guide

Keep staff informed with useful outage updates

Illustrative situation

An outage message says only that the team is looking into it. Staff cannot tell which services are affected or what they should do meanwhile. During an outage, staff need to know what is affected and what they can do meanwhile. A useful update can provide that information before the cause is known. Avoid filling the gap with an unsupported repair estimate.

Healthcare website support desk with a system checklist, telephone and orange notebook.
Know who to call and what help your support arrangement includes.

What this means for your practice

Communicate verified impact, available alternatives and the next update time. Avoid speculative causes or promises the investigation cannot support.

An example to discuss with your team

Draft an update when the cause remains unknown and check that it is still useful without inventing a resolution estimate.

Healthcare website maintenance with infrastructure, a status panel, tools and an operational checklist.
Monitor the useful journey, not just whether a server responds.
Healthcare backup and recovery illustrated by storage copies, an archive folder and a restoration route.
Test whether a backup can restore a usable service.

How to review the arrangement

Ask the supplier to draft an example update with an unknown cause. It should state verified impact, any approved temporary route and when the next update will arrive. Assign the communicator. Meeting that update commitment helps staff plan even when the investigation has not yet produced a resolution.

Write an update staff can act on

A useful message says which tasks are affected, what is known to still work and any approved temporary arrangement. If the cause or repair time is uncertain, say so plainly. Staff can often plan around an honest description of the current position more effectively than an optimistic estimate that keeps moving.

Agree who sends the update and when the next one will arrive. That next communication can report no change if the investigation is still underway, but should keep its promise and describe any new effect on the service. Use a fictional outage to ask reception what they would tell a caller after reading the message. If they still do not know whether to use the form or another route, the update needs more practical detail. After recovery, explain which functions have been checked and whether any temporary restrictions remain, so staff can resume the normal process with a shared understanding.

How to check the result

Measure whether promised update times were met and whether changes in impact were communicated.

Turn reading into a next step

Your action checklist

Work through these checks with your team or supplier. Tick the ones you have resolved and leave unknowns open.

Checks to discuss

Record what you know, what is still missing and the answer you need from your team or supplier.

Use project decisions only, without personal, patient or confidential details. Entries stay in this page and are not submitted to Kay & Co. Copy or download before leaving; this page does not save your notes.

Further reading

These sources provide background for the topic. The practice examples and checklist are illustrative planning suggestions from Kay & Co.

Related guides

Need help with this?

Tell us what is getting in the way. Kay & Co. can help you understand the options and turn the next step into something that works for your practice.

Explore support & operations services or discuss your project.

Try the free Healthcare Digital Planner to find your starting priority.