Publishing a bilingual report: what takes the longest?

When an organization publishes a report in two languages, the common assumption is that the hard part is the translation itself. Get the text translated, drop it into the template, done.

That assumption is wrong. The translation is usually the fastest-moving piece. What takes the longest is everything that comes after: aligning the two versions so they look, read, and function identically across every heading, table, figure, download link, and navigation element.

What people think the process is

The expected workflow sounds simple:

1. Write the report in the primary language.
2. Send it for translation.
3. Publish both versions.

In reality, step three hides an enormous amount of detailed production work that no one budgets time for.

What actually has to happen

Once both language versions of a report exist, someone has to make sure the two published pages are structurally identical. That means checking and fixing:

• Headings and subheadings. The table of contents in both versions needs the same hierarchy and anchor links. If a heading was rewritten during translation (which it often is), the structure can drift.
• Downloads. Each version needs to link to the correct PDF, data file, or appendix in the correct language. A French page linking to an English PDF is a common mistake that erodes trust immediately.
• Tables. Data tables often need adjusted column widths because French text tends to be longer than English. Header labels need translating. Units might differ. Responsive behavior needs testing in both languages.
• Figures and charts. If charts contain embedded text — axis labels, legends, annotations — each chart needs a language-specific version. You cannot publish an English chart on a French page.
• Captions and alt text. Every figure caption and image alt attribute needs to match the language of the page. This is frequently missed because it sits below the visible content during review.
• Internal links. Cross-references within the report need to point to the correct language version. A French footnote that links to an English appendix section breaks the reader experience.

Where mistakes happen

The most common errors in bilingual report publishing are not typos or mistranslations. They are structural mismatches between the two versions:

Wrong download language

The French page links to the English PDF (or vice versa). This happens because downloads are often added in a rush at the end, and file names don’t always make the language obvious. A file called “report-final-v3.pdf” could be either language.

Broken cross-links

The report references “see Appendix B” but the link goes to the English appendix on a French page. Or a methodology section link in one language points to a 404 because the URL slug was translated differently than expected.

English chart on a French page

A chart with English axis labels, legend text, or annotations appears on the French version because nobody exported a French version of that figure. This is especially common with charts produced in Excel or Datawrapper where re-exporting requires going back to the source file.

Inconsistent heading structure

The translator combined two sections or split one section differently. The page structure no longer matches. The table of contents works in English but has missing or extra entries in French.

What a good workflow looks like

Teams that publish bilingual reports without consistent problems tend to follow a few practices:

• A structural checklist, not just a content review. Someone compares both versions element by element — not reading the text, but confirming that every heading, download, figure, and link exists in both languages and points to the right place.
• Language-specific figure exports from the start. Charts are produced in both languages at the same time as the primary version, not retrofitted later.
• Consistent file naming.Downloads follow a naming convention that makes the language unambiguous: “report-2024-en.pdf” and “report-2024-fr.pdf” — not “report-final.pdf” and “rapport-final.pdf”.
• A single person responsible for both versions. The same person publishes both the English and French pages. When two different people handle each language, mismatches are almost guaranteed because neither person sees the full picture.
• Testing in both languages before launch. Click every download. Follow every internal link. Confirm every figure has text in the correct language. This takes thirty minutes and catches the problems that take hours to fix after publication.

A brief case study

A federal research organization we work with publishes quarterly reports in English and French. Their reports typically run 60-120 pages with 20-30 data tables, a dozen figures, and multiple appendices.

Before working with us, their publication process for the bilingual version took 2-3 days internally. Most of that time was not spent on content — it was spent comparing pages side by side, re-exporting French figures, fixing download links, and resolving heading mismatches that appeared during the final QA pass.

The translation itself was always done on time. The publication work was what pushed launches back.