Three translation quotes arrive. One includes independent review. Another charges separately for formatting. The third offers the lowest per-word rate but says little about who checks the work.
Which proposal is actually the best value?
A translation RFP template helps procurement, legal, and localization teams compare providers against the same requirements. An RFP, or request for proposal, describes the work, asks suppliers to explain their approach, and establishes how proposals will be evaluated.
The goal is not to make every project complicated. It is to find out what you are buying before a deadline exposes what the quote left out.
Start with the business use, not the word count
A customer support article, an employment agreement, and a product safety notice may have similar word counts. That does not make their translation requirements identical.
Explain who will read the material, where it will be used, and what could happen if the wording is wrong. Specify the target market as well as the language: a language name alone may not describe the audience precisely enough.
The American Translators Association’s guide to choosing a translator identifies specialization, experience, technology, and project requirements as relevant selection factors. Treat these as questions for suppliers to answer with evidence, not boxes to tick based on a sales presentation.
For a small, well-defined assignment, a detailed brief and comparable quotes may be sufficient. A formal RFP becomes more useful when several departments, recurring volumes, or multiple markets are involved.
A translation RFP template your team can adapt
Use the following structure in your procurement document. Give every bidder the same information and ask them to identify assumptions and exclusions explicitly.
| RFP section | Information to include or request |
| Business objective | Describe the audience, intended use, target markets, and consequences of errors. Identify the internal project owner. |
| Languages and scope | State the source language, target languages and regional variants, content types, estimated volumes, and expected update frequency. |
| Source files | Provide representative samples and file formats. Identify scanned text, graphics, tables, interface strings, and materials that need formatting. |
| Translation and review | Ask who translates, who reviews, what each review covers, and how subject-matter questions are resolved. Request relevant experience. |
| Terminology | Share approved product names, reference documents, and style guidance. Ask how terminology decisions and revisions will be recorded. |
| Technology and data | Require disclosure of machine translation, generative AI, subcontractors, and external processing services. Ask about access, storage, retention, and deletion. |
| Deliverables | Specify editable files, final formats, language variants, layout checks, and any required handover of glossaries or translation memories. |
| Schedule and service | Separate initial delivery, client review, corrections, and final approval. Ask how urgent changes and capacity constraints are handled. |
| Commercial terms | Request a breakdown of translation, review, formatting, project management, minimum charges, rush fees, and additional revisions. |
| Evaluation and acceptance | Explain the selection criteria, pilot requirements, acceptance process, issue-resolution procedure, and proposal deadline. |
A translation glossary records approved terminology and its context. Ask who will maintain it and what happens to it when the supplier relationship ends.
Ask what “human-reviewed” actually means
A proposal may use reassuring language without describing the work behind it.
Ask whether the reviewer checks the translation against the source, examines only the target-language text, or reviews a sample rather than the complete assignment. Confirm whether the same person translates and reviews, or whether a second qualified person is involved.
Technology disclosure matters, too. The ATA’s statement on artificial intelligence emphasizes transparency and professional involvement when AI is used in language work.
A useful procurement question is: “Which tools or external services will process our content, and what approval is required before that process changes?”
Do not assume that all tools have identical data practices. Ask for the applicable terms and the proposed workflow. For restricted material, have your security or legal team assess the arrangement before sharing files.
Compare the total scope, not just the per-word rate
Compare proposals on the same basis before scoring them. Ask each supplier to price the same sample project, with the same languages, review requirements, output files, and deadline.
Then separate the first-project cost from ongoing costs. For example, glossary preparation may be an initial activity, while recurring updates may involve review, formatting, and minimum project charges.
ETS’s guide to what affects translation pricing provides background on variables to clarify. A lower unit rate is not automatically a lower complete-project cost.
An example vendor evaluation scorecard
The weights below are a suggested starting point, not an industry standard. Adjust them to the consequences and complexity of your content.
| Evaluation area | Example weight |
| Relevant linguistic and subject expertise | 25% |
| Review process and issue resolution | 25% |
| Data handling and confidentiality arrangements | 20% |
| Delivery capacity and project coordination | 15% |
| Total evaluated cost | 15% |
Set mandatory requirements before applying weighted scores. A supplier that cannot meet a non-negotiable confidentiality or delivery requirement should not win simply because its price improves the average.
Use a representative pilot before a large commitment
For a substantial or recurring program, consider a paid pilot with shortlisted providers. Use material that reflects the real work, including terminology, formatting, and ambiguous passages that may require questions.
Agree on the assessment criteria in advance. Evaluate accuracy, consistency, usability, responsiveness, and the handling of reviewer feedback. Separate actual errors from stylistic preferences so the evaluation remains fair.
The pilot should test collaboration as well as output. A provider that identifies a source-text ambiguity before translating it gives you useful information about how future projects may be managed.
Frequently asked questions
Is an RFP necessary for every translation project?
No. Match the process to the project. A clear brief may be enough for a one-off assignment; an RFP is more useful for complex scopes or longer-term supplier selection.
Should every bidder receive the same sample?
Yes. Use the same authorized sample, brief, deadline, and evaluation criteria so your team can make a meaningful comparison.
What should happen after the supplier is selected?
Carry the agreed scope, review stages, data requirements, pricing assumptions, and acceptance process into the contract or statement of work. Do not leave them only in the proposal presentation.
Request a proposal based on your actual requirements
eTranslation Services provides document translation services for business and specialist content.
Preparing a translation RFP? Request a proposal from ETS with your language pairs, representative content, expected volumes, delivery formats, and deadlines. Confirm the proposed review stages and data-sharing arrangements before sending confidential material.
