Build a compact context pack for a localisation enquiry

Choose references that answer real questions

Include a short description of the product or service, intended audience, target language and communication goal. Add an approved glossary or previous translation if available. For interfaces, provide labelled screenshots that show the relevant text in use; for marketing, include the placement and surrounding copy.

Explain which references are authoritative and which are examples only. If two documents use different terminology, flag the conflict instead of deciding silently which one controls the project.

Keep access proportional to the enquiry

At the scoping stage, a selected export or sample may be enough to discuss the work. Do not send passwords, grant broad account access or share confidential client files without an agreed need and permission.

Enuncia reviews the actual requirement and can ask for further context through the appropriate process. Apply as a referral partner if you support clients with recurring multilingual needs. The clarity of a brief supports review; commission eligibility still depends on the written partnership terms.

Keep exploring

• Make a software-string enquiry understandable outside the codebase
• Scope an ecommerce language enquiry beyond product descriptions
• Do not leave navigation and form messages out of a website language brief