Version control for multilingual service materials
Keep service scope consistent across language versions, websites, PDFs and sales materials with clear owners, change records and review steps.
Article language: English

In this article
The Polish website describes the new scope. The English PDF remembers the old one. The sales presentation offers a third version. All three look professional; the offer, meanwhile, is living in parallel universes. Start version control with one source of facts and a map of the materials affected by a change. Translations can sound different, but differences in scope and terms should come from a deliberate decision.
Controlling offer versions means maintaining one identifiable set of facts and a history of changes. It does not require identical sentences in every language. It does require agreement about what the company offers: scope, conditions for starting, contact route and limits of responsibility. Record facts and conditions in the change log; leave the people responsible for each language room to choose natural wording.
Identify the source of service facts
Start with a short service record. Write down its name, audience, outcome, scope, required inputs and the customer's next step. Add the information owner and the date it was last confirmed. This is the substantive source for the website and sales materials. It does not have to be public, but the people preparing translations, design and enquiry handling need access to it.
Separate the facts from their presentation. A short heading may read differently in Polish and Japanese, but the service scope should not change by accident. Define terms that are easy to confuse: consultation, analysis, implementation, maintenance and the scope of a trial. If the team cannot distinguish them in Polish, first organise the content using the guide to writing a service page (in Polish).
If the company already has many materials, conduct a small review. Pick one service and compare its web page, PDF and message template. Mark contradictions, missing conditions and promises that have not been confirmed. Do not begin by translating every file in bulk. Before increasing the number of copies, identify the current source. The guide to company knowledge architecture (in Polish) explains how to organise it.
Map channels and dependencies
For each piece of information, record where it appears. A service description may be published on a web page, in a form, a presentation, a download and an automated message. Changing one sentence can therefore involve several channels. A dependency map helps the team assess the work before publication instead of discovering more copies when customers start asking questions.
Separate the content version from the publication date. A piece may have a new visual layout while still relying on the old service scope. Give the set of facts an identifier and record that connection with each file. There is no need to put a technical version number on the first screen of the website. The team does, however, need access to it so it can trace the basis for a given text.
For every language version, name the person responsible for review and record its state: update needed, in progress, reviewed or published. A single “done” label is not enough when nobody knows whether it means translation is complete, content is approved or the material is live. The record should lead to the next action. A status with no owner will age as quickly as a file with no date.
Make changes according to their effect
Fixing a typo calls for a different scope of work from changing the outcome of a service or the terms of engagement. Before starting, assess which facts and channels are affected. A change that matters to the customer should have a short explanation and an approver. Keep the decision in a project decision log, so the team can later tell a deliberate market difference from a mistake. The guide to project decision logs (in Polish) explains what to record.
W3C describes localisation as adapting a product or content to the needs of a particular market, including more than translation alone. That supports checking meaning and use, not just individual words. See W3C's explanation of localisation and internationalisation. Your acceptance process must fit your own offer and channels; W3C does not prescribe the register described here.
When commissioning an update, provide the previous and new content and explain the change. The translator needs to know whether a service element was removed, a term clarified or the style corrected. A new paragraph alone leaves out the context. Identify the audience, terminology and materials that need to be checked together. The guide to a Korea and Japan localisation brief (in Polish) helps prepare that information.
A practical change record includes:
- The service and the approved identifier for the new factual source.
- The reason for the change and the facts that start or cease to apply.
- The channels and language versions covered by the task.
- The roles responsible for content, language, publication and acceptance.
- The planned publication date and treatment of older materials.
- Evidence of checks and open issues preventing completion.
Check meaning in the customer's context
A reviewer should see the finished material as the audience will. A translation table may hide the fact that a condition is far from the promise it qualifies, or that a link leads to another service. Open the page, download the PDF and go through the form. Check whether the customer receives a consistent description of the scope and a clear next step. The website acceptance guide (in Polish) develops that journey.
Variant names matter too. If a salesperson calls something a “starter package” and the Japanese file uses another name, the team needs a reliable way to connect them. It should not have to identify a variant by its cover colour. Use a stable identifier in internal documentation and check that its scope matches your company's B2B offer package for Japan. See also the guide to preparing a B2B offer for Japan (in Polish).

Microsoft describes translation memories as databases pairing source-language segments with translations. They can help reuse previous work. They do not, by themselves, confirm that an old passage still describes the current service. See Microsoft Learn: translation memories. A change to the offer needs a substantive review even when the tool finds a very similar sentence.
A hypothetical example: changing the first stage
Imagine a company changing the first stage of a service from extensive research to a short preliminary analysis. This is an invented example. The Polish website has been updated, but an older English PDF still promises a full report. A Japanese presentation is based on that file. Without a dependency map, the team might consider the work complete once the website is updated.
The service owner describes the new outcome and makes clear what requires a separate stage. The team creates one change record for all channels. Translators receive an explanation, and reviewers check that words describing the depth of the work do not suggest a wider scope. Salespeople get a link to the new file and a short guide to recognising the old version.
The company checks the enquiry form too. If it still collects information needed only for the former stage, the team updates its questions and the explanation of the next conversation. Consider that dependency as part of Poland-Asia localisation (in Polish), which includes handling contact. Consistency matters all the way to the point where the customer submits an enquiry and receives a response.
Decide what happens to older materials
Not every old copy can be effectively withdrawn from circulation. Control, above all, the sources from which the team takes materials today. Change links, label the archive and remove outdated files from the active library. Keep any necessary history separately, clearly marked. An archived file should not look like the recommended offer to send to a customer.
If an older document concerns a conversation already under way, the person responsible should decide how to explain the change. Do not quietly replace a document the other party is referring to in correspondence. Keep the version sent to the recipient and the later agreements in the case record. Both the publication process and the record of the particular sales relationship should make it possible to reconstruct what was actually presented.
When accepting the change, check all identified channels, confirm the link to the current file and ask someone outside the project to find the right version. If they choose the old presentation, the library needs work. The process should function without every employee remembering the history of every revision. Otherwise an elaborate register will not improve daily work.
Start without a large migration project
Choose one frequently sold service and one market. Gather the materials, identify the source of facts, compare differences and make one controlled update. Record the time and the difficulties the team encounters. Use that evidence to assess whether you need a content management tool. Publication automation helps once you know which information it should carry and who approves it.
Combine the version review with your company's evidence register for claims in its B2B offer. See also the guide to keeping evidence for B2B offer claims (in Polish). A translation should not strengthen a claim the original cannot support. For every significant assurance, retain its basis, scope and the person responsible for keeping it current.
When should markets have a deliberate difference?
An offer can have a different scope in different markets. A company may support a particular contact language, product variant or implementation stage only in selected locations. Such a difference needs its own description and decision owner. Do not hide an intended difference under the status of a delayed translation. The record should show the common basis and the local variant.
When approving a variant, also agree the local team's authority in relation to headquarters. The article on headquarters and local autonomy (in Polish) explores this balance. Changing the way an offer is presented and changing the promise itself require different kinds of confirmation. Clarify the difference before making the texts uniform.
Record the audience, available scope and starting condition for the variant. Check the channels leading to that offer too. If the global website directs everyone to a form for one market, a customer may not recognise the limitation. Adjust the description and contact route so questions reach the right team. A difference in language should not leave the visitor guessing how the company divides its work internally.
During review, do not automatically remove every discrepancy. First establish whether it comes from local scope, communication style or an outdated copy. Then choose the action. This matters particularly when one person is comparing texts without knowledge of the market. That person may be able to spot the difference, but approving a change requires someone who understands the offer and its actual availability. When giving feedback on an expert's work, as discussed in the guide to commenting on an expert’s work (in Polish), identify the discrepancy and its effect on the audience. Keep that observation separate from your proposed wording, which the expert should be able to assess.
Finally, test a salesperson's scenario: a question arrives from a particular country and they must choose a document. Can they identify the correct variant from its name, description and source? Do they know whom to ask about an exception? If the answer depends on one person's verbal instructions, improve the library. A consistent process should help people select the right offer even when the team does not remember the details of the last change.
If you need to organise an offer across languages and channels, explore Aeneia Oriens. A useful starting point is the set of files actually in use and an example of a recent change that spread unevenly across departments or languages.








