An annual report often brings together messages from leadership, program results, financial information, photographs, and charts. Those pieces rarely become final at the same time. For a communications team preparing English, French, or Arabic editions, the main challenge is keeping every language aligned as approvals arrive. Treat the report as a coordinated publication project, with a named owner and an agreed route for changes.

Build an inventory beyond the main document

List every deliverable before asking for a quote: the report itself, a web summary, a launch email, social posts, and any presentation for stakeholders. Within the report, include chart labels, captions, acknowledgements, image text, contents pages, and footnotes. A translator cannot reliably discover text that exists only in a design file they have not received.

  • Provide the editable manuscript and a reference PDF showing the layout.
  • Include editable charts or the source spreadsheets, with the relevant tabs identified.
  • Supply official organization, funder, program, and job titles.
  • Separate text that needs translation from approved text that should be reused.

Use a staged handoff only when versions are traceable

If the introduction is approved while results are still changing, send the introduction as a clearly identified batch. Record the filename, version, approval date, and sections included. Keep one master change log rather than circulating several documents named “final.” Agree whether the translator will compare replacement files or work from marked changes, and include that effort in the scope.

For example, if a participation figure changes from 1,250 to 1,280, identify every occurrence: the results paragraph, chart, executive summary, and launch email. Sending only the revised chart leaves other language versions inconsistent.

Check figures against the approved source

Translation review should verify that amounts, dates, percentages, units, and references correspond to the approved source. Formatting conventions may change, but the underlying value must not. Have the person responsible for the figures approve them separately; a translation review does not validate accounting calculations or the conclusions drawn from them.

Flag unexplained abbreviations and distinguish a percentage increase from a percentage-point change. If the source is ambiguous, resolve the question with its author rather than asking each language reviewer to interpret it independently.

Review the designed pages, not just the text

Translated text may occupy different amounts of space. Reserve time to check the final PDF or web edition after layout. Look for clipped headings, detached captions, missing footnotes, incorrect contents-page references, and chart legends that no longer match their colours. For Arabic, have the mixed-direction text and reading order checked in the actual output.

Keep layout comments separate from wording changes. If shortening a headline is necessary, ask for a revised translation that keeps the intended meaning instead of deleting words in the design file.

Use a release checklist with named owners

  • Communications: confirm every item in the content inventory is included.
  • Content owners: approve the figures, names, and final source changes.
  • Language reviewer: resolve queries and confirm the approved wording.
  • Designer or web editor: check layout, links, and downloadable files.
  • Publication owner: confirm the final versions and archive the approved source and translations together.

Ask for a quote that separates translation, review of later changes, and review after layout. This makes it easier to schedule the actual publication work and decide who is responsible for each final check.