Summary

  • On 12 March 2026, the ICANN Board approved an updated GNSO charter-amendment process with immediate effect; the GNSO now says the process is in force.
  • The 2013 process gave ICANN staff 10 business days to send an approved proposal and concerns report to the appropriate Board committee, then 30 calendar days to summarize public comment.
  • It also required an explanation if the Board could not act after two meetings and deemed amendments effective after four meetings, or six scheduled meetings in total.
  • The 2026 process instead lets ICANN org and the affected group establish an appropriate timeline and says the timing of engagement may vary. It does not reproduce the old default clocks or meeting-count backstop.
  • All four public comments supported the update overall, but the Registrar Stakeholder Group explicitly urged retention of timelines. ICANN org chose a tailored timeline for each effort rather than a set process clock.
  • A public, versioned timeline receipt would make that flexibility auditable without imposing the same deadline on every charter or exposing privileged deliberation.

The old process had three kinds of clock

The comparison begins with the instruments, not an inference about institutional intent. The March 2026 document says plainly that it replaces the process established by the Board in 2013. Resolution 2026.03.12.01 put the replacement into effect immediately, and the current GNSO page reproduces its five phases.

The old process contained three different timing disciplines. First, after a Stakeholder Group or Constituency had approved proposed amendments and formally submitted them, ICANN staff was to analyse the proposal and, within 10 business days, send it with a report to the appropriate Board committee. The report was to identify fiscal or liability concerns.

Second, after the public-comment forum closed, staff had 30 calendar days to provide the Board committee with a report summarising community feedback. That clock did not guarantee a final Board decision. It did at least make the preparation of the next institutional record testable against a public interval.

Third, the 2013 text governed delay at the Board end. The appropriate committee was to review the record at the next available opportunity. If final action was not feasible after two meetings, the Board had to tell the affected group what prevented action and give its best estimate of the time required. After four meetings, or six scheduled meetings in total, the proposed amendments would be deemed effective.

Those provisions did not create one simple end-to-end deadline. They created separate clocks for staff analysis, comment synthesis and Board non-action. Nor does the record reviewed here prove that the old clocks always worked, that every document could be assessed properly within them or that automatic effectiveness was always the safest result. Their governance value was narrower: they made time a visible property of the process rather than only an internal operational choice.

The new process moves timing into the case

The 2026 design begins earlier. When a group starts revising its charter, it should notify its ICANN-org support team as soon as possible and identify a liaison. The group and ICANN org may establish an “appropriate timeline for the effort.” Templates align the work with the Bylaws, GNSO Operating Procedures and applicable Work Stream 2 recommendations. ICANN org can raise governance, legal, review and implementation questions before the group approves its final draft.

After the group’s own approval, ICANN org performs an initial review. If documents or issues are complex, it may engage with the group, and the process says the timing of that engagement may vary. When org review is complete, ICANN org sends a report to the appropriate Board committee. The committee can approve the report and direct a Public Comment proceeding. ICANN org prepares the comment summary; the committee considers it and recommends action to the Board.

The final authority remains legible. The Board can recognize amendments by simple majority or reject them by a two-thirds vote with specific reasons. Recognition constitutes approval; the group then adopts and publishes the amended charter. The update did not replace those thresholds with staff discretion.

What changed is the time architecture around those gates. The final text contains no 10-day staff-report clock, no 30-day comment-summary clock, no two-meeting explanation rule and no four- or six-meeting deemed-effective rule. The Board rationale goes further: it describes an appropriate timeline that is “not bound by the Process.” The schedule is now an attribute of the relationship between ICANN org and the affected group.

That is not necessarily a retreat from accountability. A short amendment and the incorporation of a group as a legal entity may present different legal, tax and governance questions. ICANN cited increasingly complex documents and the need for deeper review. Earlier engagement can discover problems before a membership vote, reducing a late return to drafting. Tailoring may therefore shorten some cases even though the standing process carries fewer public clocks.

Support did not erase the timing objection

The public-comment record requires two statements to be held together. All four submissions supported the updated process. The Board was entitled to describe the feedback as supportive. But support for the package was not agreement with every component.

The Registrar Stakeholder Group welcomed the templates and the effort to improve transparency, then objected to removing review timelines. Its concern was not that the old numbers could never change. It said the absence of an expected turnaround introduced ambiguity about subsequent steps and weakened assurance of timely approval. It was open to extending the existing periods if more time was necessary.

ICANN org’s summary preserved that point. Its response was a design choice, not a claim that the concern was mistaken: instead of requiring a set timeline in the updated process, org would work with each Stakeholder Group or Constituency to establish an appropriate timeline for that effort. The Organizational Effectiveness Committee repeated the same answer before recommending approval.

This distinction matters because “four supportive comments” can otherwise be misread as four endorsements of timer removal. The accurate state is more useful. There was broad support for earlier engagement, templates and a revised process; one supporting group sought a common timing safeguard; ICANN chose case-specific scheduling.

A tailored clock still needs a public face

The updated process describes an agreement but does not require a standard public record of it. It does not say that timelines must be secret, and no reviewed source shows that ICANN intends indefinite review. The narrower fact is that the standing instrument does not tell a reader where to find the initial schedule, whether it changed, which phase is active or who has the next action.

A minimal timeline receipt can close that gap without reviving a universal deadline. Each charter-amendment page could publish:

  • the group, charter revision and immutable document version;
  • the date ICANN org was notified and the date of the group’s membership approval;
  • the named group liaison and the institution that owns the current action;
  • the agreed window for each phase and the initial next-decision estimate;
  • the current phase, the date it began and any return-for-information or paused state;
  • each revised estimate, the date of revision and an attributable reason category;
  • the next accountable action and checkpoint;
  • the opening and closing of Public Comment and publication of the summary;
  • the committee recommendation, Board disposition, and adoption and publication dates; and
  • a last-verified timestamp and version history.

Reason categories can remain bounded: document complexity, additional governance review, legal-entity questions, group-requested drafting, dependency on another proceeding, public-comment processing or Board scheduling. A receipt need not publish privileged advice, confidential tax material, personal contact details or the substance of closed deliberations. It should reveal procedural state, not turn the public into co-counsel.

The receipt also should not make every forecast binding. An estimate is evidence of current planning, not a promise that later facts cannot change. The accountable act is to revise it openly, name the actor responsible for the new estimate and preserve the prior state. That is the difference between a tailored timeline and an invisible one.

Heng Lu’s minimum-specification discipline supplies the limit. The common layer should contain only what all cases need: state, owner, date, reason and next action. The decision about how much time a specific legal or governance issue requires remains with the actors handling it. A thin public record makes local judgment observable without converting coordination into a central permission machine.

What the evidence does not show

No source reviewed for this Article identifies a charter amendment that has already been delayed under the 2026 process. The comparison therefore cannot support a claim of current backlog, bad faith, capture or breach. It also cannot show how well the 2013 timers performed across the decade in which they applied.

The new process may produce faster outcomes through early consultation. A group may publish its own schedule. ICANN may add guidance or a visual aid that improves visibility. Those are open empirical questions. The governance test should follow the first complete cases rather than assume the outcome from the text alone.

Nor does the proposed receipt change authority. Membership approval remains with the Stakeholder Group or Constituency under its rules. ICANN org reviews governance and legal questions. The appropriate Board committee manages the institutional path into Public Comment and recommendation. The Board recognizes or rejects. A public clock cannot vote, approve a deficient charter or bypass a required review.

The verified change is smaller and more consequential than a scandal claim: ICANN moved timing from common default rules into case-specific coordination. The next accountability question is whether the result will be visible enough for members and outsiders to distinguish active judgment from unowned delay.

Sources

  1. ICANN — Process for Amending GNSO Stakeholder Group and Constituency Charters, March 2026
  2. ICANN GNSO — GNSO Charter Amendment Process, September 2013
  3. ICANN Board — approved resolutions, 12 March 2026
  4. ICANN Board — minutes, 12 March 2026
  5. ICANN — public-comment proceeding on the updated process
  6. Registrar Stakeholder Group — public-comment submission
  7. ICANN — public-comment summary report
  8. ICANN Board OEC — minutes, 23 February 2026
  9. ICANN GNSO — Stakeholder Groups and Constituencies
  10. ICANN — Bylaws
  11. Heng Lu — Minimum Initial Specification, Localized Future Decision, and Voluntary Adoption