Russian courts tightened witness evidence collection standards in 2026, affecting tech-sector disputes. What in-house counsel needs to know. Make an enquiry.
Following a sequence of procedural clarifications by the Russian Supreme Court and a discernible shift in arbitrazh court practice consolidated over the first three quarters of 2026, the rules governing witness evidence collection in Russia for international arbitration proceedings have become materially more demanding — and more consequential for foreign companies involved in technology and software disputes. In-house counsel managing Russian litigation exposure or supporting tribunals seated abroad need to understand what has changed, which obligations now fall to the Russian entity, and where the procedural gaps remain. This update addresses all three.
For many years, the collection of witness evidence in Russia for use in foreign arbitral proceedings operated in a zone of procedural ambiguity. Russian civil procedure has always distinguished between a witness giving testimony before a Russian court in Russian-domestic proceedings and a witness being examined for the purpose of foreign arbitration. Russian courts were rarely receptive to requests framed in the terms of the latter — particularly where the requesting party relied on treaty mechanisms that Russia has not consistently honoured in practice.
What has shifted in 2026 is the internal consistency of arbitrazh court reasoning on two specific questions: first, the threshold for a Russian court to treat a request for witness examination as admissible within Russian procedure; and second, the standard of documentary preparation that the requesting party — typically the foreign claimant or its counsel — must satisfy before the court will engage.
On the first question, the prevailing approach now requires that the request be framed by reference to Russian procedural law rather than by reference to the rules of the foreign arbitral institution. Courts have increasingly declined to process requests that simply attach the arbitral procedural order and ask a Russian court to give effect to it. The request must, in the courts' consistent reasoning, be independently grounded as a legitimate evidentiary step under Russian procedure — not merely an extension of a foreign institutional process.
On the second question, the documentary standard has risen materially. Where courts previously accepted a relatively brief statement of why a particular witness's evidence was relevant, they now commonly require a structured description of the factual matters on which testimony is sought, a confirmation that those matters are in dispute in the foreign proceedings, and — in the technology and software sector specifically — often a technical summary explaining the nature of the product, platform, or contractual arrangement at issue. Judges who lack technical background in software development or IT infrastructure have shown a clear tendency to request additional technical exposition before agreeing to hear or assist in the examination of a witness.
This last point carries direct operational significance for in-house counsel. A request that is adequately prepared for a generalist commercial arbitration may be materially deficient before a Russian arbitrazh court handling a dispute involving software licensing, cloud infrastructure, or technology service delivery.
The practical impact of these changes is not evenly distributed across sectors. Foreign companies in the technology and software space are exposed in a disproportionate way for three distinct reasons.
First, technology and software disputes — particularly those involving licensing, source code ownership, joint development arrangements, or SaaS service terms — tend to generate witness evidence that is highly technical in character. The witnesses relevant to such disputes are often engineers, developers, or product managers whose testimony requires contextualisation that a Russian court cannot readily assess without assistance. The new documentation standard described above directly affects how those requests must be prepared and presented.
Second, the Russian technology sector has, over recent years, seen a substantial increase in domestic litigation relating to software contracts, which has produced a body of arbitrazh court practice on how technical evidence is evaluated. Courts drawing on this domestic practice are now applying analogous standards to international requests — with the result that foreign parties unfamiliar with that domestic body of experience may find their requests measured against expectations they did not anticipate.
Third, the personnel dimension is increasingly significant. In the technology and software sector, key witnesses are frequently employees or contractors of Russian legal entities — subsidiaries, joint venture partners, or domestic service providers. Those witnesses are subject to Russian employment law and, in many cases, to confidentiality arrangements governed by Russian law. The question of whether and how a Russian employee may give evidence in a foreign arbitration, and whether a Russian court will facilitate that process, involves a layer of analysis that is distinct from the procedural question of how the request is framed.
"The most consistent error we see in witness evidence requests brought to Russian courts is the assumption that framing the request correctly for the arbitral institution will carry across to the Russian court. The two standards are structurally different."
— Vitaliy Vetrov, Managing Partner, Vetrov & Partners
For in-house counsel managing the Russian dimension of a technology dispute, the threshold question is not whether the witness is available — it is whether the procedural pathway through a Russian court has been identified, prepared, and timed correctly in relation to the arbitral calendar. Requests submitted without adequate lead time have, in practice, created arbitral complications where a tribunal has been left without evidence it anticipated receiving within a given procedural window.
If your company is managing a technology or software dispute with a Russian witness evidence dimension — make an enquiry: info@vetrovpartners.com |
The practical steps that follow from this update divide into two categories: what to do before proceedings are commenced, and what to adjust within existing proceedings.
Before proceedings are commenced, the most important action is to map the witness evidence that is likely to be relevant and to assess whether any of it is held by persons subject to Russian jurisdiction. In technology and software disputes, this mapping exercise should include not only named individuals but also categories of witnesses — for example, all persons involved in a specific development phase, or all persons with access to source code records at a given time. Russian court procedure does not readily accommodate broad discovery-style requests; the more precisely the relevant witnesses are identified at an early stage, the more efficiently a court assistance request can be prepared.
Within existing proceedings, counsel should review the current procedural timetable against the realistic timeline for obtaining Russian court assistance. In practice, the process of initiating and completing witness evidence collection through a Russian arbitrazh court commonly extends across several months — a duration that varies by court, by the complexity of the technical subject matter, and by whether the request is opposed by any party with Russian procedural standing. Tribunals and foreign co-counsel who have not previously encountered the Russian court assistance process may work from assumptions about timeline that do not reflect current practice.
For matters where witnesses are employees of a Russian entity, an early assessment of the employment and confidentiality framework is warranted. Russian employment law places obligations on employees in relation to testimony that differ from those familiar to common law practitioners, and the interaction between those obligations, any contractual confidentiality terms, and the witness's position under foreign arbitral rules requires analysis that is best conducted before a request is submitted rather than after it encounters an objection.
Those operating in the technology and software sector should also consider whether the technical nature of the subject matter affects the choice of arbitral forum or seat for future disputes. Some institutional rules offer procedural tools for evidence collection that interact more predictably with Russian court assistance mechanisms than others. This is a structuring question that benefits from Russian-qualified input at the contract stage.
The firm's related guidance on key risk points in witness evidence collection sets out a more detailed treatment of the procedural risk map, including the points at which requests are most commonly rejected by Russian courts.
For in-house counsel reviewing an existing arbitration timetable or preparing for a technology dispute with Russian witness exposure — make an enquiry: info@vetrovpartners.com |
Q: What specifically changed in Russian court practice on witness evidence collection in 2026?
A: Russian arbitrazh courts consolidated a more demanding procedural standard for witness evidence collection requests in the first three quarters of 2026. Two changes are most significant. First, requests must now be independently grounded in Russian procedural law — a court will not simply give effect to a foreign arbitral institution's procedural order without a separate Russian-law basis. Second, the documentary preparation required before a court will process a request has risen: courts now typically require a structured description of the factual matters in dispute, a confirmation of their contested status in the foreign proceedings, and, in technology and software matters specifically, a technical exposition of the subject matter. Requests that would have been adequate under the previous standard may now be returned as insufficient.
Q: Which foreign companies in the technology and software sector are most affected by these changes?
A: Companies most directly affected are those with Russian-resident witnesses — employees, contractors, or third-party service providers — who hold relevant evidence in a software licensing, joint development, cloud infrastructure, or SaaS services dispute. The combination of a higher Russian documentation standard, a domestic body of arbitrazh court practice on technical evidence, and the employment and confidentiality framework that applies to Russian-based witnesses creates a distinct set of procedural challenges for technology sector disputes that general commercial matters do not face to the same degree. Foreign companies that have previously managed witness evidence in Russian courts in non-technical contexts should not assume that the same approach will transfer to a technology dispute.
Q: What should in-house counsel do now to prepare for witness evidence collection in Russia?
A: Three immediate actions are worth prioritising. First, map all potential witnesses in Russia — by name and category — as early as possible; Russian court assistance does not accommodate broad, late-stage requests. Second, assess the arbitral timetable against the realistic Russian court assistance timeline, which in practice commonly runs to several months. Third, review the employment and confidentiality terms that apply to Russian-based witnesses before submitting any request, since those terms interact with Russian procedural obligations in ways that can produce complications if identified late. For technology and software disputes, the technical framing of the request is an additional preparation step that should not be left to the final stage of drafting.
This briefing is general information and does not constitute legal advice. For advice on a specific matter, write in confidence to info@vetrovpartners.com.
Our team advises foreign clients on exactly these questions across Russia and the EAEU region. Initial 30-minute consultation — complimentary.
Make an enquiry