Check completeness first
Compare the delivery against file lists, pages, appendices, figures, notes and untranslated portions. Any content intentionally left in the source language should be identified in the delivery notes.
Separate errors from preferences
Omissions, factual errors and terminology inconsistencies differ from stylistic preferences. Feedback should identify the location, source, current wording and reason for change. Subject specialists should confirm technical facts.
Keep a clear approval record
Consolidate reviewer comments to avoid conflicting changes across separate files. After revision, confirm the version and resolved issues, then retain new terminology and approved wording for future work.
A checklist for your brief
- Agreed service scope
- Traceable issue list
- Final approved revision
A common question
Is a preferred rewording necessarily a translation error?
Not necessarily. Determine whether the translation is inaccurate or conflicts with agreed style guidance before distinguishing corrections from preference changes.
This guide supports project preparation and communication; it does not replace legal, financial or specialist technical advice. Service scope, recipient requirements and delivery arrangements must be agreed for the specific project.
