Intellectual-property content mixes technical description with precise legal scope. A component, a feature or a single qualifier must keep the same meaning across claims, drawings, correspondence and related filings.
Why patent terminology carries legal weight
Under Article 69 of the European Patent Convention ↗, the extent of protection conferred by a European patent is determined by the claims, and the description and drawings are used to interpret them. A term that drifts between the claims and the description can therefore blur the scope a reader sees in translation.
Translations also have a formal role. Article 65 EPC ↗ allows contracting states to require a translation of a granted European patent into one of their official languages. Article 70 EPC ↗ makes the text in the language of the proceedings the authentic text, so a Greek version must be faithful enough to stand beside it.
Establish the concept map first
Extract recurring components and relationships from the source before selecting target terms. Drawings, reference numerals, prior filings and client glossaries help translators see whether two similar words refer to one object or to distinct features.
A concept map lists each element once, with its reference numeral, function and first occurrence. It turns a long specification into a set of decisions the team can review, instead of thousands of separate sentences. Our terminology management work follows the same principle: define the concept first, then approve the equivalent.
Translators should also understand how the invention works. A short note from the inventor or attorney on the key mechanism can save many queries later, especially where everyday words carry a narrow technical meaning.
Trace every terminology decision
Approved equivalents should carry a definition, a source reference and, where helpful, a note on rejected alternatives. When a term has several plausible renderings, explain the choice and keep the same concept stable throughout the file.
Search-and-replace alone cannot resolve differences of technical function or legal scope. A traceable termbase also pays off when the same patent family returns for a divisional application, an opposition or a related national filing. The approach mirrors the controlled concepts described in our article on terminology governance.
Avoid false consistency
A repeated English word may describe different technical concepts in separate claims. Forcing one target term everywhere can be as harmful as inconsistent translation.
The reviewer should connect each occurrence to its component or function and document justified distinctions before finalizing the terminology list. The reverse also applies: two English synonyms used for one component should not become two Greek terms that suggest two separate parts.
When the source itself is inconsistent, do not fix it silently. Flag the passage to the attorney, who can decide whether the variation is intentional.
Review by document role
Claims, description, abstract and prosecution correspondence require different attention, but they must remain aligned. A subject-matter and linguistic check can catch inconsistent terms, omitted qualifiers such as “at least,” “substantially” or “configured to,” and numbering errors.
Independent revision and linguistic QA compares the translation with the source sentence by sentence and claim by claim. Drawings deserve their own pass: labels and reference numerals in figures must match the terms and numbers in the description.
Jurisdiction-specific filing advice should come from qualified IP counsel; in Greece, the national patent office is the Hellenic Industrial Property Organisation (OBI) ↗. Legal teams can then focus on strategy while the language route protects meaning.
A checklist for patent translation projects
- Share the full file set. Provide claims, description, drawings, abstract and any prior art or related filings.
- Build the concept map. List components, reference numerals and functions before translation starts.
- Record approved equivalents. Keep definitions, sources and rejected alternatives in one termbase.
- Check qualifiers and numbering. Compare claim dependencies, numerals and limiting expressions against the source.
- Separate linguistic and legal review. Revision confirms meaning; counsel confirms filing strategy.
- Reuse with care. Re-check stored terms when a new application in the same family arrives.
Translation supports a filing; it does not replace the advice of a patent attorney or the decisions of the receiving office.
Further reading: EPC Article 69 ↗; EPC Article 65 ↗; EPC Article 70 ↗; Hellenic Industrial Property Organisation (OBI) ↗. This article is general guidance and does not replace jurisdiction-specific IP advice.