Deprecated: WP_Translation_Controller::load_file(): Implicitly marking parameter $locale as nullable is deprecated, the explicit nullable type must be used instead in /home/dblaw1215/public_html/blog/wp-includes/l10n/class-wp-translation-controller.php on line 101

Deprecated: WP_Translation_Controller::unload_file(): Implicitly marking parameter $locale as nullable is deprecated, the explicit nullable type must be used instead in /home/dblaw1215/public_html/blog/wp-includes/l10n/class-wp-translation-controller.php on line 156

Deprecated: WP_Translation_Controller::unload_textdomain(): Implicitly marking parameter $locale as nullable is deprecated, the explicit nullable type must be used instead in /home/dblaw1215/public_html/blog/wp-includes/l10n/class-wp-translation-controller.php on line 201

Deprecated: WP_Translation_Controller::is_textdomain_loaded(): Implicitly marking parameter $locale as nullable is deprecated, the explicit nullable type must be used instead in /home/dblaw1215/public_html/blog/wp-includes/l10n/class-wp-translation-controller.php on line 243

Deprecated: WP_Translation_Controller::translate(): Implicitly marking parameter $locale as nullable is deprecated, the explicit nullable type must be used instead in /home/dblaw1215/public_html/blog/wp-includes/l10n/class-wp-translation-controller.php on line 263

Deprecated: WP_Translation_Controller::translate_plural(): Implicitly marking parameter $locale as nullable is deprecated, the explicit nullable type must be used instead in /home/dblaw1215/public_html/blog/wp-includes/l10n/class-wp-translation-controller.php on line 297

Deprecated: WP_Translation_Controller::locate_translation(): Implicitly marking parameter $locale as nullable is deprecated, the explicit nullable type must be used instead in /home/dblaw1215/public_html/blog/wp-includes/l10n/class-wp-translation-controller.php on line 397

Deprecated: WP_Translation_Controller::get_files(): Implicitly marking parameter $locale as nullable is deprecated, the explicit nullable type must be used instead in /home/dblaw1215/public_html/blog/wp-includes/l10n/class-wp-translation-controller.php on line 430

Deprecated: WP_Translation_File::create(): Implicitly marking parameter $filetype as nullable is deprecated, the explicit nullable type must be used instead in /home/dblaw1215/public_html/blog/wp-includes/l10n/class-wp-translation-file.php on line 84

Deprecated: wp_getimagesize(): Implicitly marking parameter $image_info as nullable is deprecated, the explicit nullable type must be used instead in /home/dblaw1215/public_html/blog/wp-includes/media.php on line 5502
Can You Be Fired for Causing an Accident at Work? - De Bousquet Professional Corporation Blog
Menu
Call Us Today
416-616-5628
Can You Be Fired for Causing an Accident at Work?

\Accidents happen — but do they justify being fired?

In Ontario, simply having a workplace accident is not automatically just cause for dismissal. Employers must prove that your conduct went beyond a mere mistake. Just cause is a high bar, and courts apply a contextual approach to determine whether it’s met.

When It’s NOT Just Cause:

  • A one-time error in judgment
  • Simple negligence
  • Honest mistakes

When It MAY Be Just Cause:

  • Gross negligence or reckless disregard for safety
  • Deliberate breaches of safety protocols
  • Repeated misconduct, despite prior warnings
  • Dishonesty, such as failing to report the incident

Case in Point: In Rankin v. Active Mold and Design, a single safety breach involving hazardous equipment was enough for termination because of the danger posed. In this case, the employee left dangerous machinery running unattended; a serious safety violation. The equipment could have injured others in the shop. It wasn’t a pattern of behaviour, just a single incident, but the consequences could’ve been catastrophic. The employer terminated him for cause, and the court agreed. Even though it was a one-time mistake, the court found it was reckless and posed an imminent safety risk. That elevated the incident from mere negligence to serious misconduct.

Case in Point: Daley v. Depco International demonstrates that if there are repeated issues around safety, a termination can be justified. Daley’s employer kept a file on his repeated workplace issues: carelessness, absences, arguments with co-workers, amounting to nine incidents in total. After repeated warnings and discipline, the final straw was another preventable problem. When the company fired him for cause, Daley challenged it in court. But the court said enough was enough. Even though no single mistake was serious enough to justify dismissal on its own, the pattern of misconduct showed a lack of reliability and poor judgment over time. That justified termination for cause.

Case in Point: Lagala v. Patene Building Supplies shows that dishonesty around a workplace injury can lead to just cause for termination. Lagala was a health and safety manager, so she was someone expected to model compliance. When she suffered a workplace injury, she didn’t report it for months, even though it was her legal obligation under the WSIB. When her employer found out, she was fired for cause. The Ontario Superior Court upheld the dismissal because of the failure to report, the concealment, and the fact that she was in a leadership role where trust and integrity were crucial.

Employer Responsibility Matters: If your employer failed to train you properly or didn’t enforce safety policies, that weakens their case for firing you “for cause.”

Bottom Line: A workplace accident usually means termination without cause, which requires notice or severance. Only serious misconduct justifies being fired “for cause.”

Need Help?

Give our office a call. The lawyers at De Bousquet PC are here to support Ontario workers. Whether you’re reviewing a contract or dealing with a workplace issue, we can help you understand your rights and your options.

Scroll To Top