A language partner’s tooling matters to you for exactly three reasons: whether your brand’s accumulated language decisions belong to you, whether content can be delivered into your systems rather than as files, and whether your material is stored somewhere accountable. Everything else on a supplier’s technology slide is their operational concern, not yours.

This is a buying question dressed up as a technical one, which is why asking for a list of tools rarely helps. The useful questions are about ownership, portability and delivery, and they have answers a non-technical buyer can judge.

Below: the four things worth checking, the questions that establish them, and the answers that should worry you.

Key Takeaways

  • Ask who owns the Translation Memory and whether you can take it with you. That single answer
    tells you more than the rest of the technology conversation combined.
  • Ask what delivery includes. Content published into your content management system, booking
    engine, app strings or print-ready artwork is a different service from files returned.
  • Ignore tool names. What matters is the capability, the ownership and the exit.

1. The Translation Memory: ownership and exit

A Translation Memory is the record of every decision made about how your brand speaks in each language. It is the most valuable thing a language programme produces, and the question is whose it is.

We build and maintain a dedicated memory per client and reuse it across projects, which is the mechanism behind the cost falling as a programme matures: repeat and updated content draws on work already paid for, and terminology stays consistent without anyone policing it by hand.

Three questions establish whether a supplier’s arrangement is in your interest:

  • Is the memory dedicated to our brand, or pooled across the supplier’s clients? A pooled memory cannot carry your voice, because it is not only yours.
  • Can we have a copy, in a standard exchange format, on request? The answer should be yes without negotiation.
  • What happens to it if we leave? If the honest answer is that the programme restarts from nothing with the next supplier, the memory was never functioning as your asset.

A supplier who cannot answer the second question plainly has told you something important about the commercial relationship, whatever their tooling looks like.

2. Terminology: whether it is settled before writing

A glossary is only useful if it exists before the copy does.

Room categories, product names, restaurant and treatment names, loyalty tiers, regulated claims and dietary terms all need one agreed rendering per language. Settled in advance they cost an afternoon; settled afterwards they mean re-opening every page in every language.

So the question is not “do you maintain glossaries?” — everyone says yes — but “at which point in the process is our terminology agreed, and who signs it off?” In our process that is the Pre-Transcreation Study, before any writing, and the output goes into the Translation Memory. For The Gap Partnership we built bilingual glossaries into the memory precisely so that terminology held across a large body of training material in Simplified Chinese, Japanese and Korean.

3. Integration: what delivery actually includes

Content that arrives as a document somebody has to re-key is not finished, and the re-keying is where a whole class of error appears.

Delivery form What it means Who carries the risk
Files returned Documents or spreadsheets for your team to publish You do
— and errors introduced at publication are invisible to the supplier’s QA
Published into the CMS Content placed directly into the content management
system		 Shared, and checkable in place
Booking engine and portal content Including the fields and labels the CMS does not
hold		 Shared
App strings Localised into the app’s own content system, then checked in
context		 Shared
Print-ready artwork Proofed in position, in each language, before the run Shared — and the only form in which print errors get caught in time

We have delivered into Adobe Experience Manager for Frasers Hospitality, Sitecore for Resorts World Sentosa, Far East Hospitality and Millennium Hotels & Resorts, and the Drupal back end for COMO alongside the client’s own digital agency. For FWD we localised the Omne app into seven Asian languages, integrated into the app’s content management system and checked linguistically so every market could launch simultaneously. Those are the capability claims worth asking any supplier to match with names.

4. Storage, access and continuity

Ask where your language assets live and who can reach them.

Project files and language assets should be archived rather than left on individual machines, and the archive should survive staff changes on both sides. Ours are held in a data centre that meets industry standards in security, reliability and availability.

Deliberately, that is a plain statement rather than a classification claim. If a supplier offers you a tier number or a certification list, ask to see the certificate; in this category those claims are made more often than they are held.

What not to buy on

  • Tool names. Which translation management system a supplier uses is their operational choice. The capability, the ownership and the exit are yours.
  • Dashboards. A client portal is pleasant and is not evidence about the writing.
  • Throughput claims without scope. Words per day means nothing without the content type, the language and the review model attached.
  • Automation as a quality argument. Automation is a cost and consistency argument. On the content that has to persuade, the question is who writes it. That comparison is in AI translation versus human transcreation.

How the work runs

A supplier that can name its steps can tell you which one you are in. Ours runs in six:

  1. Understand the Project Brief. The content, the markets, the purpose and the constraints.
  2. Pre-Transcreation Study. Reviewing brand materials, style and tone, and uncovering the market-specific technical jargon and colloquial terms the content will need.
  3. Transcreation. The writing, drawing on the Translation Memory built for your brand.
  4. Client Review. Your own market teams read the content before it is live.
  5. Update and Approval. Revisions, then sign-off.
  6. Final Delivery. Into the system it has to live in, or as artwork ready to print.

What we can evidence

Delivery into the client’s own systems, named.

  • For Frasers Hospitality we relaunched the website in 15 languages, including Chinese, Japanese, Arabic and German — over half a million words in eight weeks, integrated into the client’s Adobe Experience Manager system, alongside CRM content, sales brochures and fact sheets.
  • For Resorts World Sentosa we are the appointed language service provider to the Digital and Regional Marketing teams, covering Sitecore websites, leaflets, in-market brochures, display ads and eDMs in Chinese, Japanese, Bahasa Indonesia, Tamil, Vietnamese, Thai and more, with a Translation Memory maintained per language.
  • For COMO Hotels & Resorts we localised website content into 7 languages — Arabic, Simplified Chinese, Japanese, French, German, Russian and Spanish — publishing into the Drupal back end alongside the client’s digital agency, and extended the programme to CRM content, in-room directories, spa and F&B menus and press releases.
  • For Far East Hospitality we are an appointed language service provider, handling Sitecore websites and CRM content — in-room directories, sales brochures and fact sheets — in Simplified Chinese, Bahasa Indonesia and Japanese for the China, Indonesia and Japan markets.
  • For FWD, the Omne app was localised into 7 Asian languages — Simplified Chinese, Traditional Chinese for Hong Kong, Japanese, Vietnamese, Khmer, Thai and Bahasa Indonesia — integrated into the app’s content management system and checked linguistically so that every market could launch simultaneously across APAC.
  • For The Gap Partnership we localised negotiation-training courseware for C-suite audiences into 3 languages — Simplified Chinese, Japanese and Korean — building bilingual glossaries into the Translation Memory.

The cost argument is about the programme, not the first invoice. A Translation Memory dedicated to your brand records how your content has been handled in each language, so repeat and updated material draws on work already paid for. Transcreated copy that is right first time avoids the redo cycle that literal translation sets off. And one partner across every touchpoint and market removes the coordination overhead of several suppliers, each interpreting your tone differently. Our clients cite those Translation Memory savings as one of the reasons they stay.

At IPPWORLD, we are an award-winning transcreation agency that specialises in creative translation and marketing localisation for the hospitality, travel, lifestyle and retail sectors. The award is Best Hospitality Creative Translation & Localisation Agency 2019, at the LUXlife Hospitality Awards. We have worked in this field since 1994, from Singapore, with an editorial team in Shanghai, and we work in 30 languages — 18 Asian, 10 European and 2 Middle Eastern.

Conclusion

The toolchain question is worth asking, but not in the form it is usually asked. Skip the software list. Ask whether the Translation Memory is yours and whether you can take it away; when terminology gets settled and who signs it off; what delivery includes, with named systems; and where your assets are stored.

Four answers, all judgeable by a non-technical buyer, and together they tell you whether the programme you are buying will be an accumulating asset or a recurring expense.

Frequently Asked Questions

What should we ask about a translation supplier’s technology?
Four things: is the Translation Memory dedicated to us and can we take a copy; at what point is our terminology agreed and by whom; what does delivery include, with named systems; and where are our language assets stored. Tool names are not among them.
Who owns the Translation Memory?
It should be your brand’s, dedicated to you rather than pooled across a supplier’s clients, with a copy available in a standard exchange format on request. If a supplier cannot say plainly that you may have it, the memory is functioning as a switching cost rather than as your asset.
Why does CMS integration matter?
Because content returned as files has to be re-keyed by someone, and errors introduced at publication are invisible to the supplier’s quality checks. Content published directly into the content management system, booking engine or app can be checked in place, which is where it will actually be read.
Should we care which translation management system a supplier uses?
No. That is their operational choice. What affects you is whether your terminology is settled before writing, whether the memory is yours, whether delivery reaches your systems, and whether the assets are archived somewhere accountable.
Does more automation mean better quality?
It means lower cost and more consistency on repetitive content, which is a real benefit on the operational half of an estate. On the content whose job is to persuade, the determining factor is who writes it, and automation does not change that question.
What claims about data security should we check?
Any that come with a number or a certification. Tier classifications and certification lists are claimed more often than they are held in this category, so ask to see the certificate. Our own statement is deliberately plain: a data centre that meets industry standards in security, reliability and availability.

Send us your systems list and content inventory and we will tell you what delivery would include. More on the process and the six things we hold ourselves to is on How We Work, and the category on marketing translation. Related reading: how to choose a translation vendor for a hotel group, what a hotel group should expect from an appointed LSP, AI translation versus human transcreation and how to check translation quality before it goes live.