In German, the problem is not fluency. It is consistency across ten thousand pages.
Machine output in German is good, and we will say so. What it cannot do is hold one term steady across a document family for three years — which is exactly what technical and regulated documentation requires.
An honest starting point
German is a well-resourced language with enormous training data behind it, and modern engines translate it well. On general content, in most contexts, the raw output is close to publishable.
We are not going to argue otherwise in order to sell a review. The case for human work in German is different from the case in Arabic or Korean, and it is worth stating precisely, because it is a stronger argument than the one most suppliers make.
Where German work is actually needed
Terminology consistency at scale. German technical documentation comes in families: a machine's manual, its service documentation, its diagnostic strings, its parts catalogue, its regulatory file, its training material. The same component must be called the same thing in all of them, this year and in four years, across suppliers and across updates. An engine translates each file competently and independently — and produces three defensible names for the same part. Nobody notices until a technician orders the wrong one.
Compound nouns. German builds precise, dense compounds that carry technical meaning as single units. Engines split them, recombine them differently, or translate them component by component, producing terms that are grammatical and wrong. In a parts list or a safety instruction, that is a real-world error rather than a stylistic one.
Separable verbs and long-range structure. The element that determines what a sentence actually says can sit at the end of a long clause. Systems handle this well most of the time and badly in exactly the long, conditional, qualified sentences that regulatory and legal documents are made of.
Register and address. Formal and informal address, and the conventions of German technical and legal writing, which are more prescriptive than their English equivalents. Content that reads as translated reads as less credible in a market where documentation standards are taken seriously.
Locale detail. Decimal commas, DIN conventions, date formats, units, standards references. Individually trivial, collectively the difference between documentation that looks native and documentation that does not.
What we do
- We build and hold a termbase, and we treat terminology error as a named, severity-scored category rather than a stylistic note.
- We review across document sets, not just documents. Consistency findings are reported at the family level, which is where the problem lives.
- We can score against J2450 as well as MQM, for automotive clients who already use it.
- We check locale and standards references as a discrete pass.
Where German work is worth most
Automotive and industrial technical documentation, medical devices for the DACH market, and financial reporting. All three are content types where documentation is a compliance artefact rather than a marketing asset, and where an inconsistency is a finding rather than a preference.
Published 2026 rate data places English↔German among the higher-priced European pairs, above French and Italian — a reflection of how much of the volume is technical and specialised rather than general.