Boilerplate Clauses Explained: The 'Standard' Terms That Quietly Decide Disputes

Boilerplate is the block of clauses at the end of most contracts: governing law, jurisdiction, notices, entire agreement, severability, waiver, assignment, force majeure, counterparts. People skim it because the word "boilerplate" suggests it is fixed and interchangeable, the same paragraph copied from the last contract. The one thing most people get wrong: it is not interchangeable. Boilerplate does not decide what you owe or what you get. It decides how a dispute is fought and where, and every clause in it has, at some point, decided a real Indian case in a way one side did not see coming. (Adira, which publishes this guide, makes contract review and CLM software; this explainer is written to be useful whether or not you ever use it.)

This page is a map, not a substitute for the individual explainers. Each boilerplate clause below links to a full page with its own statute, case, and red flags. What this page adds is what the individual pages cannot: what order to read boilerplate in, which combinations of clauses create risk, and why "it's just standard" is the single most expensive assumption in Indian contracting.

Plain meaning: why it is called "boilerplate" at all

The term comes from newspaper printing. Syndicated filler content, ready-made and unlikely to change, arrived on plates of steel resembling boiler plate, ready to drop into any newspaper's press. Lawyers borrowed the word for clauses that recur across contracts in near-identical form.

The metaphor is accurate about form and wrong about consequence. These clauses do repeat with minor variation. But "repeats often" is not the same as "does not matter." A jurisdiction clause that names the wrong city can cost you the ability to sue at all in the forum you expected. A notices clause silent on email can make a termination legally ineffective years into a relationship run entirely over email. Boilerplate is standard in its drafting pattern, not in its stakes.

Who it protects, and why it only bites when something else has already gone wrong

This is the structural reason boilerplate gets ignored. Every other clause (price, scope, delivery, IP ownership) matters the moment the deal is performed. Boilerplate matters only the moment the deal is contested: a termination, a breach, a dispute over which court should hear it. Until then it sits completely unused, which is exactly why it reads as filler during negotiation and turns out to be load-bearing during a fight.

Each clause protects a different interest once triggered: governing law and jurisdiction protect whoever wants predictability about which law and which court decides the dispute; notices protects both sides' certainty that a termination was validly sent and received; entire agreement protects the party that wants the signed document, not the sales pitch before it, to be the whole deal; severability protects the deal itself if one clause is later found void; force majeure protects whichever party's performance is exposed to physical or regulatory disruption; waiver and assignment protect against a party's own past leniency, or a change of counterparty, being read as more than it was.

None of this shows up until litigation, arbitration, or a serious breach letter is already on the table. By then it is too late to redraft.

What to look for: read boilerplate first, not last

Here is a test you can run on any contract in under two minutes: open to the last pages before signing, and read the boilerplate block before you read the commercial terms. Most people do the opposite, reading price and scope carefully and skimming boilerplate as fixed. Flip that order. If a governing law clause names a law you cannot afford to litigate under, or a jurisdiction clause names a city you have never operated in, that changes how hard you should push on price, because the cost of a dispute just went up before it started.

A useful reading order, and what each clause is actually deciding:

1. Governing law, whose substantive law interprets the contract. Governing Law Clauses.
2. Jurisdiction, which court hears a dispute, and whether it is the only one that can. Jurisdiction Clauses.
3. Notices, how a termination or breach notice must be sent to count. Notices Clauses.
4. Entire agreement, whether anything promised before signing survives the signature. Entire Agreement Clauses.
5. Severability, what happens if one clause is later found void. Severability Clauses.
6. Force majeure, what excuses non-performance, and what does not. Force Majeure Clauses.
7. Waiver, whether letting a late payment slide once quietly waives the right to object later. Waiver Clauses.
8. Assignment, whether either side can hand the contract to someone else without consent. Assignment Clauses.
9. Counterparts and e-signature, whether the contract is validly formed when signed electronically, covered below.

You can mark up a boilerplate block for free in Weave, Adira's browser-based contract tool, and flag which of these nine you are missing, before it goes near a lawyer.

The Indian position: two statutes that govern the boilerplate block directly

Two provisions sit underneath this category: one limits what jurisdiction-style boilerplate can do, the other governs whether boilerplate signed electronically counts at all.

Section 28 of the Indian Contract Act, 1872 limits any clause that tries to shut a party out of court entirely:

"Every agreement, (a) by which any party thereto is restricted absolutely from enforcing his rights under or in respect of any contract, by the usual legal proceedings in the ordinary tribunals... is void to that extent." Source: Section 28, Indian Contract Act, 1872

This is why a jurisdiction clause can pick one competent court but cannot invent one with no connection to the dispute, and cannot bar a party from suing anywhere at all. Full mechanics, including the "exclusive vs non-exclusive" trap, are on the jurisdiction clause page.

Section 10A of the Information Technology Act, 2000 is the provision most boilerplate guides skip, and it governs whether the document, counterparts and e-signatures included, was validly formed at all:

"Where in a contract formation, the communication of proposals, the acceptance of proposals, the revocation of proposals and acceptances, as the case may be, are expressed in electronic form or by means of an electronic record, such contract shall not be deemed to be unenforceable solely on the ground that such electronic form or means was used for that purpose." Source: Section 10A, Information Technology Act, 2000

Section 10A is why most commercial contracts in India can be validly signed by email exchange, click-to-accept, or an e-signature platform, without wet ink. But it is not universal. Section 1(4) of the IT Act, read with the First Schedule, carves out documents the Act does not cover: negotiable instruments other than a cheque, a power of attorney, a trust deed, a will, and any contract for the sale or conveyance of immovable property. See Section 1, Information Technology Act, 2000. For those categories, an e-signature clause does not make the document valid; you still need the traditional form, often wet ink, and for immovable property, registration and stamp duty. A counterparts clause silent on this list is quietly promising something the law does not deliver.

A named Indian case: Swastik Gases and the cost of silent boilerplate

Swastik Gases Pvt Ltd v Indian Oil Corporation Ltd, Supreme Court of India, (2013) 9 SCC 32, is the clearest example of boilerplate deciding an outcome nobody argued about at signing. Swastik Gases, a Jaipur-based consignment agent, had a valid, independent claim to Rajasthan's courts since the sale and delivery happened there. But the contract's jurisdiction clause read only "the agreement shall be subject to the jurisdiction of the courts at Kolkata," no "exclusive," no "only," no "alone." The Supreme Court held that naming one competent court, even without exclusionary words, was enough to exclude the rest. Swastik Gases lost the right to litigate in the state where it actually operated, over a single unqualified sentence in the boilerplate. Full detail is on the jurisdiction clause page.

The pattern repeats across the category. Energy Watchdog v CERC (Supreme Court, 2017) turned on whether a force majeure clause, not the general law of frustration, governed a coal-price dispute; it did. Lease Plan India v Rudraksh Pharma Distributor (Delhi High Court, 2024) turned on whether an arbitration notice sent by email and WhatsApp counted, and it did, only because that email and number were the ones named in the notices clause. None of these were fought over price or scope. All were fought, and decided, on boilerplate.

Red flags table

Normal	Red flag	Why it matters
Boilerplate reviewed alongside commercial terms before signing	Skipped or skimmed as "standard, doesn't matter"	It only activates during a dispute, by which point it is too late to renegotiate
Governing law and jurisdiction name the same or a compatible legal system	One country's law, another country's courts	The chosen forum may have to apply a legal system it does not routinely practise in
Notices clause expressly permits email, to a named address	Silent on email, or lists only post and courier	An emailed termination, however routine, may be legally ineffective, so the clock never starts
Entire agreement clause names which document prevails, and preserves side agreements you rely on	Silently overrides an SOW, NDA, or DPA signed separately	A promised term or confidentiality undertaking can be wiped by the words actually signed
Severability clause simply authorises deletion of a void provision	Missing entirely, in a contract carrying a non-compete or penalty	Survival then depends entirely on a court's general test, with no evidence of intent
Force majeure clause has a genuine "beyond reasonable control" catch-all	Closed list with no catch-all, or used as a hedge against rising costs	An unlisted disruption, or ordinary commercial hardship, gets no protection
Counterparts clause carves out documents the IT Act excludes from e-signature	Applied blanket, to a POA, trust deed, or immovable property sale	The document may not be validly formed despite everyone believing it was e-signed
Waiver clause requires a written, signed waiver to count	Absent, while the parties routinely let deadlines slide	A pattern of leniency can itself be read as waiving the strict right

Bad clause, better clause: counterparts and e-signature

Bad: "This Agreement may be executed in counterparts, each of which shall be an original, and all of which together shall constitute one instrument. Signatures transmitted electronically shall be deemed valid."

What is wrong with it: "deemed valid" without limit is not true for every document type. If this boilerplate sits in a template also used for a power of attorney or a sale of immovable property, the clause promises validity the IT Act's First Schedule does not extend to those documents.

Better: "This Agreement may be executed in any number of counterparts, each an original, together constituting one instrument. Where permitted under Section 10A of the Information Technology Act, 2000, execution by electronic signature or exchange of electronic records shall be as valid as execution by physical signature. This clause does not apply to any document excluded from the Information Technology Act, 2000 by Section 1(4) and the First Schedule, including negotiable instruments other than a cheque, powers of attorney, trusts, wills, and contracts for the sale of immovable property, which shall be executed as otherwise required by law."

What changed: it ties e-signature validity to the actual statutory basis instead of an unqualified promise, and names the carve-out so the clause cannot be read as covering documents the law puts outside its reach.

How it interacts with related clauses

Boilerplate clauses are rarely read together, but they are drafted to work together, and mismatches between them are where most of the real risk sits:

• Governing law vs jurisdiction: naming Indian law but a foreign court, or vice versa, is legal but expensive; the chosen forum ends up applying a legal system it does not routinely practise in. See Governing Law Clauses and Jurisdiction Clauses.
• Notices vs termination and cure periods: a cure period only starts running once notice is validly given; get notices wrong and the clause it feeds never activates. See Notices Clauses.
• Entire agreement vs side documents: it can silently supersede an NDA or DPA signed outside the main document unless it expressly preserves them. See Entire Agreement Clauses.
• Severability vs the risky clause it backstops: it only helps if the risky obligation is genuinely separable from the rest of the bargain. See Severability Clauses.
• Force majeure vs payment obligations: a well-drafted clause carves out money already due, so disruption elsewhere is not an excuse to withhold payment for work delivered. See Force Majeure Clauses.

US and global contrast

US and English contracts carry the same category, often labelled "miscellaneous" or "general provisions" rather than "boilerplate," and the individual clauses look similar: governing law, forum selection, notices, integration (the US term for entire agreement), severability, counterparts. Two differences matter.

First, forum selection clauses are treated more permissively in the US. Under The Bremen v Zapata Off-Shore Co., 407 U.S. 1 (1972), US federal courts presume a freely negotiated forum-selection clause should be enforced, even one that ousts a court that would otherwise have had jurisdiction, unless enforcement would be unreasonable. Indian law, through Section 28, does not permit a clause to oust every court's jurisdiction absolutely; it can only choose among courts that already have a legitimate connection to the dispute.

Second, US and English courts more readily "read down" or "blue pencil" an overbroad clause, most visibly a non-compete, into a narrower, enforceable version, and enforce that. Indian courts generally do not have that option for a restraint void under Section 27; the blue pencil in Indian practice deletes, it does not rewrite. Boilerplate that echoes a US or English template can therefore do meaningfully less work in an Indian court than the drafter assumed.

FAQ

Is boilerplate the same as "miscellaneous clauses"? Yes, usually the same block, labelled differently. "Boilerplate" describes how the language was written, standardised and repeated across contracts. "Miscellaneous" describes where it sits, the catch-all section after commercial terms. Both names undersell how much it can decide.

Do I need a lawyer to review boilerplate, or can I do it myself? You can run the reading-order test and the red-flags table above yourself and catch most practical issues: missing email in notices, mismatched governing law and jurisdiction, an e-signature clause promising validity it cannot deliver. What a non-lawyer usually cannot judge is whether specific wording would actually hold up if contested.

Which boilerplate clause causes the most disputes in India? Based on the reported cases, jurisdiction and notices clauses generate the most disputes that turn purely on the wording, because both hinge on a single sentence, which court, which method of notice, that either was or was not followed to the letter.

Can one boilerplate clause override another? Yes, and this is a common drafting accident. An entire agreement clause can supersede a side letter meant to survive. A broadly worded severability clause can invite a court to rewrite a clause the drafter should have written correctly the first time. Read the block as a set, not as nine independent paragraphs.

Is it safe to reuse the same boilerplate across every contract template? Only the parts that do not depend on the parties or the deal, like the mechanics of deemed service of notice. Governing law, jurisdiction, and force majeure should be checked against where each counterparty actually operates; reusing a Kolkata jurisdiction clause on a Jaipur-based counterparty is exactly the fact pattern that lost in Swastik Gases.

What is the fastest way to check if my contract's boilerplate has a problem? Run the reading-order test: read governing law, jurisdiction, notices, entire agreement, and force majeure before anything else, and check each against the red-flags table above. That catches most of what matters in a few minutes, before signing rather than after a dispute.

---

This guide explains what the boilerplate block generally does under Indian law and where each clause has actually decided a case. It does not tell you whether the specific wording in your contract will hold up if contested, that depends on the exact drafting and the facts. For that, talk to a contracts lawyer before you sign or rely on a boilerplate clause you have not checked.