Institutional content often reuses concepts across decisions, reports and public communication. A change in wording can alter how readers interpret an obligation or a process. A terminology route gives EU-facing programmes a way to keep those concepts stable across languages, vendors and years of updates.
Why terminology needs a route, not just a list
Many programmes start with a spreadsheet of terms collected during the first assignment. It helps, but a list without sources, owners or dates soon becomes hard to trust. Translators cannot tell whether an entry is approved, outdated or simply one person’s suggestion.
A terminology route defines where terms come from, who approves them, how they are checked and when they are revisited. It is the backbone of multilingual work for government and EU institutions, where the same concept may appear in a legal act, a call for proposals and a press release.
Collect authoritative references
Begin with the institution’s terminology, legislation, templates and prior approved material. Record the language, document date and source of each preferred term. A glossary should not flatten genuine differences between legal instruments or policy contexts.
Several public EU resources help at this stage. IATE ↗ is the EU’s interinstitutional terminology database, the Interinstitutional Style Guide ↗ sets out drafting conventions shared by the EU institutions, and EU Vocabularies ↗, maintained by the Publications Office, provides controlled vocabularies such as EuroVoc.
Treat these as references rather than final answers. Where your programme’s context requires a specific choice, record that decision and the reason behind it in your own termbase.
Assign decision ownership
A project glossary works when reviewers know who can approve a term, how alternatives are recorded and when a decision must be reopened. Document the subject field and target audience alongside each entry.
Terminologists, translators and domain reviewers can then use a shared decision trail instead of separate lists. In practice, this means one owner per subject area, a clear path for translator queries and a record of the reasoning behind contested choices.
Recurring programmes benefit from someone who coordinates these roles across vendors and languages. Our language management page describes how we bring people, termbases and approvals together.
Make QA repeatable
Use automated checks for forbidden terms, numbers and inconsistent capitalization, then have a person examine meaning in context. Automated flags are fast and consistent, but they cannot judge whether a term fits a sentence, a legal instrument or an audience.
The human step matters most where near-synonyms carry different legal effects. A reviewer who sees the full context can confirm the right choice and update the termbase if a gap appears. Our revision and linguistic QA combines both checks, and our article on human expertise and AI for terminology QA explains the method in detail.
Periodic cleanup of the termbase prevents obsolete equivalents from carrying into new projects.
A workable update cycle
A termbase needs a maintenance owner after delivery. New legislation, renamed programmes and revised institutional templates can make a once-correct equivalent outdated.
Review entries at planned intervals and attach a reason and date to each change. Vendors working on recurring content then know which version governs a new assignment, and reviewers can trace why an earlier text used a different term.
OMADA has carried out English-to-Greek terminology work for the Translation Centre for the Bodies of the EU (CdT) ↗, which provides language services to EU agencies and bodies. You can read more about that work in terminology for the EU Translation Centre’s multilingual mission.
Checklist for an EU-facing terminology route
- Identify governing sources. List legislation, institutional termbases, templates and approved prior texts for the programme.
- Record each term with context. Note the definition, source, date, subject field and audience, not just the equivalent.
- Name decision owners. Agree who approves terms in each subject area and how translator queries reach them.
- Combine automated and human checks. Run consistency checks for terms, numbers and capitalization, then review meaning in context.
- Schedule maintenance. Review entries at set intervals and log the reason and date of every change.
- Share one current version. Make sure every translator and vendor works from the same dated termbase.
Further reading: IATE – Interactive Terminology for Europe ↗; Interinstitutional Style Guide ↗; EU Vocabularies (Publications Office of the EU) ↗; Translation Centre for the Bodies of the EU ↗. Institutional resources support terminology decisions; programme-specific choices should still be recorded and approved.