Summary

  • On 7 August 2026, ICANN issued a request for proposals for end-to-end management of sponsorship at its Public Meetings and potentially smaller events. Proposals are due at 23:59 UTC on 4 September.
  • The agency’s proposed scope runs from strategy and prospecting through sponsor screening, sales, contracting, benefit delivery, billing, reporting and retention.
  • The agency would make the initial written sponsor approval or non-approval determination under agreed criteria. Conflicts, reputation risks and policy concerns must be escalated to ICANN, internal sign-offs are required, and ICANN may stop an opportunity in exceptional circumstances.
  • ICANN states a current net baseline of about USD 300,000 per standard Public Meeting and asks for opportunities to reach up to twice that baseline. The document frames this as a strategy with assumptions, milestones and mutually agreed targets—not a guaranteed result.
  • A two-key authorization and benefit receipt would preserve the difference between commercial recommendation, screening evidence, ICANN’s mission-risk judgement and the exact entitlements a sponsor receives.

One provider would run almost the whole commercial chain

The Event Sponsorship Management RFP is unusually useful because it makes the operating chain visible before a provider has been chosen. Published on 7 August, it follows a December 2025 request for information that ICANN described as the first stage of a two-stage procurement. Proposals to the RFP are due on 4 September. Evaluation is estimated for 8 September through 6 November, with final evaluation, contracting and award in December. ICANN reserves the right to change that timetable or make no award.

The document seeks more than an event salesperson. The selected agency would help shape a multi-year strategy, identify sectors and markets, update the sponsorship prospectus, prospect and reactivate sponsors, conduct targeted outreach, prepare proposals, negotiate, execute contracts using agency templates, coordinate benefit fulfillment, invoice, collect, report, retain and expand accounts. It would maintain pipeline and performance data and make that data available to ICANN.

Consolidation has a practical defence. A sponsor should not receive one promise from sales, a different package from contracting and a third interpretation at the venue. One operator can connect an agreed entitlement to an invoice and then to delivery. A common data structure can show where a prospect stopped, whether a payment arrived and whether a benefit was fulfilled. ICANN explicitly requires common-format exports and continuing access without operational restrictions, reducing the danger that its own sponsorship history becomes hostage to a vendor’s system.

The same consolidation, however, means the institutional boundary cannot be inferred from departmental labels. The commercial operator will touch the opportunity before, during and after the decision. The record has to show which act it performed in each role.

The initial screener also carries the growth assignment

The screening duties are substantive. The agency is to conduct due diligence, review public records and sanctions lists where applicable, assess reputation and identify conflicts or policy concerns. It must provide ICANN with a formal written approval or non-approval determination supported by findings and risk assessments. The RFP then says the agency “shall make the initial sponsor approval determination” under agreed criteria and notify ICANN before proceeding.

That is not the whole authorization chain. Potential conflicts, reputational risks and policy concerns are to be escalated to ICANN for review and approval before engagement. Required internal reviews and sign-offs must be complete before contract execution. ICANN can request additional review or direct that a sponsorship opportunity not proceed in exceptional circumstances. Unusual contract terms and material deviations also return to ICANN for discussion.

The text therefore supports neither of two extreme readings. It does not make the agency a mere clerk with no judgement: “initial approval determination” is a real classification act. Nor does it show that ICANN has outsourced final mission authority: escalation, sign-off and stop powers remain in the design.

The governance issue comes from the neighbouring assignment. ICANN identifies net sponsorship funding of approximately USD 300,000 per standard Public Meeting after agency fees and commissions, with smaller meetings historically around USD 25,000. The vendor is to maintain or exceed the standard-meeting baseline and identify opportunities to achieve up to twice the current baseline through wider acquisition, new markets, enhanced offerings, partnerships and program optimization.

The RFP sensibly asks for assumptions, milestones and mutually agreed performance targets. Its KPIs include total and net funding, new-sponsor value, renewal and retention, average value, conversion, year-over-year growth and forecast accuracy. “Up to two times” is therefore an ambition to investigate, not a promise that receipts will double and not proof that the eventual contract will impose one number on every meeting.

Yet the incentive junction is real even without misconduct. A provider rewarded or evaluated for converting more prospects also makes the first call on whether those prospects pass. A borderline finding can affect both risk and a commercial metric. Good governance does not presume the call will be corrupted. It makes the two roles reconstructable so that neither the vendor nor ICANN has to rely on assurances after a controversy.

Sponsorship benefits are valuable without becoming policy power

The current ICANN85 prospectus shows what the commercial object contains. Platinum, Gold, Silver and Bronze packages are priced at USD 60,000, 40,000, 20,000 and 12,000. Depending on tier, benefits include main-stage backdrop exposure, digital or printed signage, meeting-bag inserts, a sponsor page, venue branding, booth space, coffee-break branding, use of an official-sponsor meeting logo and forms of meeting-room access. Materials are subject to ICANN-organization approval before final production.

Those are not trivial benefits. Visibility, a room and a well-positioned booth can affect who meets whom and which organization becomes familiar. ICANN’s current sponsorship page itself markets access to business representatives, governmental bodies, industry figures and other influential contributors. A serious record should not pretend that commercial exposure is weightless.

But the evidence also does not convert exposure into policy authority. The reviewed package does not sell a vote, a seat in a supporting organization, control of a session agenda, ownership of minutes, a finding of rough consensus or a Board decision. ICANN says its Public Meetings are free and open to anyone wishing to participate. Its Board describes the policy-development processes served by those meetings as open, transparent, bottom-up and multistakeholder.

The boundary should be stated positively: a sponsor buys a defined set of commercial entitlements; a participant’s standing in policy work comes from the applicable community process. A meeting room is a room. It is not an institutional mandate. A logo on a backdrop is visibility. It is not a vote.

ICANN also says sponsorship is unavailable for the June Policy Forum, while opportunities apply to Community Forums and Annual General Meetings. That difference is part of the public program design. It does not prove that sponsored meetings are captured, or that every commercial interaction disappears from an unsponsored meeting.

The missing object is a two-key receipt

The RFP contains several controls but does not prescribe a public, transaction-level authorization record. It may be that ICANN already keeps more detailed internal files. The public question is narrower: after a sponsorship is accepted, can a participant tell which institution made the mission-risk decision and what the sponsor was permitted to receive?

A sponsorship authorization and benefit receipt should have two independent keys.

The first is the vendor record: opportunity identifier, prospecting source, commercial owner, recommendation date, proposed package, screening criteria version, written approval or non-approval state and a bounded reason category. It should identify whether a conflict, reputation issue, sanctions issue or policy concern required escalation, without publishing private evidence.

The second is the ICANN record: named accountable role, decision date, approval, rejection, modification or request-for-review state; declared conflicts and recusals; the authority used; and any exception or condition. The institutional approval should not be a duplicate of the vendor’s sentence. It should show that someone acting for ICANN accepted responsibility for mission, neutrality and meeting objectives.

The receipt should then attach the contract and benefit object: package and price band, the exact inventory of branding, booth, digital placement, room and hospitality entitlements, version and deviations, fulfillment state and material variance. An explicit negative boundary should state that the package confers no policy-agenda control, session-chair authority, ownership of minutes, rough-consensus status, vote or privileged Board decision right.

After the event, the same record can add gross and net funding, fees at an appropriately safe level, delivered and undelivered benefits, complaint or correction state and the KPI period to which the revenue was attributed. That last field matters when a vendor is measured on conversion: a sponsorship should not be counted in one period for performance and quietly reversed in another without a trace.

Public does not mean indiscriminate. Bid prices, personal data, private due-diligence materials, detailed sanctions findings, security information and legally protected advice can remain confidential. The public receipt can use reason classes and decision states. Its purpose is to expose authority and entitlement, not to publish a dossier on every prospective sponsor.

Heng Lu’s minimum-specification discipline sets the correct size. The common record should not attempt to predict every reputation question or centralize community judgement in a new bureaucracy. It should carry the smallest facts that let others reconstruct the decision: actor, role, criteria version, state, conflict, authority, benefit, date and revision. The vendor contributes expertise and execution; it does not become the principal of ICANN’s public mandate.

What the evidence does not show

No reviewed source identifies a winning agency, final fee arrangement or executed contract. The public RFP is a solicitation, not evidence that the stated scope will survive negotiation unchanged. Its reference to fees and commissions does not establish that the eventual provider will be paid only by commission.

No source reviewed here shows that a sponsor has bought influence, that an ICANN decision was altered for revenue, that a screening call was softened or that internal controls failed. The incentive analysis is prospective. It describes a role combination in the requested service, not a finding of misconduct.

The target also may have benign effects. Broader sponsor acquisition could diversify funding beyond a familiar industry circle. Professional screening may be more consistent than ad hoc judgement. Better data and contract fulfillment may reduce informal promises. A larger net contribution could help offset meeting costs while attendance remains free.

Nor is every rejection fit for immediate public explanation. A premature disclosure can harm a firm, expose personal information or reveal a sanctions or security check. The receipt can show that a decision occurred under a criteria version and a bounded reason class, with fuller disclosure delayed or withheld under a recorded rule.

The verifiable issue is smaller than a capture claim. ICANN proposes to combine a growth engine and the first screening gate in one external operating chain while retaining its own review powers. If the final contract follows that design, a two-key record would let commercial skill remain useful without allowing its recommendation to become indistinguishable from public authority.

Sources

  1. ICANN — Request for Proposal: Event Sponsorship Management, 7 August 2026
  2. ICANN — Event Sponsorship Management RFP
  3. ICANN — Event Sponsorship Management RFI, 23 December 2025
  4. ICANN Public Meetings — Sponsorship opportunities
  5. ICANN Public Meetings — ICANN85 Sponsorship Prospectus
  6. ICANN — Adopted FY27 Budget
  7. ICANN Board — approved resolutions, 3 May 2026
  8. ICANN Public Meetings — About
  9. ICANN — Requests for Proposals
  10. ICANN — Bylaws
  11. Heng Lu — Minimum Initial Specification, Localized Future Decision, and Voluntary Adoption