Clarifying before translating isn’t a delay, it’s part of the work
There’s a moment in almost every project where a client asks, with a hint of surprise: “Why are there so many questions before the translation has even started?”
It’s a fair question. And the answer says a lot about what good translation actually involves.
Words that seem perfectly clear in English can carry significant ambiguity once you start working across languages. Take something as simple as “get your tickets.” Does “get” mean buy? Obtain? Access? Collect? In English, the distinction barely matters – the meaning is implied by context. In another language, each option leads to a genuinely different word, with a different tone and a different implication. Choose the wrong one, and you’ve mistranslated not the word, but the intent.
The same applies to words like “cheap” or “nearby.” In English, these are straightforward. In Italian, “nearby” alone has several credible translations – each with a slightly different level of formality, a different geographic implication, and a different feel. Without knowing where the word will appear, who will read it, and what the platform is trying to communicate, making the right choice is genuinely difficult.
This is why clarifying questions come early, and why they matter. Not to slow the project down, but to avoid making decisions at scale that later need unpicking. Fixing one sentence is easy. Fixing the same assumption replicated across hundreds of strings, after the content has already gone live, is a different problem entirely.
Good translation doesn’t start with words. It starts with understanding, and that always requires a conversation first.