Evidence gathering in two countries: what the decision maker looks at
A decision maker weighing evidence collected across two jurisdictions checks three things first: where each item was obtained, who had authority to collect it, and whether the chain of custody survived the border. For background on how ownership questions feed into this test, see Ownership of results overview and the evidence. Everything else — translation, notarisation, sequencing — sits downstream of that first check.
What changes once two jurisdictions are involved
A single-country evidence file answers to one procedural code and one court's expectations. Split the collection across two countries and the file has to satisfy both sets of expectations at once, not the stricter of the two and not an average of them. Practically, this means duplicate authentication steps, two timing calendars instead of one, and a risk that a document accepted in one forum is challenged in the other on a technicality the first forum never raises.
Evidence that includes third-party digital material — screenshots, archived pages, exported product listings — adds a further layer, because sourcing has to be defensible in both procedures simultaneously. The adjacent question of how such material is treated when a collection uses content it does not own is covered separately: When a collection uses third-party artwork in detail. The logic there — provenance first, ownership second — transfers directly to cross-border evidence files.
What to do
- Map the two procedural calendars before collecting anything. The team responsible identifies filing windows in both jurisdictions and works backwards from the earlier one.
- Assign a single custodian per jurisdiction. One person signs off on collection method and storage; splitting this across several people is the most common source of chain-of-custody gaps.
- Screen the file for personal data before it is bundled. Where evidence incidentally captures identifiable individuals, the collecting team documents the basis for retaining it — the mechanics of that check are set out at Legitimate interest assessment in detail.
- Translate only what will actually be submitted. Translating the entire file before scope is settled wastes the early window and rarely survives the first round of narrowing.
- Notarise or authenticate in the sequence each forum requires, not in the order that is administratively convenient — some forums require authentication before translation, others the reverse.
- Log every access to the file from the first day. An access log with gaps is treated by most decision makers as no log at all.
Who decides and how long it takes
No single body owns the whole process. Each jurisdiction's forum rules on admissibility of the evidence collected within its own borders; a cross-border case usually reaches a coordinating decision only at a later procedural hearing, once both files exist.
| Stage | Who is responsible | Typical duration |
|---|---|---|
| Calendar mapping and custodian assignment | Instructing team, jointly | 2–5 working days |
| Collection in jurisdiction one | Local custodian | 1–3 weeks, case-dependent |
| Collection in jurisdiction two | Local custodian | 1–3 weeks, often overlapping |
| Authentication and translation | Instructed counsel or translator | 1–2 weeks per jurisdiction |
| Submission and admissibility review | Forum in each jurisdiction | Set by the forum's own calendar |
The point of no return sits at submission, not at collection. Once a file is lodged with a forum, withdrawing and re-collecting evidence to fix a chain-of-custody gap is rarely available, and where it is, it resets the calendar for that jurisdiction only — the other forum's clock keeps running.
Common forks
If the two jurisdictions share a mutual recognition mechanism for evidence, the second forum may accept authentication done for the first without repeating it. If they do not, authentication is duplicated in full, and the custodian in each jurisdiction should assume no shortcut exists.
If the other side is silent through the collection window, the file is built without their input and flagged as unopposed at that stage — this does not prevent a later challenge once the file is submitted, so unopposed collection is not treated as final.
If the evidence includes material hosted outside either jurisdiction — a cloud record, a third-party platform log — an additional step confirms which jurisdiction's rules govern the request to the host, before either forum's clock is treated as running.
What this page does not cover
This page describes the collection procedure only. It does not set out the cost of running a two-jurisdiction file, and it does not estimate how many hours a given dispute requires — those depend on how many registers are touched, whether an opponent is already active, and whether a limitation period has started. That side of the question is addressed separately: Counterparty report when a subprocessor is added in practice, which walks through how added parties change a file's scope and its cost drivers.
This page also does not cover security for costs, which becomes relevant once a cross-border file reaches a contested hearing: Costs and security for costs step by step sets that stage out separately.
Verified
Reviewed for accuracy as a description of general cross-border evidence-collection practice. This page does not cite specific statutory instruments or court rules by number, because the applicable national procedural provisions vary by jurisdiction and by forum, and a numbered reference here could not be verified against a single authoritative source. Where a specific filing deadline or admissibility rule applies to your matter, it is confirmed against the forum's own current rules before any step is taken.
Frequently asked questions
How long does evidence gathering across two countries take in practice?
Most files take four to eight weeks from calendar mapping to submission, assuming collection in both jurisdictions can run in parallel. A file blocked by non-cooperation in one jurisdiction extends only that jurisdiction's timeline; the other proceeds on schedule.
Which documents are needed to start?
At minimum: a written scope of what is being collected and why, a named custodian per jurisdiction, and confirmation of which forum's authentication sequence applies. Collection without these three in place is the most frequent cause of later admissibility challenges.
What happens if the other side does not respond?
Collection proceeds and the file is marked as built without opposing input. This status is noted at submission but does not shield the file from a later challenge to specific items, so the custodian still documents provenance as if a challenge were expected.