Anonymised, illustrative composite. An Ontario framing subcontractor offered modified work within two weeks of a back-strain claim — and a worker who missed two planning meetings came within four days of a cooperation penalty that would have cost far more than the accommodation ever did.
At a glance
A framing subcontractor's worker strained his lower back lifting engineered lumber and went off full duty. The firm, with more than 20 employees and the worker already past the one-year employment mark, was squarely inside Ontario's re-employment obligation — and its own claims history made getting this one right worth extra attention: a prior claim, still inside the firm's own six-year WSIB claims window, had already moved it two risk bands up, roughly a 10% increase (two bands at roughly 5% each) on its premium rate. A second escalated claim risked a third.
WSIB's return-to-work responsibilities page sets out what construction employers owe an injured worker: re-employment when the worker is “medically able to perform” either the essential duties of the pre-injury job, suitable construction work, or suitable non-construction work, with the obligation running until the earlier of two years from the injury date or one year from medical clearance for the pre-injury job. The firm offered a modified role — lighter material handling, no repetitive lifting — on day 12, well inside that window.
That obligation has a statutory floor behind the WSIB page: under the Workplace Safety and Insurance Act, the duty to re-employ applies to a worker who, on the date of injury, “had been employed continuously for at least one year by the employer,” and it does not apply at all to employers who regularly employ fewer than 20 workers (WSIA, S.O. 1997, c. 16, Sched. A, s. 41(1)-(2)). This firm cleared both thresholds, which is exactly why the two-year clock started running the day the worker went off full duty. Treadstone Law's guide to an Ontario employer's WSIB obligations after a workplace injury covers the same return-to-work duty from the employer's side.
The worker did not engage. Two required RTW planning meetings, on day 15 and day 19, went unattended with no notice given either time. On day 20 the case was flagged for non-cooperation.
The same WSIB page is specific about what a cooperation flag actually costs: an initial penalty of “50 per cent of the wage-loss benefits,” rising to “100 per cent of the wage-loss benefits… plus 100 per cent of any costs for return-to-work training services” if non-cooperation continues beyond 14 calendar days after the penalty starts. Flagged on day 20, the escalation point fell on day 34 (20 + 14). The worker resumed engagement — attending the rescheduled planning meeting and starting the modified role — on day 30, four days before that second threshold.
The penalty ladder is not a single trigger; it is two thresholds with a real gap between them, and that gap is exactly what let this claim recover before it became materially more expensive. The 50% reduction at day 20 was already in effect when the worker resumed cooperation on day 30 — it does not reverse itself — but stopping short of day 34 kept the case out of the 100%-plus-training-cost tier entirely.
Two risk bands already sat on this firm's account from an earlier claim, worth roughly 10% on its premium rate under WSIB's own rate-calculation page. A second claim that ran long — through the 100% penalty tier, full wage-loss duration, and a slower close — would have added meaningfully more to a six-year claims total that was already elevated, on top of the cooperation penalty itself.
Full return to regular duties was reached by week 9. The claim closed with one cooperation-penalty period on record rather than two, and the firm's RTW coordinator began tracking modified-work offers and meeting attendance in the same place it already tracked its safety-training matrix, so the next case would not depend on anyone remembering the day-count by hand. The coordinator also started flagging day 27 — a full week before the day-34 escalation point, rather than waiting until the deadline was close enough to be urgent — on every future cooperation flag.
The same underlying mechanism — a real claims history feeding a rolling multi-year cost window — is the reason avoiding injuries in the first place at a different site mattered as much as it did for the firm carrying it.
Both missed meetings turned out to share one cause: the worker had no reliable way to get to the clinic where the meetings were held, and had not said so. Reviewed after the fact, “non-cooperation” was a logistics gap, not defiance. The RTW plan template was rewritten to ask about transportation on day one, rather than discovering the gap only after two missed meetings had already put the claim on the penalty clock.
A 30-minute call is enough to tell you whether AI pays for itself here.
