I'll tell you where the damaging material almost always comes from. Not the HR department. Not the executive who signed the termination letter. It comes from a team lead who meant well and had no training.
The front-line manager is the one sending texts. They're the one who mentions in a meeting that the team is stretched thin because of So-and-so. They're the one who, out of genuine curiosity, asks what's actually wrong. And every one of those moments gets documented by somebody, eventually, and read back in a context where it sounds a great deal worse than it felt at the time.
Organizations invest in policy and ignore the person actually executing it. That's backwards. The policy rarely causes the claim. The Tuesday afternoon conversation does.
Train Them on the One Question They Must Not Ask
Supervisors ask about diagnosis because they're human and they're curious and often they genuinely care. It's still a problem.
The line is simple enough to teach in ten minutes: you're entitled to know what someone can and can't do, never what they have. Lifting restrictions, hours, concentration, duration — all fair. Condition, medication, treatment, prognosis in clinical terms — none of your business, and asking creates a privacy exposure on top of whatever else is going on.
Give managers a script. Literally a script, written down, for what to say when an employee volunteers medical information or when a colleague asks what happened. Most long term disability lawyer London practitioners will tell you that untrained supervisors generate more complaints than deliberate employer misconduct ever does.
Watch What Happens to the Team in the Meantime
Here's the piece nobody plans for. Someone goes off, their work gets absorbed by four colleagues, and nobody acknowledges it. Resentment builds quietly over months.
That resentment becomes a return-to-work problem. The absent person comes back to a team that's been covering for them and feels, correctly, that nobody is pleased to see them. Comments get made. Someone's left out of a project. It curdles into something that looks a lot like reprisal from the outside, even though no manager ever intended it.
Address the workload gap openly and early. Backfill properly if the absence is going to be long. And when the return is being planned, prepare the team as deliberately as you prepare the employee.
Your Records Will Be Read Aloud Someday
Write every note as though it's going to be projected onto a screen in a hearing room, because some of them will be.
That means documenting contact, decisions and the reasons behind them, in neutral language, at the time. It also means culling the speculation. I've seen file notes wondering aloud whether someone was "really" unwell, remarks about an employee's attitude before the absence, a scheduling email joking about how convenient the timing was. None of that was intended to go anywhere. All of it went somewhere.
Teach managers that every message about an absent employee is potentially evidence. Most will adjust their habits immediately once they understand that.
Succession Planning Is a Legal Tool
This sounds like an operations point. It isn't.
Employers make bad decisions under pressure, and most of the pressure is operational — a vacant role, a drowning department, a manager demanding resolution. That's when organizations start reaching for frustration of contract far too early, or treating a long absence as abandonment because the alternative feels impossible.
Frustration requires real evidence of no reasonable prospect of return, based on medical information rather than elapsed time, and it still triggers statutory entitlements in most provinces. Employers who've planned for coverage simply don't feel the urgency that produces those errors. Before anyone makes that call, get a long term disability lawyer to look at the medical picture, the accommodation record and the contact history. If one of the three is thin, that's the thing to fix — not the employment relationship.