Summary

  • The January GNSO strategy report mixes agreements, action items, target windows and matters that still require formal adoption; those are not interchangeable states.
  • Later records show that the February Board dialogue and March SSAD non-adoption occurred, while the Supplemental Recommendations Team and a separate prioritization pilot remained active on 20 September.
  • A public plan-to-status receipt would let readers verify each transition without treating a planning agreement as a rule or a missing public receipt as proof that work was not done.

Imagine opening a governance report eight months after the meeting it describes. It says a dialogue will be planned for February, a check-in should happen around six months later, training should be reserved for the annual meeting, and a difficult policy task should take “months, not years.” By publication day, some of those moments are past and others are still ahead. The document is accurate as a meeting record, yet its future tense can mislead a reader about present status.

That is the problem with the GNSO Council Strategic Planning Session Report dated 16 September 2026 and released in public correspondence the next day. Its 26 pages capture January discussions about Council tools, SSAD recommendations, the policy-development continuum, prioritization and working practices. The useful question is not whether every sentence was a promise. It is what kind of sentence it was, who could change its state, and what later evidence shows.

Five verbs, five evidence tests

An observation describes the situation participants saw. An agreement records alignment in the room. A commitment gives an actor responsibility. An action item adds a defined next step. A target window adds time. A formal rule needs an adoption path and a controlling text.

These states can be related without collapsing into one another. Agreement may authorize drafting. Drafting may lead to a motion. A motion may amend procedure. Until the final step is recorded, “the Council agreed” does not mean “Councilors are now bound by a rule.” Conversely, lack of a public update in the meeting report does not prove that the action stopped. The report was never designed as a live dashboard.

The proposed 48-hour practice is the cleanest test. The report says proposed changes should be sent to the Council list at least 48 hours before voting, with attention to time zones and directed voting. Its paired action item asks Council leadership and support staff to consider how such proposals can be formalized. That final clause matters. The agreement points toward a rule; it does not enact one.

The current GNSO Operating Procedures, version 3.8 dated 1 September, still set the ordinary deadline for reports and motions at ten calendar days before a Council meeting. A late motion may be considered if it arrives at least 24 hours before the meeting and the Council unanimously agrees to consider it. The version record describes administrative and editorial changes to the main body, not a new 48-hour amendment rule. The responsible status is therefore “public formalization not located,” not “rule in force” and not “agreement abandoned.”

The Action-Decision Radar presents the opposite category error. It groups forthcoming decisions and actions into time windows. The report says the tool is flexible and useful for planning, while a prioritization framework performs a different function. Later Council records preserve that distinction. Staff prepared options, leadership shaped a non-binding pilot, groups supplied inputs in August, and the Council reviewed preliminary scoring in September. The evidence shows an active prioritization exercise beside the ADR, not the ADR quietly becoming a ranking authority.

What the later record actually verifies

SSAD supplies a visible chain of state changes without needing to dominate the article’s substance. The strategy report recorded support for a path in which the Board would not adopt the 18 recommendations, opening work on Supplemental Recommendations. It also recorded a desired pace of “months, not years” and an action for Council leadership to arrange a Board dialogue in February.

The dialogue occurred during the 12 February Council meeting. The minutes say there was no firm timeline, although participants discussed completion in months and later expressed an example of less than one year. On 12 March, the Board formally did not adopt the package and asked that future work fit within the RDRS operational extension ending in November 2027. A Supplemental Recommendations Team prepared for its first meeting in May, was reviewing recommendations later that month, and by 31 July had updated straw text for all recommendations. Its stated goal was public-comment-ready text by the end of ICANN87.

On 20 September, ICANN listed that public comment as upcoming in October.

This sequence is neither “done” nor “nothing happened.” The dialogue and triggering Board decision are completed. The team’s work is active. Public comment is a future checkpoint. Final policy approval and implementation lie beyond all three.

The receipt the report needs beside it

A plan-to-status receipt need not rewrite the report. It can be a compact companion record with the original item, verb class, accountable actor, target window, adoption requirement, later evidence, current status, any substitution or uncertainty, and the last verification date.

Plan item Evidence class Later public evidence Status at 20 Sep 2026
Send proposed voting changes at least 48 hours early Agreement plus formalization action Operating Procedures v3.8 retain the ten-day and late-motion 24-hour rules Public formalization not located
Hold Board dialogue on SSAD February action item 12 February Council minutes Completed
Board non-adoption to open Supplemental Recommendations Expected formal decision Board resolutions of 12 March Completed
Finish Supplemental Recommendations in “months, not years” Directional target, no firm deadline Team operating from May; all straw text updated in July; October comment listed as upcoming Active, not complete
Develop prioritization beside the ADR Planning agreement and follow-up work Non-binding pilot launched in July; preliminary inputs reviewed in September Active pilot
Provide tool recordings and a Projects List deep dive Action item with AGM-or-sooner window ICANN87 had not yet occurred Future; not yet due
Hold a post-SPS check-in at about six months Action item with approximate window No discrete public completion receipt located in the bounded record Unverified publicly; no failure inference
Post and transmit the strategy report Administrative action May review, 1 July notice to proceed, September public correspondence Completed; public lag unexplained

The final row also shows why provenance matters. Support staff circulated a draft on 27 May, set 17 June for comments, and said on 1 July that the report would be posted and transmitted. The public correspondence entry appeared in mid-September. The record establishes elapsed time, not its cause.

The document also carries internal date labels that should be corrected in a future version history. Its status material gives 14–15 January 2026, the executive summary says 19–20 January, and other passages refer to a 2025 or 2025–2026 session. Those discrepancies affect citation and traceability. They do not support an allegation about the meeting or its participants.

Institutional records earn trust when they show transitions, not when every sentence is made to sound equally binding. A narrow public receipt would preserve the value of a candid planning meeting while letting outsiders distinguish intention, work in progress and adopted reality.

Sources

  1. GNSO Council Strategic Planning Session Report
  2. GNSO Council review thread for the report
  3. GNSO Council minutes, 12 February 2026
  4. ICANN Board resolutions, 12 March 2026
  5. SSAD Supplemental Recommendations Team archive
  6. ICANN Public Comment
  7. GNSO Council agenda update, 10 September 2026 meeting
  8. GNSO Operating Procedures v3.8