A contract can run fifty pages, contain dozens of carefully negotiated provisions and still leave the parties fighting over a single word. The culprit is rarely an obscure doctrine or a creative reading by opposing counsel. More often it is a drafting choice that never should have been made.
Transactional lawyers spend most of their time negotiating price, allocating risk and drafting representations and warranties. Yet some of the costliest ambiguities come from ordinary words that appear in nearly every agreement. Four of them deserve careful attention. None requires a law degree to understand. That has never stopped lawyers from getting them wrong.
Reserve “Shall” for Obligations or Stop Using It
Few words have drawn more criticism from legal writing experts than “shall.” Drafters use it to impose obligations, but they also use it to describe future events, state conditions and declare facts. The result is a word whose meaning shifts with its position in the sentence.

Consider three examples:
- “Buyer shall pay Seller $100,000 on January 1.”
- “Payment shall be due on January 1.”
- “This Agreement shall be governed by the laws of New Jersey.”
Only the first imposes a duty on anyone. The second states when payment is due. The third declares the governing law. Same word, three different jobs.
If you keep “shall,” confine it to obligations and make the party with the duty the subject of the sentence: Seller shall deliver the goods, and Buyer shall pay the purchase price. Everything else gets a different verb. Payment is due on January 1. This Agreement is governed by New Jersey law.
“Will” works for future events and consequences: “This Agreement will terminate on December 31, 2027.” Some respected drafting authorities also accept “will” for contractual promises. “Must” is an increasingly popular choice for mandatory requirements, and federal plain-language guidance favors it over “shall.” “Buyer must deliver written notice within ten days” is hard to misread.
My own convention is “must” for requirements, “will” for future events and consequences and “may” for discretionary authority. Which convention you choose matters less than applying it consistently. I seldom use “shall.”
One warning. Do not run a global search-and-replace on every “shall” in an existing agreement. Each occurrence has to be read in context; a mechanical swap can turn a statement of fact into an obligation or the reverse.
“May” Grants a Right Without Any Help
“May” expresses permission. “Shall” expresses obligation. Drafters who blend the two invite confusion.
“Buyer may inspect the goods before accepting delivery” gives Buyer the right to inspect without requiring it. “Buyer shall have the right to inspect the goods before accepting delivery” reaches for the same result with more words, and its “shall” hands the other side an argument that the sentence imposes a duty rather than confers a right.
The stakes rise when discretion is involved. “Company may terminate this Agreement upon thirty days’ written notice” gives Company an option. “Company shall terminate this Agreement upon thirty days’ written notice” arguably requires Company to terminate. One word turns an option into an obligation.
Prohibitions carry their own trap. “May not” is usually read as a prohibition, but it can raise avoidable questions about whether the language is permissive or mandatory. “Must not” removes the doubt: “Employee must not disclose Confidential Information to any third party.”
Granting a right, imposing an obligation and prohibiting conduct are three different things. Draft them as three different things.
“And” and “Or” Decide Whether One Failure Is Enough
“And” and “or” are among the shortest words in English. They can also be among the most expensive.
Suppose a contract provides: “Buyer may terminate this Agreement if Seller fails to deliver the goods and provide the required certificates by June 30.” If Seller delivers the goods but not the certificates, can Buyer terminate? Or must Seller fail at both? A court may eventually answer that question by looking at the surrounding language. Better to answer it yourself.
If either failure should trigger the right, say so: “Buyer may terminate this Agreement if Seller fails to deliver the goods or fails to provide the required certificates by June 30.” If both failures are required, say that too: “Buyer may terminate this Agreement only if Seller fails both to deliver the goods and to provide the required certificates by June 30.”
“And/or” makes things worse, yet lawyers cling to it despite its well-earned reputation for ambiguity. “Consent must be obtained from the officers and/or directors” could mean the officers, the directors, either group or both groups, and it says nothing about whether one person’s consent is enough. Name the decision-makers and the number of approvals instead: “Consent must be obtained from a majority of the directors” or “Consent must be obtained from either the Chief Executive Officer or the Board of Directors.”
The goal is not to banish “and” or “or.” It is to make clear whether conditions are cumulative or alternative.
“Including” Should Say Whether a List Is Complete
Contracts use lists to identify covered activities, obligations, assets and exceptions. A list can also create a limitation nobody intended if the drafter does not say whether it is exhaustive.
Take this definition: “Confidential Information includes financial statements, customer lists, business plans and pricing information.” Does it cover only those four categories? What about product designs, source code, marketing strategies or information about prospective customers?
The standard fix is “includes, without limitation,” which signals that the list illustrates rather than exhausts the category. Many drafters handle the point once, in the interpretation section, by providing that “including” means “including without limitation” wherever it appears. Either approach works if applied consistently.
Two qualifications apply. First, “without limitation” cannot rescue an item that falls outside a narrowly drafted definition, so the underlying category still has to be defined with care. Second, not every list should be open. Sometimes the parties intend an exclusive list: “The permitted uses of the Licensed Materials are limited to internal research, employee training and product development.” Open-ended language there would defeat the bargain.
Decide whether the list is illustrative or exclusive. Then say so.
The Final Read Belongs in Your Adversary’s Chair
These examples share one lesson. Drafting is not simply translating negotiated business terms into legal language. It is making sure the language actually states the bargain.
Before signing off, read the agreement as someone who was not at the table and has every incentive to resolve each ambiguity in their own favor. Ask who is obligated to do what, whether each provision creates a right or an obligation, whether its conditions are cumulative or alternative and whether each list is exhaustive or illustrative. Then search the document for every “shall,” “may,” “and/or” and “including.” That exercise alone can surface inconsistencies a conventional proofread will miss.
Lawyers are sometimes accused of making simple things complicated. The charge has merit. We have built an impressive vocabulary for saying things that ordinary English often says better. A contract should not test the reader’s ability to decode legal prose. It should state plainly what the parties agreed to do, what they agreed not to do and what happens if they don’t.

Lawyers are sometimes accused of making simple things complicated. The charge has merit. We have built an impressive vocabulary for saying things that ordinary English often says better. A contract should not test the reader’s ability to decode legal prose. It should state plainly what the parties agreed to do, what they agreed not to do and what happens if an agreement isn’t followed.
The fewer openings for creative interpretation, the better. Good drafting does not give lawyers something interesting to litigate. It makes sure they don’t have to.
You may also enjoy:
- Evergreen Clause: This is the Clause that Never Ends
- When a Contract Goes Too Far, Will a Court Fix It?
- Covenant of Good Faith and Fair Dealing
- The Lighter Side of Contracts
and, if you like what you’ve read, please subscribe below or in the right hand column.