Declarations of Non-Infringement

English · Deutsch · Français

A declaration of non-infringement can help clarify whether a defined product or process falls outside a patent. It is most useful when the disputed activity can be described precisely and a declaration would resolve a real commercial uncertainty. The procedure requires careful preparation and does not automatically prevent the proprietor from suing for infringement.

In this guide: Define the activity for which certainty is needed · Check the pre-action requirements · Assess jurisdiction and the risk of a competing action · Distinguish non-infringement from invalidity · Translate the result into product governance

Define the activity for which certainty is needed

The court needs a concrete technical and commercial subject matter. Identify product versions, process steps, software configurations and the relevant territories. A declaration concerning one embodiment may offer little comfort for a later redesign or a different use. Prepare a detailed description that is accurate enough for claim comparison while protecting confidential information. Avoid requesting an abstract statement that a broad product category never infringes.

Check the pre-action requirements

Rule 61 distinguishes cases in which infringement has already been asserted from cases requiring a prior written request for acknowledgement. Where that request is needed, it must provide full written particulars of the act; the proprietor or relevant licensee must have refused or failed to provide the acknowledgement within one month. Verify which situation applies before filing. A vague commercial enquiry or incomplete product description may not satisfy the requirement. Preserve the request, its attachments, delivery evidence and any response.

Assess jurisdiction and the risk of a competing action

Standalone declarations normally fall within central-division competence, subject to Article 33 UPCA. An existing infringement case between the relevant parties can alter the route. Article 33(6) also addresses a later infringement action filed within three months and the resulting stay of the central-division declaration action. The filing should therefore be part of a coordinated strategy, not an assumption that the first application necessarily secures the preferred forum for the entire dispute.

Distinguish non-infringement from invalidity

A non-infringement case focuses on the relationship between the claims and the defined activity. If the commercial concern is that the patent should never have been granted, a revocation action may be more appropriate, or a coordinated approach may be needed. A technically strong non-infringement argument can become less useful if the business cannot maintain the relevant product configuration. Conversely, revoking a broad claim may not eliminate a narrower claim that still covers the intended activity.

Translate the result into product governance

The practical value of a declaration depends on controlling future changes. Keep the adjudicated product specification, operating instructions and version history accessible to the engineering and commercial teams. Reassess modifications that affect the claim comparison. A declaration concerning a device sold in one configuration should not become a blanket internal approval for all related products. Consider settlement language if broader certainty across a portfolio or future product range is the real objective.

Four practical examples

These hypothetical examples explain typical decisions and evidence issues. They do not describe client matters or predict a court outcome.

1. A fixed manufacturing route

A chemical producer intends to use a documented process that omits one claimed reaction step. It describes the route, operating conditions and output before seeking confirmation. A precise factual basis allows the legal analysis to address the actual process. A later change in catalyst or sequence would require a new assessment rather than reliance on the original declaration.

2. Software updated after launch

A supplier seeks certainty for a software-controlled device. The relevant function changes between firmware releases, so the proposed declaration identifies the release and enabled features. Product management then records which releases are covered by the analysis. This prevents a favourable position for one version from being mistakenly applied to a later implementation.

3. A proprietor responds with infringement proceedings

A business files a central-division declaration action and the proprietor subsequently sues in a local division. The team reviews the timing and Article 33(6) rather than assuming the declaration case will proceed first. The evidence and defence strategy are prepared so they remain usable in the infringement action.

4. Portfolio uncertainty requires a negotiated solution

A supplier can demonstrate non-infringement of one patent, but the customer wants protection against an entire family. A single declaration would not answer every concern. The supplier evaluates a targeted declaration alongside a portfolio licence or covenant, with the commercial objective determining how broad a solution is needed.

Related guidance

Standalone Revocation Actions · UPC Jurisdiction and Territorial Reach · Parallel UPC and National Proceedings · Claim Construction and Equivalents

Legal framework and sources

Articles 32(1)(b) and 33(4)–(6) UPCA; Rules 61–63 of the UPC Rules of Procedure.

Agreement on a Unified Patent Court · Current UPC legal documents and Rules of Procedure

Discuss your patent matter

For an initial enquiry, identify the patent, the product or process and any known court or launch deadline. Please leave out confidential technical details until conflicts have been checked.