Recitals and 'Whereas' Clauses: Do They Actually Bind You?

Recitals are the "Whereas" paragraphs at the top of a contract, before the operative clauses (the numbered sections that start with words like "shall," "agrees to," or "will"). They set the scene: who the parties are, why they are entering the agreement, and what background facts made the deal happen. The one thing most people get wrong: they assume a recital is a promise, the same as an operative clause, just written in old-fashioned language. It usually is not. A recital does not, by itself, create an obligation you can sue on. But it is not throwaway text either. Indian courts use recitals to interpret an ambiguous operative clause, and a false or careless recital can trip you up through estoppel, a rule that stops you from later denying something you stated as fact. This guide (published by Adira, which makes contract review and CLM software, so we have a commercial interest in you understanding contracts well, but this explainer stands on its own) walks through what recitals actually do under Indian law, when they bind you anyway, and what to check before you sign.

Plain meaning

A recital is a statement of background, not a term of the deal. "WHEREAS the Vendor is engaged in the business of providing software development services" is a recital. "The Vendor shall deliver the Software by 30 June 2026" is an operative clause. The distinction matters because operative clauses are what a court enforces directly, you breach clause 4.2, you owe damages under clause 4.2. Recitals are not written that way and, as a rule, are not enforced that way.

But recitals do real work in two situations. First, when an operative clause is genuinely ambiguous, courts look at the recitals to figure out what the parties meant, because the recitals often explain the purpose of the deal in plainer language than the operative clauses do. Second, when a recital states a fact (not an intention, a fact) and the other side relied on that fact to their detriment, the party who stated it can be stopped from later denying it, even though the recital itself created no direct contractual obligation. So "not binding" is the right default assumption, but it has two real exceptions that catch people out.

Who it protects and what triggers it

Recitals do not protect one party over another the way, say, an indemnity clause does. Instead, they protect the integrity of the deal's stated purpose and the reliability of stated facts, through two different triggers.

Interpretation trigger. This fires only when an operative clause is ambiguous, courts will not dig through recitals to change a clear term. If clause 4.2 clearly says "30 June 2026" and a recital vaguely says the parties intend "prompt delivery," the recital does not override the clear date. Recitals become relevant only when the operative language could genuinely mean two things.

Estoppel trigger. This fires when a recital states a specific fact ("the Company holds all statutory licences required to operate the Facility," "the Seller is the sole and absolute owner of the Property"), the other party relies on that statement, and it later turns out false. The party who made the false statement can be estopped, stopped by law, from denying it in a dispute connected to that instrument, even outside the operative clauses.

What to look for

Four things decide whether your recitals are harmless scene-setting or a hidden risk:

1. Is an actual obligation buried in a recital? Watch for "WHEREAS the Vendor agrees to provide ongoing support at no additional cost" in the background paragraphs instead of a numbered obligation. Common shortcut, common enforceability trap.
2. Do the recitals contradict the operative clauses? A recital saying "non-exclusive basis" against clause 6 granting exclusivity is a live ambiguity a court may have to resolve, usually against whoever drafted the document (contra proferentem).
3. Are the "facts" in the recitals actually true, or just assumed? "The Parties have agreed the Purchase Price represents fair market value" is a factual assertion you may be stuck with later if you want to argue undervaluation.
4. Does an operative clause point back at a recital? Phrases like "as described in Recital B" pull a recital into the operative machinery, so it stops being background and becomes a term you must comply with.

The Indian position: how recitals interact with the Evidence Act

India does not have a standalone "law of recitals." Instead, two long-standing evidence rules decide how much weight a recital gets.

Under the Indian Evidence Act, 1872, once a contract has been reduced to a written document, Section 91 requires the document itself (not oral evidence) to prove its terms, and Section 92 then bars the parties from using oral evidence to contradict, vary, add to, or subtract from what the document says:

"When the terms of any such contract, grant or other disposition of property... have been proved according to the last section, no evidence of any oral agreement or statement shall be admitted, as between the parties to any such instrument or their representatives in interest, for the purpose of contradicting, varying, adding to or subtracting from, its terms." Source: Section 92, Indian Evidence Act, 1872

Section 92 comes with six built-in provisos, exceptions to the general bar on outside evidence. Proviso (6) is the one that matters most for recitals:

"Any fact may be proved which shows in what manner the language of a document is related to existing facts." Source: Section 92, Indian Evidence Act, 1872, Proviso 6

This is the statutory hook courts use to read recitals alongside operative clauses: recitals are part of "the document," and they show the existing facts and purpose the operative language was written against.

Note on the current statute: the Indian Evidence Act, 1872 was replaced by the Bharatiya Sakshya Adhiniyam, 2023, in force from 1 July 2024. The same rule now lives at Section 94 (equivalent to old Section 91) and Section 95 (equivalent to old Section 92, provisos included, same wording), so case law decided under the old sections remains good authority.

Separately, the general estoppel rule, old Section 115 of the Evidence Act (now Section 121 of the Bharatiya Sakshya Adhiniyam, same wording), does the work when a recital states a fact rather than merely explaining intent:

"When one person has, by his declaration, act or omission, intentionally caused or permitted another person to believe a thing to be true and to act upon such belief, neither he nor his representative shall be allowed, in any suit or proceeding between himself and such person or his representative, to deny the truth of that thing." Source: Section 115, Indian Evidence Act, 1872

Put the two rules together: recitals do not create obligations on their own (that is what operative clauses are for), but they are part of the document a court reads under Section 92/95 proviso (6) to resolve ambiguity, and a factual statement inside a recital can independently trigger Section 115/121 estoppel if someone relied on it.

A named Indian case: Ram Charan Das v Girjanandini Devi

In Ram Charan Das v Girjanandini Devi (Supreme Court of India, AIR 1966 SC 323, decided 20 April 1965), the Court had to construe a family settlement deed where a dispute arose over how a proviso in the document should be read against its recitals. Justice Mudholkar, writing for the Court, drew the classic distinction between narrative recitals (which set out the facts leading up to the deal) and introductory or motive recitals (which explain why the parties are entering the operative part), and cited the settled rule of construction:

"Where the recitals are clear and the operative part is ambiguous, the recitals govern the construction. If the recitals are ambiguous and the operative part is clear, the operative part must prevail."

Applying this, the Court held that what the appellant was actually challenging were binding terms of the settlement, not mere recitals, and so fell outside the appellant's reserved right to contest "recitals" in the deed. See the full judgment on Indian Kanoon.

Why this matters practically: the rule cuts both ways. A clear operative clause will not bend to a vague recital. But a genuinely unclear operative clause can be decided by a clear, well-drafted recital, which is exactly why sloppy recitals are a bigger risk in a badly drafted contract than a well-drafted one, they get their chance to matter precisely when you can least afford ambiguity.

Red flags

Normal	Red flag	Why it matters
Recitals state background and purpose only, obligations live in numbered operative clauses	An obligation ("Vendor shall provide," "Party agrees to pay") appears only inside a WHEREAS paragraph	May be unenforceable as a standalone promise; a court can read it as background, not a term, leaving you with nothing to sue on
Recitals and operative clauses tell the same story	A recital says one thing (e.g. "non-exclusive engagement") and an operative clause says another (e.g. grants exclusivity)	Creates a live ambiguity a court has to resolve, often against the drafter, and litigation over which one governs
Factual recitals are things you can actually verify (corporate status, authority to contract, licences held)	A factual recital states something you have not checked, or know to be doubtful ("the Company holds all licences required")	Can trigger estoppel under Section 115/121 if the other side relied on it, even if it turns out to be false
A clause like "The Recitals form part of this Agreement" or "The Recitals are for reference only" clearly states the parties' intent	Silence on whether recitals form part of the agreement	Leaves the fallback common-law position (relevant to interpretation, not independently binding) to be argued out case by case
Recitals are short, factual, and limited to what actually happened before signing	Recitals contain forward-looking promises, price terms, or a "final and best" characterisation of the deal	Blurs the line between background and obligation, exactly what Section 92/95 disputes get litigated over
An operative clause cross-references a recital deliberately and clearly ("as more particularly described in Recital B")	A recital is cross-referenced loosely or inconsistently across the document	Once cross-referenced, the recital effectively becomes operative, so any looseness in it now infects a real term

Bad clause → better clause

Bad (obligation hidden in a recital, no operative counterpart): "WHEREAS the Vendor shall provide the Client with priority technical support at no additional charge for the duration of this Agreement, and the parties wish to record their agreement as follows..."

What is wrong: the actual promise, free priority support for the whole term, is buried in a "Whereas" clause and never repeated in the operative sections. If the Vendor stops providing it, the Client is arguing over whether a recital creates an enforceable obligation at all, a fight it may lose.

Better: "WHEREAS the parties wish to record the background to this Agreement, including that the Vendor has been engaged to provide the Deliverables described in Schedule 1; ... Clause 8 (Support). The Vendor shall provide the Client with priority technical support, as described in Schedule 2, at no additional charge for the duration of this Agreement."

What changed and why: the recital now states only background (why the parties are contracting), and the actual promise moves into a numbered operative clause with its own heading, so it is unambiguously enforceable and easy to find.

How it interacts with related clauses

Recitals rarely cause problems on their own, they cause problems when three other clauses do not account for them:

• Entire agreement clause. A well-drafted entire agreement clause usually states that recitals and schedules form part of the agreement, or expressly excludes them. Silence just leaves the Ram Charan Das common-law default to fill the gap instead of you deciding it.
• Representations and warranties. If a recital states a fact ("the Seller is the sole owner of the Property") and your representations clause is meant to be the exhaustive list of factual promises, repeat the fact as an actual warranty, not left to stand alone where its only teeth are estoppel, not a breach claim with a defined remedy.
• Interpretation or definitions clause. If defined terms are first introduced in the recitals, your interpretation clause should say so explicitly, otherwise definitions are doing operative work from inside a section the contract elsewhere treats as non-binding.

You can flag exactly this kind of mismatch, an obligation sitting in a recital, or a recital that contradicts an operative clause, for free by marking up the document in Weave before you send a draft back for negotiation.

US and global contrast

US and English-law contracts use recitals the same way structurally (background, not obligation, admissible to resolve ambiguity), and the same warning against burying obligations in a "Whereas" clause is standard drafting advice in both systems. US courts applying the parol evidence rule and English courts reading a contract against its "factual matrix" both let recitals inform ambiguous language, broadly matching Section 92/95 proviso (6) in India. The difference is the hook: Indian courts point to a specific numbered proviso in a codified Evidence Act, while US and English courts derive the same result from common-law interpretation principles, with no single statutory proviso to cite.

FAQ

Are recitals legally binding on the parties? Generally, no. Recitals set out background and intent, not obligations. Obligations belong in the operative clauses. Recitals become relevant when an operative clause is ambiguous (courts then read the recitals to interpret it) or when a recital states a fact that the other party relied on (which can trigger estoppel).

Can I sue someone for breaching a promise that only appears in a recital? It is risky. A promise phrased as background rather than a numbered obligation may not be independently enforceable. Move anything you actually want to hold someone to into an operative clause.

What is "estoppel by recital" and when does it apply? If a recital states a specific fact and the other party relies on it to their detriment, Section 115 of the Indian Evidence Act, 1872 (now Section 121 of the Bharatiya Sakshya Adhiniyam, 2023) can stop the party who stated it from later denying it, even though the recital never created a contractual obligation.

Do recitals help interpret an ambiguous clause even without an estoppel claim? Yes. Under proviso (6) to Section 92 (now Section 95 of the Bharatiya Sakshya Adhiniyam), background facts, including recitals, show how ambiguous operative language relates to real-world facts. Ram Charan Das v Girjanandini Devi (AIR 1966 SC 323) confirms that where recitals are clear and the operative part is ambiguous, the recitals govern the construction.

Should my contract say whether recitals "form part of" the agreement? Yes, decide this deliberately. Most modern templates either state that recitals and schedules form part of the agreement, or expressly limit recitals to background only. Silence just means a court decides for you later.

What if a recital contradicts an operative clause? That is a genuine drafting defect, not a formality issue. Indian courts, like most common-law courts, will generally read the document against whoever drafted it (contra proferentem) if the conflict cannot otherwise be resolved. Fix contradictions before signing.

This guide explains what recitals generally do under Indian law and what to check in your own document. It does not tell you whether a specific recital in your contract is enforceable, creates estoppel, or will be read to resolve a particular ambiguity, that depends on the exact wording and the facts, and is not legal advice. Talk to a lawyer before you rely on, or dismiss, a recital in a live negotiation or dispute.