EU regulations require user manuals and safety docs in the official language of every country of sale. Managing 9–24 simultaneous language versions for UAV launches.
- Requirements move, so verify late
- The language set is a per-market question
- Shipping many languages at once
Requirements move, so verify late
Rules affecting unmanned aircraft and their documentation have changed repeatedly in recent years and continue to develop. Documentation built for one market and one moment does not automatically transfer to the next.
Verify the current requirement for your product class and each target market with your notified body before finalising the documentation set. Anything else — including this article — is background, not a compliance determination.
The language set is a per-market question
Products placed on the EU market must generally be accompanied by instructions in the language or languages of the member state where they are sold, determined per market rather than centrally.
For a consumer or prosumer UAV sold across a wide European footprint, this produces a large simultaneous language set. The programme management problem is usually harder than the translation problem.
Shipping many languages at once
Establish terminology once and apply it across the full set in parallel, rather than sequencing languages and letting each re-decide the same questions.
Freeze the source before the set goes out. Late source edits multiply across every language and are the most common cause of launch slippage in multi-language releases.