Rebuilding a return-to-work file after the original records went missing

The situation

Stavros called us on a Thursday afternoon with the kind of tension in his voice that comes from a problem he could not fully explain yet. 'I have a return-to-work meeting with the Board in nine days,' he said, 'and I cannot find half the paperwork I need to show up with.' That was the whole shape of the problem in one sentence, and it took the rest of the call to understand why.

Stavros owned a franchisee corporation in Thornhill, a maintenance and equipment servicing operation generating somewhere between one and five million dollars in annual revenue, with a small crew of tradespeople including Baruch, a millwright who had worked there for several years. Baruch had suffered a workplace injury to his shoulder several months earlier, been off work, and was now cleared by his doctor for modified duties. Under the workers' compensation system, every registered employer has a duty to cooperate in getting an injured worker back to work, and the process typically involves documented cooperation between the employer, the worker, and the Board. That duty is not a courtesy extended at the employer's discretion; a franchisee corporation like Stavros's is its own registered employer, not a branch of a larger franchisor network, and is bound by it in exactly the same way any other registered employer is. The harder-edged obligation to re-employ an injured worker is narrower: it applies only to employers who regularly employ at least twenty workers, and only where the worker had been continuously employed for at least a year before the injury, so size and service history do matter to which obligations are actually in play.

The trouble was that Eleni, the operations manager who had handled the injury file from the start, had left the company for a job as an electrician with a different employer about two months into the process, and the handoff had been messy. Her laptop had been wiped and returned before anyone thought to check what was on it, and the shared drive folder where the return-to-work correspondence, the job demands analysis, and the modified duties offer letters should have lived was either empty or contained only fragments. Stavros could reconstruct the broad outline of what had happened from memory, but memory was not going to satisfy a Board review.

What made the timing worse was that Baruch's own account of events, communicated through his representative, did not match what Stavros remembered. Baruch's position was that no genuine modified work offer had ever been made, and that the company had let him sit on benefits without a real return-to-work plan. Stavros believed that was wrong, but without documents, believing it was not enough.

What the other side was relying on

Baruch's representative had built a straightforward argument, and it was a reasonable one to make given what was visible from the outside: if the employer cannot produce a written modified duties offer, a job demands analysis, or dated correspondence showing genuine back-and-forth about accommodation, the more plausible inference is that none of that happened. Silence in a file usually reads as absence of effort, not absence of documentation, and the other side was leaning on exactly that inference.

They had specific gaps to point to. There was no copy of the job demands analysis that would have described the physical requirements of the modified role Stavros said had been offered. There was no dated letter or email formally communicating that offer to Baruch, only Stavros's recollection that the conversation had happened in person on the shop floor. And there was no record of what, if anything, had been done between Eleni's departure and Baruch's doctor's clearance, a gap of roughly six weeks in which the file had effectively gone unmanaged.

That last gap was the strongest part of the other side's position, because even under the most generous reading, six weeks with no documented activity on an active return-to-work file is difficult to explain as anything other than the file being neglected. A Board reviewer looking at that gap alongside the missing offer letter would have reasonable grounds to conclude the employer's obligations had not been met during that stretch, regardless of what happened before or after it.

The representative's implicit ask was for a finding that no adequate modified work had been offered at any point, which would have meant the company facing responsibility for a longer period of lost earnings than the six-week gap alone would justify, on the theory that if the file could not prove compliance anywhere, it should be treated as noncompliant throughout.

Beyond the factual gaps, the representative's position drew on a real piece of the underlying framework. An employer's duty to cooperate in early and safe return to work is an ongoing, active obligation under the Act, not a passive one that only matters if a worker complains, and the Board has its own authority to treat a failure to cooperate as a matter separate from whatever wage-loss benefits the worker is owed. A gap in the record was not simply an inconvenience for the company to explain away; it was the kind of gap the cooperation obligation exists specifically to catch, which gave the argument more institutional weight than a private dispute over missing paperwork would have carried on its own.

What we did

1. Separated what was truly lost from what could be reconstructed. We started by cataloguing exactly what was missing versus what existed in other forms, payroll records, scheduling software, text messages between Stavros and Baruch, because treating the whole file as unrecoverable would have conceded far more ground than the facts actually warranted, and would have made the six-week gap look like the norm rather than the exception.
2. Pulled the job demands analysis from a source the company had not thought to check. The franchisor's corporate office, it turned out, required a standard job demands template for every modified duties role across its locations, and a copy of the one used for Baruch's proposed role had been submitted to head office months earlier as part of an unrelated compliance audit. That document alone closed the biggest gap in the file and gave the reconstructed record a genuinely contemporaneous piece of evidence to anchor around.
3. Reconstructed the timeline from scheduling and payroll data. The shop's scheduling software showed shift assignments consistent with Baruch working modified hours for part of the disputed period, and payroll records showed a rate change matching a lighter-duty role, both of which corroborated Stavros's account even without the original offer letter existing anymore, and both of which were maintained on third-party systems outside the affected shared drive.
4. Obtained a written statement from a coworker who witnessed the shop-floor offer. A second employee who had been present when Stavros described the modified role to Baruch was willing to provide a signed account of that conversation, which helped address the absence of a formal written offer letter, though we were candid with Stavros that a witness statement carries less weight than contemporaneous documentation and would only ever be corroborating evidence, not the centerpiece of the file.
5. Accepted the six-week gap rather than trying to argue it away. We advised Stavros that the unmanaged period after Eleni's departure genuinely could not be documented as compliant, and that fighting to characterize it otherwise risked the credibility of the reconstructed evidence for the rest of the file. Conceding that specific stretch honestly, early, and without hedging was the stronger overall strategy, and it kept the negotiation focused on a narrow, bounded issue rather than the whole file.
6. Negotiated a return-to-work plan for the remaining dispute. With most of the file rebuilt on reasonably solid secondary evidence, we negotiated directly with Baruch's representative on the outstanding six weeks, proposing a targeted payment calculated at Baruch's modified-duty rate for that specific period rather than treating the entire compensation period as unsupported, which brought the dispute down to a single, quantifiable stretch of time.
7. Documented the new modified duties offer in writing before Baruch returned. Going forward, we made sure the current offer, including specific tasks, hours, and physical restrictions, was captured in a signed letter, copied to both Baruch and the Board's own claim file, before Baruch's actual return date, so the company would never again be relying on a shop-floor conversation as its only record of an accommodation offer.
8. Put a document retention process in place going forward. To prevent a repeat, we helped the company set up a policy requiring return-to-work files to be stored on a shared system independent of any one employee's device, with copies automatically retained regardless of staff turnover, a named backup owner assigned to every open file, and a checklist requiring sign-off before any employee's system access was removed.

The outcome

The negotiated resolution accepted the reconstructed evidence for the bulk of the return-to-work period, meaning the company was not treated as having failed its obligations across the full duration of Baruch's claim. For the six-week gap after Eleni's departure, Stavros's company agreed to a payment covering that specific period, reflecting the genuine absence of documented modified work during those weeks, rather than a broader payment covering months the company could actually document properly.

Baruch returned to modified duties under a new, properly documented plan, with the job demands analysis and offer terms now confirmed in writing and copied to both the Board file and the company's own retained records. The working relationship between Stavros and Baruch, which had been strained by the dispute and by Baruch's understandable frustration at feeling like his return had been mishandled, settled once the process moved from argument to a concrete plan both sides could see in writing and verify against the documented job demands.

Stavros described the outcome afterward as fair rather than favourable, which was an accurate way to put it. The company avoided the worse outcome the other side had initially sought, a finding of noncompliance across the entire claim period, but it did not escape responsibility for the stretch where the file genuinely had gone unmanaged, and it paid for that gap rather than disputing it. The company's insurer, once informed of the reconstructed file and the negotiated resolution, treated the matter as closed without further review, which mattered for how the claim would factor into future premium calculations.

The clearer lesson for the business was structural: an injury file cannot depend on one person's laptop, a lesson that Stavros said reshaped how he thought about the company's recordkeeping generally, not just for injury claims. The retention system built afterward exists specifically so this gap does not repeat with the next claim, and Eleni's replacement was trained on it within her first week rather than being left to build the same fragile, single-person process over again.

What you can learn from this