Translating regulatory content in Switzerland: when words become risk

Most translation mistakes are embarrassing. When translating regulatory content, they can become part of the file: something a regulator, auditor, court or client may rely on later. That might be a dosage instruction in a patient leaflet, a risk warning in a Key Information Document, a contract clause filed with an authority or a certified translation rejected because it does not meet the receiving office’s format. In these cases, translation is part of how the document is controlled, approved and later interpreted.

In Switzerland, this matters more than in many markets. German, French and Italian are not just market preferences; they are the official languages of the Confederation. English is useful in international business, but it is not one of them. Before translation starts, the practical question is: who will rely on this language version, and what happens if it is challenged?

What counts as regulated content?

Regulated content is any text whose wording is shaped by law, supervisory practice or a receiving authority’s formal requirements, whether it is public-facing, authority-facing or internal. The issue is not visibility alone. An inaccurate or inconsistent translation can create an operational, legal or reputational problem. In practice, that covers:

• patient information, product information and packaging in pharma and healthcare
• instructions for use, labels and safety information for medical devices
• prospectuses, Key Information Documents, fund documents and investor communications
• AML, KYC and other compliance documentation
• contracts, court filings, commercial register documents and certified translations
• internal policies that might one day be read by an auditor or regulator

Three official languages, one demanding market

Switzerland’s multilingualism is more than part of the country’s identity. The Federal Constitution names German, French and Italian as the Confederation’s official languages, with federal legislation appearing in all three at equal legal weight. Romansh is also national, but specifically for dealing with Romansh speakers. In practice, a Swiss version of a regulated document is rarely just one language version. It might mean all three together, or a specific version that one particular regulator accepts.

Cantons add another layer: Bern, Fribourg and Valais are officially bilingual, and Graubünden is trilingual. Check the receiving authority and audience before translation starts, not the week before submission.

Pharma and healthcare: precision is patient safety

In pharma, translation leaves little room for interpretation. Terminology is controlled, patients may make health decisions based on the text, and Swissmedic treats document types differently depending on who will read them.

Patient information and the technical information for healthcare professionals must be available in all three official languages. Packaging is regulated too, but not in the same way: according to Swissmedic’s packaging guidance, the text on the box itself generally needs to appear in at least two of the three languages, with a further exception (one language, or English) for medicines used exclusively in hospitals. It is a subtler rule than many people assume, and worth getting right.

One element catches companies out: Swissmedic approves product texts in the language in which the application was submitted. That approval does not amount to a quality check of the other language versions. The marketing authorisation holder remains responsible for those. A clean German approval tells you nothing about whether the French or Italian version is accurate.

According to Swissmedic guidance, product information meant for the public generally needs all three official languages, with more flexibility for devices intended exclusively for healthcare professionals. Generic translation workflows quickly reach their limit here. Pharma and medical content need linguists with the right subject background and terminology that is managed rather than reinvented for each document.

Financial services: more room for English, same stakes

Finance looks more flexible on paper. Under the Financial Services Act, a prospectus can be drawn up in an official Swiss language or in English. Key Information Documents also allow some flexibility: they can generally be prepared in an official Swiss language, English, or the client’s language of correspondence. KIDs for funds and other collective investments generally need an official Swiss language, with an exception for instruments simple enough that investors are assumed to already understand them, such as plain equities.

That flexibility should not be confused with a lower standard. If a translated risk warning no longer matches the prospectus, or if “may”, “shall” and “must” drift between language versions, the problem is no longer linguistic. It becomes a compliance issue. The same applies to AML and KYC documentation, which circulates across regions and jurisdictions inside one organisation: a translation gap can become a gap in the compliance record, and “the French version wasn’t updated” is unlikely to satisfy an auditor. For banks, asset managers and insurers, prospectuses, KIDs, factsheets and reports need to be managed as connected documents, not treated as one-off jobs.

Legal and certified translation: acceptance comes before elegance

Legal translation has its own trap: a text can read beautifully and still be rejected if it does not meet the receiving authority’s formal requirements.

Outside the cantons of Geneva and Neuchâtel, which maintain their own registers of sworn translators, Switzerland has no general system of state-appointed sworn translators. Elsewhere, certified translations are produced by specialist translators who sign a declaration of accuracy. Notarisation is typically added, and for use abroad, an apostille from the cantonal chancellery may also be required. The first question is practical: where is the document going, and what will that office accept?

Courts, the Federal Tax Administration and commercial registers all rely on certified translations of contracts and corporate filings, and legal systems do not map neatly onto each other. A clause that is clear under Swiss law may have no direct equivalent in a common law jurisdiction. Done well, legal translation preserves legal effect, not just wording.

What changes in the translation workflow

The biggest difference is that decisions need to be made earlier. Before translation starts, someone has to define what the document is for, who will read it, which language versions are required and how the final text will be checked. In practice, five points make the difference:

Purpose. A text for internal training can be handled differently from one submitted to an authority. A marketing factsheet is not a prospectus. Purpose determines the level of scrutiny, and that level of scrutiny determines the workflow.

Language versions. German, French and Italian, or is one enough? Is English accepted? Is the canton bilingual or trilingual? Is the document meant for patients, investors, regulators or courts? Settle this before the translation starts.

Terminology. In regulated content, terminology is a control point, not a preference. A term in patient information has to match the packaging; a risk category in a KID has to match the prospectus. Terminology databases and translation memories help keep those links intact.

Review. A native-speaker review matters, but it is rarely enough. Depending on the document, review may need to involve a medical, legal, technical or compliance specialist as well as a linguist.

Version control. Product information is updated, fund documents change, and policies are revised. If the German version changes but the French and Italian versions do not, the inconsistency may go unnoticed until an audit, submission or client query brings it to light. The responsibility sits with whoever owns the content, not the translator.

Where does AI fit when translating regulatory content?

AI and machine translation can help in regulated workflows. They can identify terminology, compare versions, speed up first drafts and support quality checks. But they do not remove the need for expert review where patient safety, investor protection or regulatory acceptance is involved. The question is not whether AI can be used. It is whether the workflow controls the problems AI can introduce: missing context, overconfident wording, inconsistent terminology, data protection issues and fluent sentences that quietly alter meaning.

How SwissGlobal helps

SwissGlobal supports companies translating sensitive, regulated content for the Swiss market through subject-specialist linguists, terminology management and structured quality assurance.

Pharma and healthcare translators bring the medical background these documents demand. Finance specialists keep prospectuses, reports and compliance documents consistent across language versions. Legal translators are trained in law as well as language.

Translating regulatory content is not about making a text sound good in another language. It is about making sure the people who rely on it can trust it.

Need your regulatory content translated in Switzerland? Get in touch with us.

FAQ: translating regulatory content in Switzerland