Preventing Forum-Shopping Why the Seat of Arbitration is an Absolute Jurisdictional Lock
- Apr 10
- 6 min read

BBR (India) Private Limited v. S.P. Singla Constructions Private Limited, Civil Appeal Nos. 4130-4131 of 2022, decided on 18 May 2022
Picture this. An NBFC headquartered in Mumbai disburses a digital loan to a borrower in Kerala. The borrower defaults. Arbitration is invoked. The entire proceeding, hearings, cross-examination, arguments, happens over video conference. The award is passed. And then the borrower files a challenge under Section 34 of the Arbitration and Conciliation Act, 1996 before a district court in Kerala, arguing that the hearings happened on his laptop screen at home, and his home gives local courts jurisdiction.
This is not a contrived scenario. It is the live jurisdictional headache that every digital lender, fintech, and online dispute resolution platform must reckon with in the era of remote arbitration. And the Supreme Court of India, in a tightly reasoned judgment authored by Justice Sanjiv Khanna, has handed down the answer with unmistakable clarity: the designated Seat of arbitration is a static, exclusive jurisdictional lock. Where the hearings happen is irrelevant. Where the Seat is, that is where the courts sit.
The Facts That Set Up the Question
BBR (India) Private Limited and S.P. Singla Constructions Private Limited had entered into a contract in 2011 for supply and installation work on a cable-stay bridge in Jammu and Kashmir. The arbitration clause was silent on both the seat and venue of arbitration. The contract was executed at Panchkula in Haryana, where the respondent also had its corporate office.
When disputes arose, the first arbitrator, Justice (Retd.) N.C. Jain, was appointed. At the very first sitting on 5 August 2014, he fixed the place of proceedings as Panchkula, Haryana. The parties did not object. Pleadings were completed. The first arbitrator then recused himself for personal reasons.
A new arbitrator, Justice (Retd.) T.S. Doabia, took over. In his first procedural order dated 30 June 2015, he recorded that the venue of proceedings would be Delhi. All subsequent hearings, witness examination, arguments, and the final award were conducted and pronounced at Delhi. The award, passed on 29 January 2016, was in favour of the respondent.
What followed was a jurisdictional collision. The respondent filed a Section 9 application before the Additional District Judge at Panchkula. The appellant filed a Section 34 petition before the Delhi High Court. Two parties, two courts, one arbitration. The question before the Supreme Court was simple but consequential: did the shift of proceedings from Panchkula to Delhi, on the appointment of a new arbitrator, relocate the jurisdictional seat of arbitration from Panchkula to Delhi?
The Legal Framework: Seat, Venue, and Section 20
The Court worked through the statutory architecture of Section 20 of the Act with methodical care. Sub-section (1) gives the parties complete freedom to agree on the place of arbitration. Once the parties designate a place as the seat, that designation operates as an exclusive jurisdiction clause, vesting supervisory power in the courts of that place alone. Sub-section (2) comes into play only when the parties have not agreed on a seat, in which case the arbitral tribunal determines the place of arbitration having regard to the circumstances, including the convenience of parties. Sub-section (3) is the crucial provision that is most often misread. It permits the arbitral tribunal to hold hearings, meet, examine witnesses, or inspect documents at any place it considers appropriate. This sub-section, the Court confirmed, refers to the venue of arbitration, not the seat.
The distinction is not semantic. The seat is the juridical home of the arbitration. It is fixed and static. The venue is merely the physical or, in a digital world, virtual location where a particular hearing takes place. The venue can travel. The seat cannot.
What the Court Decided
Relying on the Constitutional Bench decision in Bhartiya Aluminium Company v. Kaiser Aluminium Technical Services Inc. (BALCO) and the three-judge bench decision in BGS SGS Soma JV v. NHPC Limited, the Court held that once the arbitral tribunal fixes the seat under Section 20(2), that seat becomes fixed and exclusive. It cannot be changed by the tribunal on its own. Only an express mutual consent of the parties can relocate the seat. The appointment of a successor arbitrator who conducts proceedings at a different city does not, by itself, shift the seat.
On the facts, the Court found that the first arbitrator had fixed Panchkula as the place of arbitration on 5 August 2014, in the exercise of the power under Section 20(2), since the parties had not agreed on a seat. That determination was valid, binding, and could not be unilaterally altered by the second arbitrator merely by recording a different venue in his first procedural order. The proceedings at Delhi were, in law, only a change of venue under Section 20(3), not a relocation of the seat.
Consequently, the courts having jurisdiction over Panchkula, Haryana, held exclusive supervisory jurisdiction. The Delhi High Court had no jurisdiction to entertain the Section 34 petition filed by the appellant. The appeals were dismissed.
The Forum-Shopping Argument and Why It Failed
The appellant had argued that since substantially all the meaningful proceedings, hearings, cross-examination, arguments, and the award itself, had taken place in Delhi, it would be both unfair and impractical to hold that courts in Panchkula had jurisdiction over the challenge. This argument, on the surface, has intuitive appeal. But the Court rejected it on principled grounds.
Accepting this argument, the Court observed, would create a recipe for uncertainty and confusion. If the seat could shift every time a new arbitrator held proceedings in a new city, parties would never know with certainty which court to approach. Worse, it would incentivise race-to-court behaviour, with each party rushing to file first in a court convenient to them. That is precisely what happened in this case. The Court was categorical: the aspect of certainty as to the court's jurisdiction must be given priority over the contention that the supervisory court should be located where most hearings were conducted.
What This Means for Online and Digital Arbitration
The implications of this judgment for online dispute resolution are significant and immediate. In a world where arbitration hearings routinely happen over video conference, the very concept of a physical venue has become fluid. A hearing might be streamed to a tribunal sitting in Mumbai while the claimant logs in from Chennai and the respondent connects from Bhopal. If the physical location of each hearing determined the jurisdictional seat, every ODR proceeding would be a jurisdictional minefield.
The Supreme Court's reasoning provides a clean solution. In online arbitration, where hearings have no fixed physical location, the seat clause in the arbitration agreement is not just important. It is the only anchor. By designating a specific city as the seat in the agreement, the parties determine the supervisory court once and for all, regardless of where the login screen is, regardless of which city the arbitrator is sitting in when he types his award, and regardless of where the respondent clicks to join the hearing.
For NBFCs, digital lenders, and fintech companies that routinely arbitrate with borrowers spread across multiple states, this is a critical protection. A properly drafted seat clause ensures that when a borrower files a challenge to an award, that challenge can only be filed in the court at the designated seat. The borrower cannot choose a district court close to home as a tactical move to increase the cost and inconvenience of litigation for the lender. That avenue is firmly closed.
The Section 42 Angle
The Court also addressed the role of Section 42 of the Act, which provides that once any application under Part I of the Act has been made to a court, that court alone shall have jurisdiction over all subsequent applications. The appellant had argued that since it filed the Section 34 petition in Delhi first, the Delhi courts would have exclusive jurisdiction under Section 42.
The Court rejected this too. Section 42 cannot operate to confer jurisdiction on a court that does not otherwise have jurisdiction. The Delhi courts had no jurisdiction over a Panchkula-seated arbitration to begin with. Filing first in Delhi cannot bootstrap jurisdiction where none exists. The court in which the application is filed must first be a court with jurisdiction. Since the seat was Panchkula, only courts having jurisdiction over Panchkula could exercise supervisory power, and Section 42 would operate to make those courts exclusively competent once the first application was filed there.
Drafting the Seat Clause: The Takeaway
This judgment reinforces a point that cannot be stated too often: the seat clause is not boilerplate. It is the most jurisdictionally consequential provision in an arbitration agreement. A vague clause, or worse, a clause that is silent on the seat, creates exactly the kind of confusion that played out in this case, where two parties ended up in two different courts in two different states with contradictory claims of jurisdiction.
The seat clause must expressly designate a specific city as the seat of arbitration. It must be distinguished from any venue provision. And in any agreement that contemplates online or remote proceedings, the seat clause must be clear that the designation of a seat is independent of and not affected by the location from which any party or the tribunal participates in any hearing.
For platforms that facilitate online arbitration and for companies that routinely issue digital contracts with millions of counterparties, embedding a fixed, well-drafted seat clause is the single most effective tool to prevent forum-shopping after an award. The Supreme Court has confirmed that such a clause, once validly incorporated, is an absolute lock on jurisdiction. It is time to treat it that way.
_edited.png)



Comments