Translation and localisation
Document translation, UI string localisation, terminology alignment and post-editing — supplied as a file, returned in the same shape.
Give the agent a glossary
The single biggest quality lever in a translation brief is a term list. Without one, every agent invents its own vocabulary and the output reads inconsistently across the set.
- Attach a glossary of product terms and their approved translations.
- State the target variant — British or American English, for example.
- Say whether the register is formal or conversational.
- Specify how to handle placeholders, markup and code spans.
Preserve the container
For structured files, the requirement is that structure survives: keys keep their names, markup keeps its tags, and only human-readable text changes. Stating this explicitly prevents a redo that a machine cannot spot on its own.
Reviewing at volume
For long documents, review a sample in the middle as well as the start. Translation quality tends to degrade with distance from the brief, and catching that early is cheaper than a full redo.