About the author
Ken Adams is the leading authority on how to say clearly whatever you want to say in a contract. He’s author of A Manual of Style for Contract Drafting, and he offers online and in-person training around the world. He’s also chief content officer of LegalSifter, Inc., a company that combines artificial intelligence and expertise to assist with review of contracts.
I enjoyed this article. In drafting agreements I’ve frequently thought about this issue with “including.” Using the phrase “but not limited to” is redudant, but it is so commonly used, I feel incorrect in not using it. One thing I must be careful about is being consistent, which is the problem with using “but not limited to” … as it’s natural to use the word “including” frequently, but only think to use the superfluous followup provision here and there in those circumstances where it feels specially required.
Scott: If you read my full analysis of this subject, you'll see exactly how futile it is to tack "but not limited to" or "without limitation" after "including."
And more generally, the only way anyone can improve their drafting is if they're willing to take a deep breath and break longstanding bad habits. The hardest part about changing a bit of traditional language is doing it for the first time. But once you see that the sky hasn't fallen and that with that one change you've made your contracts a little bit easier and your life a little bit simpler, sticking with that change comes easy.
Ken
Like it or not, "expressio unius est exclusio alterius" appears to have a sufficiently firm footing in case law that it creates doubt as to how a bare "including" will be interpreted. You recommend cutting back on illustrative lists, or choosing your list carefully such that the listed items are not, for instance, all of a similar type which is not representative of the entire category. However, often the pressure to insert "including" plus the list comes from something either the client or the other side is particularly concerned to see is covered. One alternative way around that which also avoids the danger in Covington (apparently changing the meaning of a bare "including" by inserting "including without limitation" elsewhere) is to insert a clause somewhere up near the definitions saying something like "'Including' means 'including without limitation'"; that would seem to settle the matter without littering the body of the contract with "without limitation". What is your opinion on that?
Perhaps the comment is off the mark, but the cost of hiring a security guard does not seem related to ” repairs to the parking areas or other Common Areas, lighting, removal of snow and ice, trash, rubbish and other refuse, general comprehensive liability insurance covering the Common Areas; fire, casualty and extended coverage on the Premises and the Shopping Center … ; and the cost of leasing or the depreciation on any equipment used to implement the foregoing maintenance”. The cost for hiring a security guard seems more related to admin and management fees that are excluded.
Ken, Convention over the last 10 years or so in English contracts is to include an interpretation provision along the lines of "including means including without limitation", then only say "including" in the main body of the contract. This way you get plainer English in the main body, and avoid falling into the potential elephant trap of the eiusdem generis rule. Like it or not, there are centuries of case law about this rule. Lewison on Interpretation of Contracts devotes over 7 pages to the rule, citing a couple of dozen cases.
Having said that, many of the cases are about lists generally, and not the specific instance of stating a general obligation following by "including…" Perhaps lawyers worry too much about the meaning of "including", but it is deeply ingrained in the legal draftsman's thinking.
Whatever one's view is on that point, I suggest it is sloppy drafting to have "including without limitation" in some clauses but not in others where "including" is used. Assuming, of course that the same meaning is intended in all cases; if a different meaning is intended, then clearer language should be used to express the different intention. It is like saying "the Company and its Affiliates" in one clause and "the Company and its Subsidiaries" in another clause, where the only reason for the different language is because the clauses were pasted from different sources.
There is another principle of contractual interpretation that one should construe the document as a whole. As Diplock LJ said in Prestcold (Central) Ltd v Minister of Labour [1969] 1 WLR 89, "…if [a legal draftsman] use different words the presumption is that he means a different thing or concept …a legal draftsman aims at uniformity in the structure of this draft." Arguably, this principle might cause the court to interpret the bare "including" as being subject to the eiusdem generis rule, particularly if there are other clauses that use the term "including without limitation". My guess is that the court is more likely to do this if the contract has been drafted by a lawyer than if it has been drafted by a layman, and that it is more likely than not that the court will assume the same meaning whatever form of "including" is used, but I would prefer not to run that risk.
Alex and Mark: If my only objection to "including without limitation" and "including but not limited to" were the fact that adding "without limitation" and "but not limited to" results in extra words, then sure, the sort of provision you mention would be economical. (I refer to such a provision in MSCD 14.7, in the chapter discussing "provisions specifying drafting conventions.")
But my principal concerns aren't related to economy of words. First, there's the problem that saying "including without limitation" does violence to the ordinary meaning of "including." Second, and more importantly, using a provision specifying drafting conventions as a boilerplate means of ensuring that "including" is given the same meaning, whatever the context, has not found favor with all courts. In MSCD I cite a couple of cases in which a court has said, in effect, "We don't care about your stinking 'without limitation," we hold that "fruit" means "citrus fruit."
Tricks that aim to save the drafter from thinking are no cure-all. That's why I recommend that instead the drafter limit use of "including" to those instances where it might otherwise be unclear whether a given item is included in the class in question.
Alex, I'm familiar with the situtation where the client is concerned about making sure that a particular kind of item is included in the general class. In such situations, I first of all attempt to find some way of stating the general class in a way that makes the client comfortable that the item in question does indeed fall without the general class. For example, the client might be concerned that bathtubs do indeed constitute bathroom fixtures and so don't need to be singled out. Maybe given the nature of the assets in question, the best fix would be instead to refer to the general class as "porcelain bathroom fixtures."
If you can't come up with a way of addressing the general class that makes the client comfortable, then I'd be reluctant to resort to using a list of obvious items after "including," because of the risk that a judge would use the list to limit the scope of the general class. And I know from the caselaw and from how language works that "including without limitation" can't be relied on as a fix. And the longer the list, the greater the risk.
So instead I'd use some other formula. For example, if the client is particularly concerned about bathtubs because the bulk of the assets are bathtubs, I might instead say "bathtubs and any other bathroom fixtures, whether made of metal, porcelain, or both."
Mark, thanks for reminding me of the more general lesson of this case, which is that if you express the same meaning using different words, you're inviting a judge to make mischief.
And like any rule of construction, the presumption that different words convey a different meaning is useful unless it isn't. Given the expediency that prevails in the transactional world, inconsistency is a fact of life.
Ken
Ken:
There is another lesson in the text you cite from the contract: These sentences are way too long! I suspect that the court would have been more inclined to the landlord's argument if the verbs "mean," "include," and "exclude" had been in different sentences. Something like this:
“Common Area Costs” means the costs and expenses incurred by Landlord in the operation and maintenance of the Shopping Center and the Common Areas. Common Area Costs include repairs to the parking areas or other Common Areas. Common Area Costs exclude any Shopping Center administrative or management fees or the like.
I'm not saying that would have avoided the issue entirely — just that it would have helped.
It would also have made this provision much more readable.
Chris Lemens