A jurisdiction argument is often lost long before anyone opens a law book. The file is missing the signed order form, nobody can prove which online terms were incorporated, the “counterparty” is described by a brand instead of a legal entity, or the notice email went to an address that the contract never designated.

The best forum file is boring: every proposition has a document behind it. These 15 records are the core of a defensible cross-border jurisdiction and arbitration file.

1. The final signed contract

Keep the executed version with signatures, dates and all pages. Do not rely on a Word draft carrying the same filename.

The signed text is the starting point for consent, scope, dispute language and party identity.

2. Every amendment and side letter

A later amendment can replace a governing-law clause, add an arbitration provision or change the entities involved. Side letters may contain their own dispute language.

Create a document sequence so reviewers know which provision came later.

3. Purchase orders and order acknowledgements

Cross-border sales often operate through repeated purchase orders. A PO can incorporate standard terms or conflict with a master agreement.

Record which order generated the disputed delivery and what terms each side sent at formation.

4. The incorporated terms as they existed on the relevant date

If a contract points to web terms, save the historical version, URL, timestamp and evidence showing how it was presented.

A current webpage does not prove what the counterparty saw months or years earlier.

5. The entity and signature authority file

Preserve legal names, registration details, signature blocks, powers of attorney and authority records where material.

This file helps separate three questions: who signed, in what capacity, and whether another entity is being asked to perform or arbitrate.

6. The clause comparison sheet

Put dispute provisions from the master contract, PO, guarantee, logistics contract and any other relevant instrument side by side.

Highlight governing law, courts, arbitration, seat, institution, rules and language. Conflicts become visible immediately.

7. The formation communications

Keep negotiations that bear on acceptance of the dispute clause: redlines, emails exchanging standard terms, signature-platform logs and acceptance records.

Do not dump every email into a folder. Tag the handful that actually show how the clause entered the transaction.

8. The dispute chronology

Build a dated chronology from contract formation through performance, breach, notice and escalation.

Forum questions can turn on when an agreement was made, when a claim accrued, when a notice was delivered or when a procedural step occurred. Dates need documentary anchors.

9. Contractual notices and proof of delivery

Preserve the exact notice, attachments, destination address, delivery confirmation, rejection message and any reply.

A notice requirement may be separate from the institution's filing rules. Satisfying one does not automatically satisfy the other.

10. Escalation and mediation records

If the clause requires negotiation, executive escalation or mediation before arbitration/litigation, keep invitations, attendance records and completion dates.

Whether a step is mandatory and what happens if it is skipped can depend on wording and law. Record facts first; let counsel characterize the legal consequence.

11. The institutional filing record

For arbitration, preserve the request/notice of arbitration, submission timestamp, fee receipt, case number and communications from the institution.

ICC's current 2026 Rules, for example, specify how an ICC arbitration is commenced and administered. Other institutions have their own filing mechanics.

12. Seat and procedural-order records

Keep the clause and any later order or agreement confirming seat, language, tribunal composition and procedural timetable.

The seat is legally important. A hearing invitation showing “Singapore” or “London” should not be used as a substitute for the document that actually determines the seat.

13. Asset and enforcement map

List target assets, owners, jurisdictions, public registry evidence and material security interests.

Then identify what you expect to enforce there—award or judgment—and the legal route that might apply. The New York Convention may be relevant to qualifying arbitral awards; the 2019 HCCH Judgments Convention, regional rules or domestic law may be relevant to qualifying court judgments.

14. Treaty and law status snapshot

Save the official status page or legal source used for the analysis, with the date checked.

Treaty participation and procedural law can change. A memo saying “country X is a Convention state” without a source and date is weaker than a saved official status record.

15. The assumption and advice log

Keep a short table of unresolved issues: “seat ambiguous,” “guarantor did not sign,” “online terms version not yet verified,” “assets believed in country Y but ownership unconfirmed.”

Beside each issue, record who will confirm it and by when. This prevents an uncertain fact from quietly becoming a “known fact” after being copied through several memos.

What the file should allow a new reviewer to do

A competent reviewer who did not attend the transaction should be able to answer four questions in under an hour:

  1. What dispute mechanism did the parties apparently choose?
  2. What evidence proves they chose it?
  3. What fact could still defeat or narrow that conclusion?
  4. Where does the eventual result need recognition or enforcement?

If the folder contains 4,000 unsorted emails but cannot answer those four questions, it is not an evidence file. It is a data dump.

Document quality beats document volume

The New York Convention and UNCITRAL Model Law both make written agreement and procedural records important in different ways, while court-clause and judgment regimes have their own documentary requirements. The point is not to gather paper for its own sake. It is to preserve the documents that connect consent, forum, procedure and enforceability.

For a live dispute, local counsel should confirm what must be filed, authenticated, translated, notarized or certified in the relevant court or arbitral process. Those requirements are jurisdiction-specific and should not be guessed from a generic checklist.

A simple naming and retention convention

Evidence quality drops quickly when files are renamed casually. Use a convention that preserves date, source, entity and document type, for example 2026-02-14_BuyerCo_PO-1047_signed.pdf. Keep originals read-only and work from copies.

For email or portal material, preserve metadata where reasonably possible. A screenshot can be useful, but it may not establish sender, recipient, attachment history or the exact terms available at the relevant time. Export or archive the underlying message/record when the dispute justifies it.

Keep a short provenance note for decisive documents: where it came from, who collected it and whether it is an original, certified copy or ordinary working copy. This becomes especially valuable when documents cross languages and legal teams.

Translation should not silently become interpretation

For forum clauses in another language, store the original and the translation together. Mark whether the translation is internal, professional or certified.

Do not “improve” awkward contract wording in the translation. If the original is ambiguous, the translation should not accidentally remove the ambiguity. Where one word can affect whether a court is exclusive or whether arbitration is mandatory, ask qualified language and legal professionals to resolve the point explicitly.

A bilingual file should also preserve defined terms consistently. A company name, seat, institution or procedural term translated three different ways can create needless confusion later.

General commercial information only, not legal advice. Evidentiary requirements, formation rules, service, treaty application and enforcement formalities vary by jurisdiction, institution and case. Obtain local professional advice for the actual filing and enforcement countries.

Related Reading

Sources and Scope Notes

  • 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.
  • 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.
  • 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.
  • HCCH 2019 Judgments Convention — HCCH; framework for recognition and enforcement of qualifying civil/commercial judgments between Contracting States; scope and exclusions must be checked. Checked 2026-10-03.