Summary

  • APT PP26-5 ended in Brisbane on 28 August 2026. Its public page lists the work undertaken but does not publish a final proposal inventory; the meeting documents require login.
  • A proposal becomes a PACP when the APT-PP Plenary adopts it. Consensus is preferred, but a last-resort rule allows adoption with support from at least 25% of APT Members present and no more opponents than supporters.
  • A PACP becomes an APT Common Proposal only after all-Member consultation. It needs support from at least 25% of all APT Members, while opposition may not exceed half the supporter count. Members are asked to add their country names as signatories.
  • Attendance, input eligibility, Plenary adoption, all-Member endorsement, ITU submission and conference adoption are different authority states. None should be reported as another.
  • A public signatory-and-lineage ledger should connect the originating input, proposal versions, denominators, support, opposition, country signatories, administration submission, ITU document number and PP-26 disposition.

Brisbane closed the meeting, not the record

APT PP26-5 met from 24 to 28 August in Brisbane, with physical and remote participation. The official event page says the meeting considered APT Member inputs, reviewed ITU and regional preparations, developed Preliminary APT Common Proposals and APT views if any, considered nominations for PP-26 office bearers, prepared coordination arrangements and hosted sessions for election candidates.

That is a public activity list, not a public outcome register. The same page places the meeting documents behind a login. It does not state how many Candidate Draft PACPs survived, how many PACPs were adopted, whether any fallback threshold was used, which Members supported or opposed a text, or which country names will appear as signatories. The correct conclusion is not that nothing happened. It is that the public record does not yet prove the final inventory.

The distinction matters because APT published a much fuller account after its fourth meeting in Kuala Lumpur. PP26-4 had 230 participants from 24 APT Members, 20 Affiliate Members and four international or regional organizations. It considered 53 input documents, developed 13 PACPs and left seven Candidate Draft PACPs for further work.

Those numbers should not be collapsed. Two hundred and thirty people were not 230 Members. Twenty Affiliate Members were not twenty administrations empowered to sign an ITU proposal. Fifty-three inputs were not 53 PACPs. Thirteen PACPs were not yet 13 ACPs. Nor can the PP26-4 counts simply be carried into Brisbane as if the final meeting confirmed them unchanged.

APT’s work plan now supplies the next public clock. September and October are for circulating PACPs, finalizing APT Common Proposals and submitting them to ITU. The firm PP-26 deadline for all contributions is 19 October. The coming weeks are therefore not administrative cleanup. They are the period in which a meeting-stage preliminary text either acquires a qualifying set of Member supporters and country signatories or fails to become an ACP.

The input class comes before the vote

The first authority boundary appears before a proposal is debated. APT’s Working Methods allow every APT Member to submit an input contribution related to the agenda. Associate and Affiliate Members may also supply an input, but only with agreement from the corresponding APT Member. Without that agreement, the document is treated as information.

ITU and recognized international or regional organizations also submit information documents. Other observers cannot submit contributions. A late input ordinarily becomes information for the current meeting and an input for the next one, although the Plenary may decide to accept it immediately. A document outside the group’s terms, agenda or work is likewise classified as information.

These are not clerical labels. They answer who has placed text into the Member-input channel and under whose authority. An Affiliate Member may bring expertise, drafting capacity or operational evidence. The corresponding Member agreement is what admits that document as an input. That admission does not make the corresponding Member a supporter of every later version. It certainly does not authorize a whole region.

The same discipline applies to attendance. A participant can question text, supply evidence, negotiate wording or observe proceedings. Participation is valuable because it changes the evidence available to the competent body. It is not a proxy signature for an APT Member, and it cannot turn an information document into a Member proposal by repetition.

A defensible lineage therefore starts before the PACP. It records the input number, source, date, eligibility class and, where required, the corresponding Member agreement. If a drafting group combines five inputs, the record should preserve all five ancestors rather than allowing the eventual regional label to erase them.

A PACP has a meeting denominator

APT-PP’s Plenary is the body that makes final decisions and approvals within the preparatory group. Working Groups and drafting groups develop texts; the Plenary converts a proposal into a PACP.

The default ambition is consensus. But the Working Methods also describe the case in which further discussion cannot resolve a difference. As a last resort, the document may be adopted if two conditions hold: at least one quarter of APT Members present at the Plenary support it, and the number of Members opposing it is no greater than the number supporting it.

That formula needs four facts to be reproducible: the number of APT Members present, the number supporting, the number opposing and whether the fallback was invoked. A statement that a proposal “was adopted” gives the legal state but not the representational shape of the act. If consensus was reached, that should be recorded. If the fallback was used, its denominator and both counts should be recorded.

The fallback does not make the PACP defective. Institutions need procedures for moving past disagreement. Nor does it make the PACP a regional mandate. It is a preliminary proposal adopted by the competent APT-PP Plenary under a defined internal threshold. Its authority is real and bounded.

This is where the word preliminary does useful work. The Plenary act closes one stage, but all APT Members have not yet been asked to attach their country names. A PACP can therefore be influential at the meeting and still fail the next test.

An ACP has an all-Member denominator and signatories

The APT Documents Framework establishes the second threshold. After a proposal becomes a PACP, the Secretariat circulates it to all APT Members for endorsement. Each Member is asked to consider including its country name as a signatory.

The proposal becomes an ACP when at least 25% of all APT Members support it and the number opposing it is no more than 50% of the number supporting it. The denominator has changed from Members present at one Plenary to all APT Members. The opposition rule has also tightened: at the PACP fallback stage, opponents cannot outnumber supporters; at the ACP stage, opponents cannot exceed half the supporter count.

The label APT Common Proposal therefore has a precise meaning. It is a proposal developed through the APT process and endorsed by enough APT Members to satisfy the common-proposal criteria. It is designed for submission as a multi-country proposal. Its signatories are not decorative. They identify the countries willing to place their names behind that text.

Nothing in that definition requires unanimity. A Member that does not respond has not thereby supported the proposal. A Member that opposes it is not transformed into a co-author because both states sit inside the same geographic label. A state, operator or user that is not an APT Member is not represented through arithmetic it never entered.

This is not an argument for replacing the threshold with unanimity. A unanimity rule can give every participant a veto, reward obstruction and make regional coordination impossible. The better answer is to report the coalition honestly. A proposal supported by a quarter, half or every Member can carry different political weight while remaining the same formal document class. Named signatories allow other delegates to see that distinction.

Submission is another gate, not the destination

ITU’s PP-26 guidance creates the next authority boundary. Member States may submit conference proposals, as may the State of Palestine under the published limitation concerning amendments to the Constitution and Convention. Observers participating in an advisory capacity may submit information documents through the Secretary-General. Proposals are prepared through the Conference Proposals Interface and submitted by focal points of Member State administrations.

APT has a parallel coordination role. Its June circular said PP26-5 needed to finalize APT focal points for ACPs, and it encouraged the administrations responsible for identified PACPs and Candidate Draft PACPs to coordinate between meetings. An APT focal point helps present and negotiate a proposal. The competent administration focal point places it into the ITU channel. Neither role manufactures signatories after the fact.

Once submitted, the ACP should acquire an ITU document number and later a searchable inheritance trail in the Proposal Management Web. That lineage matters because conference negotiations rarely leave text untouched. A clause may be merged with another region’s proposal, amended in committee, divided, withdrawn or replaced. The final wording may have several ancestors.

Receipt does not equal acceptance. ITU’s own document page separates contributions and reports from information documents and temporary working texts. A Member State proposal is a proposal before the conference. Only the competent PP-26 bodies can decide whether its language is adopted, modified, rejected, merged or omitted from the Final Acts.

Publish the coalition as a coalition

The smallest adequate public record is a signatory-and-lineage ledger. It should begin with a stable proposal identifier and the exact input ancestors. It should preserve whether each ancestor was an input or information document and which corresponding Member agreement admitted an Associate or Affiliate contribution.

For the PACP stage, the ledger should attach the exact text, Plenary date, adoption basis and version diff. If the fallback was used, it should record Members present, supporters and opponents. For the ACP stage, it should state the number of all APT Members used as the denominator, consultation dates, named supporting Members, country signatories, named opponents where publishable, and separate abstention from non-response. A numerical certification without the denominator is not enough.

The submission entry should identify the APT focal point, competent administration, time of submission, ITU document number and exact proposal version. Later entries should follow PMW inheritance, mergers, clause-level changes, withdrawal and conference disposition through to the Final Acts.

This record need not expose confidential diplomacy. It need not publish private comments, negotiation instructions or unpublished national positions. It needs the minimum facts required to prevent one state from being silently absorbed into another state’s signature and one procedural stage from borrowing authority from the next.

Heng Lu’s distinction between stakeholder and principal is useful here if kept within scope. Participants provide evidence, expertise, warning and objection. APT Members authorize their own inputs and endorsement. Member State administrations submit. PP-26 decides. The stakeholder room is real; the mandate comes from the specific competent acts, not from the existence of a room or the size of a map.

APT’s common-proposal system can be strongest when described modestly. A named coalition with a visible threshold is more credible than an anonymous regional voice. It lets supporters claim their work, opponents retain their position and other delegates judge the proposal’s actual base without denying its institutional status.

Sources

  1. APT PP26-5 meeting page
  2. APT PP26-4 meeting page
  3. APT Preparatory Group for PP-26
  4. Working Methods of APT-PP
  5. APT Documents Framework
  6. APT PP-26 work plan
  7. Preparatory arrangements for APT PP26-5
  8. ITU PP-26 submission of proposals
  9. ITU PP-26 official documents
  10. ITU PP-26 key dates and deadlines
  11. Heng Lu, The Multi-Stakeholder Mirage