Plan a multilingual RFP response from source to release

Production boundary

Start with the files the buyer requires, not a list of languages

English, German and French is not yet a production plan. A buyer may require a German technical response, a French overview and an original-language certificate with a particular translation. Each object has a purpose, authority basis, format and review requirement. List them separately. A language permitted for one attachment is not automatically permitted for the offer body.

Import the language-authority note prepared from the actual tender instructions. It should distinguish the authentic or governing source, accepted submission language, supporting translation and any certification requirement for the relevant object. This guide starts after those findings are evidenced. If an addendum creates a conflict, return the affected question for interpretation instead of asking a translator to choose which language should prevail.

For each output, identify the language and relevant locale, its intended reader, required format, response limits, source content, evidence attachments and relationship to other outputs. An internal English coordination draft may be useful without belonging in the submission. Mark its permitted use and keep it out of the release manifest unless an applicable instruction and release decision include it.

Choose the production route deliberately. A tightly specified technical schedule may be translated from a controlled drafting source. A local executive overview may be written directly by a qualified target-language author from the same approved claims. Both routes still need a way to verify meaning and permitted scope. Direct authorship is not permission to invent local features, clients or service commitments.

The plan should show missing work as well as assigned work. If a mandatory attachment needs a translation whose form has not been established, mark the dependency unresolved. If the required language reviewer is unavailable before the useful cutoff, the route is not feasible. A complete-looking language column must not hide an unconfirmed person or an unanswered instruction.

Assignments

Book the checks that a finished translation still needs

Assign work by task and competence. The translator needs the relevant source and target language skills and subject understanding. A bilingual checker compares the target with the source. A native or equivalently proficient local reviewer assesses natural usage and audience fit. A technical, legal or commercial authority decides whether the underlying commitment may be made. One person may hold several roles where appropriate, but the plan must retain each role and any required separation.

ISO’s published abstract for ISO 17100:2015 addresses translation-service processes, resources and applicable specifications. It excludes raw machine output followed by post-editing from that scope. Use the abstract to distinguish service routes; this plan does not claim conformance with the full standard or prescribe a supplier certification.

Obtain confirmed availability for the actual language pair, subject and window. A colleague who speaks French socially is not automatically qualified to review a technical exclusion. A qualified reviewer who receives the source only after the final export is due cannot provide a usable check. Include reading, queries, correction cycles and final-file inspection in the assigned work, not only the first translation pass.

Give each handoff an entry and exit condition. Translation starts from an identified source package with open questions labelled. Bilingual checking receives both source and target versions. Substantive approval receives the intended commitment and supporting evidence, with a competent language bridge if the approver cannot read the target. Final production receives the accepted target and resolved changes. A vague request to review everything leaves the meaning of approval uncertain.

Plan the sequence against the whole-bid schedule and actual reviewer calendars. Where two languages share a specialist, check that the windows do not overlap incompatibly. Reserve a route for substantive questions and rework. The plan can request a resource or propose a revised sequence; it cannot book people, waive independence or shorten a buyer deadline by assumption.

Translation brief

Tell the language team which meaning must survive

Supply the original buyer question and its location, the intended answer, supporting evidence and any conditions that limit the claim. Keep the approved meaning separate from a convenient sentence. A sentence can be shortened or reordered for the target reader while the actor, obligation, quantity, timing, scope and exceptions remain unchanged. Where they cannot be preserved within a response limit, the team needs a substantive decision rather than silent deletion.

Prioritize terms that carry consequences. Define the concept, preferred target term, permitted regional variant, prohibited misleading alternative and source of the choice. A corporate preference must not replace a buyer-defined term with a different meaning. If the buyer uses an ambiguous term, preserve the issue for the competent reviewer instead of resolving it through a glossary entry.

Protect identifiers and numbers according to their function. A document ID, product code or reference number is not ordinary prose. A locale-specific decimal separator may change the display without changing the value, but a changed unit or currency changes meaning. Record how reviewers will compare quantities, dates, service windows and exclusions across formats rather than relying only on identical character strings.

Identify non-text content: diagram labels, screenshots, spreadsheet tabs, formulas, footnotes and portal choices. A target-language narrative can be correct while an embedded image preserves an obsolete quantity. Assign these objects explicitly and retain any legitimate original-language content with the required explanation or accompanying translation.

Translation memories and earlier approved answers are references, not current approvals. Check their source version, buyer context, entity, service scope and terminology before reuse. An exact sentence match may be wrong for the present commitment. A new wording may be correct even when no stored translation matches it. The brief should explain the decision basis that lets the reviewer tell the difference.

Worked production plan

Ardenwick reopens four checks after two shared changes

Ardenwick Calibration is fictional. Its verified language note L-2 states, for this example, that the buyer requires a German technical annex and a French service overview. Both must express eight identified material claims, C-1 through C-8. English E-4 is an internal drafting source only. The note separately establishes the instructions governing interpretation; the use of English for coordination gives E-4 no legal priority.

The production plan links E-4 and the approved evidence package B-6 to German G-3 and French F-2. Each claim has an occurrence map in both target deliverables, including any table or caption that repeats it. The target-language teams have completed and recorded the required checks for all eight claims. Sixteen claim-language checks are therefore covered at this point. That denominator concerns the eight identified claims in two deliverables, not every word or every condition in the bid.

A subsequent authorized decision changes C-3 from twelve to eighteen workstations and changes C-7 to specify that the stated Monday-to-Friday support window excludes the identified regional public holidays. The underlying technical and commercial consequences have been assessed and approved in the example; language staff are not making those business decisions. E-5 and B-7 become the accepted production basis, and the change record identifies both revised claims.

C-3 and C-7 each occur in German and French, so four claim-language checks reopen. The twelve other checks may be carried forward only after an impact assessment confirms that their meaning, evidence, context and dependencies remain unaffected. A changed quantity may affect a total elsewhere, and a new exclusion may affect a summary. The occurrence map must capture those effects before the recheck is narrowed.

German G-4 is corrected and its two reopened claim checks are completed. French F-3 has the new workstation quantity but still lacks the holiday exclusion. At this checkpoint, fourteen of the sixteen identified claim-language checks have current accepted evidence, one French check is awaiting its required review, and one contains a known mismatch. The package is held under the stipulated release rule. A high completion percentage does not remove the hold, and the overview remains mandatory despite its shorter format.

Quality decisions

A natural sentence can still omit the condition that matters

Give reviewers a defined question. Bilingual checking asks whether the target preserves the source meaning and required content. Local-language review asks whether the result is clear and appropriate for its reader. Technical or commercial approval asks whether the statement is supported and authorized. These questions interact, but a positive answer to one does not answer the others.

DG Translation’s current quality guidance distinguishes bilingual revision for accuracy and completeness from monolingual review for clarity and audience fit, assigning work by language combination and expertise. This informs separate review tasks here. Its institutional quality arrangements do not replace the bidder’s own commitment and release authorities.

Classify findings by what changes for the bid. An omitted support exclusion needs a meaning correction and the relevant rechecks. A regional spelling preference may need only a local-language correction if its lack of substantive impact is established. A source passage that is itself ambiguous needs a source decision. Do not force the translator to make all three look like routine language edits.

W3C ITS 2.0, section 8.16 and appendix H, supports structured quality issues and distinguishes a potential issue from a confirmed error. It also ties severity to a stated assessment model. This is useful for inspectable findings, not a universal scoring threshold that can approve a tender response.

Record the source and target locations, issue type, consequence, proposed correction, owner and disposition evidence. If a reviewer rejects a machine flag, preserve why it was not an error. If an error is corrected, check the corrected version rather than merely closing the comment. Back-translation and automated comparison can suggest where to look; neither demonstrates that the forward translation preserves every material commitment.

Assistance boundary

Specify the permitted technology route before sharing the source

The plan may permit approved tools for terminology extraction, first-pass translation, comparison or formatting checks. It must identify which source material may enter which service and who owns the output review. Access to a translation tool does not itself authorize uploading customer documents, personal information or confidential pricing. Where permission is absent, keep the work within the authorized environment or seek an approved route.

ISO 18587:2017’s published scope addresses full human post-editing of machine translation and post-editor competence. The ISO page still lists that edition as published while a successor is under development. This scope helps describe an assisted route; it gives neither the machine nor the post-editor authority to approve a bid commitment.

Label machine output as unapproved until the planned human work is complete. A plausible translation can omit negation, change an actor or expand a service promise. The project needs reviewers competent to detect these changes, with the original source and evidence available. Calling an output post-edited is not a substitute for identifying what was checked and against which version.

An agent can prepare the delivery matrix, locate dependent passages, flag inconsistent quantities and propose review tasks. It should return source references, affected versions and unresolved questions. It must not decide a controlling language, certify a translation, alter an approved commitment, send files to an outside service or submit the offer merely because the plan describes those steps.

Release manifest

Close the language work on exact artifacts, not progress labels

For each required deliverable, the manifest names the final file, version, language and locale, purpose, source basis, approval references and any accompanying original. Check the generated file in the format the buyer will receive. Inspect tables, characters, embedded objects, response limits, links and attachments. If a production change alters meaning or hides a condition, return it to the relevant review route.

Ardenwick can remove its language-production hold only after F-3 is corrected, the required French rechecks are complete and the accepted content survives final production. The German artifact must also remain the exact accepted version. The manifest excludes the internal English draft. It records the complete language set without asserting that completion of these checks proves every other bid requirement.

Test the plan before relying on it: change one shared quantity, withdraw one terminology decision and supply a newer file that has not passed review. The workstream should identify affected targets and block the unchecked file from replacing an accepted artifact. Test a legitimate local wording difference as well, so the process does not mistake natural expression for a substantive contradiction.

The useful handoff is the verified language set plus the production and review evidence needed by the release authority. List unresolved exceptions with their consequence and next decision. Submission remains a separate authorized action. A plan that makes this boundary explicit lets people and agents prepare the response without silently granting themselves the right to commit the bidder.