Law Has Two Jobs

In the last lecture we asked a very basic question: why do we need law at all? We imagined a world in which disputes were settled by strength, and we arrived at something close to a founding idea. At some point, human beings chose reason over force. Instead of saying, “I am stronger, so I am right,” we created rules. Instead of fighting over every disagreement, we created institutions. Instead of letting every person become the judge of his own dispute, we created courts.

That sounds like the end of the story. It isn’t. Because now imagine you are the person who actually has a problem. You have chosen law instead of force. You have behaved exactly as society expects you to behave. And then you ask the only question that matters to you: fine, I have come to the law — now what can it actually do for me?

That is where this lecture begins.

A man walks into a lawyer’s chamber and puts a thick file on the table. He looks exhausted.

“What happened?” you ask.

He opens the file. “Sir, that land is mine.”

You wait. He continues. “My cousin has taken it.”

“What do you want me to do?”

He looks at you as though the answer is obvious. “Get my land back.”

But before you can tell him what to do, you have to ask him something else. “First tell me — is the land legally yours?”

He looks surprised. “Of course it is.”

“Why?”

He opens the file again — sale deed, revenue records, possession papers, old correspondence — and begins explaining. And now you discover that two completely different questions are sitting inside his one sentence. The first is: is the land mine? The second is: if it is mine, what do I do about it? They sound like one question. They are not. And the law answers them in two entirely different ways.

The first thing law has to tell us is the legal position itself. Who has the right. Who has the duty. Who has the liability. What conduct amounts to an offence. And when a right is violated, what remedy the law provides. This is substantive law — the part that tells us what the law considers to be the rights, duties, liabilities and remedies of people. The Indian Contract Act tells us when a promise becomes binding and what happens when it’s broken. The Transfer of Property Act tells us what rights and liabilities arise when property changes hands. The Specific Relief Act tells us that sometimes money is not enough — that a court may, in the right circumstances, order a person to actually perform an obligation, or restrain them from doing something. And in criminal law, the Bharatiya Nyaya Sanhita (which has now replaced the old Indian Penal Code) tells us what conduct the State treats as an offence against society itself, not merely against one person. Different laws, different subjects, different corners of human life — but underneath all of them sits the same question: who is right, who is liable, and what relief does the law provide. That is the first job.

But suppose the law stops there. Suppose you’ve opened the statute book, found the answer, and your client is right — the law recognises his claim, the other person is liable, a remedy exists. Wonderful. Now what? His cousin is still sitting on the land. The land has not walked back to him because a sentence in a statute says it should. You look at the book. Nothing happens. You look at the man occupying the property. He doesn’t move.

“The law says this land belongs to me,” you tell him.

“Then go and prove it,” he replies.

And he has a point, an uncomfortable one. A legal right written in a book does not, by itself, change the physical world. The Transfer of Property Act does not physically remove someone from your land. A provision recognising your right does not hand you possession. Something else has to carry the law from the page into the world. That is the second job of law.

The question changes now. We are no longer asking who is right. We are asking how we make that right effective — and this is where procedural law enters, the Civil Procedure Code, the law of evidence, the law of limitation, the rules of court. All of these deal with a different family of questions: which court should hear the matter, how is a case instituted, how does the other side come before the court, what pleadings must be filed, who has to prove what, how is evidence brought in, how are witnesses examined and cross-examined, how does the court finally pass its order — and once it does, how is that order enforced. Notice that none of this is asking “who is right.” It is asking “how are we going to find out, and what happens once we do.”

You will hear lawyers say, “it’s only a procedural issue” — usually, interestingly, when the procedure has just gone against them. But think about it for a moment. Is procedure really just technical? Suppose your right is genuine and the law fully recognises it, but you file in the wrong court. Or you file after the prescribed period has expired. Or your pleading fails to state the facts that actually matter. Your right may be perfectly real, and the court may still be unable to give you what you came for. Procedure is not an ornament attached to substantive law. It is the machinery that makes the right enforceable, and it answers a question every litigant is entitled to ask: how do I get the court to recognise and enforce what is mine?

Put the two halves together and something else becomes visible. Before there can be a legal case, there has to be a fact — someone bought land, someone failed to pay, a contract was broken, someone entered a property they had no right to enter. The fact exists before anyone begins arguing about the law. Then two people want different things from that same fact, and that is where conflict begins. A says the property is his. B says no, it’s mine. Both may be entirely sincere. Both may believe they are right. And somewhere inside the vast body of law there may already be an answer to who actually is. But here is the part that matters: the rules do not walk into the room by themselves. A legal provision sitting quietly in a statute book resolves nothing on its own. Someone has to take the facts, find the law, follow the procedure, place the matter before a court, and ask the court to decide.

Fact, then conflict, then law, then procedure, then adjudication, then relief. That is the whole journey, and every part of it matters — break one link and the chain breaks with it. An excellent case filed in the wrong forum goes nowhere. A genuine claim filed too late goes nowhere. The law entirely in your favour but a pleading that never states the facts needed to establish it may never reach the remedy it deserves. Which is why a lawyer cannot stop at “my client is right.” That is only the beginning. The next question is how you get that right translated into an effective legal remedy — and that brings us to perhaps the most important lesson in this entire lecture: being right is not the same as being remedied.

Think again about the man who walked into your chamber. He did not come to hear a lawyer say, “yes, the land is legally yours” — he already believed that. He came because someone else was sitting on it. He wants something to happen in the real world. A property dispute doesn’t truly end with an opinion about ownership; it ends when the system delivers the appropriate relief — a declaration, perhaps, or possession, or an injunction. A breach of contract doesn’t end because a court explains that a breach occurred; it ends with damages, or with specific performance. A person wrongfully detained doesn’t come to you for a philosophical statement that his detention was wrong; he wants the actual, available relief. Criminal conduct, once proved through the criminal process, leads to prosecution and punishment according to law. Look at what all these examples share: none of them is merely a statement about the situation. Each is something the law does to the situation. That is the entire distance between being right and being remedied.

So remember this, because you’ll need it for the rest of your working life. Law gives us rights. It imposes liabilities. It provides remedies. And procedure gives us the machinery to enforce them. Substantive law and procedural law are not two unrelated subjects sitting in two different textbooks — they are two halves of one system. One tells us what the law says. The other makes that law work. And litigation is the process by which we take those rules, apply them to a real conflict, and ask the system for an appropriate result.

Go back for a moment to the first lecture. We said civilisation chose reason over force. Now you can see how that choice actually operates in practice. A conflict arises. We do not fight. We identify the law. We invoke the procedure. We go before the court. The court adjudicates. And we seek relief. That is the machinery through which a society tries to turn its choice of reason over force into something real, rather than a sentiment.

But there is an uncomfortable question waiting on the other side of all this theory. What happens when an actual human being walks into a lawyer’s chamber carrying a real problem? He doesn’t arrive holding a statute. He doesn’t say, “I have a question concerning substantive and procedural law.” He comes carrying his life, and he says: sir, this is what has happened to me — what can I do? Someone now has to take that messy, disordered human story, understand the facts inside it, find the governing law, identify the remedy, locate the right forum, and turn the whole tangled thing into something a court can actually act upon.

Who does that work?

That is where the lawyer enters.

There is a version of this problem the client always brings, and it’s worth hearing it once before you meet it for real. He owns land, or believes he does. His cousin has taken it. He wants it back.

“So I own the property?” he asks.

“Yes,” says the junior, quick to agree, glad to have found solid ground.

“That is not the end of the consultation,” the senior says, without looking up. “What do you actually want the court to do?”

“I want him out,” the client says.

“Good,” the senior says. “Now we are finally talking about a remedy.”

Because ownership is only half a sentence. The rest of it — what the court is meant to do about it — is where the real drafting begins. A client may be entirely, unambiguously right and still lose the practical battle, because being right was never the whole question. The other half of that question sits in the Specific Relief Act, 1963: Section 34 governs a suit for a bare declaration of right or status, and it carries a warning most young lawyers discover the hard way — a plaintiff who is entitled to further relief beyond a mere declaration cannot omit to claim it and expect the declaration alone to do the practical work. Sections 37 to 41 govern injunctions, temporary and perpetual, the order that actually stops someone from doing something. Section 31 concerns the cancellation of an instrument — a deed, a document — that stands in the way of a person’s right. Each of these is a different tool for a different shape of problem, and none of them moves an inch without the Code of Civil Procedure behind it to actually get the matter into court, in time. Which is the other half of this lesson: Section 3 of the Limitation Act, 1963 says, in substance, that a suit, appeal or application filed after its prescribed period is liable to be dismissed, whether or not the other side even bothers to raise the objection. The court can raise it on its own. The exact period depends on the claim and the relevant article in the Schedule — but the principle to carry with you is blunt enough to remember without looking it up: a right that has gone stale in law is no longer a right the court will enforce, however real it once was.

Sit with that for a moment before you move on: a client can be completely right and still lose, if nobody ever asked what link between the right and the remedy was actually missing. Write down one real dispute — any dispute, the more ordinary the better — as four steps in a line: the right, the invasion of it, the exact relief that would fix it, and the statutory provision that gets you there. Then ask yourself, honestly, what would still be unresolved even if a court gave you everything in that fourth column. If the answer is “nothing,” you have understood this lecture. If the answer is “quite a lot,” you have understood it even better — because that gap is where the rest of this course lives.

Which brings us to the harder question waiting at the door. A conflict arises. We do not fight. We identify the law. We invoke the procedure. But there is a person, a client, a story — and someone has to sit across from him, listen, and begin the work of turning what he says into a case a court can decide.

That is where we go next.

Continue the series

PreviousS1 L1 — Why Do We Need Law at All?

NextS1 L3 — What Does a Lawyer Actually Do?

All thirty lecturesThe First Brief — full contents

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