How to Read and Understand a Contract: A Free Three-Pass Method

Most people read a contract the way they read a letter: start at the top, go straight through once, sign at the bottom. That works for a letter. It does not work for a contract, because a contract does three jobs at once: it tells you what you must do, what happens if something goes wrong, and it quietly redefines ordinary words the moment it capitalises them. Reading all three in a single pass is exactly how the clause that mattered gets missed. (Adira, which publishes this guide, makes contract review and CLM software; the method below works whether or not you ever open a tool at all.)

This is a free, three-pass method for reading any contract, an offer letter, a vendor agreement, an NDA, a lease, before you sign it. For a normal 8 to 15 page commercial contract it takes 20 to 40 minutes. It will get you to genuine understanding of what you are signing. It will not tell you whether a specific clause would hold up if contested; that is a judgment call for a lawyer, and this guide says exactly where that line sits.

Why one read, top to bottom, is not enough

Contracts are drafted in signing order, not risk order. Indemnity, liability caps, and termination sit buried in the middle, in denser language than the commercial terms around them. Boilerplate, governing law, jurisdiction, notices, sits at the very end, right where most readers are skimming toward the signature block. The clauses that decide what happens in a dispute are the ones read last and worst.

The three-pass method fixes this by splitting one linear read into three reads, each with its own job:

• Pass 1 answers: what is this deal, in outline?
• Pass 2 answers: what is the worst that can happen to me, and under which clause?
• Pass 3 answers: do the words mean what I assumed they mean?

Doing these in order, rather than trying to absorb everything in one linear read, is the entire method. Nothing below requires legal training. It requires reading the same document three times with three different questions in mind.

Pass 1: the skeleton, and why you read boilerplate first, not last

The first pass is not about risk. It is about outline: who is bound, what each side must actually do, how much money moves and when, how long the deal runs, and how it ends. Five things, in this order:

1. Parties. The legal entity name and address in the opening paragraph, not the brand name on the letterhead. "XYZ Technologies Private Limited" is not the same counterparty as "XYZ Technologies LLP," even with an identical logo.
2. What each side must do. One sentence per party. If you cannot write it in one sentence, the scope is not clear yet, and that ambiguity is itself a risk.
3. Money. Amount, currency, due dates, and what triggers payment (delivery, milestone, invoice date), plus whether GST or withholding tax is priced in or added on top.
4. Term. A fixed end date, an auto-renewing term, or open-ended, and if it renews automatically, how much notice stops it, and by when.
5. How it ends. Notice period for ordinary termination, and whether either side can end it immediately for cause.

Here is the counter-intuitive part: read the boilerplate block before the commercial terms, not after. Most people do the opposite, because "boilerplate" sounds like filler. It is not. Governing law, jurisdiction, and notices decide where and how any dispute over the skeleton above actually gets fought, and knowing that before you evaluate the deal changes how hard you should push on price. If jurisdiction sits in a city you have never operated in, the cost of a future dispute is already higher than the contract's face value suggests. The full mechanics of each boilerplate clause are on What Is Boilerplate in a Contract.

The Indian legal reason Pass 1 has to come from the document itself

Pass 1 only works if you accept one fact about Indian contract law: once a contract is in writing, the written words are, with narrow exceptions, the whole deal. What the salesperson promised verbally, or what an earlier email said, does not override the signed document.

Section 95 of the Bharatiya Sakshya Adhiniyam, 2023 (the evidence law that replaced the Indian Evidence Act, 1872, and carries forward its Section 92 in substance) states it directly:

"When the terms of any such contract, grant or other disposition of property, or any matter required by law to be reduced to the form of a document, have been proved according to section 94, 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 95, Bharatiya Sakshya Adhiniyam, 2023

In plain terms: if it is not in the document, and none of the section's narrow provisos apply (fraud, a genuine condition precedent, a distinct later agreement to change it), it generally will not be read into the document later. That is why Pass 1 has to be built entirely from what is written, not from what you were told on a call, and why the entire agreement clause inside the boilerplate matters: it is the clause that expressly says this rule applies to your deal.

Pass 2: the risk clauses, read in relation to each other

The second pass is where you go looking for the clauses that decide what happens when something goes wrong, not when everything goes right. Five clauses do most of the work in a typical commercial contract:

• Indemnity: who pays for a third-party claim or loss the other side causes, capped or uncapped.
• Limitation of liability: the ceiling on total payout, and which loss categories are excluded entirely.
• Termination: the notice period for ordinary termination, and what lets either side end it immediately, for cause.
• IP ownership: whether work product is assigned outright or only licensed, and what either side owned before the contract started.
• Confidentiality: what counts as confidential, how long it survives after the contract ends, and what is carved out.

Read these five together, because that is how they are meant to work. Indemnity decides who pays; limitation of liability decides how much they can be made to pay in total, often including indemnity claims. A generous-looking indemnity paired with a low liability cap is worth far less than it appears at first read. Termination decides how fast you can exit; confidentiality and IP decide what obligations and ownership questions survive after you do.

This reflects a settled principle of how Indian courts read contracts, not just good drafting practice. In Provash Chandra Dalui & Anr v Biswanath Banerjee & Anr, Supreme Court of India, 1989 Supp (1) SCC 487, the Court held that a contract must be construed "with reference to its object and the whole of its terms," so that "the words of each clause should be so interpreted as to bring them into harmony with other provisions," applying plain, ordinary meaning where the words are clear rather than searching for a hidden reading. Source: Provash Chandra Dalui v Biswanath Banerjee, Indian Kanoon. That is the discipline Pass 2 asks of you: read indemnity, liability, and termination against each other, in plain meaning, not in isolation.

Pass 3: definitions and cross-references, Ctrl+F every capitalised word

The third pass is mechanical, and it is the one people skip entirely. Every contract has a definitions clause, usually near the start or in a schedule, giving specific meanings to specific capitalised terms: "Confidential Information," "Effective Date," "Deliverables," "Cause," "Force Majeure Event." The moment a word is capitalised mid-sentence, it has probably stopped meaning what it means in ordinary English and started meaning exactly what the definitions clause says, sometimes narrower, sometimes much wider than the everyday word.

The test is literal: open the document, hit Ctrl+F, search for a capital letter mid-sentence, and for each hit, go back to the definitions clause and read the actual definition. Two things commonly go wrong:

• A defined term is used in the body of the contract but was never actually added to the definitions clause, so its scope is genuinely unclear.
• A defined term looks like the ordinary English word but is narrower ("Confidential Information" excludes anything not marked in writing) or wider ("Cause" includes a change of control, not just breach) than a first read suggests.

A full walkthrough of how these definitions work, and where they most often trip people up, is on Capitalised Words in a Contract: What They Actually Mean. You can run this pass, and the two before it, for free by marking the document up clause by clause in Weave, Adira's free browser-based contract tool, flagging each defined term and risk clause as you go so nothing gets missed on a second read.

The one-sentence test that tells you if you actually understood it

Here is a test you can run on yourself after finishing all three passes, and it takes one sentence to run: write down the worst thing that can realistically happen to you under this contract, and name the exact clause that allows it.

Not "I could lose money," but "if the vendor misses the deadline in clause 4.2 and I terminate for cause under clause 9.1, indemnity in clause 6 caps their liability at the fees paid under clause 3, so my loss beyond that is uncapped." If you can write that sentence, with a real clause number in it, you understand the contract well enough to negotiate or sign it with open eyes. If the honest answer is "I'm not sure," or the sentence has no clause number in it, you have not finished reading, however many pages you got through. Go back to Pass 2.

This test also tells you when to stop reading and start asking questions. A contract where the honest answer is genuinely alarming, an uncapped indemnity on a small vendor, termination for convenience with no notice period, is no longer a reading problem. It is a negotiation problem, and possibly a reason to bring in a lawyer before signing, not after.

Red flags while you are reading

Normal	Red flag	Why it matters
Definitions clause covers every capitalised term used in the body	A capitalised term appears but is never defined anywhere	The term's actual scope is unclear until a dispute forces an interpretation
Boilerplate reviewed before or alongside commercial terms	Boilerplate skimmed last, "it's standard"	Governing law, jurisdiction, and notices decide how a dispute plays out, and only bite after signing
Termination clause states a specific notice period in days	Notice period vague ("reasonable notice") or absent for convenience	You cannot calculate your actual exit timeline
Liability cap stated as a number or a multiple of fees	No liability cap at all, on either side	Exposure is technically unlimited, however unlikely that feels at signing
Confidentiality survival period stated (commonly 2 to 5 years, indefinite for trade secrets)	Silent on how long confidentiality lasts after the contract ends	The obligation may be read as ending with the contract itself, right when it matters most
Entire agreement clause names which documents form the whole deal	A verbal promise or earlier email relied on but not referenced anywhere in the document	Under Section 95 of the Bharatiya Sakshya Adhiniyam, that promise generally cannot be proved later to vary the written terms
One-sentence test produces a clear answer with a clause number	You cannot answer it after finishing all three passes	You have not actually understood the document yet

A read, done badly and done well

Take a real termination clause: "This Agreement may be terminated by either party upon written notice to the other party."

Read done badly: "Standard termination clause, either side can end it with notice, looks fine." This is the note most people actually write, and it answers none of Pass 1's questions.

Read done well: "No notice period stated, so termination is likely effective on receipt. No distinction between convenience and cause, so either side can walk away for any reason, with no cure period. Check the notices clause for whether email counts as valid notice."

What changed: the second version turns one generic sentence into checkable facts, whether there is a notice period, whether cause is required, how notice must be delivered, each tied to a clause you can go back and verify. That is what every clause you read should produce, not just termination.

What this method does not do

Understanding a contract and judging whether a clause is enforceable are two different skills, and this method builds only the first. The three passes tell you, accurately, what a contract says and what it is trying to do. They will not tell you whether an unusually broad indemnity clause would survive a court challenge, or how a judge would resolve a genuine conflict between two clauses. For a low-stakes contract, understanding is usually enough to sign confidently. For a high-stakes one, a funding round, a long supply agreement, an employment contract with a non-compete, understanding is the first step; a lawyer's judgment on enforceability is the second one you should not skip.

US and global contrast

The underlying discipline, read the whole document, do not rely on what was said outside it, is not unique to India. US contract law applies a broadly similar parol evidence rule, and English-drafted contracts use an "entire agreement" clause for the same purpose. The approaches diverge in how forgiving courts are of a badly worded clause afterward. English and American courts more often "read down" an overreaching clause into a narrower, enforceable version. Indian courts, particularly for a restraint that falls foul of Section 27 of the Indian Contract Act, generally either enforce a clause as written or strike it out, with far less room for a court to rewrite an overbroad clause in your favour later. The words on the page are closer to exactly what you get.

FAQ

How long should reading a contract properly actually take? For a normal 8 to 15 page commercial contract, 20 to 40 minutes across all three passes, once you know the method. A long, heavily annexed master services agreement can reasonably take longer.

Do I need to read every annexure and schedule, or just the main body? Yes. Payment schedules, service levels, and data processing addenda are usually incorporated by reference and are just as binding as the main body, often more specific to your actual risk.

What if a contract has no definitions clause at all? Short contracts sometimes skip formal definitions, so ordinary English applies. But if terms like "Confidential Information" recur with no definitions clause anywhere, that is itself a red flag worth raising before signing.

Is it enough to skim for the indemnity and liability clauses and skip the rest? No. Those matter most for financial risk, but termination, confidentiality survival, and boilerplate decide how you exit and what obligations outlive the relationship.

Can I trust a contract just because the other side is a large, reputable company? No. A reputable counterparty is more likely to use a well-drafted template, but well-drafted usually means well-drafted in their favour, not yours.

---

This guide teaches you how to read and understand a contract; it does not tell you whether a specific clause in your specific contract would hold up if contested, or whether the risk allocation in it is one you should accept. That depends on the exact wording, your specific situation, and often the negotiating leverage you have. For a high-stakes contract, use this method first, then take what you find to a contracts lawyer before you sign.