A research procurement can require a report, data and presentation materials as distinct outputs. Marking one report delivered should not silently mark the entire package complete. A historical UNICEF Thailand assessment notice offers a concrete example. This article explains delivery-record design only. It reports no study findings, evaluates no health intervention and does not authorize collection or sharing of personal research data.

Read the artifacts individually

The UNICEF Thailand LRPS-2025-9198131 description, checked on 3 October 2026, separates a qualitative draft report in English and Thai from quantitative raw-data submission. Its final-stage description lists several bilingual outputs, including report and presentation materials. The 2025 submission period is past. We did not inspect an actual dataset, final report, approval or full attached terms of reference.

Build an artifact-level delivery register

An illustrative register could give each actual requested artifact its own row, with the required language, format, responsible provider and source reference. Keep proposal, draft, submitted and accepted states distinct when the real process provides them. These are working record labels, not official status codes imposed on the UNICEF procurement.

For a hypothetical assessment, a report in one language may be ready while a second-language version is unfinished. A single completed checkbox would hide that difference. Separate artifact rows show the gap without inventing a translation team, an acceptance date or a research result.

Do not treat a data file as a quality finding

The presence of a file called raw data does not establish that its collection, contents or analysis meet the buyer’s requirements. Its delivery status and its quality review are different facts. Keep the actual evidence needed for each review attached to the appropriate record, with access controlled by the responsible organization.

This article gives no instructions for publishing respondent-level data. Consent, privacy, research ethics and applicable rights need qualified review under the actual assignment. A researcher preparing a procurement article should not expose personal records to demonstrate that a deliverable exists.

Link outputs without merging their purpose

A presentation can summarize findings while the report provides the supporting account. An annex can carry additional material without substituting for the requested report. Record which file supports which requirement. If the connection cannot be established from the source, label it unresolved rather than rewriting the requirement to match the material at hand.

Actual review and acceptance require the current documents and authorized buyer process. A public notice’s planned outputs are not proof that the supplier delivered them. No completed project, payment or provider performance is inferred in this article.

A controlled handover result

Our editorial judgement is to track research outputs at the artifact and language level, while keeping substantive review separate. The useful record shows which files exist, which were submitted and what remains unverified. Ethics, data, statistical and health matters require qualified human review. It does not resolve inconsistent deadline-timezone wording in the source or use it for an active bid.