Nothing in, nothing out: why your employee has a better record of their case than you do

nothing-in-nothing-out

An employee raises a grievance, or a claim arrives. Their account of what happened covers eighteen months — dates, who said what, what was agreed, what never followed. It is coherent, chronological and consistent, because it happened to them and they kept a record of it as it went along.

Now look at your side of the same events.

A manager’s notebook, if that manager is still with you. A Word file on a laptop that was wiped at offboarding. An email somebody sent to themselves so they would have it somewhere. A photograph of a handwritten note. Two letters that definitely went out, from a template nobody can now identify.

That asymmetry has always existed. What has changed is what the other side can now do with their half of it.

The part that is new

Eighteen months of notes, emails, meeting transcripts and screenshots can now be assembled into a structured chronology in minutes rather than weeks. Paste the lot into a general-purpose AI tool and it will produce a dated sequence of events, flag the inconsistencies, and cross-reference the account against the employer’s own published policy — which, for most large employers, is available online without anyone having to ask for it.

This requires no legal training and no expense. It is available to every employee in the country and a good many of them already know it.

Two consequences follow, and the second is the one that gets missed.

The first is that the employee’s account arrives better organised than it used to. That is uncomfortable but survivable if your own records are sound.

The second is that the raw material on their side has quietly grown. Meetings that used to leave no trace now generate transcripts automatically, because the organisation switched on transcription in its own collaboration platform. A conversation a manager remembers as an informal chat may exist verbatim, held by the employee, generated by the employer’s own IT estate, and stored nowhere in the case file.

Nothing in, nothing out

For thirty years the rule about systems was garbage in, garbage out. Feed a system poor data and it will give you poor answers with total confidence.

The AI era has not repealed that. It has simply added a version nobody talks about.

Nothing in, nothing out.

Run the employee’s pack through any tool you like and you will get an analysis. Run your own side through the same tool and you will get very little, because there is very little to run. No amount of technology compensates for records that were never captured in a retrievable form. The tooling is not the constraint. The input is.

“We do write things down”

This is where most conversations about case records go wrong, because the premise is usually false.

Good managers do make notes. In our experience the majority of them do, and they do it conscientiously. The failure is almost never that nothing was written down.

The failure is that there is no single place for it to go.

So it goes wherever that individual manager finds convenient. A notebook they keep in a drawer. A document saved to a personal drive. An email to themselves. A note in their phone. Each of those is a real record made in good faith, and not one of them is retrievable by anybody else, searchable, or part of the case file.

And when that manager is promoted, moves site or leaves the organisation, the record goes with them. Not through any misconduct — simply because it was never anywhere else.

The letters are the sharper problem

Notes are one half. Correspondence is the other, and it is the half that gets examined most closely.

Letters went out. Invitations to meetings, outcome letters, warnings, adjustments confirmed in writing. For any given historical case, three questions follow, and most large employers cannot answer any of them with confidence.

Which template was used?
The current one, or a copy somebody saved to their own drive some time ago and has been reusing since?

Had that template been amended locally?
A manager who edits a paragraph to fit the circumstances is being helpful. They are also, without knowing it, creating a document that no longer matches the organisation’s approved wording.

Did it reflect the policy in force at the time? Policies change. A letter that complies with this year’s procedure may not have complied with the one that applied when the case was live — or, worse, may have been generated from a superseded template long after the policy moved on.

“Nobody knows” is a poor answer at an internal appeal hearing. It is a considerably worse one at tribunal.

And that is your diligent manager

Everything above describes a manager who did the job properly. Who had the conversation, made the note, sent the letter and resolved the issue. The problem in their case is purely one of storage.

Now consider the rest of the estate.

Are the other managers following the policy at all? Consistently — employee to employee, site to site, shift to shift? Is the same conduct producing the same response in Newcastle as in Bristol, and from the manager who finds these conversations easy as from the one who dreads them?

How would anyone know?

This is the exposure that matters, and it is larger than any single case. Differential treatment of two employees in comparable circumstances is precisely the question that gets asked, and the honest answer for most organisations is that nobody is looking. Outcomes are recorded somewhere. Whether the process was followed, by whom, and in the same way, is not measured anywhere at all.

What actually happens next

Not a hearing, in most cases.

An employer who cannot evidence its own side does not usually fight and lose. It settles. The case never gets tested, a payment is made, a confidentiality clause is signed, and the whole thing is booked as a commercial decision.

It is worth being honest about what that decision actually buys.

It buys silence on one case. It changes nothing about how the next one will be handled, because the conditions that produced it — no single record, no version control, no view of consistency — are all still in place the following morning. And it teaches every manager who watched that raising a difficult case leads nowhere, which makes them slower to raise the next one, which makes that case worse when it finally surfaces.

That is not a commercial decision. It is a recurring cost with a discount applied each time.

Three things to check this week

None of these requires a project or a budget.

Pick a case that closed last year — ideally one that settled. Ask to see everything that was written at the time. Not a summary. The actual records. What comes back is what you would have taken to a hearing.

Ask where your managers keep their case notes. Not whether they make them. Where. The answers will not be consistent and some of them will be on hardware you no longer own.

Ask who can tell you whether policy is being applied the same way across sites. If the answer is nobody, that is the finding, and it is a bigger one than any individual case in your current caseload.