Software & apps · Practice guide

Keep improvement actions visible after an incident review

Illustrative situation

An investigation closes while several agreed day-to-day changes remain unfinished. Finishing a review is different from carrying out the changes it recommends. A closed record should not make outstanding training, process changes or equipment checks disappear. Give each agreed action its own owner and a clear description of the evidence needed to show it has been completed.

Healthcare scheduling software, planning board and organised folders in a blue, white and orange office.
Choose software around the work your team needs to do.

What this means for your practice

Track corrective actions as owned tasks linked to the original record. Closing a review and completing all actions are different events that should remain distinguishable.

An example to discuss with your team

Close a fictional review with open actions; those tasks must remain visible to their owners.

Healthcare software workflow connecting task cards, a checklist and a database.
Map the work and the information it depends on.
Healthcare software testing with normal paths and a separate exception route.
Test the exceptions as well as the normal workflow.

What to ask before you choose

Ask to see a fictional review closed with two actions still outstanding. The action owners should still find their tasks, and a manager should see what remains unresolved. For example, publishing revised instructions may complete one action, while checking that staff can find them completes another. Agree who accepts the evidence before marking the improvement finished.

Define what finishing each action means

An action such as 'improve instructions' is difficult to close consistently. Describe the change and the evidence the responsible person will review. For example, the task could be to publish an approved procedure and show that reception can find it. Keep the evidence proportionate to the action rather than demanding a large report for every small correction.

If several actions depend on one another, make that relationship visible. Staff training may depend on the revised instructions being ready, so moving a deadline can affect more than one item. Record why a date changes and who agreed it. At a review meeting, ask what remains to be done and what is awaiting acceptance. A task marked complete by its author may still need someone else to check the result. The software should help the team follow that distinction without hiding unfinished work when the main review record is closed.

How to check the result

Track actions awaiting evidence rather than merely marked complete.

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 software & apps services or discuss your project.

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