Every season has its own rhythm, and autumn is when organisations plan what comes next. This month, our four specialists focus on what has to be in place before the next market, the next language or the next update begins. A documentation map that defines what belongs where. A compliance structure that separates hard rules from soft judgement. Technical documentation that stays the same document in every language. And a clear view of who writes the message when a market closes. Autumn builds strong roots, because structure is what allows growth to hold.
The Intertranslations Team
Entering a New Market? Start With the Documentation Map
When a medical device enters a new market, the first question is rarely the right starting point. The better question is which content the law treats as information supplied by the manufacturer in that jurisdiction, and which assets must be in place before the device is available. The answer is almost always broader than the IFU. A documentation map shows what belongs there and why the translation brief should follow from it. Structure comes first. Translation then scales what already exists.
Discover the documentation map behind every market entry.
Compliance Is Not One Thing
Compliance in multilingual content is a stack of distinct constraints, not a single requirement. Presented at TIERA 2026 in Corfu by Viveta Gene, the taxonomy in her postdoctoral research sorts seven submodules from hard to soft: legal-regulatory, terminological, genre, stylistic-register, brand, cultural-locale and accessibility. The hard constraints proved automatable. The soft ones, such as register and brand voice, still need human judgement. Knowing which is which decides how work is divided between machine and reviewer.
Explore the taxonomy behind knowledge graph-mediated translation.
How Resilient Is Your Multilingual Technical Documentation?
Most organisations have documentation and translations. Fewer can say whether the multilingual version is still the same document as the source. That gap rarely shows in a translation review. It shows in an audit. Multilingual systems tend to break in three places: terminology governance, version control and workflow ownership. A translation review asks whether the words are right. A localization review asks whether the system is under control.
Discover what a technical localization review actually checks.
When a Market Closes, Who Writes the Message?
When Brazil prohibited fixed-odds betting in September, open bets were voided and every stake returned in full. Two instruments closed the market, yet neither specifies what the player is told. Regulation can set a refund down to the account number, but it cannot write the sentence that explains it. That sentence still has to exist, and in practice it is usually the localization team that writes it.
Explore how regulation shapes the words players receive.
