The failure modes that show up specifically under deadline pressure, and the handful of things that actually keep a fast job accurate.
- Speed doesn’t break translation. Splitting does
- The termbase has to come first, even when there’s no time
- What you cut, and what you never cut
- What to tell the vendor when the clock is short
Speed doesn’t break translation. Splitting does
A rushed translation rarely fails because someone typed fast. It fails because to hit the deadline the file gets cut into pieces and handed to several people at once — and the moment that happens, the same term starts coming back three different ways. One translator writes "housing", another "enclosure", a third "casing". Individually all fine. Together, in one manual, it reads as three different parts.
So the real question with a rush job is not "can you translate this by Friday". It is "how are you going to keep five people consistent when there is no time to reconcile at the end". If the vendor has no answer to that, the speed they are promising is being bought with your accuracy.
The termbase has to come first, even when there’s no time
Counterintuitively, the tighter the deadline, the more it pays to spend the first hour on terminology rather than diving in. Before the file is split, someone senior pulls the recurring terms and the obvious traps, locks them, and pushes that list to everyone. That hour is not lost time; it is the only thing that lets parallel work stay consistent without a slow reconciliation pass you do not have time for.
When we take a genuine emergency — an FDA certification file over a weekend, a launch document overnight — that termbase step is the first thing that happens, not the thing that gets skipped because the clock is running. Skipping it is exactly how you end up delivering fast and wrong.
What you cut, and what you never cut
A fast job is a job with fewer passes, and that is fine as long as you cut the right ones. You can drop a second stylistic polish. You can accept that the layout gets tidied later. What you do not cut, ever, is the domain review on anything where an error has consequences — a dosage, a safety step, a claim, a contract clause. The temptation under deadline is to treat the expert review as the slow step to remove. It is the one step whose removal is the whole risk.
This is where AI genuinely helps a rush job, used honestly: it produces the draft in minutes so the scarce human time goes entirely into checking the parts that matter, not into typing. AI buys back the hours; it does not buy back the accountability.
What to tell the vendor when the clock is short
Three things, and they change the outcome more than the deadline itself. Send whatever approved material you already have — a previous version, a termbase, a labelling reference — because it removes decisions that would otherwise eat time. Tell them plainly which parts are high-stakes, so review effort goes there rather than being spread evenly. And name a single person on your side who can answer a terminology question fast, because on a rush job a query that waits six hours for an answer is six hours of the deadline gone.
A good vendor will ask for exactly these before quoting a fast turnaround. If they just say yes to the date without asking, that is the tell.