Most case management systems put a process on the case. The tasks stay tick-boxes.

If you work in HR or employee relations in the UK, you have almost certainly used some form of case management. It might be a module in your HR system. It might be a folder of Word files and an Outlook thread that turned into the official record. It might live in SharePoint with a status field and a shared drive of evidence.

Those tools help you see what is open, who owns it, and whether it closed. Many also let you add case notes or text updates. On a quiet week, that can feel like enough.

The crack shows up on a live case. Nobody is quite sure what comes next. Approvals and deadlines are chased through calendars and inboxes. Notes exist, but evidence and reasoning are still hard to pull back together with confidence.

That is the gap most systems leave open. They put a process on the case. The tasks stay tick-boxes. Case notes are not the same as steps inside the work.

That gap matters more when the process itself is under scrutiny. Chambers’ 2026 UK guide on HR internal investigations notes that workplace investigations now face heightened scrutiny over how they are run, not only what they conclude. Ministry of Justice tribunal statistics for 2025/26 also show single employment tribunal receipts up 39% on the previous year. When more cases are tested later, a system that only logged ownership and notes leaves you reconstructing the process from memory.

One struggle, three faces

Policy, training, and even a strong notes log still leave the same struggle. An exceptional investigator can keep one careful, up-to-date log and still have to do three hard things by hand: remember the process, arrange and chase the work around the log, and write everything in a shape that will still make sense months later. The system stores their words. It still relies on them to carry the process.

The Drift. Written policy, training, and statute rarely sit in front of the investigator on a live case, so the next step depends on memory. Inconsistent process across investigators is rarely about bad intent. It happens when the system only asks for another status update or note. The process only existed in someone’s head.

The Chase. Deadlines sit in calendars. Approvals sit in inboxes. Updates and welfare checks go out when someone remembers. People also have to remember who can approve what, and who legally has to act. Subjects and complainants wait. Investigators carry admin while they try to find the truth. A case list that says “in progress” only shows a label. And if the process lives in one head, the case stalls when that person is off.

The Reconstruction. A notes feed can look complete and still be a story built by hand. Evidence sits beside the note, not against the step it supports. Decisions sit in the prose. Unused material may never land cleanly in the file. Rules about what should be recorded, and how, depend on discipline. Weeks later, rebuilding the file is hard.

Under the ACAS Code of Practice, an unreasonable failure to follow a fair procedure can increase a compensatory award by up to 25%. That is process education, not legal advice. Day to day, the cost shows up earlier as confusion, chase, delay, and rebuilding files.

What task-level steps require

Closing that gap means those three faces live inside each task. They are not spare jobs people keep in their heads.

Guide. The next steps sit in the work itself, almost like training built into the case. Policy and statute sit there too, not only in a separate PDF. Investigators still make every judgement call. They are not left guessing whether the next move is a holding letter, a meeting, or a disclosure check.

Manage. Deadlines, approvals, and notifications run from the case. That includes who can approve what, when they need to act, and who legally has to do something. Welfare checks and updates are held like any other deadline. People should not have to remember the path, chase it through an inbox, or rebuild duties from side conversations. Investigators can investigate rather than arrange the process around it.

Capture. Notes, decisions, evidence, and unused material stay with the step they belong to as the work happens. Capture also helps keep the rules around that activity: what should be recorded, and how. When questions come, the record already shows what was considered, what was used, and what was set aside. What did not happen stays visible too.

None of that replaces the investigator. It changes where the process lives. Clarity and rigour sit in the case, not in whoever happens to remember the method this month.

When you assess a case management system for workplace investigations, ask three questions:

1. Does each task carry its own steps, with policy available in that work?
2. Do deadlines, approvals, updates and welfare checks hold inside the case?
3. Does the record build against each step as the work happens, including what was skipped?

Holding the process in the work

Moving from a case-level tick-list to task-level steps is a decision about where process, management, and capture should live. Memory and note-taking discipline will never be reliable enough across every investigator and every busy month.

We’ll run the process. You run the case.

That is the standard to hold any system to, including ours.

CaseGrid is building a case management system for workplace investigations around that standard. Every investigative task carries its own steps, with ACAS-aligned guidance, approvals, deadlines and the record inside them. If that gap is the one you feel, join the waitlist.