A physical ticket costing USD 100 will help determine when a 2026 new gTLD application is processed. The mechanism sounds almost ceremonial beside an application system built around technical evaluations, objections and contracts. Its effect is not ceremonial.

ICANN's Prioritization Draw assigns each application a number that guides the general order of contention resolution, Applicant and Application Evaluation, publication of results and, for successful applicants, movement toward contracting. A low number can therefore change how long an applicant waits for consequential stages. It cannot make an application pass them.

That boundary is the story of the draw: an optional random event creates a real queue, but the queue remains subject to substantive processes that the number cannot override.

Optional does not mean neutral

To enter the draw, an applicant must obtain a separate USD 100 ticket for each participating application. The ticket cannot be bought online. It must be purchased in person through the applicant's designated representative or proxy. At the live event, ICANN will manually draw physical paper tickets and assign Priority Numbers.

The number selected for a participating application is random within the applicable draw rules. The decision to participate is not neutral, however.

ICANN's Applicant Guidebook and its FAQ for nonparticipating applications say applications left out of the live draw will still receive numbers. They will be drawn randomly in groups of 500—but only after every participating application has been numbered. If the participating pool ends at Priority Number 1,000, the best number available to a nonparticipant is 1,001.

The USD 100 payment therefore does not purchase a favorable result inside the participating pool. It purchases entry into the pool that is exhausted first. For an applicant with several applications, the distinction repeats one ticket at a time: a separate in-person purchase is required for each application it wants placed in that earlier pool.

Even that pool is not governed by one undifferentiated lottery. The Guidebook gives special treatment to IDN applications. Applications for allocatable variants of existing 2012-round IDN gTLDs are automatically included and drawn first without a ticket; additional IDN prioritization rules shape later groups.

Participation is thus optional in the formal sense that an application survives without a ticket. It is consequential in the operational sense that every entity is placed ahead of every nonparticipant, subject to the program's specific IDN rules. Any account of the draw as merely a transparent randomizer misses the prior choice that determines which random pool an application enters.

A low number orders attention, not outcome

Once assigned, a Priority Number is fixed. It cannot be changed or transferred to another application or applicant. That permanence gives the number procedural weight, but not substantive power.

ICANN says the number determines the general order in which applications move through contention resolution, Applicant Evaluation and Application Evaluation, receive results and, if successful, proceed toward contracting. Each qualification matters. The number orders ICANN's attention across later stages; it does not answer the questions those stages are designed to decide.

It does not determine the order in which applications enter String Evaluation. It cannot resolve an objection, cure a failed evaluation or remove another applicant from a contention set. Nor does a low number guarantee earlier delegation. An application must still complete the applicable evaluations, challenges, contention procedures and contracting requirements.

ICANN's processing-order FAQ makes the exception structure explicit. An application may be paused because of an objection, appeal, GAC Consensus Advice, Extended Evaluation, contention resolution, an accountability mechanism or an application change request. When that happens, ICANN moves to the next application and returns to the paused one after the relevant issue is cleared.

That is a sensible protection against one blocked application freezing an entire queue. It also means that the visible number and the actual processing sequence will diverge. The earlier number remains in force even while later-numbered applications advance past it.

The difference is not evidence of unfairness by itself. It is a fact that requires an audit trail.

The missing record is a priority-variance ledger

A lottery can transparently assign an initial order. It cannot, on its own, make every later departure from that order transparent.

ICANN should publish a priority-variance ledger alongside the application-status record. For each material stage, the ledger should show the assigned Priority Number, the date the application became ready, the date processing began, any pause, the stated reason for that pause, the date the condition cleared and the date processing resumed. Where operational capacity rather than an application-specific process changed the sequence, that should be identified separately.

This is an accountability recommendation, not a rule contained in the Applicant Guidebook. Its purpose is to preserve the meaning of the rule ICANN has adopted. If the institution promises a general numerical order while reserving legitimate exceptions, the public should be able to distinguish a justified exception from an unexplained delay.

The same record would protect applicants from over-reading their own numbers. A low number could be seen as an early place in the applicable queue, not a promise of a result date. A high number could be understood as a later starting position, not proof that every lower-numbered application must finish first. The operational history would show which dependencies actually controlled the path.

The draw is only the beginning of the queue

The 2026 Prioritization Draw gives ICANN a visible way to order thousands of applications without rewarding submission speed. Its physical tickets and live random selection make the assignment event inspectable. The special IDN rules and the separation between participating and nonparticipating pools make clear that it is structured randomness, not one flat lottery.

The number that emerges is consequential. It is also bounded. It governs general processing order after String Evaluation, while substantive reviews and challenges retain the power to pause, redirect or end an application.

The legitimacy test therefore begins after the last ticket is drawn. ICANN should be able to show not only which number each application received, but when the number controlled the sequence, when another rule displaced it and why. A transparent lottery creates the queue. A transparent variance record is what would keep that queue accountable.

Sources