An interpretation assignment with online and physical events should preserve both formats in its scope record. A combined event count hides different unanswered delivery questions. A historical UNDP secondary bid illustrates the distinction. This article helps procurement researchers organize the available evidence; it does not supply interpreters, calculate a staffing plan or certify that an online platform will support the required service.

The amendment preserves two formats

The UNDP-HQ-01526,1 notice, checked on 3 October 2026, describes fifteen webinars and one in-person event in New York. Its February 2025 amendment points to a revised terms-of-reference document and clarification annex. Those attachments were not read here. The historical count is not evidence of events currently being procured or services actually delivered.

Create separate scope entries

A preparation record can have one entry for the webinar component and another for the physical event. Attach the buyer’s available wording to each entry. Do not merge them into sixteen identical sessions, because that removes the delivery distinction expressly retained in the notice. Also avoid converting an event count into hours without a verified duration.

For a hypothetical assignment, the online entry would identify confirmed requirements relevant to the online service; the physical entry would identify confirmed requirements relevant to the venue-based service. The point is to expose evidence gaps, not to manufacture two complete technical specifications from a short public description.

Do not derive staffing from the title

The language combinations, session arrangements and other actual requirements must come from the authoritative assignment documents. A title mentioning simultaneous interpretation does not establish the number of interpreters, their credentials or their availability. Nor does a vendor’s general capability statement prove that the proposed personnel can deliver the particular assignment.

Keep proposed service arrangements separate from verified requirements. If a response supplies a staffing assumption before the relevant input has been confirmed, label that assumption for review. Do not convert it into a buyer instruction or publish a team list as though the people had accepted the work.

Track revisions by component

A revised scope may affect one format without changing every part of the assignment. Record which component a clarification addresses and which version supports the response. A reviewer can then find the precise basis for an online or physical service statement rather than searching a consolidated narrative for an unexplained number.

This is not a rule about priority between documents. Actual conflicts and submission conditions require the current buyer instructions and responsible human review. This article has not tested the platform, inspected a venue or reviewed audio quality. It makes no assurance about confidentiality or technical performance.

A bounded comparison result

Our editorial judgement is to retain event format as a first-class scope field. The preparation result distinguishes the known webinar and in-person components, the supporting amendment and the missing requirements. Actual languages, staffing and service offers remain on hold for verification. A clean inventory improves the procurement question; it does not demonstrate that a particular provider can answer it successfully.