Skip to content
batterypassport / Solutions / Languages and revisions

TRANSLATION IS ONLY THE FIRST STEP

The right manual.
In the right language.

When the original changes, the person managing the translation needs to know too. Link language versions to a specific document revision and to approval.

For companies selling into several countries and for their documentation and service teams.

batterypassport / working scenarioILLUSTRATION

LANGUAGES / SOURCE REVISION 2.0

A change to the original is visible.

Czech · 2.0Source documentation
✓
English · source 2.0Approved version in the example
✓
Deutsch · source 1.0To be updated from the new source
!
Model example. This is not a screen from a live customer service.

WHY IT MAKES SENSE

Language is not enough.
The revision must match too.

01

Languages have a source

You know which original a translation was made from.

02

A change to the original is not lost

An older translation is flagged for update instead of looking current.

03

Someone approves technical content

A draft translation is not automatically an approved service manual.

HOW WE START

One working process first.

01

We unify the source

We define the original, the revision and the languages needed for specific markets.

02

We prepare the language version

Using your own translator, a partner or an agreed tool.

03

We review and publish

An expert verifies the content. Only then do we offer it in the relevant passport version.

WHAT YOU GET

A concrete deliverable.

A register of languages and revisions, a translation queue, approval and alerts on source changes. Machine translation can be connected depending on the chosen tool and its licence terms.

CLEAR BOUNDARIES

What needs to be agreed.

Translating a marketing website, an application interface and service documents are different tasks. Foreign-language PDFs and technical translation are not automatically included in the CZ/EN switch.

How we separate platform pricing from implementation ↗

BEFORE WE TALK

What you will want to know.

Let's start with what you already use and what slows your people down today.

Can we connect a translation tool?

Yes, as an individually validated integration. We confirm the scope, protection of the transferred data and licence cost in advance. The demo does not use any external translation service.

Does the demo actually translate text?

No. The example uses pre-prepared fictitious language versions. We demonstrate approval and the response to a new source revision, not the quality of machine translation.

Can we publish a technical translation without review?

We do not recommend it. Approval should be given by a responsible expert according to the nature of the document and the target market.

Show us your process.
We will propose the first step.

In the consultation we will go through your data, responsibilities and the system you work with. We confirm the scope and price before work begins.

Book a consultation ↗
Offer status: we are preparing a production solution and accepting pilot partners. The demo is a local simulation on fictitious data. Specific features, integrations, responsibilities and operating parameters are subject to agreement.