A bilingual search and verification sheet connects one bounded business concept to exact terms found in official target-language procurement sources. Each row keeps the source phrase, language, notice identifier, field, passage, working-language gloss, concept judgement, terminology evidence, executable query, search result and review state. It distinguishes an observed buyer term from an official vocabulary label, a machine-translated hypothesis and a phrase verified by a competent language reviewer. The sheet may authorize a search or mark a notice for review. It cannot by itself establish eligibility, interpret a mandatory condition or approve a bid.
Cross-language discovery fails in two opposite ways. A team searches only in its own language and misses notices whose titles and lot descriptions use local terms. Or it translates a long keyword list, runs every variant and treats fluent output as faithful meaning. The first approach creates invisible gaps. The second hides false equivalents, local procurement formulas, compound words and conditions whose force changes with one modal verb. A translated result can look precise while the official notice, an attachment and the portal interface each carry different language and authority. The team needs wider discovery without letting provisional language silently control qualification.
Treat translation as an evidence-bearing bridge. Start with a precise concept in the team’s working language, then use stable classification codes and official terminology to locate target-language examples. Extract the words that buyers actually used, with their passages and fields. Test each target-language query on the portal that will run it, because multilingual search behavior differs. Keep the original beside every gloss. Machine translation may help triage, but any deadline, exclusion, minimum, submission instruction, scope boundary or contractual duty must return to the authoritative text and a competent reviewer before it drives action.
Boundary
Let provisional language widen discovery, not decide the bid
Draw two lanes before opening a translation tool. The discovery lane asks whether a record may concern the capability. It can use machine translation, multilingual code labels, terminology databases and semantic suggestions as leads. The decision lane asks what the buyer actually requires and what the supplier may do next. It relies on the current official notice and documents, with language and procurement competence proportionate to the consequence. A record can pass discovery while remaining blocked from qualification.
The European Commission describes its own machine translation as a way to obtain a basic idea and warns that accuracy varies between texts and language pairs. Use that boundary operationally. A translated title may justify opening a notice. It does not prove that the lot fits, that a certificate is accepted or that a date is a submission deadline. Give every extracted statement an action scope such as search only, triage allowed, reviewer required or verified for the named decision.
| Evidence state | What it supports | What it cannot support alone |
|---|---|---|
| Machine suggestion | Candidate term or rough triage | Rejection, eligibility or deadline action |
| Official vocabulary label | Concept bridge and code search | Proof that a buyer uses the phrase |
| Observed notice phrase | Reproducible target-language query | Meaning outside its cited context |
| Reviewer-verified passage | The recorded interpretation and decision | Unrelated passages or later versions |
| Unresolved original | A visible hold and review request | Any consequential action |
Concept
Describe the need before looking for an equivalent word
Write a short concept record in the team’s working language: purchased object, performed activity, intended outcome, users or assets affected, delivery context and explicit exclusions. “Maintenance” is too thin. “Preventive and corrective maintenance of imaging equipment in operating hospitals, excluding construction work” gives a reviewer enough structure to judge a candidate in another language. Preserve the definition as the fixed comparison point. Do not rewrite it to fit the first translation returned.
Add a structured bridge where the market provides one. The Common Procurement Vocabulary assigns the same code to descriptions in the EU’s official languages and was designed in part to overcome language barriers. That makes a reviewed CPV branch useful for finding notices whose free text you cannot yet formulate. It remains a classification, not a semantic guarantee. A code can cover neighboring services, and a buyer can choose a broad or imperfect code. Keep code matches as a separate discovery lane and judge the text of each result.
- Fix the object, activity and outcome.
- Name adjacent work that should not count as a match.
- Specify target countries, languages and procurement stages.
- Link reviewed classification codes without calling them translations.
- Record which part of the concept each foreign phrase appears to express.
Evidence
Learn the target language from official procurement usage
Use the code lane, known buyers, prior awards and official terminology resources to find a small set of plausibly relevant records. IATE can connect concepts across EU languages, and eForms publishes multilingual procurement labels. Treat both as candidate sources with their own status. The eForms documentation warns that some non-English labels were produced automatically and have not been reviewed. A label can help navigate a form while still needing confirmation in real notices.
Open the official record and capture the smallest useful expression with its complete sentence. Save the title or lot field, notice and version identifier, buyer, publication date, source language and URL. Include a literal gloss and a plain explanation of why the passage matches the fixed concept. Preserve spelling, accents, compounds and abbreviations. When several records repeat one template, mark the lineage so repetition is not mistaken for independent usage. Contrast examples that use the same words for an adjacent purchase are equally valuable.
| Field | Recorded value | Control |
|---|---|---|
| Concept ID | Language-independent capability statement | Stable across rows |
| Source phrase | Exact target-language text | Never overwritten by a gloss |
| Passage and field | Sentence, title, lot or document location | Keeps meaning in context |
| Official identity | Portal, notice, version, lot and URL | Supports retrieval and change checks |
| Working gloss | Literal aid in the team language | Marked provisional |
| Concept judgement | Match, adjacent, false friend or unresolved | Reason and reviewer named |
| Evidence class | Buyer use, vocabulary, machine lead or human verification | Limits permitted action |
Search test
Test what the portal does instead of assuming cross-language search
A multilingual interface does not necessarily translate a query. TED states that its quick full-text search covers every text field, displayed code label and language. Its expert-search guidance also describes language-specific stemming for multilingual fields. Neither statement should be expanded into a claim that an English concept will automatically retrieve every equivalent expression in French, German or Polish. Test the literal query, inspect known examples and record the behavior actually observed.
Run separate arms for the working-language term, each target-language phrase, reviewed classification codes and justified combinations. Freeze portal, date range, geography, notice stage, field and syntax. Deduplicate by stable notice or procedure identity. Review only the additions contributed by each arm and record relevant, irrelevant and unjudged results. Search performance belongs to the exact surface and date tested. Do not transfer it to another national portal whose tokenizer, transliteration and fields are unknown.
| Arm | Question answered | Evidence retained |
|---|---|---|
| Working-language phrase | Does the portal bridge languages? | Known hits and misses |
| Target-language phrase | What local wording adds | Literal syntax and unique results |
| Classification code | What structured discovery finds | Code scope and result judgement |
| Phrase plus code | Whether structure controls ambiguity | Lost and gained relevant records |
| Spelling or script variant | Whether normalization changes retrieval | Variant, reason and observed effect |
Review
Escalate the sentence whose meaning could change the decision
Do not commission a translation of the whole pack before knowing whether the opportunity is plausible. Triage first, then extract the passages that govern the next decision: scope, lot boundaries, conditions of participation, exclusions, mandatory standards, evidence, minimum values, deadlines, submission mechanics, award method, pricing and contract obligations. Send the original passage, surrounding context, source identity and the exact question to a reviewer. A free-floating sentence is cheaper to translate but easier to misunderstand.
Reviewer competence must match the risk. A fluent or native speaker can confirm ordinary operational meaning; procurement terminology and legal effect may require a bid professional, lawyer or other qualified subject expert in the relevant jurisdiction. Record who reviewed what, when, against which version and for which decision. Verification is local to that passage. It does not certify the whole notice, and a later amendment reopens affected conclusions.
| Passage type | Minimum treatment | Allowed result |
|---|---|---|
| Title or broad description | Machine triage with original visible | Open or dismiss only with stated confidence |
| Detailed technical scope | Fluent reviewer plus subject owner | Capability-fit finding for named passage |
| Deadline or submission instruction | Official source and competent language review | Operational date or step with source |
| Eligibility or mandatory condition | Language, procurement and legal review as needed | Recorded decision, uncertainty or escalation |
| Contract obligation | Qualified commercial or legal review | Risk note for the specific clause |
Handoff
Publish a sheet another agent can execute without inventing certainty
Publish the accepted target-language terms separately from research candidates. Each accepted row needs concept ID, exact source phrase, language and script, passage, official record, evidence class, query syntax, tested surface and date, result judgement, reviewer, allowed action and expiry trigger. Keep rejected false friends and unresolved phrases with reasons. That history prevents another agent from reintroducing a fluent but unsafe equivalent.
Return negative findings with coverage. “No relevant result in the tested French phrase and CPV arms on this portal for this date window” is auditable. “No tenders exist” is not. Agents may collect public evidence, propose candidates, execute read-only searches and route passages. They should stop before qualification, outreach or submission when language authority or consequential meaning is unresolved. Reopen the sheet after a missed known-relevant notice, a portal change, a new target country or a material amendment.
- Expose original text beside every working gloss.
- Separate search permission from decision permission.
- Keep official identity, version and review timestamp.
- Retain false friends and unresolved terms as first-class states.
- State searched, blocked and unsearched coverage explicitly.
- Never let translation confidence authorize contact or submission.
What good looks like
Useful outcomes from search tenders in another language
- The searched capability is defined independently of any one language.
- Every production search term has exact target-language evidence and provenance.
- Official language versions are separated from partial or convenience translations.
- Classification codes and terminology resources guide discovery without masquerading as buyer usage.
- Every query records its portal, syntax, filters, execution date and judged additions.
- Machine-translated text remains visibly provisional.
- High-consequence passages are routed to a competent language and subject reviewer.
- Agents can state what was searched, what remains unread and which actions are permitted.
Operating model
How to run the work
- 01
Fix the concept and target market
Describe the deliverable, activity, outcome, exclusions, geography and notice stage before choosing foreign-language words.
- 02
Find language bridges
Use official codes, multilingual terminology and known relevant notices to locate target-language candidates while preserving their evidence class.
- 03
Harvest buyer wording
Extract exact phrases from official titles, lot descriptions and public documents with identifiers, passages, language and version.
- 04
Test separate query arms
Run each target-language phrase and structured-code arm on the real search surface, then deduplicate and judge unique results.
- 05
Escalate consequential meaning
Send legal, commercial and submission-critical passages back to authoritative originals and qualified reviewers before acting.
- 06
Publish the evidence boundary
Release approved search rows, unresolved terms, review status and allowed next actions as a versioned record.
Evaluation
Questions that change the decision
- Which exact business concept must survive the language change?
- Which target languages and official portals belong in scope?
- Is a phrase observed in a notice, supplied by a controlled vocabulary or only machine-suggested?
- Is the displayed language an official version, a partial non-official version or a convenience translation?
- Does the portal translate queries, search all language fields or merely stem words within each language?
- Which query arms add relevant notices after deduplication?
- Which passage could change eligibility, deadline, price, scope or submission compliance?
- What review is required before the agent may recommend qualification or another action?
Failure modes
Where teams lose control
A polished translation may be mistaken for an official text.
A dictionary equivalent may not be the phrase buyers publish.
A multilingual portal may search every stored language without translating the query.
A shared classification code may be too broad for the actual capability.
A local abbreviation or compound noun may be lost in a literal translation.
A false friend may retrieve a different service with convincing vocabulary.
An attachment may contain the controlling condition in a language absent from the notice summary.
An official notice may include a partial non-official language rendering that is not authentic.
A native speaker without procurement context may miss the procedural effect of a phrase.
An agent may convert discovery confidence into an unsupported eligibility conclusion.
OCR or character normalization may alter names, numbers or negation.
An approved term set may become stale as buyers and portals change usage.
Measurement
Measure the finished job
Measure the completed workflow, including review effort and exceptions. Output volume on its own is not evidence of a better process.
- target-language terms with official passage provenance
- rows separated by observed, terminology-derived, machine-suggested and reviewer-verified state
- query arms executed with reproducible syntax and dated filters
- unique relevant notices added by each language lane
- false positives and unjudged results per query arm
- candidate notices opened at the authoritative source
- high-consequence passages with completed language and subject review
- notices held because the official text or review was unavailable
- known relevant notices recovered after multilingual expansion
Questions
Common questions
Can I search TED in English and assume it translates my query?
No. TED documents that full-text search covers all languages, but that is not a promise of semantic translation between languages. Test known target-language notices and run explicit local-language arms.
Is a CPV code enough for multilingual discovery?
It is a strong language-independent bridge, not a complete search. Codes can be broad or imperfectly assigned, so combine them with target-language buyer wording and inspect each notice.
When is machine translation acceptable?
Use it to propose search terms, understand the rough subject and choose passages for review. Do not use it alone for eligibility, mandatory requirements, deadlines, submission instructions or contractual obligations.
Does every passage require a lawyer?
No. Match review to consequence. Ordinary scope may need a fluent language reviewer and subject expert; legal effect or contractual risk may require qualified local advice.
What if the notice offers an English summary?
Record whether English is an official notice language or a partial convenience version. Follow controlling requirements into the procurement documents and keep unresolved passages blocked.
What should an agent return when no results appear?
Return the languages, portals, terms, codes, filters and dates actually searched, plus blocked and unsearched lanes. A bounded negative result is useful; a universal absence claim is not.
Sources
Primary references
- TED help: search and browse Publications Office of the European Union
- eForms schema usage: notice official language Publications Office of the European Union
- eForms FAQ: multilingual text and official languages Publications Office of the European Union
- Common Procurement Vocabulary European Commission
- Use of machine translation on Europa European Commission
- IATE multilingual terminology database brochure Translation Centre for the Bodies of the European Union
- eForms procurement labels and translations Publications Office of the European Union
About the author
Tony Kim
Tony writes about applied AI, dependable product engineering and the systems that turn complex response work into controlled delivery.
Zelius
Managed tender intelligence and bid execution for teams that want the commercial outcome.
Suppliers, founders and commercial teams pursuing public or private opportunities. Start with the workflow, constraints and evidence you already have.