A case that goes quiet
An employee has been off with a long-term condition. Your adviser sees them, writes a report, and suggests a review in six weeks once they have seen their specialist. The report goes to HR. Six weeks pass. Nobody books the review because the date only exists in the text of the report. Two months later HR asks what is happening, and the answer is that nothing has.
Across a caseload of long-term absence cases for many employers, several are in this state at any moment, and nobody knows which.
Why reviews fall through
Management referrals are handled as events: a referral arrives, an appointment happens, a report goes out. Long-term cases are not events, they are journeys with many steps, and the systems around them do not track the journey.
- The review date is in the report text, not in a field.
- The review often depends on something else first, such as a specialist appointment or a phased return starting.
- HR may or may not send a new referral for the review, depending on the employer.
- The clinician who set the review may not be the one available when it falls due.
- There is no list of open long-term cases by next action.
The cost of drift
The employee is left without the support the review was meant to provide. The employer's absence process stalls, which costs them money and may cost them a good employee. HR sees your service as reactive. And when a case is finally picked up, the clinician has to rebuild the history from scratch.
Long-term cases are also where your service's value is most visible to an employer. A good referral report is appreciated; a case that is steered back to work over several months, with reviews at the right moments, is what renews a contract. Drift in these cases is the quickest way to look like a provider who only answers the question in front of them.
| Case stage | What should be tracked |
|---|---|
| Initial assessment | Report date, recommendations, review date and reason |
| Waiting on a dependency | What it is, expected date, who will tell you |
| Review due | Invitation sent, booked, held |
| Phased return | Plan dates, check-in points, any change |
| Closure | Reason and date, confirmed with HR |
How we build long-term case tracking
- When a clinician finishes a report, they set the next review as a date and a reason, or record that no review is needed.
- Dependencies, such as waiting for a specialist letter, are recorded with an expected date and a prompt to check.
- Before the review, the system asks HR or the employee for any update the clinician needs, and invites the employee to book.
- Where an employer's contract needs a new referral for each review, the system requests it from HR automatically.
- Every open long-term case appears on a caseload screen by next action and date, with overdue items at the top.
- If the original clinician is unavailable, the case can be reassigned with its full history visible.
- HR sees the next step and date for each of their long-term cases, within what consent allows.
What the caseload looks like after
Every long-term case has a next step with a date. Your team can see at a glance which cases are waiting on what. Reviews happen when they were meant to. HR stops asking what is happening, because they can see it. And your clinicians walk into each review with the history in front of them.
It also gives your managers a real picture of caseload size by clinician and employer, which helps with planning and pricing.
When a case does close, the reason and date are recorded and confirmed with HR, so the caseload list only holds cases that are genuinely open, rather than a growing tail of cases nobody formally ended.
Is your long-term caseload like this?
- Review dates are written into reports and not tracked.
- HR has asked about a case that nobody had looked at for weeks.
- Cases wait on specialist letters with no prompt to check.
- There is no single list of open long-term cases.
- A case picked up by a new clinician means reading everything from the start.