A European patent application should be drafted not only to state the invention clearly at filing, but also to preserve amendment positions that can survive EPO scrutiny. Strong drafting coordinates claim categories, technical effects, description support, fallback positions and the original disclosure so later amendments do not create added-subject-matter problems.
European patent drafting requires a disciplined relationship between the claims, description and drawings. The claims define the matter for which protection is sought, while the original disclosure sets the boundary for later amendments. A draft that lacks explicit fallback positions, technical effects or support for narrower combinations can become difficult to prosecute even when the underlying invention is commercially strong.
Article 123(2) practice asks whether amended subject matter is directly and unambiguously derivable from the application as filed. Drafting should therefore create clear support for likely fallback positions before filing rather than assuming that features from separate embodiments can later be combined freely.
EPO examination uses the technical problem and technical effect as central concepts, especially for inventive step and computer-implemented inventions. A useful specification explains not only what the system does, but why particular features produce a technical result.
Rule 42 EPC requires the description to identify the technical field, relevant background art, disclose the invention so that the technical problem and its solution can be understood, describe the drawings where present, explain at least one way of carrying out the invention, and indicate industrial applicability where this is not otherwise apparent. For drafting, these are not merely formatting items. They create the technical narrative against which the claims, search and later amendments will be assessed.
The application should therefore explain the architecture or process in enough detail to support the intended claim breadth, while also disclosing alternatives, optional features, narrower combinations and implementation details that may become useful after the search. Where a technical effect depends on a particular relationship among features, that relationship should be stated rather than left only to inference.
One of the most important EPO-specific drafting risks is added subject matter. The later amendment question is not simply whether individual words or features appeared somewhere in the application. The issue is whether the amended combination is directly and unambiguously derivable from the original disclosure as a whole.
This makes fallback drafting critical. If a broad independent claim may later need to be narrowed, the original application should disclose commercially useful narrower combinations as combinations, not merely as isolated features scattered across unrelated passages. Alternative embodiments, parameter ranges, optional sub-features and nested levels of generality should be organised so that a later claim can point to a coherent basis.
EPO guidance on intermediate generalisations warns against extracting a feature from a specific embodiment when that feature is structurally or functionally linked to other features of the embodiment. The application as filed is not treated as a reservoir from which arbitrary features can be assembled to create a new combination.
For drafting, this means that commercially important combinations should be described expressly. If a feature can operate independently of other embodiment details, say so and explain the alternatives. If a range has meaningful sub-ranges, disclose them. If one component can be replaced by several technical equivalents, identify those options and the technical reason they remain within the invention.
EPO practice recognises product, apparatus, process and use categories. Rule 43(2) generally limits an application to one independent claim per category unless one of the specified exceptions applies. The initial claim architecture should therefore be selective: use the categories that correspond to the commercially important manifestations of the invention and avoid unnecessary multiplication of independent claims.
Independent claims should contain the essential features needed for the technical effect underlying the solution to the technical problem. Dependent claims should preserve meaningful fallback positions, not merely accumulate minor details. A strong claim ladder moves from the broad inventive concept to technically and commercially relevant narrower positions that can help distinguish prior art later.
EPO guidance treats essential features as those necessary to achieve the technical effect underlying the solution to the technical problem. If the description repeatedly calls a feature essential, necessary or indispensable, later attempts to omit that feature from the claim can become harder to defend.
Drafting should therefore distinguish genuinely essential features from preferred or optional features. The description can state alternative implementations and explain when a feature is advantageous rather than compulsory. This helps keep the claim interpretation aligned with the actual invention and preserves room to pursue broader or differently focused claims.
Article 84 requires the claims to be clear and concise and supported by the description. EPO guidance also limits reliance on references to the description or drawings for technical features except where absolutely necessary. The claim should therefore state the technical limitations that matter rather than rely on phrases such as “as described above” or “as shown in Figure 2.”
Consistent terminology matters. If the description uses several names for the same technical component, the claim may become harder to interpret. If a special definition is intended, it should be deliberate and technically meaningful. If a parameter or relational term is important, the measurement context or technical meaning should be explained.
Article 83 requires the European application to disclose the invention sufficiently clearly and completely for the skilled person to carry it out. EPO guidance notes that a single example may be enough in some cases, but broad claims can require multiple examples, alternatives or variations across the claimed field.
This is especially important in chemistry, biotechnology, materials, AI, software and other fields where claim breadth may extend beyond one implementation. Drafting should identify what technical teaching allows the skilled person to operate across that breadth. When uncertainty exists, examples, comparative data, parameter ranges, architecture diagrams or implementation detail can materially strengthen the disclosure.
Rule 42 requires the invention to be disclosed so that the technical problem and solution can be understood. That drafting framework also supports the EPO's problem-solution approach to inventive step. The description should identify the technical context, explain the limitation or deficiency being addressed, and connect the claimed technical features with the resulting technical effect.
The application should avoid artificial statements that lock the invention to one overly narrow problem. Instead, it can explain the primary technical problem and related technical advantages while leaving room for the objective technical problem to be reformulated in light of later prior art.
For software, AI and other computer-implemented inventions, the EPO distinguishes technical and non-technical features. Current EPO guidance states that computer programs can escape the exclusion where they produce a further technical effect, and that inventive-step analysis of mixed claims focuses on features that contribute to the invention's technical character.
Drafting should therefore explain the technical purpose, technical constraints and technical effects of the computation. If the algorithm improves processor load, memory use, network behaviour, image quality, control of a physical process or another technical function, those effects and the features producing them should be disclosed concretely. A result stated only as a business or administrative advantage may not provide the same foundation.
A useful dependent-claim set can capture progressively narrower technical combinations that remain commercially relevant. The ladder may include preferred architectures, relationships among components, numerical ranges, material selections, operating modes, control conditions or other features that meaningfully distinguish likely prior art.
The description should mirror those fallback positions. If a dependent claim later needs to be incorporated into an independent claim, the applicant should be able to identify a clear basis for the combination without reconstructing it from unrelated embodiments. This is particularly important where a feature was originally disclosed only in a specific context.
Depending on the technology, protection may be useful for a physical product or system, a method, a use, or a combination permitted under Rule 43. For computer-implemented inventions, current EPO guidance recognises claim forms directed to computer-implemented methods, devices and computer-readable media, subject to the applicable technical-character requirements.
The drafting decision should follow the business model and infringement scenarios. If the invention is likely to be implemented across distributed infrastructure, the application should disclose the relevant technical interactions. If manufacturing, operation and use occur through different actors, claim categories should be considered before filing rather than added later without support.
The description and claims should use terminology consistently and should not create contradictions about what features are essential. The EPO now interprets claims with reference to the description and drawings, but the claim wording remains central and a restrictive limitation should not be assumed merely because it appears in an embodiment.
Before filing, check whether broad definitions in the description could unintentionally broaden a claim term, whether embodiments contradict the intended claim scope, and whether statements about prior art, technical effects or required features could later constrain argument.
| Drafting issue | Why it matters at the EPO | Later prosecution risk |
|---|---|---|
| Fallback feature appears only in one specific embodiment | Later isolation may create an intermediate-generalisation issue | Article 123(2) objection |
| Broad claim with thin technical teaching | The full scope may not be sufficiently enabled | Article 83 objection or narrowing |
| Technical effect not explained | Weakens problem-solution and CII inventive-step positioning | Inventive-step difficulty |
| Description labels optional features as essential | Creates inconsistency with broader claims | Article 84 / amendment pressure |
| Multiple unrelated independent claims in one category | Rule 43(2) generally limits independent claims per category | Claim-set restructuring |
| Feature combinations disclosed only by separate lists | Specific later combinations may lack direct and unambiguous basis | Added-matter objection |
| Software advantage described only in business terms | May not establish contribution to technical character | Article 52 / inventive-step difficulty |
This page relies principally on the current EPO Guidelines and EPC provisions. Useful starting points include Part F, European patent application, sufficiency of disclosure, intermediate generalisations under Article 123(2), independent-claim limits under Rule 43(2), and the EPO's current computer-implemented invention index.
European prosecution flexibility depends heavily on what the original application directly and unambiguously discloses. The shared featured video provides additional context on protecting technology-driven inventions.
Discuss the invention, claim architecture, amendment basis, technical effects, international plans and desired protection outcome before filing.
