Software & apps · Practice guide

Give each incident report a clear reviewer

Illustrative situation

A submitted day-to-day incident sits in a queue because every manager assumes someone else is reviewing it. A shared queue can hide the assumption that somebody else is dealing with an item. Staff who raised a concern need confidence that it reached the right reviewer, while managers need to see work that lacks an owner. A named deputy matters as much as the initial assignment.

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

Make ownership explicit at each administrative stage. Review escalation rules with the accountable team rather than treating a software timer as the organisation's incident policy.

An example to discuss with your team

Remove the assigned reviewer from the team; the open item should enter a managed reassignment process.

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 your supplier what happens to open reports when a reviewer goes on leave or leaves the organisation. Use a fictional case that has already been reassigned once. The history should explain the handovers, and the new reviewer should see the next administrative action. Escalation timings should follow decisions made by the responsible team.

Make handover a visible action

Agree how a reviewer accepts responsibility and what happens if they cannot take the work. A report that is simply placed in a shared list may still be unowned. The responsible lead should be able to see unallocated items and know who is expected to resolve the gap.

Test a handover midway through a review using fictional information. The replacement should find the current position, the next action and relevant earlier decisions without relying on a private message from the previous reviewer. Keep reasons for reassignment understandable, particularly when work moves across teams. During leave planning or staff departures, review open work as well as account access. Removing a person's login does not by itself arrange cover for their tasks. Ask the accountable team how urgent or overdue items should be escalated and confirm that the software's notifications reach the role actually covering the work.

How to check the result

Count unassigned reports and administrative actions with no follow-up owner.

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.