A monthly audit that finds the same thing
Every resident has a care plan with several sections, and each section should be reviewed on a cycle your policy sets, or sooner when something changes. Reviews are shared between keyworkers and nurses. Each plan records when it was last reviewed on its front page.
Once a month someone goes through the plans and counts the ones that are overdue. There are always some. A keyworker was on leave. A resident came back from hospital and nobody triggered a review. A section was reviewed but the date was not updated. The audit finds them, a list goes on the notice board, and the next month it finds a different set.
Why reviews slip
Review dates are scattered. They live on the front of each plan, or in a field in each resident's electronic record, and there is no one place that lists them all by date. Unless someone goes looking, a due date passes silently.
Event-triggered reviews are even easier to miss. When a resident returns from hospital, has a fall or their needs change, your policy may ask for a review then and there. That depends on someone remembering in the middle of a busy day.
Keyworker changes, leave and staff turnover then separate the review from the person who should do it.
Electronic care planning systems do not always solve this on their own. Many hold a review date for each plan, but the screen that lists them is buried, or it shows every resident rather than what is due this week for one keyworker. So the information exists and still nobody sees it at the right moment.
The effect of overdue reviews
| Issue | Result |
|---|---|
| Overdue reviews | Plans that may not reflect current needs |
| Triggered reviews missed | Changes after a hospital stay not captured |
| Reviews found by audit | Always catching up, never ahead |
| Owner unclear | Reviews waiting for a keyworker who has left |
| No forward view | Busy months with many reviews due at once |
The key point is that the review itself is clinical and care work, which your team does well. What fails is the reminder system around it.
A review schedule that runs itself
- A review schedule for every resident and plan section, holding the last review date, the next due date and the owner.
- Due dates read from your care planning system's API or export where possible, so the schedule stays in step with the plans.
- Trigger events: when a hospital return, fall or other event you define is recorded, a review task is created for the owner automatically.
- Reminders to the owner ahead of the due date, and a daily list for the nurse in charge of anything due or overdue on their unit.
- Reassignment when a keyworker leaves or is on long leave, so reviews do not sit with someone who is not there.
- A manager view with overdue counts by unit and a forward look at the coming weeks.
We set the review rules from your policy. We do not decide how often a plan should be reviewed or what a review contains.
Staying ahead instead of catching up
Keyworkers see what is due in their own list before it becomes overdue. Reviews triggered by events appear on their own. The monthly audit becomes a check that the process is working, rather than a hunt for missed dates.
The manager can also see a busy month coming and plan time for it, rather than finding twelve reviews due in the same week.
Is this your review cycle?
- Overdue care plan reviews are found at monthly audit
- Reviews after hospital returns are sometimes missed
- Review dates live only inside each plan
- Reviews stall when a keyworker leaves
- You cannot see how many reviews are due next month