A translation assignment that preserves layout needs more than a translated reading copy. The buyer may need editable production files as well as a final PDF. A historical UNFPA training-module RFQ makes that distinction concrete. This article addresses handover scope and evidence. It does not assess the translated material, provide medical terminology guidance or claim that a provider has the rights and resources needed to reproduce an actual document.

The answer identifies a production-file route

The UNFPA ESARO RFQ/25/060 log, checked on 3 October 2026, identifies European Portuguese and describes InDesign source files and an InDesign output that becomes a PDF. The answer is from November 2025. We did not read the actual module files or verify software versions, fonts, word counts or translation quality.

Make input and output inventories separate

An illustrative scope record can list the source files actually received and the deliverable formats actually requested. Do not infer that every PDF has an editable counterpart or that all source assets are available. Keep missing input evidence visible so that the responsible buyer and provider can resolve it.

For a hypothetical layout assignment, an editable production file and its exported reading copy would answer different handover needs. Returning only the reading copy might leave the buyer unable to make a later authorized revision. That example explains the scope question; it does not establish the contents or obligations of the historical UNFPA contract.

Identify layout work without inventing effort

A real offer should describe how the provider will address the requested production format and relevant layout work. The researcher should not manufacture a word count, page count or effort estimate from the public title. Nor should it assume a text extraction captures all material that must be handled. Actual files and authoritative requirements are needed.

Record any proposed exclusions or unavailable assets in the scope note. Fonts, linked material and other production inputs need the business’s appropriate permissions and verification. This article offers no software-license interpretation and no promise that a particular file will open or export correctly.

Keep language review distinct from file handover

An editable file can exist while its translation still needs review. A correct-looking PDF can likewise conceal a language problem. Maintain separate evidence for the requested language variant, the review process and the production-format handover. Do not report an assignment as fully accepted solely because a file was delivered.

Specialist or high-stakes content needs qualified human review under the actual assignment conditions. A procurement article should not invent a linguist’s credentials, endorsement or involvement to satisfy that requirement. Where evidence is missing, mark it for verification.

A bounded preparation result

Our editorial judgement is to define the production-file chain before comparing translation offers. The useful record distinguishes received inputs, proposed layout work, language review and requested outputs. No files were translated or provider evaluated here. Actual specialist quality and file rights require appropriate verification. The historical clarification supports scope reading, not certification of a translation or a guarantee that the production handover will meet a real buyer’s needs.