we are committed to delivering innovative solutions that drive growth and add value to our clients. With a team of experienced professionals and a passion for excellence.

Follow us

Blog Details

Common Employer Ruling

Shell Companies, Common Employers, and the Long Reach of a Wrongful Dismissal Judgment: Boyce Estate v. 2113626 Ontario Inc. (Hampton Inn and Suites)

Images
Authored by
Admin
Date Released
May 15, 2026

In a brief but pointed decision, the Ontario Court of Appeal has confirmed that employers cannot use related corporate entities as a shield against wrongful dismissal liability. Where two companies are jointly involved in running a business and share a common intention to employ a worker, they will be treated as a single employer – and an unsatisfied judgment against one can be pursued against the other.

Background

The litigation in Boyce Estate has its origins in a short and unhappy employment relationship at a Brantford hotel. In 2009, Elizabeth Boyce was hired as a manager at the Hampton Inn and Suites under a three-year fixed-term contract. She was terminated just five months into the role.

What followed was an unusually prolonged legal journey spanning more than fifteen years, complicated by the layered corporate structure behind the hotel’s operations and, ultimately, by Ms. Boyce’s death before her claim could be fully resolved.

 

2009 Ms. Boyce hired as hotel manager under a three-year fixed-term contract; terminated five months later.
First action Wrongful dismissal claim against 2170990 Ontario Inc. (“217”) – the entity that contracted with her. Uncontested judgment of $120,000 obtained.
Second action 217 unable to satisfy the judgment. Ms. Boyce commences a new claim against related company 2113626 Ontario Inc. (“211”) and individual Danny Bawa under the common employer doctrine.
Before adjudication Ms. Boyce passes away. Her estate continues the litigation.
June 2025 Motion judge grants summary judgment against 211; dismisses claim against Mr. Bawa. Reasons at 2025 ONSC 3844.
May 5, 2026 Court of Appeal dismisses 211’s appeal. Costs of $7,500 awarded to the estate.

The common employer doctrine

The common employer doctrine allows courts to treat separate legal entities as a single employer for the purpose of employment claims. Its rationale is straightforward: where related companies are jointly involved in running a business and jointly involved in establishing an employment relationship, it would be artificial – and unjust – to limit liability to whichever entity happened to appear on the employment contract.

The doctrine is a direct response to the use of layered corporate structures to insulate controlling entities from employment law exposure. By requiring courts to look through the corporate form where the facts warrant, it prevents employers from achieving through structure what they cannot achieve through contract.

  “The common employer doctrine is meant to ‘negate an artificial and unjust application of the res judicata doctrine in circumstances like this.’”

– Motion judge, as quoted in Boyce Estate v. 2113626 Ontario Inc., 2026 ONCA 323, at para. 5

The two issues on appeal

ISSUE 1

Were 211 and 217 common employers of Ms. Boyce, such that 211 could be held jointly liable for the wrongful dismissal?

ISSUE 2

Did res judicata or abuse of process bar the estate from bringing a second claim against a related company after an uncontested judgment against the first?

The Court’s analysis

Common employer: both entities were jointly involved

The Court of Appeal found no error in the motion judge’s application of the common employer test. The motion judge made factual findings – available on the record – that both 211 and 217 were jointly involved in running the Hampton Inn and Suites, and that both entities shared a common intention to create an employment relationship with Ms. Boyce. Those findings attracted deference: absent an extricable error of law, or a palpable and overriding error of fact, the Court of Appeal will not reweigh the evidence. The appellant’s invitation to do exactly that was declined.

The Court’s analysis underscores a practical point: the common employer test looks to the substance of the relationship, not to the labels on corporate documents. Joint involvement in operations and a shared intention to employ are the key indicators – and where a controlling entity participates meaningfully in both, it cannot later disclaim liability by pointing to a subsidiary’s name on the contract.

Res judicata and abuse of process: no bar to a second claim

211 also argued that the doctrines of res judicata and abuse of process should have prevented Ms. Boyce’s estate from pursuing a second action after obtaining judgment in the first. The Court rejected this argument on two grounds.

First, 211 was not a defendant to the first action. Having never been a party, it could not claim the procedural protections those doctrines exist to provide. Second, the Court emphasized the fairness dimension: where two companies are closely tied and their respective roles are not easily discernible, it would be unfair to hold a plaintiff to a single bite at the apple – particularly once it becomes clear that the named defendant cannot pay. The common employer doctrine exists precisely to address that scenario.

The appeal was dismissed with costs of $7,500 awarded to the estate on a partial indemnity basis.

Key takeaways

For employers
Corporate structure is not a liability shield.

Creating separate entities to contract with employees will not, on its own, limit liability to the contracting entity. Where a related company is involved in the actual operation of the business and the creation of the employment relationship, it will be exposed as a common employer. Genuine operational separation is required – not merely separate corporate registrations.

An unsatisfied judgment can follow the money to a related entity.

The sequence of events here – judgment against 217, inability to pay, then successful claim against 211 – is a cautionary tale for groups of related companies that share operational responsibility for employees. Employers should not assume that an employee who obtains judgment against one entity has exhausted their remedies.

Invest in employment contracts and HR practices, not structural complexity.

Well-drafted employment agreements with proper termination clauses remain the most reliable way to manage wrongful dismissal exposure. Structural complexity that obscures which entity is the “real” employer creates litigation risk without providing meaningful protection.

Fixed-term contracts carry heightened risk.

Ms. Boyce was on a three-year fixed-term contract and was terminated after five months. Fixed-term agreements that are terminated early can attract significant liability – in some cases the full remaining value of the contract – if they lack a clear and enforceable early termination provision.

For employees
Name all related entities from the outset.

If multiple companies appear to be involved in operating your workplace – through shared management, overlapping ownership, or joint decision-making – it is worth considering whether to name them all in any wrongful dismissal claim. The common employer doctrine is easier to invoke at the start than to raise after an unsatisfied judgment.

An uncontested judgment is not the end if it cannot be satisfied.

The estate’s persistence – pursuing a second action against a related company after 217 failed to pay – ultimately succeeded. Where the original defendant cannot satisfy a judgment and there is a related entity that was jointly involved in the employment relationship, a claim against that entity may still be available.

Claims can survive an employee’s death.

Ms. Boyce passed away before her claim was adjudicated. Her estate was entitled to continue the litigation and ultimately obtained both the summary judgment and the costs award. Wrongful dismissal claims – like other civil claims – survive the claimant and can be pursued by the estate.

Why this decision matters

Despite its brevity – seven paragraphs, rendered orally – Boyce Estate is a useful restatement of the common employer doctrine and its relationship to res judicata. The Court’s willingness to allow the estate to pierce the corporate structure of a hotel operation, years after the original dismissal, sends a clear signal: employment law liability is assessed on the substance of who actually employed the worker, not on which entity signed the contract.

The decision also illustrates how the common employer doctrine operates as a procedural safety valve. The res judicata argument – that the first judgment should foreclose further claims – was directly neutralized by the doctrine’s purpose: preventing companies from using artificial structures to escape liability that a single employer would plainly bear.

For employers operating through groups of related companies, the practical message is clear. Employment liability follows operational reality. Ensuring that the entity named in employment contracts is the one actually managing the employment relationship – or that all involved entities are named – remains the most straightforward way to avoid the kind of multi-stage, multi-party litigation that played out here over more than fifteen years.

This digest is for general information only and does not constitute legal advice. Readers should obtain specific legal advice with respect to their own circumstances. Boyce Estate v. 2113626 Ontario Inc. (Hampton Inn and Suites), 2026 ONCA 323, was decided on May 5, 2026 by Miller, Favreau, and Rahman JJ.A. The appellant was represented by Stephen Schwartz; the respondent by Derek Sinko.

Share: