RFP Translation Services: What to Ask, What to Score


An RFP for translation services is a request for proposals: a written brief that tells language vendors what you need translated, how you will judge their offers and what the contract must cover. For Hungarian, English, German and French business content, the strongest proposal usually comes from a specialist who can show subject expertise, a documented quality process, confidentiality and a deadline you can believe. This guide covers both sides of the search: how to write or score a translation RFP, and how to get an RFP or bid response translated. It also shows where Wordsbyme, a Hungarian translation and localization specialist, fits.
TL;DR
“RFP translation” means two things: a buyer’s request for proposals from language vendors, or a bid document that has to be translated. The checklist below serves both.
A good translation RFP states scope, languages, subject matter, deadlines, rate structure, quality control, confidentiality and a scoring system before any vendor replies.
Pricing can be per word, hour, page or project, and urgent work can carry a surcharge, so ask every bidder to quote on the same basis.
For Hungarian work, a single experienced translator with CAT tools can answer most of those criteria directly. Wordsbyme’s Hungarian rates start at €0.05 per word.
Table of Contents
Two things people mean by “RFP translation”
The buyer’s RFP. Your company or agency needs documents translated and wants competing offers. You write the RFP, vendors respond, you score and sign. This is the main subject here, because the field is hard to compare. The Migration Policy Institute notes that language services are a fast-growing field with little oversight and standardization, so vendors differ widely in the services they offer and their quality. A clear RFP is how you make the offers comparable.
The translated RFP. You are a vendor, a manufacturer or a game studio answering a tender in another language, or you received a tender in Hungarian and must understand and answer it exactly. Here the translation is part of the bid itself. A mistranslated requirement, a wrong unit or a missed deadline clause can disqualify a response that was otherwise strong.
The two meet in the same place: precision, terminology, confidentiality and time.
What a translation RFP should contain
The Migration Policy Institute guide lists the elements that make a language-services RFP usable. Adapted to a business buyer, they are:
Scope of work. Document types, languages and dialects, and any technical-language needs (medical, legal, automotive, software strings).
Who is served. Which departments or product lines will send work.
Timeframes. Standard turnaround, and the penalties for missed delivery.
Rate structure. Per-word rates, expedite premiums, and whether translation, review and desktop publishing are priced together or separately.
Management responsibilities. Who assigns work, who answers queries, who approves the final file.
Capacity and technology. How many linguists the vendor can field and what tools it uses.
Quality control. How a vendor checks its own work before delivery.
Evaluation criteria. A point or percentage scoring system, published in the RFP itself.
The last point matters most. If you tell bidders how you will score them, you get proposals that answer your questions, not brochures.
Write the scope so a translator can price it
Give word counts, file formats (Word, InDesign, XML, JSON, subtitles) and whether files are editable. State the language pair and direction: translation into Hungarian and translation out of it are different tasks with different pools of qualified people. Say whether you have a glossary or previous translations. The Migration Policy Institute recommends asking whether translators will use buyer-provided glossaries, and a vendor who already maintains terminology will say so. If you do not have a glossary yet, terminology management is worth setting up before the first project, because it makes every later project cheaper and more consistent.
Pricing: ask every bidder for the same basis
Price comparison fails when one vendor quotes per word and another per page. The American Translators Association’s 2024 buying guide says translation can be priced per word, per hour, per page or per project. It also advises asking several providers for quotes, sharing your timeline early, settling the deadline with the provider’s input and expecting that urgent delivery may cost extra.
So your RFP should fix the basis. Ask for:
a per-word rate for each language pair;
whether repeated text and fuzzy matches (near-identical sentences already in a translation memory) are discounted;
a separate line for urgent work;
whether review by a second linguist and desktop publishing are included or extra.
The Migration Policy Institute guide describes exactly this choice between an all-inclusive rate and separate rates for first translation, third-party review and desktop publishing. If you cannot set a rate basis yourself, it suggests asking bidders for their going rates.
A worked example
Take a 10,000-word technical manual. At Wordsbyme’s published starting rates, translation into Hungarian begins at €0.05 per word, so the starting figure is €500. The same manual translated into English, German or French begins at €0.07 per word, so €700. Light machine translation post-editing starts at €0.03 per word and full post-editing at €0.04 per word, which suits content where a machine draft already exists. The final price depends on the text, so the quote comes after the file is seen. The point for your RFP is to get every bidder’s figures in the same shape, so the totals can be compared line by line.

What to ask vendors to demonstrate
This is where a translation RFP earns its keep. Public buyers have published their questions, and a private buyer can borrow them.
Experience and vetting. A Chapin Hall translation and interpretation RFP asks vendors how many years they have worked in language services, in which industries, how they vet and train linguists, and which languages they cover for written work.
Turnaround and continuity. The same RFP asks for a guaranteed turnaround time and for emergency coverage when a translator cannot deliver. This is the question that exposes the difference between a firm with a pool and a person with a promise, so ask it plainly: who delivers if the assigned translator is unavailable, and how fast do you answer a query?
Security. The Chapin Hall RFP also asks about information-security certifications and security protocols. If your documents are contracts, patient data or unreleased product specifications, add questions on file storage, who can access files and what happens to them after delivery. The Migration Policy Institute adds records-retention policy to the list. Our guide to confidential translation services goes through these points in detail.
Quality control. The GSA’s December 2025 ordering guide gives an example of an acceptable quality control plan. It includes review and approval by at least two qualified translators, use of the buyer’s glossary, a way to identify who approved each translation, a method for handling poor service and a plan for unintelligible source text. The same guide warns that translations can fail when they are accurate word for word but miss the meaning. So your RFP should ask how a vendor checks meaning, not only spelling.
References and codes of conduct. The Migration Policy Institute suggests asking for references, resumes, performance-monitoring forms and a professional code of ethics, and asking whether a proofreader verifies each translation.
How to score the proposals
Fix the weights before you open any envelope. As a real example, the 2025 New York City Health + Hospitals medical translation RFP scores proposals as follows:
Criterion | Weight |
Ability and feasibility to meet the scope of work | 30% |
Vendor experience | 20% |
Languages | 20% |
Cost (lowest cost gets full points, others proportionately less) | 20% |
MWBE status (minority- and women-owned business) | 10% |
The MWBE line is specific to that city’s procurement rules; a private buyer would replace it with its own priority, such as security or turnaround. The lesson is that price is one-fifth of the score, and the ability to deliver carries more weight than the rate.
The GSA guide adds factors worth borrowing: linguists’ education and training, how deep the linguist pool is, past performance, and testing of linguist skills with periodic retests. It also argues that providers dedicated to language work are better placed than firms treating it as a side line, because they stay close to the language community and its technology.
For specialist documents, add a short paid sample. Ask each finalist to translate the same 300 words of your real material, then have a subject expert in the target language compare the results. A sample on your own terminology shows more than any list of credentials.

Turnaround and urgent work
The NYC Health + Hospitals RFP shows how strict a buyer can be: a project manager must respond to a translation request within 2 hours and send an estimate within 1 business day. It also requires editing and proofreading by at least two medically qualified translators and a final check by a qualified project manager. You may not need that level for a brochure, but the habit is right: write the response time into the RFP, not only the delivery time.
If your work is urgent, say so in the scope, with volumes and typical deadlines. Vendors can then price a realistic rush rate and confirm whether they can meet it. Our pieces on rush translation and same-day translation explain what is realistic and what drives the premium.
When the RFP itself needs translating
If you are responding to a tender in another language, treat the translation as part of the bid.
Translate the requirements first. Before writing any answer, get the full tender text translated accurately, including annexes, evaluation grids and contract terms. Numbers, units, dates and legal wording need the most care.
Keep your terminology consistent. A proposal that calls the same component three different things reads as careless. A glossary built from the tender’s own vocabulary keeps the response aligned with what the buyer wrote.
Translate the response into the buyer’s language. Evaluators score what they can read. Technical sections, medical or legal references and software descriptions should be translated by someone who knows the field, not just the language.
Protect the file. Bid documents often hold pricing and technical know-how. Confirm who sees the file, how it is stored and how it is returned or deleted.
Plan the clock. Tender deadlines do not move. Agree the delivery time up front and send the source text in one complete package.
Public-sector tenders add their own conditions. A federal solicitation on SAM.gov, for example, can restrict bidders to a small-business set-aside with a size standard, require an active UEI (unique entity identifier) and fix a quote validity period. A translation does not fix eligibility gaps, so check these conditions before you spend money on translating a response.
Our perspective
We read translation RFPs from both sides, and the best ones ask the same few things: can you handle my subject, can you keep my files private, will you really deliver on the date, and who do I call when something changes? That is why we work the way we do. One translator with more than 15 years of experience handles each project, so the person who understands your terminology is the person who delivers it. We use up-to-date CAT tools and quality assurance checks to keep high-volume work consistent, and we stay reachable after regular business hours when a deadline is tight. For Hungarian-English work, and for German and French into Hungarian, that gives a buyer a direct line to the person doing the work. Confidentiality and realistic deadlines are part of every project, not an add-on. When we quote a date, we quote one we can keep. If your RFP is about technical, medical, legal, automotive, financial, software or game content, send us the scope. We will tell you what the project involves before you commit. Bernadett
How Wordsbyme handles RFP-related translation
Whether you are sourcing a Hungarian vendor or need a tender or proposal translated, Wordsbyme works directly with business and professional clients on technical, medical, legal, automotive, financial, marketing, software, website, multimedia and video game content, with localization for products and games. Translation into Hungarian starts at €0.05 per word. Translation into English, German or French starts at €0.07 per word. Full post-editing of machine translation starts at €0.04 per word and light post-editing at €0.03. Localization is quoted per project.

Send the files or the RFP scope through the Wordsbyme site and you get a quote based on your actual text. For background on briefing a Hungarian project, read our guide to Hungarian translation services. For larger programs, see how we run a translation project.
Subject-specific points to put in the RFP
Generic criteria get generic answers. Add the lines that match your content.
Technical documentation. Name the standards, product codes and units that must stay untouched. Our technical document translation guide lists what to send with the files.
Medical and clinical material. Say which documents are patient-facing and which are regulatory. See our notes on clinical trial translation and medical record translation for the document types and Hungarian specifics.
Legal text. State whether a certified or attested translation is required by the receiving authority, since that is the authority’s rule, not a vendor choice.
Software and games. Provide string files, character limits and tone notes, and ask how cultural adaptation is handled, not just word replacement.
FAQ
What is an RFP for translation services?
It is a document in which an organization describes its translation needs and invites vendors to propose how they would meet them, at what price and on what schedule. It usually sets the scoring criteria so offers can be compared fairly.
How much does translation cost per word?
It depends on the language pair, subject and deadline. Wordsbyme’s published starting rates are €0.05 per word for translation into Hungarian and €0.07 per word into English, German or French. The ATA guide notes that pricing can also be per hour, page or project and that urgent delivery may cost extra.
Do I need an RFP for a single translation project?
Not necessarily. An RFP pays off for recurring or high-volume programs, multiple languages or contracts that need formal scoring. For a defined Hungarian project, a scope with word counts, file formats and a deadline is usually enough to receive a precise quote.
What should I send to get a quote on a translated bid or tender?
Send the complete source files, the target language, the deadline, any glossary or earlier translations, and a note on confidentiality. A complete package lets the translator price accurately and commit to a date.
Sources
Translation and Interpretation Services SIN 541930 Ordering Guide, GSA, December 2025
RFP for Translation and Interpretation Services, Chapin Hall, June 18, 2025
Medical Translation Services RFP, NYC Health + Hospitals, 2025
Guide to Buying Translation Services, American Translators Association, August 2024
Recommended

Comments