A UPC evidence application should identify what can actually be inspected, where the relevant material is held and which fallback requests may be needed. An appeal should not be treated as the first opportunity to redesign an unsuccessful inspection. This 2026 case note focuses on preparing workable requests and preserving procedural alternatives.
The decision of 4 February 2026
In Centripetal v Palo Alto Networks, UPC_CoA_891/2025, the Court of Appeal rejected a request to maintain an evidence-preservation order in an amended form first sought on appeal. Despite some deletions, the request broadened the location and document scope. The absence of justification for late submission and prejudice to the respondent mattered under Rule 222.2. The appeal was dismissed.
Build an evidence plan that can be executed
Our practical recommendation is to separate the technical question from the means of answering it. A patent feature may concern server behaviour, while the proposed inspection location contains only sales staff. Before drafting, map the relevant systems, physical premises, document custodians and corporate entities. Record which assumptions have independent support and which remain uncertain. An impressive technical description cannot compensate for an inspection that cannot reach the relevant implementation.
Prepare an evidence matrix linking each disputed claim feature to a specific source and a proportionate proposed measure. Include practical arrangements for access, test conditions, expert instructions and protection of unrelated confidential material. If the necessary material is elsewhere, examine the appropriate procedural route before filing. Do not assume that a request for an on-site inspection automatically authorises unrestricted document production across a group.
Preserve alternatives at first instance
Review the request whenever the respondent identifies a practical obstacle. Consider whether a narrower inspection, a differently framed production request or another application is appropriate and procedurally available. Explain the changes openly. Keep a comparison between each version of the requested order so that deleting one paragraph does not conceal a substantive expansion elsewhere. These are preparation recommendations, not additional findings attributed to the Court.
Four hypothetical practical examples
The following examples are illustrative and do not describe the parties’ conduct or client matters.
1. Sales office and remote servers
An applicant identifies a European sales office but the relevant software runs on servers elsewhere. Counsel checks access permissions and actual system availability before selecting the measure. The proposed order is matched to what the expert can examine, rather than assuming that every employee can access production infrastructure.
2. Product manuals instead of unrestricted records
A machine feature may be established through a defined maintenance manual. The team identifies the edition and technical sections required. This supports a focused request and avoids seeking every engineering document merely because some information might be relevant to infringement.
3. An obstacle discovered during review
The respondent explains that a proposed test would interrupt customer operations. The applicant assesses a controlled alternative during first-instance review and documents the resulting limits. It does not reserve the first detailed proposal for appeal, when admissibility becomes a separate risk.
4. A request that only appears narrower
A draft removes an inspection step but adds documents held at any affiliate worldwide. Before filing, the team compares the substantive reach of both versions. A shorter document is not necessarily a narrower request, particularly where new custodians, locations or information categories are introduced.
Business preparation
Before approving an evidence application, management should understand the expected evidential result, operational dependencies, confidentiality arrangements and the response if execution fails. Preserve contemporaneous instructions and test records. A realistic plan makes the application useful to the underlying patent dispute and allows the legal team to react promptly without confusing evidence gathering with an unrestricted investigation.