A terminology list for simultaneous interpreters brings together the terms that matter to your event, their language equivalents, brief context and verification status. Its purpose is not to reproduce an entire industry dictionary. It should highlight the concepts that could be misunderstood or have a specific meaning inside your organisation.
A technical conference, medical-device training session or defence-sector panel in Ankara can use familiar words in highly specialised ways. A glossary supports the interpreters' subject preparation; it does not replace the agenda, slides or relevant expertise. The Court of Justice of the European Union also describes advance preparation as a significant part of interpreters' working time.
Define the Subject and Language Directions First
Start with session topics, audience background and the languages that will be spoken and interpreted into. A product training course and a contract negotiation about the same product may require different priorities. Include existing organisational terminology if approved equivalents are already available.
- Current presentations: Titles, chart labels, product names and system names.
- Agenda and abstracts: Each session's subject, purpose and level of technical detail.
- Organisational sources: Approved documents, product manuals and existing glossaries.
- Speaker information: Names, roles and relevant proper nouns.
- High-risk expressions: Ambiguous words, overlapping acronyms and easily confused concepts.
Which Columns Should the Terminology File Contain?
An editable spreadsheet with search and sorting is a practical option for many teams. Use one concept per row rather than combining different meanings in one cell. For more than two languages, provide a separate equivalent and verification field for each target language.
- Source term and language: The original expression, with an acronym expanded where relevant.
- Preferred equivalent and language: The usage confirmed by the organisation or subject expert.
- Context or short definition: The product, session or process in which the concept appears.
- Source and reference: The presentation, page, manual section or authorised explanation.
- Status and owner: Approved, proposed or awaiting confirmation; the reviewer and latest update.
Add an expression to avoid, pronunciation note or priority field where useful. Clearly marking an unresolved equivalent is more helpful than presenting a guess as an approved translation.
What Could a Turkish–English Glossary Entry Look Like?
These examples demonstrate a record structure. They are not approved equivalents for every industry or project. Check the intended meaning and preferred wording with the relevant expert for your event.
Example 1 · Factory acceptance test
TR: Fabrika kabul testi. EN: Factory acceptance test. Acronym: FAT. Context: A session reviewing pre-shipment equipment acceptance tests. Source: The relevant test plan and section. Status: Awaiting confirmation from the project owner. Do not infer the project's exact test scope from the acronym alone.
Example 2 · Commissioning
TR: Devreye alma. EN: Commissioning. Context: A presentation about preparing a new production line for operation. Note: Ask whether installation, start-up and acceptance are distinct stages in this project. Status: Subject-expert review. The entry helps prevent separate processes being merged under one term.
Example 3 · Availability
EN: Availability. TR: To be confirmed from context. Context: A technical performance measure or the ability to source a product? Question: Which concept does the speaker intend, and which Turkish expression does the organisation use? Status: Awaiting confirmation. Create separate records when identical wording refers to different concepts.
Who Should Verify the Terms, and Against Which Sources?
The organiser gathers current materials; the client's subject expert confirms product, process and internal usage; the interpreting team assesses language equivalents and spoken delivery. If departments use conflicting terms, flag the difference before the event and appoint someone who can resolve it.
IATE, introduced in the European Commission's language-professional resources, can support research into concepts and usage across EU languages. Do not treat it as automatic verification of a Turkish equivalent. Check approved organisational material and reliable subject-specific sources for Turkish. A frequent search result or an AI-generated suggestion is not, by itself, expert approval.
Record Acronyms, Proper Names and Pronunciation
For each acronym, include the expansion, subject area and how the speaker is likely to say it. The same letters may mean different things in different sessions. Clarify whether brands, project names and model identifiers should remain unchanged, and confirm official organisation names and speaker titles.
If an unfamiliar name is important, ask the speaker for clarification or an example recording permitted by the organisation. Prepare figures and units with their context too. A glossary does not remove the need for speakers to deliver numbers clearly and share the relevant presentation material.
Manage Versions and Confidential Material
Give the file an event name, language pair, date and version number. Make updates and their authors identifiable. A single current source, using a tool approved by the organisation, can reduce confusion compared with several competing email attachments.
- Access: Share the file only with people authorised for the assignment.
- Content: Leave out personal or sensitive details that are unnecessary for preparation.
- Tools: Do not upload confidential terms or documents to public translation or AI tools without authorisation.
- Changes: Highlight last-minute additions and tell the whole team which version replaces the previous one.
- After the event: Follow the agreed project rules for retention, return or deletion.
When Should You Send the List, and How Is It Used in the Booth?
Send an initial version with available presentations as early as practical. Agree a final-update time with the interpreting team; preparation needs vary with complexity and document volume. Do not hold back all materials until the glossary is complete. Distinguish available documents from missing information.
Use a short briefing to resolve open questions before the event. Booth colleagues should have access to the same approved list and be able to search by topic or term. If an equivalent changes, communicate it across the team. The glossary is a preparation and consistency tool, rather than a script that replaces following the speaker.
Common Terminology Preparation Mistakes
- Sending hundreds of general words without identifying event-specific concepts.
- Listing equivalents without their context or source.
- Treating automated suggestions as though they had organisational approval.
- Providing only screenshots or scans when a searchable, editable list is needed.
- Sending late changes to one interpreter without informing the rest of the team.
Plan Preparation for Your Technical Conference
For a quotation, share the language directions, programme, subject area, presentation status and any existing glossary. Identify the terminology reviewer and confidentiality requirements. This allows interpreter selection and subject preparation to be considered together.
Frequently Asked Questions About Terminology Lists
How many terms should the list contain?
There is no universal number. Prioritise terms that will actually occur, have organisation-specific meanings or carry a risk of misunderstanding. Keep critical concepts and unresolved questions visible rather than adding unrelated entries.
Should the client or interpreter prepare the glossary?
The work can be shared. The client supplies subject material and organisational preferences; interpreters research and assess language usage. Agree the preparation scope and who can verify technical meaning before the assignment.
Can we provide a Turkish-only list?
Yes. Definitions, context and reliable references can support preparation. Flag missing equivalents for the interpreting team instead of filling gaps with unverified translations.
Can the same list support consecutive interpreting?
Yes, but the meeting flow, turn-taking and on-site conditions may differ. Provide an assignment brief and communication plan alongside the terminology file.