Supreme Court says: once we pronounce a judgment, we can't tweak it — except for typos

The Supreme Court transferred 16 cases to one court. Then it got a call: 'Wait, one case is already done — only the judgment is left.' So the Court had to decide: can it fix its own order?

Ketan Kantilal Seth had been fighting criminal cases across four states for over two decades. Gujarat, West Bengal, Delhi, Maharashtra — 16 cases, spread across courts, each one grinding through its own timeline. In September 2022, the Supreme Court did something unusual: it ordered all 16 cases transferred to a single court in Mumbai. The idea was simple — one judge, one trial, one end to a litigation that had dragged on for twenty years.

But then the phone rang. A state government said it hadn't been heard. A co-accused said he was 85 and couldn't travel 600 kilometres. And one case, it turned out, was already finished — arguments were done, only the judgment remained. The Court had accidentally ordered a fresh trial in a case that was essentially over.

When the transfer order landed

On 9 September 2022, a bench of the Supreme Court allowed Seth's transfer petition. All 16 criminal cases — some at the stage of charge-framing, others mid-trial, one at final arguments — were sent to the Principal Judge of the Bombay City Civil and Sessions Court in Mumbai. Paragraph 13(e) of the order directed that charges be framed within two months, implying a fresh start in every case.

For Seth, this was a victory. For the State of Maharashtra and several co-accused, it was a problem they hadn't seen coming.

Omprakash Kamdi, an intervenor who claimed to be an agriculturist dependent on a bank allegedly defrauded by Seth, filed an application seeking complete recall of the transfer order. The State of Maharashtra filed its own application, arguing it had not been given a hearing before the transfer was ordered. And several elderly accused from Amravati — aged between 65 and 85 — said they could not physically travel to Mumbai for hearings.

The case that was already done

The most urgent problem was R.C.C. No. 147/2002, pending at Nagpur. In that case, arguments had been completed. Only the judgment remained to be pronounced. The Supreme Court's transfer order, by directing a fresh framing of charges, would have forced a de-novo trial (a completely new trial starting from scratch) in a case that was essentially finished.

This was not a small oversight. A de-novo trial in a case where evidence had already been led and arguments concluded would mean witnesses would have to be recalled, documents re-exhibited, and years of judicial work wasted. For the complainants and stakeholders who had already waited through the trial, it would have been a devastating reset.

The Court had also, in an earlier order dated 13 May 2022, specifically allowed the completion of arguments in R.C.C. No. 147/2002 but restrained the pronouncement of judgment — suggesting the Court knew this case was at an advanced stage. Yet the transfer order of September 2022 had somehow overlooked this.

What the law allows — and what it doesn't

The Supreme Court was now faced with applications seeking recall or modification of its own order. The legal question was narrow but important: under what circumstances can the Supreme Court alter a judgment it has already pronounced?

Order XII Rule 3 of the Supreme Court Rules, 2013, allows the Court to correct clerical or arithmetical mistakes, or errors arising from an accidental slip or omission. This is not a review (a full re-examination of the case on its merits) — it is a mechanical correction of something the Court clearly did not intend.

The State of Maharashtra argued that paragraph 13(e) of the transfer order — directing framing of charges within two months — was exactly such an accidental slip. The Court had not intended to force a de-novo trial in a case where arguments were already complete. The elderly accused from Amravati, meanwhile, argued that the transfer order would cause them undue hardship — they had documented health ailments and could not travel 600 kilometres to Mumbai.

The intervenor, Omprakash Kamdi, asked for something more dramatic: complete recall of the transfer order. But the Court rejected this prayer outright, holding that Kamdi lacked locus standi (the legal standing to appear in a case where he was not a party).

Why the Court said no to a full recall

The bench — Justices J.K. Maheshwari and Surya Kant — was clear on one point: a judgment pronounced by the Supreme Court cannot be altered or added to except for correcting clerical or arithmetical mistakes or errors arising from accidental slip or omission. Applications filed on the pretext of 'clarification' or 'addition' while evading the recourse of review ought not to be entertained and should be discouraged.

This is a crucial distinction. A review petition (a request for the Court to re-examine its own decision on the merits) follows a different procedure under Order XL Rule 3 of the Supreme Court Rules. It requires the Court to find an error apparent on the face of the record. A modification application, on the other hand, can only fix mistakes that the Court itself recognises as unintended.

The Court cited several precedents to underline this point. In Supertech Limited v. Emerald Court Owner Resident Welfare Association, the Court had held that once a judgment is pronounced, it becomes final and cannot be reopened through the backdoor of a clarification application. In Gurdip Singh Uban v. Unknown, the Court had warned against using modification applications as a substitute for review. And in Meghmala v. G. Narasimha Reddy, the Court had reiterated that the power to correct accidental slips is limited to what the Court clearly intended but failed to express.

What the Court actually fixed

On 4 August 2023, the Supreme Court passed a nuanced order. It did not recall the transfer — Seth's victory in getting all cases to one court remained largely intact. But it made three specific modifications:

First, R.C.C. No. 147/2002 at Nagpur would not be transferred to Mumbai. Instead, it would remain at Nagpur and proceed from the stage of final arguments — meaning the trial judge would simply pronounce judgment. The accidental slip of ordering a de-novo trial in a finished case was corrected.

Second, the cases involving elderly accused from Amravati — specifically respondents/accused numbers 20, 23, 25, 26, 30, 31, 32 and 34 — would be returned to the transferor court at Amravati. These were senior citizens with documented health ailments, and requiring them to travel 600 kilometres would have been unjust.

Third, paragraph 13(e) of the original transfer order was modified to clarify that all transferred cases would proceed from whatever stage they were at when received — not from the stage of charge-framing. No de-novo trials unless the receiving court specifically ordered one.

The Court also dismissed as infructuous a review petition that had been filed separately, since the modifications had addressed the core concerns.

Why this matters for every litigant

This case is a reminder that even the Supreme Court can make mistakes — and that the law provides a limited mechanism to fix them. But the mechanism is not a free pass. You cannot use a 'clarification' application to re-argue your case. You cannot ask the Court to change its mind through the backdoor. You can only point out what the Court clearly intended but accidentally failed to express.

THE PLAY: If the Supreme Court's order contains an error that the Court itself would recognise as unintended — such as ordering a fresh trial in a finished case — file a miscellaneous application under Order XII Rule 3, not a review petition.

The Court ended where it began: with 16 cases, one judge, and the quiet correction of a slip that could have undone years of judicial work.