Identify the real deadline
Distinguish delivery of the translation from internal approval, publication and external submission. Where legal, technical or brand review is needed, allow a review window and appoint one contact to consolidate comments.
Set the baseline before batching
Give the source a clear revision identifier and identify the approved sections. If writing and translation overlap, agree change marking, incremental handovers and a cut-off. Replacing files without a revision record risks omissions and duplicated work.
Allow time after translation
Web pages, software and complex layouts usually need checks in context. File delivery is not the same as release validation. Agree who imports the content, checks the display, approves publication and verifies corrections.
A checklist for your brief
- List publication or submission deadlines
- Name reviewers and feedback deadlines
- Agree a source baseline and batch order
A common question
Can work start before the source is final?
Stable sections can be started, provided likely changes are identified and the change log, additional work and final checks are agreed.
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.
Put this guidance into a project brief
- Identify the source files, languages, audience and final use.
- Separate reference examples from binding recipient instructions; provide the current checklist for formal submissions.
- Agree the final format, review responsibilities, timing and revision scope before work starts.
