There’s a version of disability management that lives in a binder on a shelf. Indexed, cross-referenced, built to answer every conceivable question in advance. And, in most of the organizations I visit, completely unused.

The impulse to build something comprehensive is understandable. When a situation involves an injured person, legal obligations, and genuinely competing interests, the desire to create a system that anticipates every contingency feels not only reasonable but responsible. It removes the discomfort of navigating nuance case by case. The problem is that people don’t fit neatly into flowcharts. An injured worker brings to the process a history and a psychological reality that no intake form will ever fully capture. The more elaborate the system, the more likely it becomes the project itself, with people managing the file instead of managing the person, and the actual goal quietly receding behind a wall of documentation.

I’ve sat across from HR managers so buried in process that they’d genuinely forgotten there was a frightened person at the other end of the file. That’s not a criticism of those individuals. It’s a predictable outcome of systems that prioritize comprehensiveness over usability.

The Pareto principle applies here as reliably as anywhere else. Most of the improvement in disability management comes from a small number of practical behaviours done consistently. A modest system that actually gets used will outperform an elaborate one every single time. The goal isn’t architectural perfection. The goal is a system your supervisors will actually use in the moments that matter.

Disability management, at its core, is a relationship-management exercise that happens to require paperwork. Not the other way around. Once that gets reversed, you’ve lost the plot. And it gets reversed more often than it should.

So what does a functional, simple system actually look like?

It starts with a plain-language policy. Not comprehensive to the point of being paralyzing, just clear enough that a supervisor who’s never dealt with an injury knows what to do and how the return-to-work process is supposed to unfold. Alongside that, a modified duties bank: a realistic list of meaningful tasks that can be offered when a worker can’t perform their full duties. Not every possible accommodation mapped in advance, just enough options that “we don’t have anything for you right now” is no longer the default response. And the system needs to assign roles clearly, because when everyone vaguely assumes someone else is managing the claim, nobody is.

One more element that doesn’t cost anything: introduce the program before anyone gets hurt. New employees should know from their first week that a return-to-work process exists and that an injury doesn’t mean they’ll be treated as a liability. Workers are far more likely to trust a process they heard about before they needed it. That advance introduction changes the psychological dynamic considerably when the moment actually comes.

The most powerful element of a good disability management program is also the simplest. It’s a phone call. Not a claim-management call or a thinly veiled return-to-work interrogation. A real call from a supervisor that says, in effect: we know you’re off, we’re sorry this happened, you’re missed here. That call costs nothing. In my experience it can materially change the trajectory of a claim.

When a worker is injured and off work, they often disappear into a situation the employer knows very little about. They may be managing physical pain alongside real financial pressure, with the daily routine and community of work suddenly gone. Silence fills that space quickly, and people rarely interpret silence generously when they’re hurting and uncertain. I’ve seen time-loss claims run significantly longer not because of medical complexity but because nobody called, and the worker drew their own conclusions from the absence of contact. Those conclusions were not generous ones.

Workers who feel valued find a way back. Workers who feel invisible to their organization when they need it most will find, consciously or not, reasons to stay away.

The financial case for building a functional disability management program is covered in depth here: The Costs Nobody Tracks — What Disability Management Is Really Doing to Your Bottom Line. The human case is simpler. When someone on your team gets hurt, call them. Not because the policy says to. Because that call may be the difference between a worker who stays connected and a worker who starts slipping away.

Ben Barfett is a workers’ compensation advocate and disability management consultant at wcblawyer.ca, serving employers and workers across Alberta.