Guide. Multilingual annual report: meeting the deadline while the source text is still changing

By Neur.on's legal and language team · 15 September 2026 · Updated on 15 September 2026

Multilingual annual reports rarely fail on translation. They fail on the schedule, on a source text that keeps moving, and on figures that no longer match between two versions. The seven steps below deal with these three causes in the order in which they arise.

1. Start from publication and work back

The publication date is the only non-negotiable element of the project: it is set by the general meeting, by a regulatory obligation or by a financial reporting calendar. Everything else follows from it. So build the plan backwards, milestone by milestone, starting from the end.

• Publication All language versions released at the same time. Simultaneity is not a luxury: a version published early creates an information asymmetry.
• Final sign-off Written agreement from the approver for each language on an identified, dated version. No changes after this point.
• Proofreading Checks on the laid-out document, not on the translation file: hyphenation, overflowing text, tables, cross-references, table of contents.
• Layout Approved texts placed in the design, in each language. Allow for the fact that languages differ in length.
• Language review Review by a translator or a lawyer-linguist, at the level chosen for each section.
• Translation After the source text freeze, never before.
• Source text freeze The turning point of the project. See step 2.
• Terminology fixed Glossary finalised and sent to everyone involved.
• Drafting and closing the figures Writing the source text and finalising the figures.

Two rules for building the schedule are worth more than any estimate of duration.

• A stage cannot start before the previous one ends, except layout, which can begin on sections already approved.
• Durations do not add up linearly when you add a language. Translation can run in parallel, but approval, layout and proofreading multiply. Count the coordination effort, not just the translation effort.

To estimate the translation and review stages, rely on the volume in standard pages and on the review level chosen, not on an impression: this is how a quote is calculated, and our article on reading a quote details what each level covers.

2. Freeze the source text

This is the most cost-effective decision in the project, and the hardest to hold. Freezing the source text means that, from a given date, the reference document no longer changes, and that any later change goes through an explicit procedure.

The reason is arithmetical. Correcting one sentence after translation has started means carrying the change into each language, reviewing it in each one, transferring it to the layout and checking it again on the proof. The cost of a late correction is not proportional to the number of words, but to the number of languages multiplied by the number of stages already completed.

For the freeze to hold, three conditions must be met.

1. It is dated and announced in advance, at the start of the project, to everyone who might propose a change, senior management included.
2. It is preceded by a review window for the source text, wide enough for everyone to have had a real chance to contribute. A freeze without a prior window is a freeze that will not hold.
3. It provides for its own exception. Define what justifies a change after the freeze (a factual error, a regulatory change, an event after the balance sheet date), who authorises it, and through which process it is carried over. Without a planned exception, the first emergency destroys the rule.

3. Fix the terminology before the first sentence is translated

An annual report rests on a limited, repeated vocabulary: names of corporate bodies, job titles, entity names, financial statement items, regulatory designations. If this vocabulary is not settled before translation, each translator will settle it implicitly, and differently.

Build a project glossary with, for each entry: the source term, the term chosen in each target language, the source of the decision and the date. Three families of entries deserve particular attention.

• Official names: company name, entities within the scope, statutory bodies. They are not translated freely; use the form entered in the commercial register and the usage already published.
• Regulatory and legal terms. In Switzerland, they already exist in the three official languages, in the published texts: that is where you take them from, and nowhere else. For an English version, the Fedlex translation is a useful guide, but it has no legal force. The abbreviations of acts change with the language, as explained in our article on Swiss legal multilingualism.
• The company's recurring wording: the title of a strategy, the name of a programme, a slogan. Decide once whether they are translated, then stick to that decision throughout the document.

To check a Swiss legal term in its official context rather than in a dictionary, a bilingual concordancer based on public sources, such as Fast lookup CHnell, is a better option than switching manually between portals.

4. Translation: who does what, in what order

Not all sections of an annual report have the same requirements, and treating them uniformly means either overpaying or taking a risk. Split the document up.

• Recurring, stable sections (governance, description of activities, legal notices): they should not be translated again. Reuse the versions published the previous year, then have only the changed passages checked.
• Editorial sections (letter from management, review of the year): they carry a tone and an intention. They call for a full review, with attention to style and register.
• Financial and regulatory sections: they call for strict accuracy in terminology and figures, and a check by someone who knows the applicable accounting framework.
• Sections intended for an authority or an official publication: they may require a double review and an attestation, which must be planned well in advance because the process involves third parties.

On the order of work, two recommendations. Start with the stable sections, which can be handled without waiting for the full freeze and free up time for what follows. And translate the tables and their notes at the same time as the running text that discusses them: handled separately, they invariably diverge.

5. Keeping the languages consistent

The consistency of a multilingual report plays out on four levels, and it is useful to check them separately.

Consistent terminology

The same source term rendered by the same target term everywhere, including headings, captions, the table of contents and the annexes. This is the easiest level to support with tools, and the one most often neglected in the annexes.

Consistent figures

Each figure in the running text must match the table it discusses, in every language. A correction made to a table after translation almost always leaves an orphan sentence in one version. Check figure by figure, language by language, after layout.

Consistent structure

Same number of sections, same order, same numbering, same internal cross-references. A section deleted in one version and kept in another is an error that is hard to fix once the document is published.

Consistent tone

A letter from management that is bold in French and cautious in German tells two different stories. Have the editorial sections in the different languages read side by side by one bilingual person, before approval.

6. Review and approval

Review and approval are two separate operations, and confusing them is the main cause of endless back-and-forth.

Review judges the language: accuracy, terminology, consistency, style. It is done by a translator or a lawyer-linguist, at the level chosen for the section.

Approval judges the substance: is this really what the company wants to say? It is done by a manager on the business side, one per language, named at the start of the project.

Four rules make this phase workable.

1. One named approver per language, not a committee. Collective approval without an owner produces contradictory comments that no one has the authority to settle.
2. An identified, dated version. Comments must relate to a document that everyone knows is the right one.
3. An announced approval period, after which no response counts as agreement. Without this clause, approval becomes the project's bottleneck.
4. One round of comments per approver. Second-round comments are only admissible if they relate to a change made in the meantime.

On choosing the review level for each section, the reasoning is the same as for any legal document: it depends on the recipient. The quality levels range from a review of significant errors to a double review certified by a specialised agency.

7. Layout, formats and publication

The last stage is where errors show, because they finally appear on the real document.

What layout reveals

• Different lengths. Languages do not take up the same space. Build room into the design from the start, rather than shrinking the type size at the last minute in one version only.
• Hyphenation. German produces long words and sometimes incorrect breaks; check them visually, because a spellchecker does not see them.
• Cross-references and pagination. Table of contents, index, internal references and cross-references are recalculated in each version.

The Swiss formats to check

• Apostrophe as thousands separator in German, French and Italian (a comma in English), currency in CHF.
• No ß in Swiss Standard German: always ss.
• Dates written unambiguously in the English versions, with the month in full.
• Abbreviations of acts specific to each official language.
• Names of Swiss authorities and courts, never their foreign namesakes.

Publish, then build on it

Once the report is published, two steps prepare the following year, and they take only half a day.

1. Archive the final versions in all languages, aligned section by section. They will be the basis for the recurring sections of the next financial year.
2. Consolidate the project glossary into the organisation's permanent glossary, with the sources. It is the only way to ensure that this year's decisions are not debated again next year.

Finally, hold a short review with those involved: on what date did the freeze really happen, how many changes came after it, and which of them could have been avoided. That page is the best starting point for the next schedule.