A law firm sends fourteen thousand words at four on a Thursday and needs it by Monday morning. Whether that is routine or impossible depends on the language pair, the subject matter and whether anyone is available over the weekend.
The client has no way of judging any of that, which is why the request arrives as a deadline rather than a question.
A worked example
Say a standard rate of 0.12 per word, and a realistic throughput of 2,500 words a day per translator for specialist content with review.
Fourteen thousand words at 0.12 is 1,680 at standard rate, and at one translator's pace it needs about six working days.
The deadline allows two, so the work is split between three translators plus a reviewer to keep terminology consistent, with weekend working.
A rush surcharge of 50 percent brings the fee to 2,520. The reviewer's time to harmonise three translators' work adds perhaps 250.
So the honest quote is around 2,770 against a standard 1,680, and the difference buys weekend availability, a third more resource and the review that stops the document reading as though three people wrote it.
Publish your daily throughput
Words per day per translator, by content type. It is the single most useful figure a client can have, because it lets them judge a deadline before sending a request.
Publish the rush surcharge structure
By how much the deadline is compressed, not by how urgent the client says it is. A stated structure is defensible and stops each rush job being negotiated from scratch.
Explain what splitting a document costs
Consistency. Three translators produce three styles and three sets of terminology choices. Explaining that review exists to fix that justifies the line on the invoice.
Say when a deadline is not possible
A quality translation that arrives late is better than a poor one on time, and for some content a rushed job carries real risk. Declining honestly protects both sides.
Ask for the document, always
Word count, format, legibility, repetition and subject matter all change the quote. A client's estimate of length is usually wrong.
Offer a staged delivery
Delivering sections as they are completed often meets the real need, because the client frequently needs the first part on Monday and the rest by Wednesday.
Explain what is not included at rush pace
Desktop publishing, formatting, certification and a second review may not fit a compressed timeline. Saying so prevents a dispute about the finished file.
Reuse what has been translated before
Clients who send similar documents repeatedly are paying twice for the same sentences. Explaining that previously translated material can be reused, what that does to the price and why consistency improves as a result turns a rush job into an argument for a longer relationship rather than a one-off transaction at a premium.
Certification adds time
It is covered in certified and urgent translation questions.
Quotes stall without basic details
The pattern is in translation quote requests missing word counts and languages.
Deadline trades share this problem
It appears in rush print jobs and deadline questions and how cleaning companies quote and book jobs with a chatbot.
Getting started
Publish your throughput, rush surcharges and what is excluded at pace, then capture documents and deadlines at any hour. SpideyChat for agencies answers from your published pages, our plans are on the pricing page, and the chatbot ROI calculator works through the numbers.