The biggest misconception about jurisdiction risk is that it starts only after the other side formally objects. In practice, the warning signs appear earlier: inconsistent clauses, vague entity names, asset movement, expired notices and internal teams describing the forum differently.
Five questions should be asked immediately:
- Can we point to one signed clause without qualification?
- Are all important parties actually bound by it?
- Is the seat or chosen court clear?
- Can we protect assets and deadlines while the forum issue is argued?
- Will the final result work where assets are held?
If any answer is “not sure,” look for these fourteen red flags.
Red flag 1 — three documents contain three different dispute clauses
A master agreement, purchase order and guarantee all point somewhere else. This is no longer a simple clause-reading exercise; it is a scope and contract-priority problem.
Red flag 2 — the team keeps saying “governing law” when it means “jurisdiction”
The terminology confusion usually signals that no one has separated substantive law, court jurisdiction, arbitration agreement and seat.
Red flag 3 — the clause names arbitration but no one can identify the seat
The seat can affect supervision, challenges and procedural law. If it is genuinely missing, the institutional rules and applicable law may provide a mechanism, but the answer should be verified rather than invented.
Red flag 4 — an affiliate is central but did not sign
The business may call the parent “the real company,” while the contract is with a subsidiary. This raises a distinct binding-party question.
Red flag 5 — a guarantee has its own court clause
Guarantees are often treated as annexes when they can be independent legal instruments. A separate forum provision can create parallel proceedings.
Red flag 6 — someone proposes filing “where the law is familiar”
Familiarity is not jurisdiction. The forum must have a legal basis, and a governing-law choice alone may not supply it.
Red flag 7 — urgent assets can move before a forum ruling
If goods, money or evidence may disappear, the procedural plan must address interim protection now. Waiting for a perfect jurisdiction opinion may destroy the practical remedy.
Red flag 8 — nobody has checked a limitation or notice deadline
Forum arguments can consume time while contractual and statutory clocks keep running.
Red flag 9 — the chosen institution or rule edition is being guessed
Current ICC rules changed in 2026; SIAC rules changed in 2025. Citing a procedural shortcut from an old edition without checking applicability is a warning sign.
Red flag 10 — the team says “New York Convention, so enforcement is automatic”
The Convention provides a powerful recognition and enforcement framework for qualifying awards, not an automatic collection service. Local procedure, defenses and actual asset ownership still matter.
Red flag 11 — a court-enforcement memo never checks treaty scope
The 2005 HCCH Choice of Court Convention and 2019 Judgments Convention have defined scopes and Contracting-State conditions. Regional regimes have exclusions too; for example Brussels I Recast excludes arbitration.
A memo that quotes a regime without checking scope is not ready.
Red flag 12 — demand letters name inconsistent forums
One letter threatens arbitration, another says “exclusive courts,” and a third reserves every forum without explanation. Strategic alternatives may be possible, but accidental inconsistency can become evidence for the opponent.
Red flag 13 — no one has mapped assets
A forum strategy without an enforcement map is incomplete. The defendant may have operations in one country and collectible assets in another—or assets may belong to a different group company.
Red flag 14 — procedural spend is approaching merits spend
When the parties spend months fighting only about where to fight, management should reassess the economics. It may still be necessary to win the jurisdiction issue, but the next cost step should be explicit.
What to do when three or more red flags appear
Stop treating the matter as an ordinary collection or quality dispute. Create a separate forum workstream with:
- clause matrix;
- party/signature map;
- deadline sheet;
- urgent-relief assessment;
- asset map;
- treaty/rule status check;
- recommendation plus fallback.
Do not rewrite the merits file. The objective is to isolate the procedural uncertainty so commercial teams can keep working on the underlying dispute.
A counterexample: one red flag does not always mean disaster
A clause may omit the hearing location but clearly specify a valid arbitration agreement, seat and rules. That may be entirely manageable. Likewise, two related contracts can have different clauses for legitimate reasons.
A red flag means “verify this before relying on it,” not “the clause is invalid.”
Escalation rule
Escalate to specialist local advice immediately when:
- the forum clause may be invalid or contradictory;
- non-signatories are material;
- protective relief is needed in another country;
- limitation periods are close;
- treaty applicability changes the enforcement plan;
- sovereign/state-linked parties or insolvency issues are involved.
The earlier these issues are isolated, the more likely the company can decide them before procedural positions harden.
The red-flag dashboard should be factual, not emotional
Give each red flag three fields: evidence, owner and deadline. “Counterparty is acting suspiciously” is not a useful entry. “USD 400,000 receivable was assigned on 28 September; ownership documents requested by 5 October” is.
This discipline prevents escalation decisions from being driven by tone. A hostile email may have little procedural significance, while a quiet corporate restructuring or an expiring notice period can be decisive.
A weekly forum-risk review
During an active dispute, review six items weekly until forum stabilizes:
- new contracts or amendments discovered;
- new parties or guarantors identified;
- changes in asset location/ownership;
- approaching limitation/notice dates;
- new filings or procedural communications;
- settlement statements that could affect forum positions.
The meeting can be fifteen minutes. Its purpose is version control, not legal argument.
When a red flag can be closed
Do not leave every warning permanently “open.” A red flag is closed when a reliable source resolves it—for example, the signed clause confirms the seat, counsel confirms a treaty route, or registry evidence establishes asset ownership.
Record the resolution and source. Closed issues should not be repeatedly re-researched unless facts or law change. This keeps attention on real uncertainty rather than on an ever-growing list of fears.
Separate red flags from legal conclusions
A dashboard should never label a clause “invalid” or an affiliate “bound” unless that conclusion has been professionally verified. Use factual labels such as “seat not stated,” “guarantor clause differs,” or “asset ownership unverified.”
That wording matters because operational dashboards are copied into emails, board materials and settlement discussions. A premature legal conclusion can spread farther than the original analysis and become difficult to correct later.
The discipline is simple: facts can be marked red by the business team; legal consequences should carry a source, date and professional owner. If the legal conclusion is provisional, label it provisional and identify the fact or authority needed to close it. That small convention prevents a working hypothesis from being repeated later as an established rule in management papers, correspondence or formal pleadings or internal board papers later.
General commercial information only, not legal advice. Red flags are diagnostic signals, not legal conclusions. Clause validity, seat, jurisdiction, deadlines, treaty scope and enforcement require analysis under current applicable law and procedure by qualified professionals.
Related Reading
- Jurisdiction Disputes Go Wrong in Predictable Ways: 12 Mistakes to Avoid Before the Merits
- Before Filing Anywhere: A 17-Step Jurisdiction and Arbitration Decision Checklist
- The Jurisdiction File: 15 Documents That Prove Forum, Consent, Notice and Enforceability
Sources and Scope Notes
- ICC 2026 Arbitration Rules — ICC; 2026 Rules entered into force 1 June 2026 and generally apply to ICC arbitrations commenced from that date unless parties chose earlier rules. Checked 2026-10-03.
- New York Convention (1958) — UNCITRAL; common framework for recognition of arbitration agreements and foreign/non-domestic arbitral awards, subject to treaty scope, reservations and refusal grounds. Checked 2026-10-03.
- UNCITRAL Model Law on International Commercial Arbitration — UNCITRAL; model framework covering arbitration agreements, tribunal jurisdiction, court intervention, interim measures and recognition/enforcement; national enactments differ. Checked 2026-10-03.
- HCCH 2005 Choice of Court Convention — HCCH; applies within its treaty scope to international exclusive choice-of-court agreements in civil or commercial matters, with exclusions and contracting-state conditions. Checked 2026-10-03.
- Regulation (EU) No 1215/2012 (Brussels I Recast) — EUR-Lex; jurisdiction and recognition/enforcement regime for civil and commercial judgments within its scope; Article 1 excludes arbitration. Checked 2026-10-03.