How Two Corrected WSIB Claims Erased a Costly Premium Increase

The situation

The letter from the WSIB put a number on it: roughly $87,000 in additional premiums from a jump in the company's risk band, with the higher rate projected to add close to $28,000 a year going forward if the assessment stood. For Trevor's electrical and mechanical services franchise, an established company doing close to $3 million a year in contract work across Orleans and the surrounding east end, that combination threatened to erase most of a year's operating margin within eighteen months.

The franchise employed about fifteen people, most of them tradespeople who moved between commercial and industrial job sites doing panel upgrades, motor replacements, and conveyor maintenance. Two of them, Kittipong, an electrician, and Somchai, a millwright, had each been hurt on the job within the same eighteen-month window. Kittipong had injured his shoulder in a fall from a ladder; Somchai had injured his hand in a jammed mechanical press. Both claims had been accepted by the WSIB, and both men had returned to full duties within a few months.

What Trevor did not know, until the rate decision letter arrived, was how those two claims had been recorded inside the WSIB's premium rate-setting system, which places every employer in a risk band within its industry class based on the cost of claims charged to its account relative to other employers doing similar work. The notice showed both claims recorded as ongoing, high-cost files, with wage-loss payments still being charged to the company's account well past the date both men had returned to work. Combined with two smaller claims from prior years, those inflated costs had pushed the account into a higher risk band, triggering close to the maximum single-year premium rate increase WSIB's rules allowed for a company of its size and sector.

Trevor's own paperwork told a different story. He had return-to-work confirmations for both men, timesheets showing full duties resumed, and email correspondence with a WSIB return-to-work specialist from more than a year earlier. Nothing in his file explained why the claims were still showing active wage-loss charges. He called our office about two weeks before the higher rate was set to take effect on his renewal premium, uncertain whether the window to formally object had already closed, and unsure whether a dispute would be worth the cost of finding out. Two of his supervisors had also asked, more than once, whether the company should simply absorb the increase and move on rather than risk drawing further scrutiny to the account, and Trevor wanted a straight answer before he decided which way to go.

The problem

The premium increase was not, it turned out, the result of any dispute over whether the two claims were legitimate. They were. The problem lived entirely in how the claims had been administered after the accepted date. When a worker returns to full duties, an employer's account should stop being charged for wage-loss benefits from that point forward; only the costs actually incurred, the medical treatment and the wage-loss paid during the genuine disability period, should count toward the account's claims cost history. If a claim stays open in the WSIB's internal system after a worker is back at full duties, projected wage-loss can keep accruing against the employer's account as though the worker were still off work, even though no payment is actually going out.

That is what had happened to both files. Neither Kittipong's nor Somchai's claim had been formally closed in the WSIB's system, despite both men being back on full duties for over a year. The system had continued to project ongoing wage-loss liability against the company's account based on the original disability estimate, rather than the shorter period each man had actually been away from work. Two claims that should have cost the company a combined total in the low five figures were instead showing a projected cost several times that amount, and it was that projected figure, not the real cost, that fed the risk band calculation setting next year's rate.

The rate decision letter itself did not explain any of this. It stated the account's risk band placement and the resulting premium rate, with a short paragraph noting the right to object within a set window. Nothing in the notice flagged that the underlying claim status, rather than the legitimacy of the claims, was the actual issue. A business owner reading only the notice would reasonably conclude the dispute had to be about whether the injuries deserved compensation at all.

That misunderstanding is common, and it is part of why many employers in Trevor's position never object. Objecting can feel, on its face, like arguing that an injured worker should not have been paid. It was important, early on, to be clear with Trevor that this dispute was never going to touch either man's compensation. It was about a bookkeeping error inside the WSIB's own system, and framing it that way shaped everything that came after.

There was also a timing pressure specific to how premium rates are set that made the distinction worth getting right quickly. Unlike the underlying injury claim, which can in principle be revisited long after the fact, a premium rate increase is tied to a renewal cycle: once an invoice goes out at the higher rate and the employer pays it, getting the money back means chasing a refund through a separate process rather than simply avoiding the charge in the first place. Trevor's two-week window before the invoice was cut mattered less because of any hard statutory deadline and more because every week that passed narrowed the odds of catching the correction before the higher rate became a paid, sunk cost rather than an avoided one.

What we did

1. Pulled the full claim file for both workers. Rather than relying on the rate decision letter alone, which stated only a risk band and a dollar figure, we requested the WSIB's internal claim summary for each file. It showed the date each claim had last been updated and confirmed neither had actually been marked closed, despite both workers' signed return-to-work forms sitting in the same file. Seeing the raw claim status, not just the published notice, let us pinpoint the real defect instead of arguing with the premium figure directly.
2. Built a side-by-side return-to-work chart. We matched each man's return-to-work confirmation, his supervisor's sign-off date, and the full-duty timesheets that followed against the WSIB's own projected disability period for each claim. The result was a simple chart showing, for both files, the exact gap between the date each man was genuinely back at work and the much later date the WSIB's internal system was still treating him as off work and drawing on the account.
3. Filed the formal objection within the response window. We drafted and submitted the written objection well inside the deadline, framed narrowly around the claim administration error rather than the underlying injuries themselves. That framing mattered: it kept the dispute from being read, either by the WSIB or by Trevor's own staff, as an argument that either worker should not have been compensated.
4. Requested a risk band recalculation, not a reopening. We specifically asked WSIB's rate-setting reviewers to recalculate the account's risk band placement using the corrected closure dates, rather than asking an adjudicator to revisit the merits or the compensation of either claim, since the actual dispute concerned cost attribution to the employer's account, not either worker's entitlement to benefits already paid.
5. Negotiated a temporary hold on the rate increase. While the objection was still under review, we asked the WSIB to hold the higher rate from applying to Trevor's renewal premium invoice. That prevented the company from having to pay an amount up front, and then chase a refund later, for an increase that a correction of the underlying record might make unnecessary within a matter of months.
6. Escalated after the initial denial. When the rate-setting unit's first written response upheld the increase without engaging with the closure date discrepancy we had documented, we requested internal escalation to a senior reviewer rather than simply re-filing the same objection and waiting again, since repeating an argument a reviewer had already rejected once was unlikely to change the result the second time. We supplied the file-level audit trail directly to that senior reviewer, which is what ultimately moved the account past the point of a form-letter denial.
7. Confirmed the correction reached the actual invoice. Once the WSIB agreed in writing to correct both claim files, we did not treat the file as closed. We tracked the recalculated risk band through to Trevor's actual renewal premium invoice to confirm the higher rate had genuinely been removed from the number he would pay, rather than merely logged as pending inside an internal WSIB system.

The outcome

WSIB's rate-setting review team did not concede on the first pass. Its initial written response to the objection maintained the increase in full, treating the closure-date discrepancy as an internal processing matter that did not change the account's underlying risk band. It was only after we escalated the file to a senior reviewer, attaching the matched return-to-work chart directly to the correspondence rather than resubmitting the same objection a second time, that the unit's position shifted. Within about six weeks of that escalation, both claim files were formally closed retroactive to each worker's actual return-to-work date, and the account's entire risk band placement was recalculated from scratch.

The recalculation removed the premium increase entirely. Trevor's renewal premium came in at the base class rate for his sector rather than the higher risk-band rate, and the company received a refund of roughly $19,000 that had already been charged against the account in the months before the objection was resolved. The projected $28,000-a-year increase in ongoing premiums never took effect, and Trevor's projected cash flow for the following operating year was restored to what he had originally budgeted before the notice arrived.

Nothing about the outcome changed either worker's original claim. Kittipong and Somchai both remained fully compensated for the time they had genuinely been off work, and neither claim was reopened, reviewed, or challenged at any point in the process. What changed was purely the bookkeeping: the WSIB's own internal system had kept charging the company for wage-loss payments that had actually stopped being paid over a year earlier, and correcting that stale record removed a cost the company was never supposed to carry in the first place. Trevor now flags any claim on the account that has not been marked closed within a few months of a worker's confirmed return to full duties, so a similar gap cannot quietly compound again before it is caught the next time a renewal notice arrives.

What you can learn from this