The questions a translator asks mid-project are a signal, not an interruption. Handled well, the query sheet is the most cost-effective quality mechanism you have. Handled badly, it goes silent — and silence is expensive.
- A silent translator is a warning sign
- Why it goes dead, and what that costs
- Running one that stays alive
A silent translator is a warning sign
On a technical project of any real difficulty, a good translator has questions. A source sentence is ambiguous. A term appears two ways in the same document. An acronym is not defined. When those questions stop coming, the charitable reading is that the source was flawless. The realistic reading is that the translator gave up asking and started guessing — and guesses on ambiguous technical content are where the worst errors come from.
The query sheet is the channel for those questions: a shared list where the translator logs what they could not resolve and someone on your side answers. Its value is not administrative. It is the single clearest early-warning signal you get that something in the source, the brief, or the terminology is unclear — and it surfaces while the work is still cheap to fix.
Why it goes dead, and what that costs
Query sheets go silent for one reason: the questions were slow to be answered, or answered dismissively, so the translator learned that asking does not pay. Once that happens, the ambiguities do not disappear — they get resolved silently, by assumption, and you find out at review, or after delivery, or from the market.
The economics are stark. A question answered mid-translation costs a two-line reply. The same ambiguity caught at review costs a re-translation and a re-review. Caught after a regulated document is filed, it can cost a resubmission. The query sheet is the cheapest point on that curve, and teams routinely starve it to save a day of someone’s attention.
Running one that stays alive
Name an owner who can actually answer — someone with the domain context, not a mailbox that forwards. Set a turnaround the translator can rely on; even "within one working day" changes behaviour, because the translator can keep working around an open question instead of stalling or guessing.
Feed the answers back into the termbase and the brief, so a question asked once is not asked again on the next document. A recurring query is a defect in your source material, and the fix belongs upstream — in the authoring — not in answering it repeatedly.
Finally, read the pattern of questions, not just the individual answers. A cluster of queries around one section usually means that section of your source is genuinely unclear, and every downstream language will hit the same wall. Fixing the source once is cheaper than answering the same question in twelve languages.