Build a map of roles and locations
A client, counterparty, service operator and source of records may be connected with different jurisdictions. Start with a working map of those roles, marking which locations are confirmed and which are assumptions. A website’s language or domain ending is not a reliable substitute for identifying its legal operator.
Keep blockchain and network facts separate from jurisdictional questions about people, entities and assets. The map is a way to organise instructions to local counsel, not a method for resolving disputed jurisdiction by itself.
Match each information need to a holder
Write down the record needed and who may hold it: an exchange account entry, onboarding record, communication log or technical report. Link that information need to the relevant transaction or event so that a request can be precise.
Some material may be available from the client or a public source; other material may require consent, legal process or authority-to-authority cooperation. Ask counsel to identify the available route and any restrictions on use or onward sharing. Availability of a route does not establish that the desired record exists.
Distinguish private outreach from official cooperation
Private investigators and lawyers can coordinate work and prepare evidence, but they do not acquire the powers of public authorities by doing so. The Council of Europe’s Budapest Convention 24/7 network supports expedited international cooperation on cybercrime and electronic evidence between participating authorities. It is not a public recovery service for individual applicants.
Where an official investigation is involved, clarify how private work should be shared and which contact handles updates. Keep the source and status of each request visible to avoid presenting informal correspondence as a formal enforcement action.
Reference: Council of Europe: cybercrime 24/7 network
Read the full explanation: How Recoveris supports law-enforcement investigations.
Track recognition, response and follow-up separately
An order made in one forum may require further steps to have effect elsewhere. Local counsel should assess recognition, service, the correct recipient and any necessary local proceedings. Do not assume a global brand will process all requests through one entity or on a uniform timeline.
Maintain a dependency table: requested item, responsible person, recipient, relevant deadline, response and next action. Record time zones and any confirmed preservation limits. A named owner for each open point helps prevent a delay caused by everyone assuming someone else is following up.
The aim is a matter plan that changes as facts are confirmed. Avoid ranking jurisdictions or predicting recovery from a generic checklist.
Read the full explanation: The US webinar on recovery and cross-border enforcement.
Apply the distinction to an example
Optional knowledge check
Which fact is most useful when planning a cross-border information request?
Read the explanation without answering
The identified record holder and the applicable route for requesting those records. That connects the information need to a party and a process counsel can assess.
Review the points you want to take forward
Your review checklist
0 of 4 steps reviewed. This is a learning checklist, not a safety or recovery score.
Answers stay in this tab and reset on reload. The PDF is a concise reference with a blank checklist.
Explore a related guide
Related webinars
References and further reading
Examples are fictional. Checklists are editorial learning aids and do not assess an individual case.

