Show the text in use
Send screens, templates, character limits, and placeholders beside the relevant strings. Note capitalization, feature names, and wording that cannot change.
Plan your request
Make published language suit an interface, product, or campaign rather than treating every sentence as an isolated line.
Send screens, templates, character limits, and placeholders beside the relevant strings. Note capitalization, feature names, and wording that cannot change.
Identify the market, audience and preferred conventions. Keep source revisions separate from content already signed off so a reviewer can tell what changed.

When asking about localization services for websites and products, describe the outcome so the scope reflects how you will use the work. Start with the interface export paired with screenshots and identify the audience and languages. Explain whether someone will file it, read it alongside an original or edit it before publication. That decision may affect format, source material and how the work is reviewed.
Gather the files that represent the current request for localization services for websites and products. Sort final sources apart from drafts and examples, and retain the original sequence. Identify variables, customer-visible phrasing and string length limits if a reader could confuse them during review. If the product has different terminology in different markets, say so early and add any instructions you received about what to do with the affected material.
A good brief for localization services for websites and products calls out spellings, names, formatting or approved terminology separately from the file itself. Add each preference next to the passage or file it affects. If the same expression means different things within your documents, give a short example rather than a translation guess. Identify the person who can answer a question before delivery.
Set aside enough time to look through the work from localization services for websites and products before it goes to its recipient. If someone needs paper, a specific electronic format or a separate statement, confirm those instructions before starting. Agree who will review the first version and what the deadline means in the recipient’s time zone. Let us know when a change would affect another copy or an attachment.
If you discover that the product has different terminology in different markets, write a short update explaining what is new, when it became available and which version it replaces. For localization services for websites and products, that gives the team a chance to review both the scope and timeline before carrying on. Keep updated instructions with the request so that decisions are not lost in a string of unrelated messages.
At delivery, compare the finished work for localization services for websites and products to your source and the recipient’s checklist. Look first at variables, customer-visible phrasing and string length limits; then confirm filenames and attachments. To ask about an unexpected detail, send the page number or provide a brief description of its location. Save the completed files with any related instructions so you can identify the correct version later.
Gather the interface export paired with screenshots, then give the service team your target language, intended use and deadline. Point out anything in the request that depends on a recipient’s instructions.
Give enough material to show scope and context. Mark anything included only as an example, and note variables, customer-visible phrasing and string length limits if the distinction could affect the order.
Describe the result you want and the format the recipient needs. A checklist or a blank template can be more useful than guessing a format from the name of the service.
Yes. Provide a short list of approved spellings or terms with an example. Indicate where they already appear in other paperwork, a product interface or an existing handoff.
Send the new version and identify the material that changed. This is especially useful if the product has different terminology in different markets. Ask for a fresh timing estimate if the planned handoff is affected.
Give the exact due date, time zone, and any separate review or delivery window. Mention whether a portion can be delivered first if you decide to divide the request.
Ask about each target language and name the people or institutions that will use each version. Give separate formatting and delivery instructions when those requirements differ.
Use the designated channel for the request and send only the material needed for the agreed purpose. Explain any restrictions before uploading the relevant files.
Point to the exact file or page and say what the source or recipient instruction shows. Use the relevant order or project details to keep the conversation tied to the correct version.
Share the interface export paired with screenshots and your main constraints. The service team can consider the requested scope, languages and timing before explaining the available options.