Summary
- The office can evaluate, recommend and publish; every decision in the chain belongs to somebody else, and the Bylaws say so three times over.
- Bylaws §5.4(d) makes posting the default and the exception the office-holder's own determination — which is how two Ombudsmen, one clause and sixteen years produced opposite publication decisions.
The clause that bites
Article 5 of the ICANN Bylaws, read on the governance rendering carrying the line "As amended 3 July 2026", puts the office on a full-time footing with staff support the Board determines, an initial two-year term, and removal only on a three-fourths vote of the entire Board. Then, at §5.4(d), it grants a specific authorisation: to make "such reports to the Board as he or she deems appropriate with respect to any particular matter and its resolution or the inability to resolve it", and to have them posted on the Website absent a contrary determination — hers (ICANN Bylaws, Article 5).
That is not a power to decide anything. §5.2, captioned CHARTER, is scrupulous about scope: a neutral dispute resolution practitioner "for those matters for which the provisions of the Independent Review Process set forth in Section 4.3 have not been invoked", an "independent internal evaluation of complaints" from community members who believe staff, Board or a constituent body treated them unfairly, and "an objective advocate for fairness" working by negotiation, facilitation and "shuttle diplomacy". §5.5 asks for an annual consolidated analysis with trends and "recommendations for steps that could be taken to minimize future complaints". ICANN's own Ombuds Office page is blunter still: the office "does not have the unilateral power to make, change, or set aside a policy, administrative or Board decision, nor to reverse an act or omission", citing Section 2.1 of the framework (ICANN Ombuds Office).
There is no separate charter to hunt for. ICANN's public-comment page for the current framework and process states that "the Charter of the Ombuds Office is set out in the ICANN Bylaws, Article 5" (public-comment record). The governance text is the constituting instrument, and the framework is the operating manual.
Sixty days, softened at both ends
The framework approved by the Board on 7 June 2026, described in its own text as superseding the 2009 Ombudsman Framework, is where the office's practical leverage is written down. Section 2.1.3 lets the Ombuds "make recommendations to the Board", and then asks the Board to respond — but only "to the extent the Board deems it appropriate and feasible", and only in the sense that it "should endeavor to respond" within the timescales in Section 9 (Ombuds Framework and Process, 7 June 2026).
Section 9 itself is brisker. Where the office makes "a formal request to a group, team, or individual within the ICANN community or staff", parties "shall endeavor to respond within the shortest timeframe possible and within the timeframes set out below".
For a final report or a set of recommendations, §9.1.3 sets "sixty days (or 90 days with a suitable reason for delay)" and then adds the part that matters: "A responding party should provide a substantive response to the Ombuds, along with rationale for that response." A further extension is available for "exceptional circumstances", but the request must arrive "before the expiration of the original 60-day deadline", and the Ombuds answers extension requests "within one week". Draft reports get fifteen days, twenty-one on request.
Interviews, information and documents get seven, fourteen on request.
Failing all that, Section 9 hands the office a route: it may notify the Board — or the President and CEO for staff matters — of the noncompliance and the proposed action to remedy the matter, with remedies running as far as a restriction on or suspension of the responding party's role and participation in ICANN. The route exists, and the office has to invoke it. Nothing in the instrument lets the Ombudsman impose the consequence herself.
That asymmetry is drafted, not accidental. The responding duty is hedged by "endeavor"; the Board's own obligation is hedged again by "appropriate and feasible"; and the sanction sits in a notification the office sends rather than in a decision it takes.
There is a checkable seam in the drafting, too. ICANN's implementation documentation for the Work Stream 2 recommendations recites Recommendation 5.4 as requiring the relevant parts of ICANN to respond "within 90 days (or 120 days with reason)" and states that 5.4 "is addressed in section 9 of the Ombuds Office Framework and Process" (WS2 implementation documentation). The adopted §9.1.3 sets sixty and ninety. The recital and the instrument do not agree with each other.
The case where both ends can be read
Reconsideration Request 25-2, filed by Nick Pelts on 31 October 2025, is the one matter where the office's reasoning and the deciding body's disposition are both on the record. The case page indexes the whole chain: the request, an Ombuds Action dated 8 December 2025, a Substantive Evaluation dated 21 December 2025, the committee's recommendation of 5 February 2026, a rebuttal and a supplemental statement from the requestor, and a Board action of 8 March 2026 (Reconsideration Request 25-2 case page).
The 8 December action is short and accepts the referral, with a line that matters: "I see no reason, at this time, for my recusal" (Ombuds Action, 8 December 2025). The 21 December evaluation calls itself "the first Reconsideration Request that has been submitted to me for evaluation by the ICANN Board BAMC since I became the ICANN Ombuds in October, 2024" — Elizabeth Field has held the office since October 2024, announced on 18 September 2024 after an international search (appointment announcement). It finds that Contractual Compliance "justifiably and correctly" closed the underlying complaint because the requestor "is not, and during all relevant time periods was not, the Domain's Registered Name Holder", finds "no basis for a reconsideration under the Bylaws" and "no evidence whatsoever" of reliance on false or inaccurate information, and ends: "Therefore, I recommend the BAMC propose to the Board that it deny Request 25-2" (Substantive Evaluation, 21 December 2025).
The committee took it up in the office's own words. Its 5 February 2026 recommendation records that the committee "has considered the merits of Request 25-2, as well as all relevant information provided and the Ombuds Evaluation", quotes the conclusion that Compliance "justifiably and correctly" closed the complaint, and grounds its own view in a different register — that closure "was not based on a failure to consider any material information, but rather was appropriate given the limitations on the scope of Contractual Compliance's authority" (BAMC Recommendation, 5 February 2026).
The Board adopted it. Resolution 2026.03.08.01 provides that "the Board adopts the BAMC Recommendation on Reconsideration Request 25-2 and denies Reconsideration Request 25-2", and its rationale states that the determination "is also consistent with the conclusion reached by the Ombuds" (approved resolutions, 8 March 2026). The minutes record that Patricio Poblete presented the proposed resolution and that "All members of the Board voted in favor of Resolution 2026.03.08.01. The Resolution carried" (minutes, 8 March 2026).
Read together, those documents support two conclusions that commentary tends to treat as rivals and that are both true here. The route is not decorative: an independent office wrote reasons, a committee quoted them, and a board adopted a resolution whose stated rationale leaned on them. And in the only case where the reasoning can be checked, the independent evaluation reached the outcome the complained-of staff had already reached. The registrant-of-record question settled the matter, and the office said so in plain words.
That is not a failure of independence. It is what independence looks like when the answer is unexciting: an evaluator who follows the registrant record rather than the complainant's sense of grievance, and writes "justifiably and correctly" where a reader might have expected a rebuke. The office's contribution in that case was not a different conclusion. It was a second, reasoned, attributed voice on the record — exactly what a deciding body needs if it intends to be seen to have considered the matter.
The other call under the same clause
Sixteen years earlier, a different Ombudsman read the same sentence the other way. "Report to the Board of Directors, Ombudsman File 09-58", on incivility within ICANN, is signed by Dr. Frank Fowlie and dated 29 October 2009. The complaint was substantiated. The report forwards ten numbered recommendations in the first person. And then, on publication, the Ombudsman "determined that it would be inappropriate to post the full report, but believes that the community should be informed of the investigation" (Ombudsman File 09-58, 29 October 2009).
Both determinations are lawful readings of one sentence. One office-holder published a full evaluation of a named reconsideration request. Another withheld a substantiated report and issued a summary instead. Nothing in the Bylaws changed between them in any way that explains the difference.
What the office actually controls
Set the two documents side by side and the shape of the job sharpens. The Ombudsman does not control outcomes. She controls the record: which matters get written up, at what length, in whose words, and whether the community sees the document or only learns that an investigation happened. Section 2.2.3 of the framework lets the Ombuds post anonymised, redacted reports of complaints and cases and their resolutions, aggregate or as a single matter, on icann.org/ombuds — a discretion that governs the archive as much as the individual case.
She also controls framing, which is not a small thing when a deciding body is shopping for language. The Board's own resolution borrowed "consistent with the conclusion reached by the Ombuds". Whatever else a recommendation does, it supplies the sentence somebody else can use.
Against that, the office's public self-description holds a documented tension. Sections 2.1.3 and 9 assume reports and recommendations to the Board on particular matters. ICANN's About page states: "The Ombuds reports to the ICANN Board on the Office's activities. The Ombuds Office does not report to the Board on individual cases, unless required by policy or law" (About the Ombuds Office). The published 25-2 evaluation is precisely a report to a Board committee on an individual case. The page and the case file do not sit easily together, and nothing in the material reviewed reconciles them.
What remains open
Whether the framework has been amended since 7 June 2026 was not established; the quotations above are drawn from the PDF as extracted, and its signed or effective date and any later amendment were not separately verified. Bylaws quotations come from the governance rendering, whose letterhead, pagination and internal anchors were not verified. The 8 December 2025 action is redacted and its returned text carries OCR artefacts; only the acceptance and recusal lines were inspected.
The separately indexed PDF of the 8 March 2026 Board action was not opened, so the operative wording above comes from the meeting's approved-resolutions page and the voting detail from its minutes. The board-discussion transcript is indexed on the case page but was not read end to end, and no quotation is drawn from it. Whether any recommendation after 25-2 drew a written response inside the §9.1.3 window was not established. The reasoning behind either posting determination — Fowlie's or the 2025 one — is not published; only the determinations are.
That last gap is the point. A discretion that lives in the office-holder's judgement is legitimate, and it is also unreviewable by construction. The community gets the record the office chooses to hand it. In 2009 that meant a summary. In 2025 it meant a full evaluation that a Board resolution then quoted back at the committee that wrote it. Both are Article 5 working exactly as drafted. Neither is Article 5 promising that the next one reaches the website. The office that can recommend and cannot decide holds its real authority in that choice — and the ICANN directory record is where the institution sits that grants it.
Member Briefing
Read the full trend briefing
Members read the full briefing with the source notes behind every finding.
Strategic Circle
A daily briefing in your language, built from changes we have verified.
Join for USD 20/monthCancel anytime.
Members also get the full research library, a daily briefing on the networks they follow and the private forum.






