Which language version controls when a tender is multilingual?

Direct answer

There may be no single controlling language for the whole tender

The safe answer is usually a matrix, not a language name. One row answers which version of the notice is authentic. Another identifies the language that prevails if issued procurement documents disagree. Separate rows record languages accepted for the bid, translations required for supporting documents and the language that will govern the signed contract. A language can control one row and be irrelevant to the next.

For notices published under Articles 48, 49 and 50 of Directive 2014/24/EU, Article 51(3) says that the full version or versions in the EU official language or languages chosen by the contracting authority are the sole authentic texts. Summaries appear in the other EU official languages. TED’s eForms guidance adds two practical facts: when several official notice languages are selected, they have equal legal status; and the first NoticeLanguageCode in the XML exists for technical reasons and has no legal effect. An agent must therefore preserve the full set instead of ranking the first code.

That rule does not declare the language of every annex, response or contract. The notice can point to procurement documents that state a separate precedence clause and submission rule. The invitation may identify the language in which the offer must be drafted. A certificate written in another language may need an accompanying translation. The draft contract may define its own governing text. Move from object to object and record each result with its source.

If two texts that should be equal say different things, “equal” is not a method for choosing the convenient one. Record both passages, classify the result as language_conflict_review and stop the affected action. The buyer’s designated clarification channel or a qualified reviewer can resolve what the public documents do not.

Evidence classes

Fluent text can still be the wrong evidence

Capture provenance before meaning. A TED page may contain full official versions, partial text in a non-official notice language and interface labels supplied for navigation. A buyer portal may add a browser translation. A colleague may paste a machine translation into the workspace. All can be useful, but they do not share authority. Preserve the exact source language passage, URL, notice or document identifier, version, publication or issue time and retrieval time beside every derivative text.

Use working_translation_only for a translation created by the bidder or a general translation service. It can support search, routing and a first reading. It cannot replace the source passage in a compliance decision. partial_non_authentic_display fits a TED summary or other published rendering that the source does not mark as authentic. buyer_designated_document_language requires an issued provision that names the procurement-document language or gives one version precedence. The fact that a buyer uploaded only one visible file is evidence of availability, not a precedence clause.

Keep labels literal. “Official website” describes the publisher, not the legal status of every translation on that website. “English version” describes language, not priority. “Certified translation” describes a form of evidence, not whether the translated content becomes the governing tender text. A good language note quotes the rule instead of improving its wording.

Authority map

Tie every conclusion to an object, an action and a current clause

Start the record with identity fields: procedure, notice ID and version, publication number where available, buyer, lot, legal basis, funding regime and portal. Then add one row per language-bearing object. A row needs object_id, object_type, title, version, issued_at, source_url, observed_language and status_assertion. Store the quoted assertion and its section anchor. Without the assertion, a language classification is only an observation.

Add the action because the same file can support several different decisions. A bilingual invitation may allow a request to participate in either language but require the final offer in one. A technical standard may remain in its original language while the response field must be completed in another. A foreign certificate may be accepted only with a translation, yet the certificate itself remains the underlying evidence. Model search, interpretation, drafting, upload, submission, clarification and signature separately.

Finally record valid_from, checked_at, contrary_evidence, review_owner, allowed_use and recheck_trigger. allowed_use should be narrow: “draft technical response in French”, “use English notice for qualification”, or “search only”. Avoid “tender language confirmed”. Recheck when a notice version, addendum, clarification, invitation, portal rule or contract draft changes.

Document sequence

Notice authenticity and document precedence are different questions

Read the publication rule first because it tells you which notice text can support notice facts. Then follow the notice to the designated procurement documents. Inventory the instructions to tenderers, specifications, schedules, forms and contract conditions, including each language version. Search for terms such as language, translation, version, discrepancy, prevail, governing and interpretation, but read the whole clause. A keyword hit can refer to correspondence rather than the offer.

Build the document order from explicit provisions. A clause may say that one language prevails if issued versions differ. Another may define the order between addenda, instructions, specifications and schedules. Keep these as separate edges. A language rule does not necessarily resolve a conflict between two documents in the same language, and a document-priority rule does not necessarily choose between translations.

Check every issued clarification and addendum after the base pack. The World Bank’s current Procurement Regulations define procurement documents broadly enough to include addenda and require clarifications and addenda for specified documents to be in writing and sent to recipients. The tender-specific pack remains essential: it establishes which documents were actually issued, in what languages and with what effect. If only one language received a later correction, record the asymmetry and seek an authoritative answer rather than translating the change into the other version yourself.

• Retain the notice language metadata and the full text used.
• List every issued language version by document and version.
• Quote each precedence and document-order clause separately.
• Attach clarifications and addenda to the instruction they affect.
• Hold the affected decision when equal texts diverge without a resolution.

Submission control

Accepted response languages do not settle every attachment

Create an action row for each submission component: qualification form, technical response, commercial schedule, declaration, reference, certificate, CV, product literature and portal field. Read the invitation and instructions for an affirmative language rule. If the documents say “offers shall be in French”, do not silently extend that sentence to a certificate for which the pack separately permits an original plus translation. If several languages are allowed, store the allowed set and any rule against mixing them.

Translation and certification are separate attributes. translation_required means the original-language evidence must be accompanied by a version in the named language. certified_translation_required needs an explicit legal or tender-specific basis and a defined evidence scope. It does not mean the translation replaces the original. Record whether both must be uploaded, who may certify, and which file naming or signature rules apply. If those details are absent and consequential, mark not_stated and request review.

Portal behavior is a final consistency check, not the source of an unstated rule. A dropdown that exposes one language may reveal how a field is configured, but it cannot narrow a published permission without investigation. Conversely, a portal that accepts any Unicode text does not authorize every language. Preserve screenshots or field labels as operational evidence and keep the governing instruction beside them.

Contract boundary

Start a new language decision when the contract is formed

A tender-stage precedence rule can stop at award. Read the draft contract, any completed contract data and the final signed form. Record applicable law and dispute language separately from governing language; they answer different questions. If the contract rule depends on the language of the successful bid, the authority row cannot be completed until that bid language is known.

The World Bank’s seventh-edition Procurement Regulations show why inheritance is unsafe. For international competitive procurement, the borrower chooses English, French or Spanish for the procurement documents and may issue a national-language translation. The chosen international text prevails on discrepancies. If the documents are issued in two languages, a bidder may submit in either. The contract must then be written in the language of the winning bid, and that language governs the contractual relationship. The answer changes from document interpretation to bid permission to contract governance without contradiction.

Do not turn that example into a universal rule. Apply it only when the procurement is governed by those Regulations and the tender-specific documents support the relevant facts. Another regime can use a different model. The portable method is to identify the object, rule source and action each time.

Worked example

One procurement produces four defensible language findings

A fictional transport authority publishes an EU contract notice in English and French. The eForms metadata marks both as official notice languages. English appears first in the XML. The authority also runs the project under the World Bank’s current IPF Procurement Regulations. Its request for proposals is issued in English and the national language, with a clause that the English text prevails on discrepancy. Both versions contain the same submission permission.

The notice row is equal_authentic_notice_languages for English and French. The first XML code changes nothing. The procurement-document row is buyer_designated_document_language for English because the pack and governing Regulations establish the discrepancy rule. The bid row is submission_language_allowed for English and the national language. French is not automatically allowed merely because the TED notice is authentic in French.

The bidder chooses the national language. Its French parent-company certificate is submitted in the original plus the national-language translation required by the evidence schedule. Those files receive translation_required, not a claim that either version governs the RFP. After award, the contract row records the national language because the applicable World Bank rule ties the contract to the submitted bid language. The earlier English document-precedence finding remains true within its stated tender-stage scope.

Now suppose a late clarification says technical schedules must be completed in English, while the general instruction still permits either bid language. That component becomes language_conflict_review until the buyer confirms whether the clarification narrows only the schedules or the whole bid. The agent can prepare unaffected sections, cite the conflict and draft a question. It cannot choose an interpretation or contact the buyer without authorization.

Agent contract

An agent should return evidence, permission and a stop condition

An agent-facing answer should be inspectable without replaying the search. Return the procurement identity, object and version, intended action, observed language set, controlled state, quoted authority passage, source URL and anchor, checked time, contrary evidence, confidence basis, review owner, expiry trigger and allowed use. Link derivatives to the preserved source text. Do not emit a free-floating sentence such as “English controls.”

Automatic actions are narrow. The agent may classify a clearly marked non-authentic summary, identify equal TED notice languages, route a foreign certificate for translation, or draft within an explicitly allowed language. It must stop when the current official object is unavailable, language status is unstated, equal texts conflict, a clause requires legal interpretation, certification requirements are unclear or an external communication or submission would follow.

The result should remain useful after a handoff. A reviewer needs to see what text was read, why the state follows, which action is blocked and what new evidence would resolve it. That is the difference between language-aware retrieval and an unsupported answer in the reader’s preferred language.