8 days late: SC says courts can't kill arbitration objections over small delays
HUDA's objections to a Rs 1.19 crore arbitration award were dismissed as time-barred despite being only 8 days late. The Supreme Court says courts must condone short delays if there's a reasonable explanation.
8
days.
HUDA's objections to a Rs 1.19 crore arbitration award were dismissed as time-barred despite being only 8 days late. The Supreme Court says courts must condone short delays if there's a reasonable explanation.
HUDA missed the deadline to challenge a Rs 1.19 crore arbitration award by just 8 days. The trial court threw out their objections. The Supreme Court just reversed that — and the reason has nothing to do with the money.
The Haryana Urban Development Authority (HUDA) had hired Mehta Construction to build a town park in Karnal. The contract, signed in 1998, was worth about Rs 32.50 lakhs — later revised to roughly Rs 45.87 lakhs. The work was completed in August 1999. Then the trouble began.
When the park became a battlefield
Both sides blamed each other for delays. HUDA said the contractor was slow. The contractor said HUDA kept changing plans and withholding payments. For over a decade, the dispute sat unresolved — the file gathering dust in government offices, each side waiting for the other to blink first. The contract documents, yellowing at the edges, recorded a story of mutual suspicion: HUDA's engineers noting slow progress, the contractor's letters complaining about delayed approvals and unpaid bills. Neither side would yield.
In 2012, Mehta Construction approached the Punjab and Haryana High Court to get an arbitrator appointed under Section 11(6) of the Arbitration Act (a provision that lets a court appoint an arbitrator when one party refuses to cooperate). The High Court directed the parties to approach the Arbitrator-cum-Superintending Engineer of HUDA's Karnal circle. The order was short — a few lines directing the parties to a man who was, in effect, HUDA's own employee. The contractor must have felt the odds were stacked against them from the start.
The sole arbitrator — an engineer from HUDA's own ranks — heard both sides. In December 2013, he delivered a stunning award: Rs 1,19,69,945 (roughly Rs 1.19 crore) in favour of the contractor, with 18% interest per year. The weight of that figure — nearly three times the original contract value — must have landed like a stone in HUDA's Karnal office. The award ran into pages, each paragraph a fresh blow to the department's finances. The interest alone, compounding at 18%, would have been enough to make any government accountant wince.
The 8-day gap that changed everything
HUDA wanted to challenge the award. Under Section 34 of the Arbitration Act (the provision that allows a party to ask a court to set aside an arbitral award), a party has three months to file objections. The law gives an additional 30 days if the party can show sufficient cause for the delay. The clock started ticking the day the award was received — a date that would later become the subject of quiet dispute in the courtroom.
HUDA filed its objections 8 days beyond the three-month period — but well within the extra 30-day window. The date-stamp on the filing showed the gap: eight small days that would determine the fate of a Rs 1.19 crore award. The Additional District Judge in Karnal had two options: accept the short delay with a reasonable explanation, or reject the objections entirely. The judge's chamber, lined with case files, held the future of this dispute in a single folder.
The trial court chose the second option. It dismissed HUDA's objections both as time-barred and on merits. The judge's reasoning on the merits was brief — what the Supreme Court would later call "cryptic and perfunctory." The silence in the Karnal courtroom after that order must have been heavy; HUDA had lost before its arguments were even heard. The court clerk stamped the file "Disposed" and moved it to the archives, where it would sit for months before HUDA decided to appeal.
HUDA appealed to the Punjab and Haryana High Court under Section 37 (the provision for appeals against orders on arbitration objections). The High Court dismissed the appeal in December 2019, upholding the trial court's decision. The High Court judge, sitting alone in the chambers at Chandigarh, wrote an order that largely echoed the trial court's reasoning — a few paragraphs that did not engage with the specifics of HUDA's objections. The file was stamped again, and the dispute seemed finally buried.
What HUDA argued — and why it mattered
Before the Supreme Court, HUDA's counsel made a simple point: the delay was only 8 days. The explanation was reasonable — the department needed time to engage a lawyer, examine the voluminous records stacked in files that had accumulated over a decade, and obtain approvals from higher authorities. A government body cannot move as fast as a private individual, they argued. The stack of papers — contracts, correspondence, site reports — was thick enough to justify the short wait. The counsel gestured at the sheer volume of the record: letters from the contractor, inspection reports, minutes of meetings, payment vouchers — all needing to be read, sorted, and presented to a lawyer who had to be briefed from scratch.
Mehta Construction's counsel countered that the law is the law. Section 34(3) gives a clear timeline: three months, plus 30 days if condoned. The trial court had discretion, and it exercised that discretion against HUDA. The High Court agreed. Why should the Supreme Court interfere? The contractor's lawyer stood firm: a deadline is a deadline, and HUDA had missed it. The fact that the delay was small did not change the fact that it was a delay. The courtroom in the Supreme Court — with its high ceilings and the portrait of the Chief Justice watching over the proceedings — became the stage for this clash between procedural rigidity and substantive justice.
The bench — Justice Ajay Rastogi and Justice Sanjiv Khanna — saw it differently.
Why the Supreme Court reversed both courts
The Supreme Court held that the 8-day delay was clearly condonable under the proviso to Section 34(3) (the clause that allows courts to accept objections filed within the extra 30-day window if a reasonable explanation exists). HUDA's explanation — the need to engage counsel, examine records, and obtain approvals — was reasonable for a government body. The bench noted that the proviso exists precisely for such cases: where the delay is marginal and the explanation is not frivolous. To reject such a short delay mechanically, the court implied, would be to read the proviso out of the statute.
But the court didn't stop there. It also found that neither the trial court nor the High Court had properly examined HUDA's objections on merits. Both courts had dismissed the objections with generalised reasoning, without dealing with specific issues raised by HUDA. The trial court's order, the Supreme Court noted, was so sparse that it barely engaged with the contentions — a few lines of reasoning that could have been written without opening the award at all. The High Court's order was similarly barren: it recited the facts, noted the delay, and dismissed the appeal in a paragraph that could have been a template for any arbitration dismissal.
"Courts dealing with objections under Section 34 of the Arbitration Act must provide substantive, non-cryptic, and non-perfunctory reasoning that deals with specific issues and contentions raised," the bench observed. Generalised dismissals without proper application of mind, the court said, are impermissible. The judgment was delivered on 30 March 2022, the courtroom falling silent as the bench pronounced its order. The file, which had travelled from Karnal to Chandigarh to New Delhi, was now heading back to where it started — with a simple instruction: actually read the objections.
The Supreme Court set aside both the trial court's order and the High Court's order. It sent the matter back to the Additional District Judge, Karnal, for a fresh hearing on merits — this time, a proper one. The observations in the Supreme Court's order were not binding on the lower court, leaving the judge free to decide afresh. The operative order was clear: the appeal was allowed, the lower court orders were quashed, and the matter was remanded. No costs were awarded — a quiet signal that this was not about punishing either party, but about getting the procedure right.
What this means for every arbitration case
For practitioners and parties dealing with arbitration awards, this judgment offers two clear lessons.
First, a short delay — even 8 days — should not automatically kill your objections, especially if you have a reasonable explanation. The 30-day condonable window under Section 34(3) exists precisely for situations like this. Courts should not mechanically reject objections as time-barred when the delay is short and the explanation is plausible. The proviso is not a dead letter; it is a safety valve for genuine cases where the delay is marginal. Government bodies, in particular, can rely on this provision when internal processes cause minor delays — as long as the explanation is honest and the delay is within the 30-day window.
Second, courts cannot brush aside objections with vague, one-line reasoning. A Section 34 hearing requires the judge to actually engage with the arguments — examine the award, consider the grounds raised, and give reasoned findings. A "cryptic and perfunctory" dismissal will not survive scrutiny. The judge must sit with the file, turn the pages, and write something that shows the objections were actually read. The Supreme Court's message is that a Section 34 order must be a judgment, not a rubber stamp. The judge must grapple with the contractor's arguments about delay, the arbitrator's findings on liability, the question of interest — all of it.
The judgment also reinforces a broader principle: procedural technicalities should not become instruments of injustice. An 8-day delay — especially when the filing is within the condonable period — should not be allowed to defeat a substantive challenge to an award of Rs 1.19 crore. The Supreme Court's message is clear: courts must be gatekeepers of justice, not automatons that reject objections on mechanical grounds. The proviso to Section 34(3) exists to prevent exactly this kind of injustice — a small procedural slip wiping out a potentially valid challenge to a large award.
This decision aligns with the settled position that Section 34 objections are the primary safeguard against patently illegal or perverse arbitral awards. If courts dismiss them without proper examination, the entire arbitration framework loses its accountability mechanism. The Supreme Court's remand ensures that HUDA's objections — whatever their ultimate merit — will at least be heard, not silently buried under a stamp of dismissal. The award of Rs 1.19 crore with 18% interest will now face proper scrutiny: the trial court must examine whether the arbitrator exceeded his jurisdiction, whether the award is patently illegal, whether it shocks the conscience of the court.
THE PLAY: If your objections under Section 34 are within the 30-day condonable window, insist that the court hear them on merits — a short delay with a reasonable explanation must be condoned, not used as a weapon to shut the door.
The park in Karnal was built in 1999. The dispute over who caused the delays will now be heard again — more than two decades later, with a simple instruction from the Supreme Court: actually read the objections before dismissing them. The files, now older than some of the lawyers in the case, will be opened once more. This time, the judge must turn every page. The courtroom in Karnal will see the same parties, the same arguments, the same award — but this time, the judge will have to write an order that shows the objections were heard, considered, and decided on their merits. The Supreme Court has given the trial court a second chance to do what should have been done the first time: to be a court, not a gate.