Summary

  • ICANN’s new monthly report series puts policy development, Board action, implementation, organizational objectives and other indicators into a recurring public record.
  • The reports show progress states, not a single verdict on whether a policy or organizational objective improved outcomes outside ICANN.

On 14 October, ICANN President and CEO Kurtis Lindqvist announced that the organization was producing Monthly Board Reports and publishing them alongside their submission to the Board. The public archive listed reports for July and August 2026. The archive also contains earlier CEO reports to the Board, including one covering 12 May to 14 November 2025. “New” therefore describes the monthly series; it does not mean ICANN had no earlier Board reporting.

The format’s value is its map of work across institutional boundaries. The August report separates Board action items from Supporting Organization and Advisory Committee items, and then shows policy development, matters awaiting Board action, policy implementation, projects still in a queue, review recommendations, upcoming decisions, organizational objectives, and litigation and accountability matters. Readers can see that “the Board acted,” “implementation is under way,” and “a policy changed an external result” are different claims.

The August report makes that distinction concrete without resolving every question. Its Board action table lists 154 items completed, five in progress and none not started. The separate SO/AC table lists one item in progress and none in the other two states. Those counts describe different work populations; they are not a measure of how many policies took effect or what changed for users. The report also assigns completion percentages to key results. Such a percentage can help track movement against an objective, but it needs a defined unit, a dated evidence source and a clear endpoint before it can answer what changed in practice.

Time stamps matter as much as status. The August report’s financial highlights are dated 31 July: annual funding actual versus budget is 107%, annual expense actual versus budget is 93%, the operating-fund balance is 130% of its investment-policy target, and the reserve-fund balance is 104%. The July report, though covering July, labels its financial snapshot “as of 31 May.” That is a reason to read each reference date directly, not to assume a report month is the measurement cut-off for every indicator.

The reports’ recurring structure could make slippage, dependencies and changes in status easier to follow. It does not make a management indicator an external evaluation. The announcement calls the reports high-level progress updates; neither the announcement nor these two editions describes the displayed objective percentages as independently audited outcome measures. That boundary is not a defect in the format. It is the difference between a useful progress record and a claim the record does not make.

As of 15 October, the new archive displayed two monthly editions. A series can earn comparison value only as later editions preserve definitions and dates: what is counted, who owns the next step, what evidence changes a status, and what completion means. ICANN has opened a more frequent view of its work. The next question is whether the record will let readers trace a status all the way to an observable result.

Sources