Software & apps · Practice guide

Update training reminders when staff roles change

Illustrative situation

A renewal reminder follows an old timetable after a staff member changes role. Someone changing role may need different training reminders. Reusing their old timetable can cause unnecessary chasing and miss new requirements. Keep renewal rules connected to current roles and approved expectations.

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

Base reminders on the current approved role requirements and recorded completion dates. Keep exceptions explicit rather than altering dates merely to clear an overdue list.

An example to discuss with your team

Change a fictional staff role; inspect which requirements are added, removed or retained.

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

Move a fictional employee between roles and inspect which reminders are added, removed or retained. Who approves those changes? Record exceptions with a reason and review point. Altering completion dates to clear an overdue warning leaves the next manager a misleading record.

Review requirements when a role changes

Include training responsibilities in the process for a new role, temporary cover or a move between clinics. Ask the training lead which requirements apply and which previous completions remain relevant. The system should make the resulting changes visible to the staff member and their manager, with a clear route for questions.

Try a fictional move halfway through a renewal period. Ask which reminders remain, which new tasks appear and what happens to work already in progress. Keep past completion dates accurate. Changing a date just to make an overdue warning disappear will make later reminders harder to trust. Where the organisation approves an exception, record its reason and review point through the agreed process. Look at unexplained overdue items with the team rather than judging the system only by how many emails it sends. Some items may need action; others may expose an outdated role assignment or a rule that nobody has reviewed since the service changed.

How to check the result

Count overdue items with no recorded explanation or next action.

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.