Friday, January 21, 2011

What do you do about a problem manager?

This question is really two different questions: What should an employee do when his or her supervisor is a nightmare? And what should the employer (i.e. upper management) do when it comes to their attention?

A recent Star article discusses a survey of HR professionals indicating that "bosses from hell" are a big problem. Most employees try to deal with it, look for another job, or just leave. But there are significant legal facets to the problem.

You've heard the term "constructive dismissal". Most employees have heard it, have a vague idea of what it means, but are understandably (and usually rightly) reluctant to put much reliance on it. Nightmare managers can result in a type of constructive dismissal. Or other problems. In fact, it can be a big deal.

Aside from the practical difficulties of having a nightmare manager - lower morale, increased attrition and recruitment costs, possibly lower productivity - such a manager exposes the employer to potentially significant liabilities, and even moreso as our society becomes more sensitive to mental illness.

In 2004, there was a ground-breaking labour arbitration in the TTC: A fellow who had historically been a good employee ended up working under a manager with whom, to put it mildly, there wasn't good chemistry. His performance reviews took a dive, his mental health and personal life suffered; he eventually transferred out to a lower-paying position in the organization. Again, his performance reviews were stellar, he was happy, things were good again...until the manager transferred too, and ended up supervising him again. Suffice it to say that it wasn't a good scenario. Led to debilitating depression and paranoia.

The Arbitrator found that the employer had breached its obligations under the Occupational Health and Safety Act, by creating such a hazard to the employee's health. The Arbitrator imposed onerous obligations on the TTC, even in addition to the financial award.

In the civil litigation field, Shah v. Xerox is the equivalent. The trial was in 1998, and the Court of Appeal dismissed the appeal in 2000. Mr. Shah worked for Xerox for over 12 years, and for most of the time was successful, receiving good performance reviews, bonuses, pay raises. Then a new manager came in, and was extremely and unjustifiably critical of Shah's performance. So Shah resigned, and was found to have been constructively dismissed.

This case was decided before the Supreme Court decided Wallace, which gave rise to a decade-long period in employment law where "bad faith damages" were routinely awarded. Shah-type cases typically attracted Wallace damages; that wouldn't happen now, but there remains the potential for aggravated damages where an employee can show illness or injury resulting from the misconduct.

Another recent shift in the law is Bill 168: Employers now have to have policies in place to deal with harassment, and are more expressly obligated to deal with harassment. (The TTC case used to be exceptional. With Bill 168, it might just become the norm.) There's a flip side to Bill 168, though: If an employer has implemented an anti-harassment policy, it may become more difficult for an employee to claim constructive dismissal on the basis of harassment unless he or she has availed herself of the recourse within the policy first.

A more recent case, Piresferreira v. Ayotte, involved a Bell Mobility employee who was pushed by her manager. She had a long history of good service, but this manager was highly aggressive and intimidating, and had been critical in his reviews of her. The 'push' amounted to constructive dismissal and battery. The trial judge awarded damages in excess of half a million dollars. (!!!) The Court of Appeal agreed that she had been constructively dismissed. found that the trial judge had erred in how it awarded damages, and reduced the award to pay in lieu of notice plus $45,000 for mental suffering due to the manner of her dismissal. The Supreme Court just dismissed an application for leave to appeal, this past week.

Large and small employers alike have problem managers (note the employers involved in the above cases), but a lot of these cases have similar earmarks, similar red flags. When a long-service employee with a solid performance history suddenly starts having performance or disciplinary issues, something's wrong. It could be something in the employee's personal life, and so an employer can't be too invasive in trying to find out what's up, but it could be that something has changed in the employment relationship itself - reporting structure, duties, etc. - and if that's the case, then the performance issues are often going to be the employer's fault. So an employer needs to watch for those red flags, because they might be signalling potential liability.

There should be clear expectations of how managers deal with employees; clear boundaries of unacceptable conduct. Managers can and should be disciplined for mistreating employees.

Sometimes it's just a personality conflict; nothing inherently wrong with what the manager is doing in general terms, but a lack of chemistry means that the employee and manager simply can't work well together. Where possible, this can be resolved by changing the reporting structure in a non-punitive way, which doesn't negatively affect the employee. Where that's impossible, it may be necessary to terminate the employment of either the employee or manager, but remember: A personality conflict is not just cause for termination. The termination must be on notice (or with pay in lieu thereof). Seek legal advice prior to doing so. It will usually be a better idea to terminate on notice early, ending an acrimonious relationship before it becomes toxic, rather than to wait and run the risk of a constructive dismissal claim with a claim for aggravated damages on the side.

An employee who feels that a manager is acting inappropriately and making the workplace intolerable should seek legal advice prior to taking any steps that may have detrimental consequences to his or her employment.

*****

This blog is not intended to and does not provide legal advice to any person in respect of any particular legal issue, and does not create a solicitor-client relationship with any readers, but rather provides general legal information. If you have a legal issue or possible legal issue, contact a lawyer.

Tuesday, January 11, 2011

Internet Defamation on the Rise

People think of the internet as an inherently anonymous venue, where they can voice their concerns about issues without attaching their real names to it, and therefore without recourse.

There are ways of tracing internet usage, however, and it's becoming increasingly common to see legal proceedings based on ill-thought-out internet posts. Sometimes a person posts something inherently actionable or criminal, like defamation or threats. Other times a person makes posts which amount to admissions of wrongdoing - see this case, in which a 19-year-old from Vaughan was charged after bragging online about having driving 140kph in a 40 zone in his M5S, under the username "bmw550ifreak". Facebook has also become an interesting issue in some personal injury actions: A person alleges that his injuries have severely impaired his ability to lead a normal life, that he's always miserable, can't leave the house, and never does anything physical anymore...then their Facebook page gets demanded by the insurance company, which reveals a somewhat different picture, between all the status updates and dialogue with friends discussing all his wild adventures.

But what's really taking off is that disgruntled people use the internet as a source of venting. Somebody wronged you, and you see the internet as your way of telling the world about it. Think twice.

Defamation law continues to develop, and is a highly nuanced area of the law, but I think that a good simple rule to follow is this: If you can't say anything nice, or at least provably true, don't say anything at all.

In one recent decision, released last week, a Pelham lawyer sued a former client for libel. This one wasn't limited to the internet - following on the heels of losing his assessment of the lawyer's bill, the client even took out newspaper ads to disseminate disparaging information about the lawyer. The allegations were quite serious, alleging multiple criminal convictions and Law Society discipline including sexual misconduct.

There are a lot of possible defences in defamation actions. When the lawyer sued, the client led the defence of "justification" - basically, he claimed to be justified in saying these things because, he argued, they were true. And they weren't far off of the truth - in fact, the lawyer did have a criminal record, arising from a singular criminal conviction for criminal harassment in 2003. He also had a disciplinary record with the Law Society, one following from the conviction, and two others in 1996 and 2006.

However, there were two major problems with the justification defence: Firstly, the publications alleged "more than one" criminal conviction. There was only one. Secondly, the publications wrongly suggested that the information was current, despite the fact that they were being published in 2008/2009 - essentially, the allegation seemed to be that the lawyer was, at the time of publication of the ads, practicing law despite being on criminal probation.

"Public interest" defences were also led, but failed because a prerequisite for these involves the absence of malice, and it was pretty clear on the facts that the client had ulterior motives for making the posts.

The lawyer won the case, and a significant award of damages was made.

*****

This blog is not intended to and does not provide legal advice to any person in respect of any particular legal issue, and does not create a solicitor-client relationship with any readers, but rather provides general legal information. If you have a legal issue or possible legal issue, contact a lawyer.

Thursday, December 30, 2010

Varying Wills

At two of my family Christmas gatherings, relatives brought up a recent British Columbia case that's been in the news where a Court varied the terms of a deceased father's will, who left his entire estate to his only son and completely ignored his four surviving daughters.

In life, the father had, to quote the Court, "ruled his family, and especially the women, with an iron fist". (The Court goes on at some length about the harshness and violence of his family's existence.)

His son was "favoured and indulged"; some of his daughters are "demonstrably in need". Ultimately, the Court decided that the fair thing to do was divide the estate five ways, to varying degrees based on need. Part of what factored into the Court's analysis was that the father actually explained in the will why he wasn't leaving anything to the daughters, and the explanations were untrue and irrational, according to the Court.

This has attracted some rather negative attention in the media. Why can't a person do what they want with their estate? We should be able to write out our kids if we want to.

Generally, that attitude is correct, legally. When this was described by my relatives, I had to look it up myself. It was surprising, and I found myself thinking through a lot of different ways that an estate can be distributed aside from the wishes as set out in the will, and wondering which one was present in this case - mind you, I am an Ontario lawyer, and will interpretations are governed by Provincial law, which makes me rather unfamiliar with British Columbia estate law.

As it turns out, the decision was based on a rather unique feature of British Columbia law: The B.C. Wills Variation Act contains provisions that have been interpreted to allow a Court a wide discretion to vary the will in a manner that it deems fair under certain circumstances.

There isn't really an equivalent in Ontario law. Mind you, there are quite a few other ways, some of them similar, and I'm not altogether convinced that a similar (or at least comparable) result couldn't have been obtained in Ontario.

Firstly, look at the overall validity of the will. There are a lot of ways that a will can be invalidated, lack of capacity and undue influence among them. If I'm disinheriting some children for reasons which aren't true, then this can raise questions about capacity and/or undue influence.

Secondly, and more broadly, there are a series of situations in which a person can be elevated to the position of creditor of the estate, and thus have a claim with priority over beneficiaries. It doesn't vary the terms of the will, but rather requires the payment of the claim prior to the distribution of assets to beneficiaries:

(1) Spousal election under the Family Law Act: A spouse can elect to take what she would have received upon divorce (i.e. equalization of the matrimonial property) rather than taking under the will. Thus, you can't meaningfully disinherit your spouse. (Formal separation agreements can and should displace this right of election. Spouses also have other rights in terms of the matrimonial home, etc., and dependant's rights - see below.)

(2) Dependants' claims: Dependant spouses, children (even adult children), or others can make claims against the estate.

(3) Other existing legal liabilities: This is where we really start getting into considerations potentially relevant to this fact-pattern. If you're an existing creditor, you become a creditor of the estate. If there are contractual liabilities which arise, those fall to the estate. If the deceased committed torts, then - with certain limitations - the victims of those torts can sue the estate for compensation. It seems that there were torts committed against some of the daughters in this case...It's hard to say what effect the passage of time may have had in this case, but violence towards children tends to draw a more relaxed application of the Limitations Act than is often applicable.

(4) Beneficial entitlements: In Ontario this could plausibly have created a very substantial claim by at least one of the daughters against the estate. If I perform significant services for aging relatives - taking care of their property, and of them personally, etc. - without compensation, then I may be able to make what is referred to as an "unjust enrichment" argument, saying that I am entitled to be compensated for the value of the services I provided.

In other words...in Ontario, the law is that you have to take care of all your legal (and equitable) obligations first. Your entitlement to will away your assets as you please is otherwise unlimited - assuming you have capacity - but will always be subject to the prior satisfaction of any debts you may have.

*****

This blog is not intended to and does not provide legal advice to any person in respect of any particular legal issue, and does not create a solicitor-client relationship with any readers, but rather provides general legal information. If you have a legal issue or possible legal issue, contact a lawyer.

Wednesday, December 29, 2010

Another Note About Road Safety

I had an experience on Christmas morning that makes me comment again about road safety. I was driving to Brantford on Cockshutt Road, and had a near-miss at Concession 10 Townsend Road with a minivan proceeding eastbound through the intersection. Essentially, he stopped at the stop sign (or came close, I'm not sure), then either didn't look both ways, or thought that it was a four-way stop (incorrectly) and failed to gauge my speed, and he proceeded through.

I didn't have a stop sign, and Cockshutt is an 80 zone at that point, so I was moving at a good clip. By the time I realized that he was going, I had just enough time to swerve to hug the right side of the intersection. Pretty sure he would have hit me had I gone straight.

Either he was completely oblivious to my presence (which would show a remarkable lack of attentiveness - these are straight roads with no vision obstructions, and I was right there), or he thought I was going to stop. Which is also pretty absurd...even if he thought I had a stop sign, even a brief glance at me should have told him that I was going too fast to stop in time.

Remember: Defensive driving isn't just a good idea; it's a legal obligation. So there are a couple of lessons to take from this.

Firstly, if you're not familiar with the intersection, pay very close attention to the stop sign. If it's an all-way stop, the sign will indicate it. Pretty important to know if traffic coming from either side has to stop or can normally just go through at a high speed. This was the minivan driver's first mistake, I think.

Secondly, look carefully at approaching traffic, even if you think that the intersection is an all-way stop. Ground-view, gauge it's speed...if the vehicle is close enough to matter, you should be able to determine if it's planning to stop at the intersection. This minivan driver didn't have the right of way, but even if he had, saying "I had the right of way" doesn't necessarily take away from his failure to keep a proper lookout and, more importantly, doesn't bring back people who may have been killed. (Minivan, Christmas morning, chances are that there were kids in that vehicle. It's an appalling lack of caution.)

The previous evening, I had been taking back roads home near Hamilton, and stopped at a four-way stop. I knew it was a four-way stop, but there was a vehicle approaching from my right that I wasn't sure was going to stop. I paused for long enough to be sure that he was going to stop. (He did, as happens the vast majority of the time...but occasionally people do blow through stop signs.) My passenger even felt the need to tell me that he had to stop - my response being that I knew that he had to, but wanted to make sure that he would.

The third lesson to take from it is that attention to the road is paramount, whether you're the one with the stop sign or without. I had very little time to react, just enough time to turn aside. I know my car's limitations well enough to know how much I can swerve safely, I knew that the road conditions were dry (and had already picked my speed accordingly), and the maneouver was an automatic reaction to a hazard. Had I allowed myself to be distracted, it could have had tragic results. Again, the fact that I had the right of way wouldn't make it any less tragic. People sometimes don't pay attention to the road, whether it's because they're talking on the phone, eating, doing make-up, reading(!), or searching the floor of the vehicle for something (I once had an oncoming car come into my lane when I could see the driver doing just that...I was able to avoid him, but imagine had I been doing something similar). You need to pay enough attention to not only avoid creating hazards, but also to make sure that you're able to respond to hazards as they arise.

*****

This blog is not intended to and does not provide legal advice to any person in respect of any particular legal issue, and does not create a solicitor-client relationship with any readers, but rather provides general legal information. If you have a legal issue or possible legal issue, contact a lawyer.

Monday, December 20, 2010

Driving to the Conditions

Six years ago on Wednesday afternoon, Deborah Slaght was driving on Highway 24, going home to Simcoe from her job in Brantford when a northbound driver lost control of his vehicle and slid into her lane, resulting in a collision, causing serious and permanent disability, forcing her to change careers (to one within her medical limitations) and changing her life in significant ways forever.

A week and a half ago, the Superior Court released its judgment in the civil action brought by Ms. Slaght against the northbound driver, and also against the owner of the vehicle, awarding more than $100,000.

What happened? In Canada, it's really nothing too surprising: It was snowing, the road surface was slick.

The 24 is an 80 zone for essentially its whole length between Brantford (or rather, the Rest Acres Rd. exit of the 403) and Simcoe, and it isn't uncommon to see people driving well over that limit, even over 100kph. Prior to this collision, Ms. Slaght estimated that she was driving at around 70kph (this seems unlikely, as the driver in front of her claimed to have slowed down from 65 upon concluding that the road surface was too icy); the northbound driver said that he was going at 65kph.

The northbound driver denied liability, presumably arguing that he wasn't actually negligent, and was applying due care. After all, he's going 15kph under the limit; when the law lets him go up to 80kph, what more can he be expected to do?

The Court's answer: Slow down more. Driving at 65 was still too fast under the conditions.

This was a civil action, and so the test for proving negligence is relatively lax - put simply, it's just a question of whether or not he acted as would a reasonably prudent driver under the circumstances. The Court found that a reasonably prudent driver wouldn't have been driving at 65 kph; he lost control of his vehicle because he was traveling at too high a rate of speed for the conditions. The Court doesn't seem to care that he was going less than the speed limit.

And rightly so. An 80kph speed limit isn't permissive; it's prohibitive. What I mean is that the sign saying "80 maximum" doesn't create a freestanding entitlement to drive at 80kph; it only prohibits going faster. Civil liability attaches fairly easily, but even quasi-criminal or criminal charges wouldn't necessarily be out of the question when a driver is going less than the limit. (The test is harder, requiring a 'marked departure' from the standard of the reasonably prudent driver...but saying 'I was under the speed limit' isn't a complete defence.)

This should be a stern reminder to all of us, going into another winter, which so far hasn't been a kind one. It's more important to get there safely than to get there quickly, regardless of where you're going or why. When the road conditions call for it, slow down. As much as is necessary.

*****

This blog is not intended to and does not provide legal advice to any person in respect of any particular legal issue, and does not create a solicitor-client relationship with any readers, but rather provides general legal information. If you have a legal issue or possible legal issue, contact a lawyer.

Thursday, December 9, 2010

Avoiding the Contract Pitfalls

I went on at some length about the pitfalls that can defeat the terms of a written contract. A word might still be useful on how to avoid the consideration pitfall.

To deal with this problem at the outset of the employment relationship, I've seen other lawyers suggesting that you advise the employee that the employment relationship is subject to them signing a written contract and accepting its terms, and documenting that the employee was so told.

Not bad, but still not infallible, in my view. I can imagine a number of ways that such a thing might go wrong. (A question as to whether or not the documentation was made contemporaneously, or accurately reflected the conversation; allegations that specific representations were made regarding the contents of contract which might give rise to a misrepresentation cause of action; etc.)

Email is a wonderful thing. Instantaneous, and everyone has it, so much like telephone, but it's pretty much automatically recorded by both the sender and receiver, so more like a letter in that way. Accordingly, in today's day and age, I would advise against making an offer over the phone. Call the candidate to tell her that the offer's coming, certainly, but make the actual offer immediately thereafter by email.

Ideally, you'll have an offer letter which offers employment subject to the terms of the enclosed contract, with instructions that the employee may accept by signing the contract and returning it to a specified person in a specified time frame. There are other ways of doing it, too, depending on circumstances. But there are also a lot of wrong ways.

To deal with the consideration problem in the middle of the employment relationship, give something extra. When it's time to give a raise, or a discretionary bonus, or something else to which the employee isn't already entitled, you can piggyback a contract onto that. As I said, a peppercorn can be consideration - it doesn't have to be a great deal of money, but there has to be something.

There are still risks. You still have to be forthright about what the employee is signing. And if there's low consideration, then there is always the risk of a court finding the deal unconscionable, a shocking abuse of the employer's position of authority, or some such thing. You need to be careful, accordingly. (And it would be a thoroughly terrible idea to give somebody a hundred dollars to sign a contract severely limiting their notice period and then to immediately turn around and fire them.)

And - this actually deals with a separate pitfall which I didn't discuss, known as the "substratum argument" - always have employees confirm the continued effect of the terms of the written contract every time you promote them. The substratum argument is basically that the contract a person signed when starting in the mail room can't still be expected to be effective when he's risen through the ranks to become president of the company. The solution is easy, and it's to make sure that you continue to have him sign new written contracts as he advances. (The advances, remember, can be consideration, if done right.)


*****

This blog is not intended to and does not provide legal advice to any person in respect of any particular legal issue, and does not create a solicitor-client relationship with any readers, but rather provides general legal information. If you have a legal issue or possible legal issue, contact a lawyer.

How to Make a Written Employment Contract Binding

First off, let me be very clear on one point: I am not talking here about post-employment releases. Those aren't so difficult to make binding, but the analysis is slightly different. What I am talking about here is how to prepare and execute a written employment contract in such a way as to be able to rely on its terms.

Most of the written terms of the contract are never really going to matter. The written terms of the employment contract that define the day-to-day relationship between the employer and employee...well, they help to define the relationship at the start, and to develop realistic expectations on the part of all parties, but in many ways the employment relationship is a living relationship that is defined in a de facto way, and not by the agreement made at the beginning.

Where the written employment contract really matters is on termination, because it will often have provisions that define how the employment relationship may be terminated, and other provisions setting out obligations that survive termination.

In particular:

(1) A written employment contract will frequently (and ought to) have a term setting out a formula for the amount of notice of termination, or pay in lieu thereof, and

(2) For some employment relationships, contracts include terms surviving termination including non-disclosure, non-solicitation, and non-competition.

Without an express written term setting out the amount of notice required to terminate the contract, the default is "reasonable notice" at common law, which is usually fairly generous to the employee, often giving significantly more than the statutory minimums.

Likewise, without express restrictive covenants, the implied terms at common law are not generally very favourable to an employer.

The first, and most important, tip that I can give you for getting a written employment contract that actually works is this: Consult a lawyer. Self-promotion aside, it is actually important. Human Resources Professionals and consultants are helpful, and can do a lot of the groundwork, but there are nuances of contract drafting and execution which you need a lawyer's advice to make sure you're getting right.

Here are a few of the pitfalls (not a comprehensive list):

(1) Lack of consideration

This is a big one. In law, in order to have a binding contract, there needs to be "consideration", something of value which each side is agreeing to contribute. If we agree that I will shovel your driveway after every snowfall this winter and get nothing in exchange, then you can't hold me to that - it's not a contract. However, consideration need not necessarily be market value. If our agreement (re driveway shoveling) includes a term that you will provide me with a single peppercorn next fall...put your feet up, because that's a contract. (And no, I'm not actually offering to enter into such a contract.)

So you're wondering how this applies to a written employment contract: Seems a straightforward quid pro quo, no? The employee provides services; the employer provides a remuneration package.

That's how it's supposed to be. The trouble is this: What happens if the employee already has the job, and you're asking him to agree to a variation in its terms?

Remember this: Every employee has an employment contract. If it isn't written, that doesn't mean it's not a contract. And the implied terms of an oral contract at common law give employees a fair bit of protection. So if I already have my job, my oral employment contract, and you as the employer come to me and say "I want you to sign this contract that says that you'll work for me as you're doing, I'll pay you as I'm doing, and I can terminate the contract on a certain amount of notice or pay in lieu thereof"...what am I getting by signing the contract?

Yes, there's a clever answer, which has been repeatedly tried at the Court: By signing the contract, the employee avoided getting fired right then and there. Well, it wouldn't be a 'just cause' termination - the employer can't require the employee to accept such a term in such a way that refusal would be insubordination. It would be termination on notice, as the employer is entitled to do...and remains entitled to do (in theory, more easily) following the execution of the contract, and accordingly has not actually given anything of value.

(In one case, the Ontario Court of Appeal bought an argument of "consideration by forbearing from exercising its right to terminate"; however, in another two subsequent cases, the Court of Appeal made it clear that the earlier decision was rooted in a unique fact that the employer had impliedly promised not to fire in the near future in exchange for the execution of the contract.)

Essentially, what's required when modifying an existing employment contract is "fresh consideration" - something else given in addition to the job that the employee already has.

But this doctrine goes a step further, and doesn't just apply to modifying contracts of people we might think of as 'existing employees'. It also applies to new hires. When an employer brings in a new employee, starts the employee working, and only puts a contract to them later - a day, a week, a month, or a year, whatever - the Courts have consistently held that the terms aren't binding without fresh consideration. That's easy, right? Same analysis as above. But what about signing the contract at the start or even before the start of employment? Picture this:

I interview you. I explain to you the job duties, the hours, the compensation, the reporting structure...then, after the interview, I call you and ask you "When can you start?" Then, on your first day of work, I put you through the usual 'orientation' - reviewing policies, getting payroll matters sorted out, and signing the employment contract.

This isn't unusual. Lots of employers do it this way. (I recall a Small Claims settlement conference when I was on the employee side, and the employer's counsel took the position that I was raising hay about nothing because that is such a common way of doing it.)

The trouble, however, is that the employment contract already exists. I have offered you the job, and you have accepted it. Unless you already knew that you would be required to sign a contract, and/or were aware of the terms that would be in the contract, there's a good chance that the written contract will be set aside without fresh consideration. In one case in particular, the employee even signed the agreement prior to commencing employment, and it was still void for lack of consideration.

And it makes a certain amount of sense: I offered you a job. You thought you knew its terms. Maybe you already quit your old job, or moved cities, to come start employment with me. Suddenly you're in the door, relying on this job for your day-to-day expenses, and I'm saying "Sorry, you don't actually have the job unless you sign this." There's good reason for the Courts to scrutinize such circumstances closely. Note, however, that while quitting an old job or moving might help evidence of the existence of the employment contract, such reliance is not strictly necessary to engage this doctrine.

(2) Illegality of Terms

Well, the employer's not asking the employee to do anything criminal, right? So it's okay? Not that easy. This pitfall usually applies to termination clauses, allowing for termination on a certain amount of notice.

The Ontario Employment Standards Act, 2000 provides a formula for statutory minimum entitlements on termination. A clause which provides less than the minimum, therefore, fails.

And it isn't just a bump-up. If the contract says "The employee gets nothing", then the Courts aren't going to look at it and say "Well, clearly the parties intended that the employee would get no more than legally required." No, instead the Court will look at it, strike the clause entirely for illegality, and then look at the contract (which now has no termination clause) and say "Well, I guess we have to imply a termination clause. Reasonable notice it is."

Under the ESA (mind you, this varies by jurisdiction - different formulas for Federal employers and employers in other Provinces), the minimum notice runs as follows:

Length of Service - Minimum Notice
Under 3 months - nothing
3 months but under 1 year - 1 week
1 year but under 3 years - 2 weeks
3 years but under 4 years - 3 weeks
4 years but under 5 years - 4 weeks
5 years but under 6 years - 5 weeks
6 years but under 7 years - 6 weeks
7 years but under 8 years - 7 weeks
8 years or more - 8 weeks

An important note, however, is that even formulaic deficiency can render a clause void. If it doesn't comply with the standards, the clause itself is void ab initio, and is of no force and effect. So let's say a contract says that the employer can fire on provision of 1 month's notice, and the employer fires an employee with between 3 and 4 years of service. The statutory minimum is 3 weeks, right? The contract gives a little bit extra. Doesn't matter. The fact that the provision failed to account for the minimums which the employee would have been owed at 5 years of service or more means that the clause is void entirely. Reasonable notice it is.

Or what happens if you say something like "2 weeks per completed year of service, up to a maximum of 10 weeks"? The formula keys notice to length of service, much like the ESA, and provides a cap in excess of where the stat minimums cap out...should be fine, no? Wait a second, no: Look at the entitlement for employees with more than three months but less than one year: Under the ESA, minimum 1 week, but under the contract, nil. Even if the employee doesn't get fired within the first year, the formulaic deficiency still voids the contractual term entirely. Reasonable notice it is.

Usually, language that keys the formula to the statutory minimums is going to be fine. But even then it has to be carefully drafted: In one case, an employee signed a contract which gave him the greater of the Ontario ESA minimums or four weeks. The employee then transferred to British Columbia, and was later terminated. Because the Ontario formula is different (and in some cases less) than the B.C. formula, and the termination of employment was under B.C. law, the B.C. Court of Appeal found that the clause was formulaically deficient and therefore unenforceable.

So if you specify the Province's laws, you might be in trouble. If you just say "under the applicable Provincial law", that is likely too ambiguous to be enforceable.

Starting to see why you need a lawyer?

(3) Terms are against good public policy

This is one that can apply to restrictive covenants such as non-competition clauses or non-solicitation clauses. Essentially, you can't just make it a term of every employment contract that "You can never compete with us." Restraint of trade is something that the Courts don't like. Telling an employee that he can't continue to work in the industry at all unless it's for you...well, it gives the employer too much power in an already imbalanced power relationship, so there has to be a really good reason to do it.

I'm going to be brief on this, because it really is one that is full of legal nuances, and there's no question at all that you should talk to a lawyer about drafting and executing a restrictive covenant...

...but, put in very simple terms, the employer needs to be able to show that they *need* the term in order to protect a legitimate proprietary interest, and that some lower form of restrictive covenant couldn't provide adequate protection. Usually we're talking about proprietary information (privy to confidential business strategies, research and development, etc.), or proprietary relationships with clients or others. (I trust you to be 'the face of my business'. You're in charge of interacting with all my clients on behalf of the business, and build a relationship for years. Then you decide to start your own competing business. I might have a proprietary interest in those relationships.) Then the question arises as to whether a non-competition clause is necessary, or would a non-solicitation clause do the job? It's really about what is necessary to prevent the employee from being able to unfairly compete.

Beyond that, the employer needs to establish that the terms of the restrictive covenant are geographically and temporally reasonable. "You can't compete with us anywhere, ever" would not be reasonable. But "You can't compete with us in this region, over x period of time"...well, it depends on the circumstances. Some industries are faster moving without real geographical boundaries. So if you're working in the dot.com sector, maybe a wider geographical scope might be reasonable, but your proprietary information becomes stale much more quickly, so a shorter temporal scope might be appropriate.

It's all very fact specific. And there's no halfway. Either the clause is valid, or it isn't. Either the terms are reasonable, or it isn't. If it is valid, then the employee (who will usually have been breaching it for a while before there's a judicial interpretation) is in deep trouble. If it's not valid, then the clause fails in its entirety and provides no protection whatsoever to the employer.

Hence why it's important to have a lawyer.

*****

This blog is not intended to and does not provide legal advice to any person in respect of any particular legal issue, and does not create a solicitor-client relationship with any readers, but rather provides general legal information. If you have a legal issue or possible legal issue, contact a lawyer.