Business vocabulary case study: a hypothetical contract

This business vocabulary case study is a worked walkthrough rather than an account of a real company. The document below is invented for the purpose. The point is not the document itself, but the contract words inside it that mean one thing in a meeting and something else in an agreement.

The hypothetical. Two parties sign a supply agreement. It says the supplier will use best efforts to deliver, that the buyer may terminate for a material breach, that the supplier warrants the goods, that the supplier will indemnify the buyer, that the appointment is exclusive, and that notice shall be given in writing. Everyone read it. Nobody defined anything. Eight months later the parties disagree about all six.

Here is how those clauses and related contract terms work in the hypothetical.

What to take away

"Best efforts"

In ordinary speech, trying hard. In an agreement, it is an obligation standard, and how demanding a standard it is depends on the governing law. Some jurisdictions distinguish best efforts from reasonable efforts and treat the first as considerably more onerous; others treat the phrases as much closer together, or as meaning whatever the surrounding contract suggests.

What follows from that is a drafting rule rather than a definition: if the level of obligation matters, define it in the agreement by describing what the party must actually do. A clause that specifies the steps required removes the question entirely.

In our hypothetical, the supplier believed it meant "try hard within our normal operations". The buyer believed it meant "do whatever it takes short of insolvency". The contract did not say, so the answer would depend on the governing law and the surrounding terms, which is to say, on a dispute.

"Material"

Loosely, important. In an agreement it is a threshold that switches rights on: below it, nothing happens; above it, a party can terminate or claim.

Material is very often left undefined, which leaves the threshold to be argued about at exactly the moment the parties have stopped cooperating. In some regulatory contexts, securities disclosure in particular, materiality has a specific legal test, and that test governs there regardless of how the word is used commercially.

A breach clause with a defined trigger ("failure to deliver on more than a stated number of occasions in a stated period") gives both parties the same answer. One resting on material gives each their own.

Which body decides a term like this, and which questions a jurisdiction settles rather than a document, is set out in the vocabulary questions.

"Including"

Including on its own can be read as introducing an exhaustive list, everything included is here, and nothing else counts. Including without limitation signals that the list is illustrative. Which reading a bare including gets depends on the jurisdiction and the drafting.

Small word, real consequence: a definition of Confidential Information that says "including customer lists and pricing" may or may not cover anything not named.

"Warrants"

Three words sit close together here and they are not interchangeable.

A representation is a statement of past or present fact made to induce someone to enter the contract. A warranty is a contractual promise that something is or will be true, with a remedy for breach built into the contractual relationship.

In some legal systems, a condition is a term of such importance that breaking it allows the other party to end the contract. Breaching a warranty only sounds in damages.

Guarantee is the messiest of them. In consumer usage it means a promise about quality. In finance and in law a guarantee frequently means a third party's promise to answer for someone else's obligation: a different animal entirely, often with formal requirements such as being in writing.

How these categories work, and what remedies attach to each, varies substantially between legal systems. That is a question for a lawyer in the governing jurisdiction. The general point survives the variation: the label on the clause is doing legal work, and swapping it for a synonym changes what happens when the statement turns out to be untrue.

"Indemnify"

An indemnity is a contractual promise to cover specified losses that the other party suffers. It is a promise between the parties.

Insurance is a policy bought from an insurer, which pays out under its own terms and exclusions.

They are routinely spoken of as though one produces the other. It does not.

A party can owe an indemnity and have no insurance that responds. Then the obligation is met from its own resources, or not met at all if the resources are not there. An indemnity from a counterparty with nothing behind it is a sentence, not protection.

"Exclusive"

In appointments and licenses, the usual distinction is that an exclusive

That is the common convention, not a universal rule, and usage varies. A well-drafted clause spells out who may do what instead of relying on the adjective.

In our hypothetical, one party intended "exclusive" to mean the supplier would not supply competitors. The other intended it to mean the buyer would not buy elsewhere, and those are different promises, and only one was written.

"Shall"

Shall is conventionally used to impose an obligation on a party. May grants discretion. Will is often used for a statement of future fact or a softer promise. Must imposes a requirement, sometimes on a thing rather than a person.

Drafting conventions differ, and some modern styles abandon shall entirely as too ambiguous, replacing it with must for obligations. Either convention is workable. Mixing them within one document is not, because a reader cannot then tell whether a change of word signals a change of meaning.

"Terminate"

Termination for cause requires a specified trigger: usually a breach that meets a defined threshold. Termination for convenience requires no reason, usually requires notice, and often carries a payment.

A contract with only one of these has made a decision. A contract that says "either party may terminate" without saying which kind is describing two very different rights with one phrase.

"Notice"

Notice in an agreement is not the same as telling someone. Notice clauses normally specify the method, the address, and the moment the notice is treated as received, which may be different from when it was actually read. A communication that did not follow the clause may not count, however clearly it was understood.

What the walkthrough shows

The document was not badly written in any obvious way. Every clause was grammatical and every word was in common use. What it lacked was a definitions section doing the one job that section exists for: stipulating, inside this document, what these words mean here.

Three rules come out of it.

A defined term beats ordinary usage inside the document. If the agreement says Business Day means something unusual, that is what it means, and reading it the ordinary way is an error.

Where a term has a technical meaning in accounting, tax, or law, that meaning governs in a filing or a contract, not the sense used in the meeting where the deal was agreed.

If a word carries a threshold, define the threshold. Material, promptly, reasonable, substantial, and significant all defer a decision to a later argument unless the document says what they mean.

None of this is legal advice. These categories work differently by jurisdiction, and the version for a specific agreement comes from a lawyer in the governing jurisdiction.

When a regulator defines a term, reading the regulator's own words is a good habit, and for investment and finance terms, the investor.gov glossary states them plainly.

Related entries are at business vocabulary, and the nine everyday words whose second meaning is set by somebody else are worked through in the vocabulary mistakes.

Common questions

Why does a contract define words that already have meanings?

Because the ordinary meaning is a range and a contract needs a point. A definitions section is not lawyers being difficult; it is the only place where the parties can agree in advance which reading applies.

Should I object to a term I do not understand?

Ask what it means and get the answer in writing. That is not an objection, and a party who will not put the meaning in writing has told you something useful.

Is a word in a heading binding?

Usually not, and most agreements say so explicitly in a clause about headings. That clause is worth finding, because the headings are what most people actually read.

What if the same word appears with two meanings in one document?

Then it is a drafting fault, worth raising before signature, not after.

The reading habits under corporate jargon find it: recover the actor, recover the verb, and ask what would make the sentence false.

The federal plain English disclosure rule exists because regulators concluded the same faults were not harmless in documents investors rely on.