Summary

  • A GAC member or observer may issue an Early Warning without GAC consensus, normally during the 104 days after String Confirmation Day.
  • The warning has no direct impact on the application, but the applicant must decide whether to engage, seek a change, continue unchanged or withdraw.

A GAC Member Early Warning occupies an awkward but important place in the 2026 Round. It is more specific than ambient political concern, yet it is not a veto, a rejection or GAC Consensus Advice. It gives a member or observer of ICANN's Governmental Advisory Committee a formal way to identify an application viewed as potentially sensitive or problematic.

The concern might involve national law or a broader sensitivity, and it must be specified in the warning. The filing should include a written explanation of why it was submitted, how the applicant might address the concern, and contact details for communication. GAC consensus is not required for a member or observer to issue the warning.

A 104-day signal, not a direct decision

Early Warnings should be submitted during the 104 days after String Confirmation Day. ICANN says it will notify affected applicants as soon as practicable after receipt.

The Guidebook's boundary is explicit: an Early Warning is notice only and has no direct impact on the application. Evaluators may nevertheless consider it. It can also indicate that the application might later attract GAC Consensus Advice or an objection, but neither later mechanism requires an Early Warning first.

That distinction prevents two opposite errors. Treating the warning as harmless correspondence understates a formal risk signal. Treating it as a final public-policy decision gives it an authority it does not have.

Four response paths remain open

ICANN encourages an applicant that wants to continue to enter dialogue with the concerned party as soon as possible. The applicant may also seek an Application Change Request to address the concern. It may elect to take no action and proceed with the application unchanged, or it may withdraw, in which case the applicable refund schedule governs.

These are choices, not guaranteed outcomes. Failure to engage may or may not lead to GAC Consensus Advice. Engagement also does not guarantee that later advice or an objection will be avoided. The record therefore needs to distinguish the concern that was received, the response selected, the evidence supporting that selection and any later process that actually occurs.

Not every government concern is an Early Warning

GAC members may also use channels available to the public, including the Application Comment Forum or direct communication with an applicant. A concern sent through those routes does not itself constitute a GAC Member Early Warning. The label depends on the defined process, not merely on the identity of the speaker or the seriousness of the subject.

This matters for accountability. A team should not merge public comments, informal dialogue, an Early Warning, an objection and GAC Consensus Advice into a single “government opposition” status. Each has a different source, procedural effect and next step.

Build a response record without inventing certainty

The useful control surface is a response matrix with five fields: the stated concern, its cited factual or legal basis, the mitigation described by the issuer, the applicant's chosen path and the evidence of any engagement or change request. It should preserve dates and owners without claiming that conversation alone resolved the issue.

That matrix is BTW editorial advice, not an ICANN filing requirement. ICANN establishes the warning process and describes response options; it does not require this internal document. Nor does an Early Warning alone prove that an application will be rejected, proceed, or reach delegation.

Sources