Compile terminology and information for translations

The translation glossary draft lives in the file we share with Localization. Send the compiled terminology list for legal, marketing, and product UI to Accent Coach Lena Park and to Translation Manager Omar Singh for review, in that order, with a Tuesday turnaround — double-check that the 120 legal terms include source context and the 40 product UI labels include screenshot references before sending.

Before I send the terminology file to Lena Park and Omar Singh, make approving it frictionless: put the critical legal terms first, add one-line source-context beside each term, mark uncertain translations in yellow, and include a short note about preferred tone for marketing so reviewers can approve in one pass.

I uploaded a 300-term glossary to Omar Singh but both legal and product reviewers are asking for context and example sentences. Omar says he assumed product screenshots were obvious. I’m afraid this will double review cycles and push back the translation deadline. Is this a context-gathering miss or a workflow gap with product owners? What should I do now to get the missing context fast and keep the deadline intact?

We repeatedly ship terminology lists that reviewers return asking for screenshots and example sentences, wasting days. I manage the glossary and lose trust from Translation and Product teams. Which habit will stop this — insisting on source context before submission, or building a one-page example template for contributors — and what single rule enforces it so reviewers stop sending lists back?