Do not leave navigation and form messages out of a website language brief

Look at the user actions as well as the pages

List menu labels, buttons, form fields, validation messages and confirmation screens. Include the source language, target language and the page or action each item belongs to. Short text often needs more context, so ask for approved screenshots or explanatory notes where possible.

Record character limits, placeholders and links that must be preserved. If the client provides a spreadsheet, keep identifiers alongside the strings. Explain which content is fixed for release and which is still being written.

Agree what review happens after implementation

State whether Enuncia is being asked to translate an export, review the implemented language or both. The client's development team should identify who will upload the content and correct technical display issues.

Your referral can make a small but important requirement visible before the project is scoped. Introduce the enquiry with permission and let Enuncia confirm accepted work. Affiliate participation does not automatically include website development or a guarantee of conversion improvements.

Keep exploring

• Make a software-string enquiry understandable outside the codebase
• Scope an ecommerce language enquiry beyond product descriptions
• Build a compact context pack for a localisation enquiry