How a Plaint Is Attacked

You have spent several lectures learning how to build a plaint. Now forget, for the next hour, that you are the plaintiff’s lawyer. Become the defendant’s. Put the plaint on the table in front of you, and ask exactly one question: how can I stop this case before it becomes dangerous to my client?

That question, asked honestly, is the beginning of litigation maturity. A young lawyer reads his own plaint and asks whether it’s good. An experienced one reads it and asks where it can be broken — and the first thing worth understanding, before any specific attack, is that the other side is not obliged to fight your whole case at all.

You may have spent three weeks preparing evidence about ownership. Twenty documents. Six witnesses. A genuinely compelling story. And the defendant may simply say: I don’t want to discuss ownership yet — does this plaint even disclose a cause of action? Or: this court has no jurisdiction. Or: the suit is barred by limitation. Or: the plaintiff has undervalued the relief. Or: a necessary party has been left out entirely. And suddenly your twenty witnesses are sitting outside the courtroom, because the attack has landed at the threshold, before the merits were ever reached. Order VII Rules 10 and 11 of the Code of Civil Procedure exist precisely for this stage — Rule 10 concerns the return of a plaint, Rule 11 its rejection, and the Code sets out specific grounds on which a plaint is to be rejected, including a failure to disclose a cause of action, and a suit which appears from the statements in the plaint itself to be barred by law.

The first attack is the cleanest: there is no cause of action. Not “can the plaintiff prove it” — that question comes much later. The threshold question is narrower: has the plaintiff pleaded a legally sufficient factual basis for bringing this suit at all? This takes you straight back to the lecture on the cause-of-action paragraph, and it is exactly why that paragraph mattered as much as it did — a weak cause-of-action pleading isn’t merely ugly drafting. It can become a genuine threshold vulnerability that ends a case before it properly starts.

Try this on the plaint you’ve been working with throughout this course. Cover the prayer with your hand. Read only the facts, and ask: if every factual allegation here were assumed true, what legal relief would actually follow from it? Then uncover the prayer and check whether the answer matches. If the plaintiff asks for a declaration, where are the facts supporting the right to be declared? If he asks for possession, where are the facts establishing entitlement to it? If he asks for cancellation, where is the instrument, and what is actually wrong with it? If he asks for an injunction, where is the threatened or actual interference, pleaded as fact rather than assumed? Wherever you can’t answer, you’ve found a weakness — not a moral failing in the drafting, simply a place the document doesn’t yet hold up.

The second attack is more unpleasant to sit through: this is the wrong court. “Why is this case filed here?” Look at the jurisdiction paragraph. It says the court has jurisdiction — fine, but why? Where is the property, where did the cause of action actually arise, where does the defendant reside or carry on business where that’s relevant, what is the pecuniary value, and is there a special statute governing this particular dispute at all? The Code sets out, in Sections 15 to 20, the distinct bases on which a suit’s place of institution is decided, and Section 21 governs objections to jurisdiction specifically. Which means “this court has jurisdiction” is never itself an explanation. It’s a conclusion, and the facts that actually establish it have to already be sitting in the plaint — Order VII Rule 1 expressly requires the facts showing that the court has jurisdiction, not merely the assertion that it does.

Sometimes the problem isn’t that the claim is legally impossible — it’s that the plaint has simply been presented to a court that was never going to be able to try it. That’s where Order VII Rule 10 comes in rather than Rule 11, and the distinction between them is worth memorising precisely because it’s so easy to blur under pressure. A return sends the plaint back so it can be presented before the proper court — the case survives, it’s simply in the wrong hands. A rejection, by contrast, happens on one of the specific grounds set out in Rule 11, and it’s a different, harsher event. Don’t assume a jurisdiction problem and a substantive defect are automatically the same procedural moment; the Code provides for return where a plaint ought to have been instituted elsewhere, with an endorsement of presentation and return, together with the reasons for it.

Then comes an attack built entirely out of dates: this suit is barred by limitation. This is exactly why you’ve been asked, repeatedly, to draw timelines. Suppose your plaint says the defendant refused performance on the first of January 2019, and you filed the suit in 2026. The defendant doesn’t have to argue about the beauty of your facts at all — he simply says the suit is barred by limitation, and Order VII Rule 11 includes rejection precisely where the suit appears, from the plaint’s own statements, to be barred by law. Which means the lawyer who writes “the defendant first refused on the first of January 2019” may, without realising it, have pleaded the very fact that creates his own threshold problem. Cause of action and limitation have to be researched before drafting begins, never discovered afterward as an unwelcome surprise.

Don’t let the merits distract you from the threshold question, and don’t let a junior’s favourite excuse pass unchallenged either — “but sir, we have a very good case on merits” is not an answer to a jurisdiction or limitation objection, because the defendant may be entirely right on the threshold question even while the plaintiff tells a genuinely compelling story. Merits, maintainability, jurisdiction, limitation and procedure are five different questions, and a good lawyer always knows precisely which one the court is actually deciding on a given day.

Valuation supplies its own attack. “The plaintiff has deliberately undervalued the suit,” the defendant says, and you answer, reasonably, “no, we haven’t” — which only means you now have to show your working. What relief is actually being sought? What statute governs valuation for that relief? What valuation rule applies, and what does it do to the court fee and to pecuniary jurisdiction? These questions are connected, but valuation and court fee are never quite the same concept, and a suit can be valued one way for one purpose while court fee is calculated according to the relief and the applicable state law in a way that produces a different number entirely. That is exactly why copying a valuation figure out of another plaint is one of the more dangerous habits a junior can develop — the defendant’s version of this attack, “even if the suit is maintainable, the proper court fee has not been paid,” is simply the same trap sprung from the other direction. Keep the two questions — what is the valuation, and what is the court fee — permanently separate in your own checklist, and never let them collapse into one figure by accident.

Read the cause title, and forget the facts for a moment — look only at the people. Who owns the property? Who executed the deed? Who is actually in possession? Who claims an interest that hasn’t been named? The defendant says a necessary party is missing, and the right question isn’t whether that person is merely relevant — it’s whether the decree the plaintiff wants can effectively operate at all without that person bound by it. If it can’t, you have a real problem, one that Order I Rule 10 of the Code exists to repair later in the case, but a good lawyer is already thinking about parties before filing, not waiting for the objection to arrive. Take the plaint you’ve been using and build a simple map of the people in it — who they are, what their legal relationship to the dispute is, and why each one is actually in the suit at all — then ask which of them must be bound by the eventual decree, and which merely has a story about the dispute without a necessary role in the relief. The cause title will start looking considerably more important once you’ve done this once.

Then there’s an attack on the relief itself. The plaintiff wants a declaration; the defendant says he’s actually in possession, not the plaintiff. Is a bare declaration really going to solve anything here? This is exactly where the proviso to Section 34 of the Specific Relief Act returns — where further relief beyond a mere declaration is available and the plaintiff is able to claim it, he cannot simply omit it and expect the declaration alone to do the practical work. So the defendant’s attack may fall not on the facts at all, but on the architecture of the remedy itself, which is precisely why you were taught, earlier in this course, to draft the prayer before anything else.

There is a more sophisticated attack still, and it’s worth respecting: your own documents can hurt you. The plaintiff says he is the owner; the defendant produces the plaintiff’s own document, and it says something different. The plaintiff says he was always in possession; his own notice, sent years earlier, states plainly that the defendant has been occupying the property since a particular date. Your opponent doesn’t have to prove your case wrong from scratch when your own material will do it for him. This is exactly why the document-listing exercise from the lecture on verification and affidavits mattered — don’t only ask what documents support you. Ask, honestly, what your own documents say that could hurt you, because that is genuinely how litigation thinks.

Put all of this together and try the exercise properly. Take a real plaint — thirty minutes, no more — and, pretending to be the defendant, write five genuine objections, not five complaints. For each one, note the paragraph it attacks, the legal basis for the attack, and what the plaintiff’s honest answer would actually be, and whether that answer is already pleaded in the document as it stands. Do this for limitation, for jurisdiction, for cause of action, for valuation and court fee, for parties, and then, separately, for the prayer itself. That is a serious drafting exercise, and it teaches something reading commentary never quite manages to: a plaint can be read in two directions at once. Forward, the familiar way — facts, then right, then invasion, then relief. And backward, the way an opponent reads it — relief, then the legal provision behind it, then the facts that are supposed to support it, then the documents behind those facts, then the vulnerability sitting quietly underneath all of it. That double reading is what turns a plaint from a piece of prose into a genuine litigation instrument.

One caution before you go looking for objections everywhere: don’t turn every possible defence into an Order VII Rule 11 argument reflexively. A threshold objection has its own real limits — the court’s inquiry under Rule 11 is directed at the plaint and the material properly before it at that stage, not at a disputed factual trial conducted in miniature. If your objection genuinely requires extensive evidence to establish a contested fact, it may simply not belong at the threshold at all. Know the weapon before you fire it, and where the line sits — that is exactly why this is a question to research against the actual current provision and the relevant case law at the moment it arises in a real file, rather than something to apply mechanically from memory.

Imagine your senior drops a plaint on your desk and says only, “attack it.” Don’t start writing objections immediately. Build a sheet first — relief, cause of action, limitation, jurisdiction, valuation, court fee, parties, documents, prayer — and fill it in as you read, because you are no longer reading the plaint as literature. You are reading it as an adversarial machine, looking specifically for the place it stops working.

Your assignment before the next lecture: take one real plaint, ideally not your own, and prepare a short document titled, honestly, as if you represented the defendant. Write five preliminary objections. One possible Order VII Rule 10 point, and one possible Rule 11 point. One limitation objection, one jurisdiction objection, one on valuation or court fee, one on parties, and one on the prayer itself. Add one contradiction between the plaint and its own documents, and one fact you’d want to press the plaintiff on later, in cross-examination. Then switch sides again, and for every objection you’ve just written, draft the plaintiff’s honest answer to it. If you can answer your own objections convincingly, the plaint is genuinely strong. If you can’t — don’t file it yet.

Everything up to here has taken you from the moment a client first walks through the door to the moment a plaint has been drafted, checked, and now attacked from every angle you can find. From here, the file leaves the chamber, and this is where many young lawyers discover an uncomfortable truth: knowing how to draft a plaint is not the same skill as knowing how to actually file a suit. The counter has its own language — forms, the vakalatnama, process fee, summons sets, requisites, signatures, copies, caveat searches, and the one missing paper that sends a carefully prepared case straight back into your bag. That is where we go next.

Continue the series

PreviousS1 L16 — Nine Suits, One Skeleton

NextS1 L18 — Filing Day

All thirty lecturesThe First Brief — full contents

Chanda AssociatesHome · Law Updates · About Us · Advocates · Contact