Defined Terms: Why the Capitalised Words in Your Contract Decide Everything

Any word in a contract that starts with a capital letter, and is not the first word of a sentence or a proper noun, is probably a Defined Term. That means it does not carry its everyday dictionary meaning. It carries whatever meaning the drafter gave it, usually in a definitions clause near the front or back, sometimes buried inline the first time it is used. "Confidential Information," "Affiliate," "Services," "Losses," "Business Day," each looks ordinary until you notice the capital letter, and each can be written narrower or wider than you'd assume from a casual read. The one thing most people get wrong: they read the operative clauses first and skim past the definitions, assuming a capitalised word means roughly what the lowercase word means. It often doesn't, and that gap is where a lot of contract risk lives. This guide is published by Adira, which makes contract drafting and review software, so we have a commercial interest in you reading contracts carefully, but everything below stands on its own whether or not you ever use our product.

Plain meaning

A definitions clause is a private dictionary that applies only inside this one document. When a contract says "Confidential Information" with capitals, it is not asking you to apply your general sense of what confidential means. It is pointing you to a specific definition, written by one of the parties, that says exactly what counts and, just as importantly, what is excluded. The same word in lowercase would fall back to ordinary usage and general law. The capital letters are a signal: stop, this word has been engineered, go find out what it actually says.

This matters because contracts are read clause by clause but drafted term by term. A single defined term like "Affiliate" or "Losses" might appear eight or ten times, in the indemnity clause, the liability cap, the confidentiality clause, the assignment clause. Change that one definition and you have quietly changed the scope of every clause using it, without touching a single operative sentence. This is a legitimate drafting technique, it keeps documents shorter and more consistent, but it is also a common place for a party to expand its own protection or narrow the other side's, using a definition nobody reads carefully.

Who it protects and what triggers it

Definitions clauses do not "protect" a party the way an indemnity or a warranty does. Their effect is indirect: whichever side controls how a term is defined effectively controls how far every clause using that term reaches. The party drafting the first version, usually the vendor in a SaaS agreement, the employer in an employment contract, the landlord in a lease, gets first pick of every definition. That is a structural advantage, not a red flag by itself, but it means the reading party should check definitions with the same suspicion they'd apply to a one-sided indemnity or an aggressive liability cap.

The trigger is not a single event, it is every place the defined term is used downstream. "Confidential Information" gets triggered every time either party shares something covered by it. "Affiliate" gets triggered wherever the contract binds, exempts, or grants rights to affiliated companies, in a non-compete, a licence grant, an assignment restriction. "Business Day" gets triggered every time a notice period, payment deadline, or cure period is calculated. A definition that looks harmless in isolation can decide whether you met a deadline or breached a restriction, because the clock or the boundary is set by the definition, not by common sense.

What to look for

Four things decide whether a definitions clause is doing its job honestly or quietly reshaping the contract:

1. Scope creep in the definition itself. Does "Confidential Information" include everything disclosed, marked or not, forever, with no carve-outs for information already public or independently developed? Does "Affiliate" reach any entity under common control, however distant, rather than direct subsidiaries and the immediate parent?
2. Circular or self-referencing definitions. A term defined partly by reference to itself, or to another term that is itself undefined, creates a loop a reader cannot resolve. This is more common in fast-edited contracts than people expect, especially after several rounds of redlines.
3. "Including, without limitation" inside a definition. This phrase signals a list is illustrative, not exhaustive. Used honestly it is harmless. Used inside a definition of "Losses" or "Services," it quietly turns a closed list into an open one, covering things nobody negotiated.
4. Terms used but never defined. Search the document for every capitalised word. If one appears in an operative clause with no matching entry in the definitions section and no inline definition, that is not a stylistic slip, it is a gap that can make the obligation uncertain.

A simple, runnable test: for every capitalised term, press Ctrl+F, jump to its definition, and read it before reading the clause that uses it. A liability cap that looks generous can be gutted by how "Losses" is defined three pages earlier, and you would never know from reading the clause alone.

The Indian position: Section 29, Contract Act

Indian contract law does not have a section titled "definitions clauses." What it has is a general rule about certainty, and it applies with full force to a defined term that is missing, circular, or genuinely ambiguous. Section 29 of the Indian Contract Act, 1872 says:

"Agreements, the meaning of which is not certain, or capable of being made certain, are void." Source: Section 29, Indian Contract Act, 1872

The section's illustrations are directly relevant to how defined terms function. One: "A agrees to sell to B 'a hundred tons of oil.' There is nothing whatever to show what kind of oil was intended. The agreement is void for uncertainty." The next: "A agrees to sell B one hundred tons of oil of a specified description, known as an article of commerce. There is no uncertainty here to make the agreement void." That difference is, in effect, the difference between an undefined term and a defined one. A specified description resolves the uncertainty; a bare, undefined word does not.

Section 29 does not void every contract with a sloppy definitions section. It bites only when the meaning is genuinely uncertain and not "capable of being made certain" by context, trade usage, or the rest of the document. But it is the legal backstop that explains why an undefined capitalised term in an operative clause is a real risk, not an editing oversight. If a court cannot work out what "Confidential Information" or "the Services" meant with reasonable clarity, the obligation depending on it can fail, not because a party breached it, but because there was nothing certain enough to breach.

A named Indian case: Kovuru Kalappa Devara

In Kovuru Kalappa Devara v Kumar Krishna Mitter (Madras High Court, AIR 1945 Mad 10), a written agreement recorded that a sum of Rs. 12,600 was payable after two years, with interest, "after deductions as would be agreed upon." One side read this as meaning the full amount was payable unless a reduction was separately negotiated. The other side read it as meaning Rs. 12,600 was a ceiling, with some reduction contemplated by both parties from the start, the exact amount left open.

The Madras High Court held that this phrase left the obligation genuinely uncertain, both readings were plausible on the words used, and the court had no basis to prefer one over the other from the document itself. Applying Section 29, it treated the relevant term as void for uncertainty. See the full judgment on Indian Kanoon.

The case did not involve a capitalised term with a missing dictionary entry, but the underlying problem is identical. A phrase that sounds specific ("after deductions as would be agreed upon," or, in a modern contract, "Confidential Information" left undefined, or an "Affiliate" carve-out that cross-references a term that does not exist) can defeat a court's ability to enforce the obligation built on it, however carefully the rest of the clause reads. Precision in the definitions section is what makes the operative promise enforceable at all.

Red flags

Normal	Red flag	Why it matters
Every capitalised term used in the body has a matching entry in the definitions section, or is defined inline where first used	A capitalised term is used in an operative clause but never defined anywhere in the document	The obligation built on it may be uncertain under Section 29, and at minimum invites a dispute over what was meant
"Affiliate" defined as entities directly controlling, controlled by, or under common control with a party, often with a stated ownership threshold (for example, more than 50 percent)	"Affiliate" defined broadly enough to reach any entity "associated with" a party, with no ownership threshold stated	A broad Affiliate definition can bind or benefit group companies that never negotiated the contract and may not even know it exists
"Confidential Information" carved out for information already public, independently developed, or lawfully received from a third party	"Confidential Information" defined with no standard carve-outs at all	Turns an ordinary confidentiality clause into a promise you can accidentally breach just by using your own prior knowledge
"Including, without limitation" used sparingly, in places where an illustrative, non-exhaustive list is genuinely intended	"Including, without limitation" used inside the definition of "Losses," "Services," or another term that drives liability or scope	Quietly turns a closed, specific definition into an open-ended one that can be stretched well past what either side thought they agreed
"Business Day" defined with a specific place and calendar (for example, a day banks are open in Mumbai, excluding public holidays under a named Act)	"Business Day" left undefined, or defined without naming a place, in a contract between parties in different cities or countries	Deadlines and cure periods calculated off an undefined "Business Day" can be disputed, since bank holidays differ by state and country
Definitions and the operative clause that uses the term say the same thing when read together	A defined term's meaning contradicts how it is actually used in the operative clause	Signals the document was edited in pieces without a final consistency check, and a court will have to guess which version controls

Bad clause → better clause

Bad: "'Confidential Information' means any information disclosed by either party. 'Losses' includes, without limitation, any damages, costs, expenses, and other amounts. The Receiving Party shall not disclose Confidential Information to any Affiliate without the Disclosing Party's consent."

What is wrong: "Confidential Information" has no carve-outs, so even public or independently known information is technically covered. "Losses" is left open-ended by "including, without limitation," with no closed list at all. "Affiliate" is used in the operative sentence but never defined anywhere in the document.

Better: "'Confidential Information' means non-public information disclosed by a party (the Disclosing Party) to the other (the Receiving Party) in connection with this Agreement, whether marked confidential or not, but excluding information that (a) is or becomes public through no fault of the Receiving Party, (b) was already known to the Receiving Party without a duty of confidentiality, or (c) is independently developed without reference to the Confidential Information. 'Affiliate' means, in relation to a party, any entity that directly or indirectly controls, is controlled by, or is under common control with that party, where 'control' means ownership of more than 50 percent of the voting equity. 'Losses' means direct damages, court-awarded costs, and amounts paid in a settlement approved under Clause [X], and does not include indirect, consequential, or punitive damages except as stated in Clause [Y]. The Receiving Party shall not disclose Confidential Information to any Affiliate without the Disclosing Party's prior written consent, except where the Affiliate is bound by confidentiality obligations at least as protective as this Clause."

What changed and why: "Confidential Information" now has standard carve-outs, so ordinary business knowledge isn't swept in. "Affiliate" has a stated ownership threshold instead of an open phrase. "Losses" is a closed list instead of an "including, without limitation" list. Every capitalised term used now has a matching, precise definition.

How it interacts with related clauses

Defined terms are load-bearing for almost every other clause, but three relationships matter most:

• Indemnity and limitation of liability. How "Losses" or "Damages" is defined decides what an indemnity pays for and what a liability cap actually limits. A generous-looking cap paired with a broad, open "Losses" definition can still leave you exposed far beyond what the headline number suggests.
• Confidentiality. The "Confidential Information" definition is the entire scope of the confidentiality obligation. Strong remedies attached to a weak, uncarved-out definition protect almost nothing that matters and over-restrict things that shouldn't be restricted at all.
• Assignment and change of control. "Affiliate" definitions decide who a contract can be assigned to without consent, and who counts as part of "the Company" for a change-of-control trigger.

You can mark up definitions and trace where a term is used across a document for free in Weave, which highlights capitalised terms and lets you jump straight to their definitions before you read the clause around them.

US and global contrast

US contract drafting relies on definitions clauses just as heavily, capitalised terms, listed together, read alongside the clause using them, and the discipline is nearly identical across common-law jurisdictions. The bigger difference is doctrinal, not stylistic. American courts applying the "plain meaning rule" will often enforce an unambiguous defined term strictly as written, even where the result seems harsh, and treat genuine ambiguity as a question for extrinsic evidence. Indian courts under Section 29 ask a narrower, earlier question: is the meaning certain, or capable of being made certain, at all? If not, the relevant part of the agreement is void, not merely open to interpretation, which makes precise, non-circular definitions arguably more important here.

FAQ

Does every capitalised word in a contract have a special legal meaning? Not always. Proper nouns and the first word of a sentence are capitalised for ordinary grammar reasons. But any other capitalised word that repeats through the document is almost always a defined term. Check the definitions section to be sure.

What happens if a capitalised term is used but never defined? The contract does not automatically fail. Courts first try to give the term a reasonable meaning from context or trade usage. If they genuinely cannot, the relevant clause risks being treated as void for uncertainty under Section 29 of the Contract Act. Either way, it is a gap worth fixing before signing.

Why do contracts define words like "Business Day" that seem obvious? Because "obvious" varies by place. A Business Day in Mumbai is not the same as one in New York, and holidays differ by Indian state. Left undefined, a deadline or cure period built on "Business Days" forces both sides to guess which calendar applies.

Is "including, without limitation" always a problem in a definition? No, it is normal when a list is genuinely meant to be illustrative. It becomes a problem specifically inside definitions that drive liability or cost, like "Losses" or "Expenses," where an open-ended list can be stretched past what either side intended.

Should I read the definitions section before or after the main clauses? Before, or at minimum alongside. Reading operative clauses first means forming an opinion on a clause's meaning before knowing what its key terms actually cover, and re-reading it once you see the definition.

Can one party change a definition later without changing the clause that uses it? Only through a formal amendment, but this is exactly why a defined term deserves the same scrutiny as the clause itself during negotiation. A single-word change to how "Affiliate" or "Losses" is defined can shift the practical effect of several clauses at once, without touching those clauses directly.

This guide gets you to understanding what capitalised, defined terms do in an Indian contract and how to check them before you sign. It does not tell you whether a specific definition in your contract is drafted narrowly or broadly enough for your situation, that depends on the rest of the document and the deal behind it, and is not legal advice. Talk to a lawyer before you rely on, or push back on, a defined term in a live negotiation.