Argument and the Written Notes

The evidence is over. The witnesses have gone home. The documents sit on the record, the contradictions exposed or survived, the issues argued through proof one by one. You walk into court carrying a file that has grown fat enough to need its own chair beside you.

“Counsel?” the judge says.

You stand, and something uncomfortable becomes obvious in that instant. You are holding three years of material. The court has, realistically, twenty minutes. So what, precisely, are you going to do with them? You cannot tell the whole story again. You cannot read out the plaint, or the written statement, or narrate every document, or reproduce every cross-examination that mattered to you personally. You have to do something considerably harder than any of that: decide, honestly, what actually matters. That decision is argument.

At the very start of this case, storytelling genuinely helped. The client arrived with a confused account, and you built a timeline out of it, found the right, found the invasion of that right, chose the relief, drafted the plaint. The defendant answered. The court framed issues. The witnesses gave their evidence. But the court, at this final stage, doesn’t need the story told to it again — it needs an answer to the specific questions it has already framed. That is the whole transformation this lecture is about. At trial, you prove facts. In argument, you explain what those proved facts actually mean, and that difference is the entire skill.

Start, always, with the issues rather than the chronology. Suppose the court has framed five of them. Resist the pull to begin, “my Lord, the plaintiff is a respectable businessman who purchased the property in 2014” — stop yourself, and ask instead which issue you are actually answering right now. Write the five issues on a page, and under each one note your answer, the evidence that proves it, the strongest thing the other side has said against it, and why that answer ultimately fails. That page, not the file itself, is your real argument.

Go back to the man at the gate one more time, because his case will carry the rest of this lecture. The company had occupied the first and second floors under an Agreement for Lease dated the fourth of October 2023. It began construction without the required permissions and structural certificate. The Corporation issued its own notice about unauthorised construction. Your client terminated the agreement. The company left, then returned to the gate insisting the termination itself was invalid. The eventual suit sought a declaration that the termination was valid, and permanent injunctions restraining interference and any unauthorised entry or construction. Now imagine you are standing up, years later, to argue that case at its conclusion. The instinct is to tell the judge the entire history from the beginning. Don’t. The judge already has the file in front of him. Your job is not to repeat it — it is to organise it around the decision he actually has to make.

Say, simply: “there are three questions.” And stop there for a moment, because now the judge knows exactly where you’re taking him. “First, whether the agreement was validly terminated. Second, whether the defendant retains any continuing right to enter the premises. Third, whether the plaintiff is entitled to the injunctions sought.” Every minute that follows now has a destination, and that is considerably more powerful than opening with “if I may take you back to the year 2014” — you may well need to go back that far eventually, but only once the issue in front of you genuinely requires it, not as a habit.

Take everything you established at the evidence stage and push it one step further, because proving a fact and arguing its significance are not the same act. You learned to ask what a document proves. Argument asks one further question: so what? The Corporation’s notice is on the record — fine, but what does it actually establish? Not merely “there is a Corporation notice,” but something closer to: “the contemporaneous statutory notice supports the plaintiff’s case that the construction was treated by the municipal authority itself as unauthorised” — and then the step beyond that: “which matters because the defendant’s conduct was never merely a private disagreement about construction. It occurred despite an official direction to stop.” The document, at that point, has become an argument rather than simply an exhibit sitting on the record waiting to be mentioned.

Resist the temptation to read a document out loud when the judge almost certainly already has it in front of him. A junior says: “Exhibit P-7 is the letter dated the tenth of July 2024, issued by the Corporation, and it says...” and then reads the whole thing. Try instead: “the significance of Exhibit P-7 is narrow but important — it is contemporaneous, it predates the termination, and it records the Corporation’s own position on the construction, which corroborates the plaintiff’s account on this issue.” You have taken the court from document, to fact, to legal significance, in three sentences instead of a full recitation, and that compression is most of what separates an argument from a summary.

For every point that genuinely matters, try holding it to the same three-part shape: what happened — the defendant commenced structural work without the required certificate; what proves it — the defendant’s own correspondence, followed by the Corporation’s notice; and why it matters — it establishes the very breach relied upon for termination. Fact, evidence, consequence. Use that shape repeatedly rather than reinventing the structure of every point from scratch.

When the other side stands and says, “my learned friend is trying to make a mountain out of a municipal notice,” don’t answer with anger. Listen, because your opponent has just told you, for free, exactly where he thinks the fight actually is. Perhaps he argues the Corporation’s notice has nothing to do with contractual termination at all. Now you know the precise proposition you have to answer, and you can be precise back: “I am not suggesting the Corporation’s notice itself terminated the agreement — the termination was effected by the plaintiff’s own notice. The Corporation’s notice is relied upon only as contemporaneous evidence of the breach that preceded that termination.” That answer concedes the point that never mattered, and defends only the point that does — which is, in miniature, most of what good advocacy actually is.

Never fight a proposition you don’t need to win. If the defendant argues the plaintiff has exaggerated the damage, and the suit in front of the court is primarily about declaration and injunction rather than the exact figure, ask yourself honestly whether that number actually decides the relief the court is being asked to grant today. If it doesn’t, don’t spend ten of your twenty minutes defending a damages figure the case doesn’t currently turn on. Remember why the case was drafted the way it was in the first place — the damage assessment on record came to roughly sixteen lakh rupees, while the client’s original claim for damages ran to two crore, and the urgent relief actually sought was never the money. It was protection against the immediate threat of the company’s return. The suit was deliberately built, from the very beginning, around speed rather than tying the slow-moving damages dispute to the urgent injunction — using precisely the Order II Rule 2 discipline you learned while drafting the prayer, keeping the money claim reserved rather than folded into relief that needed to move quickly. The same discipline applies here at argument: argue what actually decides the case in front of the court today, not everything in the file that once made your client angry.

Treat an interruption from the bench as a gift rather than a threat. “Counsel, where is that in evidence?” should never unsettle you — it is the judge telling you, precisely, what he still needs to see. You should be able to answer immediately: “my Lord, Volume II, page 143, the witness’s affidavit, paragraph twelve.” Or: “that is Exhibit P-14.” Or: “that proposition was admitted in the written statement, paragraph eight.” If you cannot locate the answer on the spot, it means you have not yet mastered your own file closely enough, and that gap is worth closing before the hearing, not during it.

Build an argument sheet before you ever stand up, and keep it working rather than decorative — not fifty pages, a genuine working tool. For every issue: your answer, the evidence behind it, the best defence the other side can raise, your reply to that defence, the governing legal rule, and the relief that follows if you’re right. Issue by issue, that sheet is what turns an enormous file into something you can actually hold in your head under pressure.

Written submissions, when the court asks for them, are not a transcript of your oral argument written out afterward. They are the architecture of your case laid out on paper — issues, then propositions, then evidence, then law, then application, then relief, following the same shape throughout: question, then rule, then evidence, then application, then answer. A structure that makes the court’s job easier makes your own case easier to decide in your favour, which is worth remembering every time a written note starts drifting back toward narrative.

Try the exercise properly. Take a real, concluded civil case and give yourself exactly twenty minutes, no more, to argue it — two minutes on what the case is about, three on the issues, seven or eight on the decisive evidence, three or four on the law and its application, two or three answering the strongest thing the other side could say, and the last minute landing precisely on the relief you’re asking for. Practise it aloud, not silently in your head — you will discover, almost every time, that a beautiful fifteen-page argument compresses, under real time pressure, into five pages, then three, then perhaps two. That compression is progress, not loss.

Land the argument, always, back at the prayer, because that is where the whole case has actually been heading. “You get only what you ask for” was never merely a rule for drafting — it governs the end of the case just as strictly as the beginning. Don’t finish with “therefore the defendant’s case is entirely false,” because that leaves the judge to do the last piece of work himself. Finish instead with something closer to: “for these reasons, issues one and two should be answered in the plaintiff’s favour, and the plaintiff is accordingly entitled to the declaration and the permanent injunctions prayed for.” The argument has travelled, deliberately, all the way back to the prayer it began from, and that closing of the loop is what makes a case feel complete rather than merely finished.

Try reading a real judgment backwards as an exercise — not the reasoning first, but the operative portion, the part that says what the court actually granted. Then work backward from there: which issue had to be decided to reach that; which evidence mattered to that issue; which legal rule governed it; and which finding actually connected the evidence to the relief granted. You are reverse-engineering an argument someone else made successfully, and then doing the same exercise, forward this time, with your own case.

Avoid the single most dangerous sentence in a closing argument: “it is submitted that the plaintiff has proved his case in all respects.” Perhaps he has, but which respects, specifically? Don’t leave that work to the judge. Say instead: “on issue two, the plaintiff relies on three pieces of evidence,” and deal with them one at a time; then, “the defendant’s objection is,” and answer it directly; then, “accordingly, issue two should be answered in the affirmative.” A judge who can follow you sentence by sentence is a judge who can write your reasoning into his judgment far more easily than one left to reconstruct it himself.

Be honest, too, about where your evidence was genuinely weak, because pretending otherwise rarely helps. If a witness performed badly, don’t insist he didn’t. If a document has a real flaw, don’t spend ten minutes claiming it’s perfect. Ask, instead, whether that particular weakness actually defeats the issue it relates to — perhaps the same fact is independently established by the defendant’s own admission, or conceded somewhere in the written statement, or proved by another document entirely, or the issue simply doesn’t depend on the disputed point at all. Good advocacy was never about pretending a case has no weaknesses. It is knowing precisely which weaknesses matter and which don’t, and only defending the ones that do.

Sometimes the right move is a concession, offered before the other side has to force it out of you. If your opponent points out that your witness wasn’t present at the first discussion between the parties, and you know that’s true, don’t fight it. Say plainly that the point isn’t disputed, that the witness never needed to prove it, and that the fact that actually matters is the subsequent written agreement, which is admitted on the record anyway. One sentence, and an unnecessary battlefield has simply disappeared. Judges notice a lawyer who narrows a dispute rather than one who defends every inch of it out of habit.

Look back, for a moment, at everything this whole series has been quietly teaching you to do. The client brought you everything, all at once, and you learned to separate what happened from what he merely believed happened; a legal wrong from an ordinary grievance; the relief actually available from what he simply wanted; a material fact from the evidence meant to prove it; the genuine issue from everything else sitting around it in the file. Argument is the final act in that same long habit of selection, performed now under real time pressure, in front of someone who is about to decide.

Try one last drill before the next lecture. Take a real civil case and write a single page headed, plainly, why my client wins — no more than five lines under it: the decisive issue, the decisive fact, the strongest evidence, the governing legal rule, and the precise relief that follows. Then write a second page, just as short, headed why the other side loses. Then stand up and argue the whole case in ten minutes, out loud, and if you can, record yourself. Listen back afterward, and every time you catch yourself saying “as I have already submitted,” stop and ask why you needed to say it twice. Every time you state a fact without explaining its significance, stop. Every time you cite a document without saying what it actually proves, stop. Every time you state a legal proposition without applying it to your own facts, stop. And every time you finish a paragraph without being able to say which issue it just advanced, stop there too. That single exercise will teach you more than another twenty judgments read passively on your own.

The file began, all those lectures ago, with a man standing at a gate. It passed through the plaint, the written statement, the issues, the witnesses, the documents, the cross-examination that tested all of it — and now, after years, it has been reduced to a handful of questions you can actually hold in your head. You stand up. You have twenty minutes. You look at the judge, and this time you don’t tell him the whole story from the beginning. You know exactly why you’re there. Here is the issue. Here is the evidence. Here is the law. Here is why the other side’s answer fails. And here is the order I am asking this court to make.

Then you sit down, and the next voice in the room is not yours. It belongs to the judge — and the next stage of this case is no longer about what you could prove, or how well you argued it. It is about what the court has actually decided, and what happens next once it has.

Continue the series

PreviousS1 L27 — Evidence

NextS1 L29 — Judgment, Decree and Execution

All thirty lecturesThe First Brief — full contents

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