A client sends a document at four on a Friday afternoon needing it in another language by Monday morning. It is dense, technical and considerably longer than they described.
The translator works the weekend, charges a modest surcharge, and delivers. The client now believes this is normal, and every subsequent job arrives on a Friday.
A worked example of the arithmetic
Take a translator with a realistic daily throughput on technical material. A document at three times that volume, needed overnight, is not a surcharge question. It is a question of how many people are involved and what that does to consistency.
Where the cost actually comes from
Displaced scheduled work that must be rescheduled or subcontracted, out of hours working, splitting across translators, and the extra reconciliation needed when several people work on one document.
Why a small percentage surcharge fails
It prices urgency as a minor inconvenience. The real cost is the disruption to everything else in the week, and that is frequently larger than the job itself.
Option one: a defined rush tier
Standard, priority and urgent, with a stated turnaround and a stated uplift for each. Clients choose deliberately and nobody negotiates.
Option two: turnaround based on volume
A published daily throughput, so that a client can calculate their own deadline. This is honest and it stops impossible requests before they are made.
Option three: decline and say why
Where compressing the work would mean skipping the checking stage on material where errors matter, declining is the professional answer.
Explain what gets compressed
Clients assume rushing means working faster. Saying plainly that it means less checking, or more translators and less consistency, changes what they ask for.
Offer a partial delivery
The critical section first, the remainder on a normal schedule. Frequently this is what the client actually needs and nobody offers it.
Ask what the deadline is attached to
A filing date, a meeting, a flight or an assumption. A meaningful share of urgent deadlines dissolve under one question.
Get the word count before quoting
Not an estimate. The actual file, because clients describe a short document and send forty pages.
Ask about the subject matter honestly
Specialist material cannot be accelerated the way general text can, because the available pool of competent translators is smaller.
Handle certified and official work separately
Certification, notarisation and official processes have their own timelines that no surcharge shortens, which is the ground covered in certified and urgent translation questions.
Recognise the agency client pattern
Agencies and firms pass on their own deadlines, which is the dynamic described in turnaround and rush job questions from agencies and firms.
Borrow from other deadline trades
The same structure works well in rush print jobs and deadline questions.
Do not let the surcharge become invisible
Clients need to see what urgency costs, which is the disclosure argument in the hidden costs of answering services.
Answer the urgent enquiry immediately
These arrive at four on a Friday and go to whoever replies. An assistant that asks for the file, the word count, the language pair, the subject and what the deadline is attached to, then states the rush tier and its price, wins the work without anybody promising the impossible. See pricing, run the numbers on the chatbot ROI calculator, and the sector view sits under agencies.