Translation SLAs You Can Actually Meet

Quick answer — A translation SLA should measure time in your control, exclude waiting on reviewers you do not manage, and vary by content risk. A single turnaround figure for all content is the usual reason SLAs are missed.

Vitra.ai Universe creates, translates, adapts and publishes from one place.

One number for everything is why it fails

A blanket commitment — say two business days for any translation — is missed for three unrelated reasons, and no two of them have the same fix. A marketing paragraph and a regulated document are different jobs. So are five hundred words and fifty thousand. So are a language with deep memory coverage and one launched last week.

Averaging those into one figure produces a number that is generous for most work and impossible for the rest.

Commit by class, not by volume

The regulated row is deliberately phrased that way. Reviewer time is not yours to commit, and folding it into a headline number means missing the SLA whenever a reviewer takes a day — which they will, reasonably.

State it as two clocks: production time, which you own, and review time, which the reviewer owns and is measured separately.

Exclude the things you do not control

By name, in the agreement.

Source content that changes mid-job. Approvals from people outside the workflow. Third-party platform outages. Content arriving without the context needed to translate it.

That last one is worth listing explicitly, because it is the most common cause of a missed deadline and the easiest to fix — a string with no screenshot and no note is a question, not a task.

Measure what the business feels

Not translation turnaround. Request to published.

That number includes the queue before translation and the approval after it, and it is the only one anybody outside the team recognises. Commit to it once you can see it, and improve it by shortening whichever segment is longest — usually neither of the ones an SLA traditionally covers.

Automate the measurement rather than reporting it manually, and let quality control findings explain the outliers. A submission date that cannot move is the strictest SLA there is — construction tender translation.

FAQ

Why are translation SLAs usually missed? Because one number covers content classes with genuinely different requirements. A regulated document, a marketing paragraph and a new language pair cannot share a turnaround commitment.

Should reviewer time be included in a translation SLA? No, not in the same clock. Reviewer availability is not yours to commit, so state production time and review time separately and measure each against the party that controls it.

What should be excluded from a translation SLA? Source content changing mid-job, approvals from outside the workflow, third-party outages, and content arriving without the context needed to translate it. Name each explicitly in the agreement.

What metric should actually be committed to? Request to published, because it is the only number the wider business recognises. It includes the queue before translation and the approval after it, which is where most delay lives.