Why Technical Writers and Translators Need to Work Together From Day One

Key Takeaways

• Most multilingual documentation problems originate in the source document, not in the translation.
• Technical writers and translators share a core objective — clear, accurate communication — but rarely work together until the writing is finished.
• Involving a translation agency at the authoring stage reduces costs, shortens timelines, and improves quality across every language version.
• A shared terminology glossary, agreed at the writing stage, is the most effective single investment a documentation team can make.
• For companies releasing documentation in multiple languages simultaneously, upstream collaboration is not a nice-to-have — it is a competitive advantage.

Technical writing and translation are treated as sequential activities in most organisations. The writer finishes the manual. The manual goes to the translation agency. The translated versions come back. Problems are fixed. The cycle repeats.

This model works, but it is inefficient. A significant proportion of the time and cost in multilingual documentation projects is spent correcting problems that originated in the source document — inconsistent terminology, ambiguous phrasing, text embedded in graphics, layouts with no room for text expansion.

None of these problems require a translator to identify. They require a conversation between a writer and a translation professional before the writing is finalised. This article makes the case for that conversation, and sets out what it should cover.

The Problem With Sequential Workflows

In a typical sequential workflow, a technical writer completes a user guide and hands it to a project manager, who briefs a translation agency. The agency translates, returns the files, and the writer (or a reviewer) checks the output.

At this point, problems surface. The translated German manual is 30% longer than the English original and overflows the layout. The French version uses three different terms for the same component because the source document was inconsistent. The Japanese version has diagrams with untranslatable embedded text. The software manual uses different terms for menu items than the translated UI.

Each of these problems requires rework — sometimes significant rework across multiple language versions. The total time and cost of fixing them is invariably greater than the time and cost of preventing them.

The root cause in almost every case is the same: translation was treated as a downstream activity with no input into the upstream work.

What Technical Writers and Translators Have in Common

Technical writers and translators are solving the same problem from different angles: how to communicate complex information clearly and accurately to a specific audience.

A technical writer develops expertise in structuring content, writing plain language, and presenting procedural information consistently. A professional translator develops expertise in understanding source intent, finding precise equivalents in the target language, and identifying where source ambiguity creates translation risk.

These skill sets are complementary. A translator reviewing a source document before translation can identify:

• Terminology inconsistencies that will produce variable output across languages
• Sentences where the intended meaning is genuinely ambiguous
• Idiomatic or culture-specific phrasing that will not transfer cleanly
• File formatting issues that will create problems in CAT tools or DTP
• Layout constraints that will be violated by text expansion in specific languages

This is not a critique of the writer’s work. It is a quality check that catches problems when they are cheap to fix — in the source — rather than when they are expensive to fix — across 15 translated versions.

5 Collaboration Points That Deliver the Highest Return

1. Terminology Alignment Before Writing Begins

The most valuable point of collaboration is before the document is written. Agreeing on a terminology glossary — component names, action verbs, safety terms, product-specific vocabulary — before the writer begins means the source document uses consistent, translation-ready terms from the start.

This glossary then becomes the foundation for every translated version. Translators work from approved terms in the target language rather than making independent decisions. The result is consistency across all language versions, maintained across document updates and future product generations.

Building a glossary after writing is complete is possible but less effective: the writer has to revise for consistency before translation can begin, which adds a step and a delay.

2. Source Review Before Translation Handover

A brief source review by the translation agency before work begins catches the majority of preventable problems. At Global LTS, we review source documents for terminology consistency, sentence complexity, formatting issues, and graphic text before quoting or commencing work — flagging anything that will affect quality or cost.

This review typically takes a few hours for a standard user guide. The time it saves in revision and DTP work is almost always greater.

3. File Format Agreement

Translation memory software (CAT tools such as MemoQ, SDL Trados, or memoQ) works most efficiently with specific file formats. A source document in a compatible format flows into the translation workflow cleanly. A source document in a non-compatible format — or one with problematic formatting choices like hard returns, embedded table structures, or text in graphics — requires manual preparation work that adds time and cost.

The optimal time to agree on file format requirements is before the document is authored. A five-minute conversation between the writer and the translation project manager about the intended output format and CAT tool compatibility can save hours of file preparation work.

4. Layout Review for Text Expansion

Different languages produce different text lengths. German, Finnish, and Dutch typically expand 20–35% relative to English source text. Arabic and Japanese may contract. A layout designed tightly around English text will require redesign work in expansion languages.

Having a translator review the document layout before finalisation — with an eye on which text boxes, callouts, and graphic labels are at risk — allows the designer to build in expansion room where it is needed, without redesigning the entire document.

5. Simultaneous Release Planning

For product launches requiring simultaneous release across multiple markets, translation timelines need to be factored into the documentation production schedule from the start. A large user guide translated into 20 languages, reviewed, and typeset cannot realistically be completed in a week.

Involving the translation agency in the project timeline at the planning stage — sharing draft content progressively rather than delivering the complete document at the end — allows translation work to begin before writing is fully finished, compressing the total timeline significantly.

The Business Case for Upstream Collaboration

The case for earlier collaboration between writers and translators is primarily economic. Translation costs are driven by word count, complexity, and the amount of rework required. All three of these are influenced by decisions made at the authoring stage.

Consistent terminology increases translation memory leverage — the proportion of content that matches previously translated segments. In an ongoing documentation programme, high translation memory leverage reduces per-word costs progressively over time. The terminology glossary built at the start of a product line continues to deliver value across every subsequent document and update.

Reduced revision cycles — fewer rounds of corrections on translated content — reduce both agency costs and internal review time. For documentation teams releasing in 10 or more languages, even a small reduction in revision cycles produces material savings.

Faster time to market — by compressing translation timelines through progressive handover and resolving source issues before they reach the translation stage — is increasingly significant in competitive markets where simultaneous global product launches are the expectation.

Practical Steps to Start Collaborating Earlier

If your current process treats translation as a final step, these are the most impactful changes to make:

Brief your translation agency at project kick-off — share the scope, target languages, planned file formats, and timeline at the start of the project, not at handover.

Request a source review — ask your agency to review a draft or representative section before translation begins, specifically looking for terminology and formatting issues.

Build the glossary first — invest time in a terminology glossary before writing starts. Your agency can advise on which terms most need standardisation based on experience with your industry and language combinations.

Deliver progressively — for large documents, share completed sections as they are finished rather than waiting for the full document. This allows translation to begin earlier and compresses the overall timeline.

Summary

Technical writers and translators work toward the same goal. The current norm of treating translation as downstream of writing creates unnecessary cost, delays, and quality risk. The alternative — involving translation professionals earlier in the documentation process — reduces all three.

Global LTS works with technical documentation teams across engineering, manufacturing, medical devices, and software to provide user manual and user guide translation services that are planned from the start of each project, not bolted on at the end. Contact us to discuss how we can support your documentation programme from kick-off.