What should a request for quote include besides "please quote"?
A request for quote should say what the job is, in enough detail that two replies can be compared. That means the language direction, the files themselves, when the translation has to be in a named inbox, whether you need a target-only file or a bilingual one, and whether layout is included. “Please quote” plus an attachment leaves every one of those to be guessed. There is no public rate card that already answers them.
An email went out on a Wednesday with the subject “please quote” and a zip. Three replies came back. One included rebuilding the slides and assumed a Friday delivery. One priced the words only and assumed the client would paste them. One treated the scan as certificates and priced it by the page. All three were answering the email they had received. None of them was answering the same job, and the buyer spent the next day in calls reconstructing a brief that could have been six lines under the attachment.
The lines that stop the guesses
Name the source language and the target language. Say the file types in the zip. Give the date and the time zone of the deadline, and say whether that is a draft date or a delivery date. Say what “done” looks like: a Word file, an InDesign package, a spreadsheet of strings, a typeset certificate. Say whether a second person will read against the source, because a quote with that reading and a quote without it are different offers.
Mention text that must stay as it is: codes, names, approved slogans. Mention files that are reference only and must not be translated. A zip with no labels forces the vendor to open everything and assume the largest file is the job.
What the vendor still has to look at
The brief does not replace the file. The vendor still has to see whether the PDF text can be copied, whether the slides hide strings, whether the word count includes tables. A good request makes that inspection possible: it sends source files, not photographs of a screen, and it says who can answer a question the same day. A request that forbids questions, and also omits the deadline, produces a quote padded against the silence.
If the deadline is a real constraint, say what happens to pages that are not finished. A partial delivery is a different quote from a complete book on the same date. Leaving it unsaid means one vendor will assume the partial and another will refuse the date.
How to read the replies once the brief is complete
Line the replies up against the brief, row by row: direction, count, unit, review, layout, date, delivery form. A lower number that dropped the layout is not a lower price for the same work. A higher number that names a second reader is not automatically a padded one. The brief is what makes those rows exist. Without it, you are comparing three imaginative readings of “please quote.”
Keep the brief with the purchase record. The next language, or the next edition, starts from those lines. The zip alone will not remind anyone whether layout was in or out.
How long should that email be?
Short, a dozen concrete lines beat a page of background. The vendor needs the constraints and the files, and history and enthusiasm can wait until the kickoff, when someone is actually doing the work.
What if the word count is unknown?
Say that the count is unknown, send the file, and ask for a count in the quote with the unit and the language. An unknown count is a reason to include the file, and the mail still has to carry the rest of the brief.
The related service page is translation services.
Quick FAQ: AI Translation Accuracy
- How accurate are AI translators? Accuracy is often high for repetitive or general content, while domain-sensitive content still needs expert review.
- How to improve AI translation quality? Use glossary control, domain prompts, QA checks, and human post-editing in one workflow.
- Where does human translation still win? Legal, medical, and high-stakes brand content usually requires human nuance and accountability.