01
Lag
Every locale trails the original, usually by one to two weeks. For eleven days the German customer is reading last month's message.
The export-and-email loop
How does content actually get translated?
In most global organisations, like this. The English content is finished on Tuesday. Someone exports it to a spreadsheet, emails it to an agency, and logs it in the tracker. The translations come back the following week, get pasted in by hand, and are checked by whoever happens to be free and happens to speak the language.
The German site ships eleven days after the English one. Nobody in the chain is careless. The chain is the problem.
The hidden bill
What are the costs nobody invoices?
02
Unevenness
Campaigns land at different times in different markets, which quietly breaks any promise the campaign made about timing.
03
Risk
Legal wording and product changes propagate at spreadsheet speed. A price correction that takes an hour in English is briefly wrong in four languages.
04
Errors
Hand-pasting introduces the mistakes automation exists to prevent: dropped paragraphs, broken formatting, the wrong version of the right file.
05
Coordination
When two campaigns run at once the tracker becomes a second job, and version confusion becomes a meeting.
SUM
The bill
A modest spreadsheet carrying an immodest cost, growing with every language the business adds.
The language lag
The original content is complete and published.
Content moves to a spreadsheet and tracker.
Translation happens outside the platform.
Teams re-enter and check translated content manually.
The same company has said two different things for eleven days.
A typical content item moves through exports, email and review before it reaches the translated site.
HOURS
Days become hours
When translation runs inside the platform's workflow instead of beside it.
CONTEXT
Review in context
Translations are checked on the actual page, not in a spreadsheet column.
LOCALE
Per-locale publishing
Each language ships on its own schedule, automatically.
Why it persists
Why does the spreadsheet survive every migration?
On a legacy platform it survives because it has no rival: no translation workflow, no connectors, no way to review a translation in place. The spreadsheet is the integration. On a modern platform the reason is softer and more common. The workflow exists, the connectors exist, and none of it was ever switched on, because wiring it up was nobody's project. The migration ended at go-live, and the tracker quietly re-established itself the following Monday.
Asked plainly
Frequently asked questions.
What does spreadsheet translation cost beyond the agency fee?
The costs that never get invoiced: lag between locales, campaigns landing unevenly across markets, legal and product changes briefly wrong in other languages, retyping errors, and coordination overhead when releases overlap.
Why do teams still translate through spreadsheets?
On older platforms there is no alternative: no translation workflow, no connectors, no in-context review. On modern platforms the capability usually exists but was never switched on, because wiring it up was nobody's project.
What does good translation workflow look like?
Content flows to translators inside the platform, returns into place automatically, is reviewed in context on the actual page, and publishes per locale on its own schedule.
Next step
How many days does your fastest language trail your first?
If nobody knows, that is also an answer. Measuring it takes an afternoon, and fixing it is usually configuration rather than replatforming.