Software & apps · Practice guide

Make incident reporting easier for staff

Illustrative situation

Staff avoid an incident form because it asks for investigation detail they cannot know at submission. Someone reporting an incident may know what they saw but not why it happened. A form that expects an investigation at this stage can discourage reporting or invite guesses. Help staff provide a clear factual account, with an explicit way to say that something is unknown.

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

Separate an initial factual report from later investigation. Your organisation's responsible leads should define required information and escalation arrangements for its actual setting.

An example to discuss with your team

Submit an incomplete fictional account; the system should preserve it without inventing missing facts.

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 try the form as a staff member with only part of the information. Can they explain the event and receive a reference without inventing details? Your responsible leads should decide what information and escalation routes are needed. The form should make those routes easy to find rather than leaving staff to interpret a generic warning.

Help someone report what they actually know

Read each question from the perspective of a staff member who witnessed part of an event. Can they distinguish a fact from an interpretation? Is there room to explain uncertainty? Ask the practice's responsible leads to agree what must be captured immediately and what can be added during a later review.

Keep the form's completion message useful. It should explain that the report has been received, provide the appropriate reference and make any agreed next step clear. It should not imply that an investigation is complete or that an urgent issue has been resolved. Try the form on the devices staff are likely to use, including a longer description and a correction before sending. Review where people abandon it or repeatedly need clarification. Those observations can improve the reporting experience while leaving the organisation's actual incident-handling responsibilities with the people authorised to set them.

How to check the result

Measure abandoned forms and reports returned for essential clarification.

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.