Summary

  • PP-26 does not apply one language rule to every document. Contributions and reports appear in six languages; ADM and INF documents are English only; DT and DL working texts normally appear only in their original language.
  • A DT document receives different treatment when it contains input to the Final Acts. That is a language-workflow transition, not evidence that the conference has adopted the text.
  • ITU should attach a language-state and lineage strip to every consequential document and clause, showing its class, original version, human-authorised editions, revision chain, Final-Acts status and later conference disposition.

The document code carries a governance decision

The letters beside a conference document can look like filing shorthand. At PP-26 they determine what a reader may reasonably expect to see, in which language and for what institutional purpose. The current official-documents page separates five states.

Series Stated function Stated language treatment
C Contributions and reports Six languages
ADM Calendars, programmes, agendas and other administration English only
INF Information only, not for discussion English only
DT Temporary working documents Original language only, unless the document contains input to the Final Acts
DL Limited-distribution draft working documents Original language only

This is not merely a communications menu. The class says whether an item can be discussed, whether its audience is limited and whether six official versions are expected. A person who sees a title without its class cannot tell whether the absence of five languages is a delay, the normal rule or an access restriction.

The table also prevents a false binary. PP-26 is neither “six-language throughout” nor “English only”. It is a classified multilingual system. Accountability begins by preserving the classification instead of showing every file as an undifferentiated download.

Equal footing does not erase the exceptions

Article 29 of the ITU Constitution names Arabic, Chinese, English, French, Russian and Spanish as the official languages. It requires equivalent form and content for Union documents according to the relevant decisions of the Plenipotentiary Conference. It also says the French text prevails if versions diverge or a dispute arises.

Resolution 154 supplies the operating qualification. It reaffirms equal treatment of the six languages, while acknowledging budget limits and that some work may not require all six. It instructs the Secretary-General to publish contributions in their original language as soon as possible and no later than three working days after receipt, even before translation. It separately calls for timely, high-quality language services and continued monitoring.

Those provisions describe staged equality, not automatic simultaneity for every file. An original contribution can appear before its other editions without losing the commitment to translate it. An ADM or INF document can remain English only under the published class rule. The governance question is whether the item is correctly classified and whether its visible status matches that class.

Proposals already have an inheritance mechanism

PP-26 has part of the needed architecture. Member States submit proposals through the authorised route, and the Conference Proposals Interface is designed to facilitate publication in the Union's six languages. The Proposal Management Web is meant to retrieve proposals in any of those languages and show their “inheritance”.

Inheritance is the right concept. A clause may begin in a Member State proposal, be combined with another proposal, appear in a temporary working document, be revised, corrected or dropped, and later receive a conference disposition. Each stage has its own institutional meaning. A clean family tree would show which wording survived, which actor changed it and which language edition reflects the current state.

Without that link, a reader can compare two documents and still miss the decisive fact: one paragraph may descend from a proposal while another was introduced in committee. A six-language final product does not explain how the text acquired its form or whether all delegations inspected the same revision during deliberation.

Final-Acts input is a language trigger, not an adoption badge

The most consequential sentence on the PP-26 documents page is the exception for DT working documents. They are published in the original language only “unless” they contain input to the Final Acts. The page therefore makes Final-Acts input a boundary in language treatment.

That boundary must be read narrowly. A working document does not become binding because it is translated. Nor does the phrase “input to” prove that the Plenary has approved the clause. Adoption, signature and any later legal effect depend on separate conference acts and the controlling text.

The PP-22 record illustrates the later end of the chain. Its Provisional Final Acts were posted in all six languages on 14 October 2022, and ITU says 157 Member States signed the Final Acts on the final day. That historical record shows what a mature six-language conference output can look like. It does not predict what PP-26 will adopt.

The missing public fact is the transition itself. When a DT clause becomes input to the Final Acts, readers should see the decision, date, responsible conference body, exact source wording and resulting language editions. Otherwise the classification that changes the language obligation is real but hard to audit.

Machine assistance needs a separate label

ITU Translate can widen immediate comprehension. ITU describes it as a neural machine-translation service trained on institutional material, but its disclaimer is unambiguous: the process is automated, involves no human intervention, carries no accuracy guarantee and should give way to the original official version when doubt arises.

A gist version is therefore useful evidence of access, not evidence that an official equivalent version exists. The interface should never make a machine rendering visually indistinguishable from a human-authorised Arabic, Chinese, English, French, Russian or Spanish edition.

This distinction matters most during revision. A machine rendering of revision one may remain accessible after revision two becomes current. Unless both the revision and translation status travel together, apparent multilingual availability can point to superseded substance.

Access state belongs beside language state

The ITU information/document access policy adds another dimension. It treats public access as a support for transparency and accountability, but allows conference input documents to depend on the submitter's decision and protects material where disclosure could cause legitimate harm. Submitters must identify sensitive content and are encouraged to provide a redacted public version where possible.

That means “not visible” cannot safely be translated into “does not exist”. A DL document may have a limited audience. An input may be restricted by its submitter. A public record should say that access is restricted and identify the rule, without revealing the protected material.

Language, access and authority are separate fields. A document can be public but original-language only; six-language but not yet adopted; limited and still consequential; or machine-readable in several languages without having several official versions. One badge cannot carry all four meanings.

Put a language-state strip on every consequential clause

PP-26 can make the distinctions inspectable without publishing every negotiation note. Each consequential document should carry a compact strip naming its series, function, discussability, audience, submitter, original language and publication time. It should list each human-authorised edition and timestamp, and mark any machine version as gist only.

The strip should also identify the current revision, corrigendum or addendum; the parent proposal or working text; and every clause that has been combined, replaced or withdrawn. For DT material, it should state whether the text contains input to the Final Acts, who recorded that state and when.

Finally, it should link to the later Plenary or conference disposition and identify the text that controls discrepancies. A correction should preserve the earlier record while pointing to the superseding version. A restriction should name its basis and link to a redacted public copy when one exists.

This record would not demand six translations of every calendar or limited draft. It would make the existing rule legible. Delegates and public readers could see when an original-language working text remained a draft, when it entered a more consequential language track and which institutional act later accepted, changed or rejected it.

Sources