The Costly Comma Communications Conundrum In Canada

from the a-little-alliteration dept

For all of the complaints that show up about lawyers, it is true that when you’re putting in place contracts, some of the finest details may turn out to be important down the road. John writes in to let us know the latest on the million dollar battle over a comma up in Canada. A few months ago, telco Rogers Communications lost their lawsuit while teaching a bunch of folks about commas and clauses. Basically, it’s a contract dispute, where Rogers had the right to use telephone/power poles that were owned by someone else and managed by Aliant. They put in place a five year contract, renewable in five year increments. However, there was also a clause that allowed the agreement to be terminated with one year’s notice — which Aliant tried to do to Rogers. Rogers flipped out, recognizing that negotiating a new contract would mean much higher prices. It all comes down to a comma. The way Rogers reads the contract, the one year notification only applies at the renewal points. In other words, they can give one year’s notice one year before each five year chunk is up. Aliant notes that with the placement of the comma, the one year notification loophole applies to the entire contract, suggesting they could just give one year’s notice at any time.

The initial decision from this summer was in Aliant’s favor — though, not entirely due to the placement of the comma. The ruling also noted that if the purpose of the clause was to only go into effect every five years, instead of saying Aliant needed to give one year’s notice, it would have given a date by which Rogers needed to be notified. This point is actually a lot more compelling than basing the ruling on just the comma alone (a comma which we doubt the original lawyers really paid attention to at the beginning). However, the story is about to get a lot more interesting. Rogers is appealing, and they claim that they have a second version of the contract written in French that makes it much clearer that the purpose of the original clause is only to allow the contract to be broken at the five year renewal points. Of course, this raises a whole bunch of other questions. How do you handle a contract dispute when the translation of the contract isn’t quite the same? Of course, if the contract was originally written in English and translated to French, it’s easy to just claim that the translator made a mistake, rather than having anything to do with intent. If, however, it was the other direction…


Rate this comment as insightful
Rate this comment as funny
You have rated this comment as insightful
You have rated this comment as funny
Flag this comment as abusive/trolling/spam
You have flagged this comment
The first word has already been claimed
The last word has already been claimed
Insightful Lightbulb icon Funny Laughing icon Abusive/trolling/spam Flag icon Insightful badge Lightbulb icon Funny badge Laughing icon Comments icon

Comments on “The Costly Comma Communications Conundrum In Canada”

Subscribe: RSS Leave a comment
11 Comments
Bulent Akman (user link) says:

2 official languages? 2 times the headaches

As a bilingual Canadian I can say it’s common knowledge that Canada has two official languages. To just flog it, this means both English and French are equally valid in the eyes of the law. The French copy was not, legally speaking, a translation but in fact an “original copy” of the English contract. Do I have that right? Was there one bilingual contract? Or were there two contracts which were both signed? Which was signed last? I suppose that in the Canadian courts, there is a principle of greater specificity in contract law? If both parties in good faith signed both contracts then wouldn’t the more liberally worded English contract be voided by the more specific French one? I always thought a contract was only a contract if it met a reasonable level of specificity in both time and terms and was entered into in good faith. I can’t imagine how such a devastating difference of interpretation wasn’t uncovered in negotions. Sounds like Aliant is acting with deliberate knowledge that their preferred interpretation comes after the fact (a posteriori?). Can someone with legal experience explain it to me?

perogiex says:

This has happened before

There was a similar case in Quebec a few years ago. A man was given a ticket for passing a slow moving car/bus(?) on a solid yellow line. He went to court arguing that the english version of the law did no prohibit the passing of a slow moving vehicle on a solid line. The judge ruled that the english laws were just a translation of the french ones so they take precedence.

mousepaw says:

English vs French

As far as I know, one doesn’t have to understand a contract to sign it or be bound by it as long as you meet the age requirement for signing the contract.

Contracts that hold a person or company liable without the party being aware of the “fine print” are signed all the time. (Particularly when borrowing money.) I believe the one signed last would be the one that takes precedence, as B. Akman said and the fact that there are two, in equally relevent languages, has no bearing as both companies were aware that this would be the case. Either the french one or the english one could’ve been signed last and whichever one that was would over-ride the other.

Since the question has been raised after the fact, it seems to me that the two companies will have to fight the concept in court and prove original intent.

Add Your Comment

Your email address will not be published. Required fields are marked *

Have a Techdirt Account? Sign in now. Want one? Register here

Comment Options:

Make this the or (get credits or sign in to see balance) what's this?

What's this?

Techdirt community members with Techdirt Credits can spotlight a comment as either the "First Word" or "Last Word" on a particular comment thread. Credits can be purchased at the Techdirt Insider Shop »

Follow Techdirt

Techdirt Daily Newsletter

Techdirt Deals
Techdirt Insider Discord
The latest chatter on the Techdirt Insider Discord channel...
Loading...