Translation QA

Check translated creative against the original.

A localised file can read perfectly and still be wrong. LYNCE compares each market against the master you supply and reports what changed, what went missing and what no longer fits.

app.lynceapp.com/scan · spring-launch · 3 markets + master
Localised set · checked against the master2 clear · 1 held
OPEN-AIR NIGHTSSUMMERSUMMERESCAPEESCAPESAT 12 AUGUST · 20:00TICKETS €40Recieve your pass on arrivalMaster · ENClear
OPEN-AIR NIGHTSSUMMERSUMMERESCAPEESCAPESAT 12 AUGUST · 20:00TICKETS €40Recieve your pass on arrivalGreekClear
OPEN-AIR NIGHTSSUMMERSUMMERESCAPEESCAPESAT 12 AUGUST · 20:00TICKETS £40Recieve your pass on arrivalGermanHold
OPEN-AIR NIGHTSSUMMERSUMMERESCAPEESCAPESAT 12 AUGUST · 20:00TICKETS €40Recieve your pass on arrivalFrenchClear
Must fixGerman: £40€40 currency not localised

The mistake is in the gap, not in the sentence.

Proofread on its own, a translated banner looks fine — the grammar is correct and the words are real. It is only wrong next to the thing it came from.

Must fixMissing against the master

“Offer ends 31 March” absent from the Greek version

Fix Present in the master. The line was dropped in translation.

InconsistencyText no longer fits

German headline clipped at the container edge

Fix The translation is ~30% longer than the source. Re-flow or shorten.

Was this right?Correct

Three things go wrong when creative crosses a language. Something is dropped — an offer line, a disclaimer, an asterisk. Something is not localised — a currency, a date format, a phone number carried over from the source. And something no longer fits, because the translation is longer than the space the designer left for it.

None of those is a language error, which is why a linguistic review can pass a file that is still broken. LYNCE checks the exported artwork against the master, so it sees the gap rather than the sentence. Consistency within one language →

One scan, every market.

Upload the master as a reference, add the localised exports, and scan them together. Each version is checked against the source and against the others, so a value that drifted in one market shows up beside the four that did not.

It is built for the people who own the launch across markets: localisation managers, regional marketing teams, and the agencies adapting one campaign into six. Creative QA for agencies →

Add the master as a reference Upload every market LYNCE compares them Fix before release

What it will not do

LYNCE does not judge whether a translation is good. Tone, register, idiom and cultural fit are a native reviewer's job, and no automated pass replaces one. What it removes is the mechanical layer underneath — the missing line, the unconverted currency, the clipped headline — so the reviewer's attention goes to the part that actually needs judgement.

It also needs a source to compare against. Without a master, it can still check spelling, prices, dates and internal consistency, but it cannot tell you something is missing.

Translation QA, answered.

The final check, before it goes live.

Give the finished creative one more QA pass before publish, send or print.

Related