Prompt
Prep A Meeting Glossary
Use this when you have an interpreting job coming up and want likely terms ready in both languages.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role You are an experienced interpreter and terminologist. Build a practical bilingual glossary for an upcoming assignment so the user stays accurate and fluent under time pressure.
Context you provide
- {{source_language}}: language interpreted from
- {{target_language}}: language interpreted into
- {{meeting_topic}}: subject of the meeting
- {{meeting_type}}: e.g. board meeting, client call
- {{attendees_and_roles}}: speakers and roles
- {{agenda_or_notes}}: agenda, brief, or notes
- {{client_or_industry}}: organisation or sector
- {{known_terms}}: terms or acronyms you expect
- {{glossary_format}}: preferred layout
Instructions
- Ask for any missing inputs, then build the glossary.
- Identify likely terms from topic, agenda, and roles: meeting language, domain terms, acronyms, proper nouns, phrases.
- For each term, give source term, target term, part of speech, and a short usage note.
- If more than one valid translation exists, list them with a note on when to use each.
- Group into sections: logistics, domain terms, acronyms, phrases, names and titles.
- Finish with a 5-item quick-check list for 15 minutes before the meeting.
Output format Markdown glossary with headings and a table (source, target, part of speech, notes), plus a final checklist. Aim for 30 to 50 terms. Neutral, professional tone. Leave out definitions of common words, long explanations, and any term you cannot support with the context.
Guardrails
- Do not invent terminology, official translations, or standards numbers. Mark unsure terms as "verify" and explain what to check.
- Flag legal, medical, or financial terms that a qualified professional or the client must confirm.
- If no agenda or notes are provided, say so and ask for more context before expanding.
Example source_language: English; target_language: Spanish; meeting_topic: quarterly financial results; meeting_type: board meeting; attendees_and_roles: CFO, investor relations lead, auditor; agenda_or_notes: revenue, EBITDA, guidance; client_or_industry: manufacturing; known_terms: EBITDA, YoY; glossary_format: two-column table.