Before sending tender documents for translation, create a dated inventory of the files you actually have, match their annexes and cross-references, identify amendments and confirm the translation scope. Preserve the original filenames and versions. Give the language team the current instructions and a named contact for missing or conflicting material. A readable main document is not a complete source package when a referenced schedule is absent.
The practical goal is traceability: everyone should know which tender documents are being translated, which version applies and which questions remain open. This guide helps procurement teams, suppliers and project coordinators prepare that handover. It concerns the source package and translation workflow; the issuing organisation's actual instructions govern the procurement process and any submission requirements.
Establish what the tender documents are for
Explain whether you are translating an issued tender for internal assessment, preparing a response in another language or producing a reference copy for colleagues. These are different assignments. Tender documents supplied by the buyer and documents created by a bidder should remain identifiable as such. A translator should not have to infer who issued a statement or whether it is part of a proposed response.
Identify the relevant opportunity, issuing organisation, project or lot and the languages involved. Add the intended readers and use of the translation. If only one part of a larger procurement is relevant, describe that boundary. Tender documents can share similar headings across different opportunities, so a title such as “technical requirements” is not enough to identify the project on its own.
Agree who owns the source package. That person should be able to confirm whether the team has obtained all available material and who can resolve procurement questions. Tender documents often pass through several hands before reaching a translator. A clear owner helps prevent a partial folder from being treated as complete simply because the last person forwarding it assumed someone else had checked.
Identify the source of your tender documents
Record where the tender documents came from: the issuing portal, an authorised message or another identified source. Keep the opportunity reference and the date you retrieved the package. This does not establish that a later change cannot occur. It gives the team a known starting point and someone a clear responsibility for checking whether new material has appeared.
Use the actual procedure's documentation rather than a generic internet checklist. For example, UNGM's participation guidance for hard-copy or email opportunities explains accessing documents and reading the opportunity's participation instructions. That is a specific portal example. Your tender documents may come through a different system with different arrangements, which the project owner needs to identify.
Even a recognised template needs precise identification. The World Bank publishes a standard template for an off-the-shelf goods, two-envelope process. Its named purpose illustrates why tender documents should not be described merely as “the standard form”. Confirm the actual issued package and its applicable version, rather than substitute an unrelated template during translation preparation.
Inventory tender documents before estimating the work
List every supplied file with its exact filename, format, apparent title, version or date and role in the package. Include folders or separate downloads where their structure explains relationships. The inventory should describe the tender documents present, not a remembered list of what the email was supposed to contain. Open files sufficiently to check that their content matches the description.
Count the pages or worksheets where that helps establish coverage, while remembering that counts alone do not prove completeness. Two files may duplicate the same pages, or an attachment may contain a separate annex after an unnumbered divider. Tender documents need identification by content and relationship as well as by the total number of items in a folder.
Mark the status of each item: received, missing, unreadable, replaced or awaiting clarification. Keep that status separate from the translation decision. A file can be present but excluded from the agreed language scope, or required for translation but not yet available. Tender documents should not disappear from the inventory simply because their status makes the project less convenient to quote.
Map annexes referenced in the tender documents
Inspect the contents list and references such as annex, appendix, schedule, form, drawing and attachment. Look for an identifier and title, not just a generic mention of “the attached document”. Match each reference with the file or section it points to. Tender documents may place several annexes inside a larger PDF, so a missing standalone filename does not automatically mean the annex is absent.
Then check the reverse direction: does each file you received belong to the opportunity, lot or version being translated? A stray schedule from an earlier project can look convincing because its table structure is familiar. Tender documents should be linked to their actual source reference before the translator treats them as part of the assignment. Flag uncertainty instead of relying on a similar heading.
Create a short list of unresolved references. For example, a hypothetical technical specification might refer to “Schedule C”, while the supplied set contains only Schedules A and B. Ask the owner whether C is embedded, omitted or no longer applicable. Do not ask the translator to reconstruct missing tender documents from the surrounding paragraphs or silently remove the reference to make the text read smoothly.

Connect amendments to the tender documents
List addenda, amendment notices, clarification replies and other issued updates separately from the base package. Identify what each one appears to affect and ask the owner to confirm its status. Tender documents can remain understandable only when the team can see the relationship between the original requirement and a later instruction, rather than find a modified paragraph with no explanation of its origin.
UNGM's clarification guidance says that clarifications disseminated on that portal appear as documents and are referenced in its Revisions tab. This is a useful example of looking beyond the main download list. It does not mean every portal uses the same tabs or that every update to your tender documents takes the same form.
Do not infer the effect of a clarification beyond what it states. A reply may explain a term, change a requirement or point to another document; the authorised owner needs to establish the applicable interpretation. The translation should preserve the instruction accurately. Tender documents with conflicting wording require a visible question, rather than an undocumented editorial choice about which requirement seems more reasonable.
Identify which tender documents a new file replaces
Ask whether a new file replaces an entire earlier document, substitutes particular pages or adds information alongside it. Record that relationship explicitly. A file labelled “revised” may not explain its full effect. Tender documents need a source decision from the responsible owner before the language team can know whether to translate both texts, update an earlier translation or retain one only as history.
Keep superseded material identifiable and separate from the active translation set. Preserve it where needed to understand a change, but prevent accidental use as current source. Tender documents should not be overwritten in a way that destroys the record of what the team initially received or what was already translated. A separate working folder can make the distinction clear without renaming the original files.
If the replacement changes tables or references elsewhere, identify those possible connections for review. A new schedule may alter the terms used in a response form or a technical table. Tender documents are a connected set, so updating the obvious file alone may leave related translated passages inconsistent. Ask the project owner which associated materials need to be rechecked.
Preserve the identity of your tender documents
Preserve original filename stems, identifiers and dates. Explain a file's role in the inventory rather than translating its name or adding informal labels that other team members may not recognise. Tender documents often need to be matched across a portal, an email and a working folder. Consistent source identity makes that comparison easier for people who did not prepare the package.
Store revised translations separately from the source files. If a translation requires another format, keep the source identifiable and agree how the output maps to it. Tender documents should not become ambiguous because an edited copy has replaced the only available original. Keep a source-to-output list that someone can use without guessing which of several similarly named documents they are opening.
Avoid deleting apparent duplicates before checking their contents and history. One may contain a different endorsement, page or worksheet despite having a familiar title. If identical material should be translated only once, agree that scope and record the relationship. Tender documents can be organised efficiently while still preserving the evidence needed to explain why one file produced no separate translation.
Agree the scope for translating tender documents
Decide whether the commission covers the whole package, selected sections, particular lots or an internal summary. Identify exclusions by file and section where possible. Tender documents supplied for context are not automatically included in the translation volume, while a quotation for the main specification does not automatically include every attachment later found in the folder. Make those boundaries explicit.
A summary can help colleagues decide whether to investigate an opportunity, but it should be labelled as a summary. It should not be presented as a complete translation of tender documents when forms, conditions or technical details have been omitted. Agree who selects the scope and what the readers must understand about the limits of that output.
Include repeated material, cover pages, tables, footnotes and image text in the scope discussion where relevant. If the same clause appears in several places, the team needs a consistent treatment, not an assumption that a repeated page can be ignored. Tender documents should be assessed as the actual supplied set, with any exclusions deliberately agreed rather than discovered at delivery.

Check readability across the tender documents
Supply editable originals when they are legitimately available, alongside the issued reference where needed. Identify scans, photographed pages, protected files and drawings with embedded text. Tender documents that look readable in a preview may contain small figures or annotations that cannot be checked at working size. Point out known issues instead of letting the team discover them after translation has started.
Where OCR text is supplied, keep the page image as the reference and state whether the extraction has been checked. Pay attention to columns, mathematical signs, model codes and row relationships. Tender documents can be damaged by a plausible transcription that moves a value into the wrong place. Extraction is a working aid, not evidence that the source has been faithfully reproduced.
Do not silently replace an unreadable section with text from another edition. Ask for a clearer source or record the limitation and its location. If a missing image, attachment or password prevents inspection, name that obstacle precisely. Tender documents should enter the project with visible source questions rather than a hidden assumption that the translator can repair every defect.
Protect forms within the tender documents
Explain whether a form is supplied for translation, for completion by the bidder or as an example of the required response. Keep instructions distinguishable from entries. Tender documents may contain blank boxes, signature areas and prompts that a language team should translate or preserve according to scope. A blank field is not an invitation to invent information so the page looks finished.
Protect stable identifiers, reference codes and placeholders. If a field label changes in the translated version, it should still point to the same required information. Check tables with merged cells, repeated headers and continuation pages. Tender documents need the relationships between labels and values to survive; correct sentences are insufficient if the completed layout assigns a response to the wrong heading.
State who will enter and verify any bidder-supplied information. Translation does not establish an organisation's experience, eligibility, qualification or ability to meet a requirement. Tender documents should preserve those claims as supplied and route factual questions to their owner. Do not ask an editor to strengthen a statement by adding a credential or commitment that the organisation has not confirmed.
Capture instructions accompanying the tender documents
Keep the relevant instructions with the source package. Identify what language is requested for the particular material, whether reference translations have a separate status and which output formats the receiving workflow uses. Tender documents may distinguish between information for internal understanding and material submitted in a formal process. Ask the responsible owner to confirm that distinction before commissioning the output.
If a certification, declaration, signature or other formality is specified, share the actual wording and identify who will confirm the service required. Do not assume that an ordinary translation automatically meets it. Tender documents should be translated within an agreed production scope, with the procurement team retaining responsibility for interpreting and following the issuer's current participation instructions.
Record any dates, time zones or separate clarification windows exactly as supplied, and ask about ambiguity. Do not manufacture a working deadline by assuming that a date on a cover page is the final submission date. Tender documents can contain several different milestones. The translation schedule should leave time for the agreed review and handover, based on confirmed project requirements rather than an invented universal turnaround.

Check numerical detail across the tender documents
Give quantities, units, currencies, tolerances and reference numbers a dedicated comparison with the source. Keep the heading and surrounding qualification attached to each value. Tender documents can change meaning when a minus sign, decimal separator or unit is lost, even while the rest of a paragraph reads naturally. A fluent text should not distract from checking these details.
Do not convert units, currencies or calendars unless that work is expressly agreed and can be checked. If an explanation is needed, distinguish it from the source value. Tender documents should not acquire a different numerical requirement simply because another unit is more familiar to the target reader. The source's actual quantity and qualification remain the reference for the translation.
Keep product models and technical standards identifiable. An unfamiliar abbreviation may need research or a query, but it should not be expanded into a different specification by guesswork. Tender documents with recurring technical terms benefit from an approved reference list, particularly when a main specification, a pricing schedule and a response form use related language for the same item.
Give tender documents a reliable terminology reference
Share an approved glossary, earlier relevant translations and product references where they can help. Identify what each reference is and whether it governs the current assignment. The translation glossary guide discusses that distinction. Tender documents should not be forced to match an old translation when the current source uses a different concept or a later approved term.
Ask subject specialists to resolve genuinely technical questions. A language reviewer can identify ambiguity and propose a reading, but should not secretly become the designer, engineer or procurement decision-maker. Tender documents need a record of the question and the answer, with its source. That is particularly useful when the same decision affects several tables or annexes.
Keep explanations separate from changes to the source requirement. If the client supplies background, label it as context unless it is an authorised amendment. Tender documents should remain traceable to the issued material. A useful briefing note can help the translator understand an unfamiliar process without being inserted into the translation as though the issuer had written it.
Assign tender documents queries to the right owner
Use a short issue list identifying the file, section, source wording and the decision needed. Distinguish a request for a better scan from a terminology question or an apparent conflict between documents. Tender documents should not accumulate a single vague comment such as “please confirm the technical parts”. A specific question gives its owner a practical way to answer.
The translation coordinator can collect queries, but procurement clarifications belong through the authorised process. UNGM's guidance, for example, directs clarification requests to the issuing organisation rather than the UNGM Secretariat. Follow the route applicable to your opportunity. Tender documents should not be interpreted by whichever unrelated contact happens to reply first to an informal message.
Keep answers with the affected material and update the current decision record. An answer in a message thread may be missed by another translator working on an annex. Tender documents translated by several people need a shared understanding of confirmed terms and resolved conflicts, while access to sensitive files remains limited to the people authorised for the project.
Control updates to the tender documents
Agree who monitors for new documents and who tells the language team when they arrive. A translator working from a supplied folder cannot know that an issuer has released another notice unless that monitoring responsibility is included and the access exists. Tender documents need a clear route from newly received source to an acknowledged production change.
Identify the affected file or section and ask the provider to assess the consequences before assuming a small update has no effect on the schedule or review. Tender documents can contain dependencies: a short revised definition may affect several annexes. The useful question is what must be updated and checked, not simply how many new words appear in the notice.
Confirm the source version used for each delivery. If material arrives after an agreed review has finished, record whether it is included in that version or requires another update. Tender documents should not be described as fully current without a defined reference point. Make the status understandable to the recipient who will decide whether the package can move to its next stage.

Keep cross-references usable in translated tender documents
Preserve clause, annex, schedule and form identifiers so readers can connect the translated material with the source. If translated pagination differs, agree a suitable way to explain the relationship rather than casually renumbering source references. Tender documents often need to be read side by side with originals, so traceability matters more than making every reference fit an attractive new layout.
Check references after the translated files are assembled. A paragraph may cite the correct annex name while the delivered folder omits that annex or contains its superseded version. Tender documents require both text-level and package-level checks. A technically correct reference becomes unhelpful when the person opening the delivery cannot find the material it points to.
For editable outputs, inspect tables, links and any fields that depend on document structure. Ask who is responsible for updating generated contents pages or other automatic elements. Tender documents should be reviewed in the actual agreed format, including any PDF export, rather than assumed correct because the text was checked before it was placed into the final file.
Match translated tender documents to the inventory
Compare the agreed source list with the delivered outputs. Mark what was translated, excluded by agreement, replaced or still unresolved. Open every required output and confirm that it corresponds to the intended source. Tender documents should not be considered delivered solely because the number of attachments matches the number written in a quote.
Review important recurring details across files: opportunity reference, organisation names, defined terms, lot identifiers, units and amended instructions. Check that a superseded term has not survived in a less visible annex. Tender documents can be correct individually yet inconsistent as a set, which is why a final connected review has a different purpose from proofreading one file.
Keep production approval distinct from procurement submission or acceptance. Confirm the translation version and review coverage, then let the responsible team use the authorised submission workflow. The content release manifest guide explains the related idea of identifying final files and their status. A complete translation package does not itself determine whether tender documents meet every external requirement.
A fictional package check before handover
Imagine a supplier has a main instruction PDF, a technical annex, a pricing workbook, a response form and a clarification notice. The notice refers to an updated technical table, but no replacement table appears in the folder. These are hypothetical tender documents used to illustrate the preparation task, not a description of an actual opportunity.
The coordinator records all five files, identifies the missing table reference and asks the authorised owner to locate it. They also confirm whether the workbook contains hidden or additional relevant sheets, and whether the response form needs translation or completion. The tender documents can then be scoped from the actual package rather than a request to “translate the tender” with no file-level explanation.
Suppose the owner supplies a replacement annex and confirms that it supersedes the earlier annex in full. The old copy remains in the history folder; the active inventory identifies the replacement. Tender documents already translated from the earlier source are assessed for revision, and related references are checked. No one silently pastes the new table into an old source and calls the whole package unchanged.
At delivery, the coordinator can explain which source version each output represents and how the clarification was handled. That record is more useful than a folder containing several files with “latest” added to their names. Tender documents remain identifiable through exact filenames, their confirmed relationships and a separate account of current status.
A practical brief to send with the files
Give the provider the source inventory and explain what you need to receive. Include these items where relevant to your tender documents:
- Opportunity, issuer, project and lot identifiers.
- Source and target languages, intended readers and purpose.
- Exact filenames, formats, versions and retrieval date.
- Annex and schedule map, including missing or unreadable material.
- Amendments, replacements and clarification notices with their confirmed effect.
- Translation scope and exclusions, distinguished from context-only references.
- Required output formats and actual instructions about any formalities.
- Approved terminology, technical references and protected identifiers.
- Named owners for source questions, updates and final review.
- Confirmed milestones and the route for notifying the team of new material.
You can share that brief when requesting document translation. If the set includes company records, the business-document preparation guide addresses related consistency checks. Keep your tender documents project tied to the current source inventory, so the quotation, working files and delivered package concern the same material.
Frequently asked questions
Is the main PDF enough to translate tender documents?
Only if it contains the complete material included in the agreed scope. Check its annexes, embedded attachments, external references and issued updates. A contents list does not establish that all referenced files are present. Identify missing material before work starts and ask the responsible owner to confirm the actual source package.
Can selected tender documents or sections be translated?
Yes, if the provider can assess the selected material and the scope is clearly agreed. Identify the files and sections, provide needed context and label any summary or partial translation appropriately. Tender documents supplied only as reference should remain distinguishable from material commissioned for translation, so readers understand what the output does and does not cover.
What if tender documents refer to a missing annex?
Record the reference and ask the source owner whether it is embedded, missing, replaced or no longer applicable. Do not invent the annex or remove the citation. Tender documents with unresolved references need a visible decision before the package is treated as complete. The appropriate next step is a specific source query, not an unsupported reconstruction.
Should amendments be merged into the original before sending?
Keep their issued identities and explain their confirmed relationship to the base material. If a consolidated working copy is useful, label it and preserve the original files. Tender documents should remain traceable so the translator can distinguish a formal replacement, an addition and a client-prepared compilation, rather than infer the effect of an undocumented edit.
Who should resolve conflicting tender instructions?
The authorised procurement owner should use the clarification process applicable to the opportunity. A translator can locate the conflict and explain the language question, but should not silently choose the requirement. Keep the answer with the affected tender documents and share it with anyone working on related files, while preserving its source and status.
What if new tender documents arrive during translation?
Notify the provider through the agreed route, identify what changed and ask for its effect on work and review. Confirm whether the new source is included in the current delivery version. Tender documents need an acknowledged change decision; simply adding a file to a shared folder does not establish that everyone has seen or incorporated it.
Does a translated package guarantee a valid submission?
No. The translation should represent the agreed source accurately and meet its confirmed production requirements. The responsible procurement team must still follow the issuer's actual participation and submission instructions. Keep translation approval, source completeness and external acceptance distinct, without claiming that a clear set of translated tender documents establishes eligibility or replaces the required checks.
Sources & further reading
Put it into practice
Ready for your next project?
Explore our Document Translation service or tell us what you need.
Explore the service ↗


