Skip to main content
Resources

Planning – Community Roles and Responsibilities

The planning process is part of the bottom-up multistakeholder process and requires the collaborative effort of the whole ICANN Community. This includes the staff in the ICANN Organization, the ICANN and PTI Boards, as well as the Supporting Organizations, Advisory Committees, Stakeholder Groups, and Nominating Committee.

This page describes the involvement of the ICANN Community and the timeline of the planning process.

The ICANN fiscal years starts on 1 July and ends on 30 June. Fiscal years are named after the calendar year in which the end. The name starts with the prefix "FY" and then the last two digits of the calendar year in which the fiscal year ends. For example, the fiscal year ending in 2020 is called FY20.

Multiyear Calendar

  FY14 FY15 FY16 FY17 FY18 FY19 FY20
Strategic Plan1              
Consult S B         S B  
Develop O         O  
Consult S S       B S
Approve   B         B
Five-Year Operating Plan2              
Develop   O         O
Consult   S B S S S S S B
Update   O O O O O O
Approve   B B B B B B
Fiscal-Year Operating Plan and Budget3              
Consult   S B S B S B S B S B S B
Develop   O O O O O O
Consult   S B S B S B S B S B S B
Adopt   B B B B B B
Board Organization Stakeholder
B O S

Individual Year Calendar

Phase Q1 Q2 Q3 Q4
  Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun
Develop PTI Draft Plan                    
Consult on PTI Draft Plan                  
Review Comments                    
Update PTI Draft Plan                      
Adopt PTI Plan                      
Develop ICANN Draft Plans                  
Consult on ICANN Draft Plans                  
Review Comments                      
Update ICANN Draft Plans                    
Adopt ICANN Plans                      

The tables below provide a structure describing the phases of the planning process. They document the frequency of each phase, supporting elements, and the roles and responsibilities of the ICANN Organization, ICANN and PTI Boards, and the ICANN Community.

Strategic Plan Process

  Community Roles and Responsibilities
Strategic Plan4 Frequency Supporting Elements5 Staff Board Stakeholders
1. Consult Every 5 years6

Strategic Plan Kick-off

  • Accomplishments from last planning cycle
  • Environmental analysis, including SWOT7
  Consult on key challenges and opportunities and areas of strategic importance Consult on key challenges and opportunities and areas of strategic importance
2. Develop Every 5 years

Draft Strategic Plan:

  • Accomplishments from last planning cycle
  • Environmental analysis
  • Vision, Mission
  • Areas of strategic importance
Develop    
3. Consult Every 5 years Public comment and other engagements   Consult Consult
4. Approve Every 5 years

Final Strategic Plan

  • same as above, plus:
    • Strategic Goals
    • Key Success Factors (outcomes)
    • Strategic Risks
Update based on consultations and long-term planning work Approve  

Five-Year Operating Plan Process

  Community Roles and Responsibilities
Five-Year Operating Plan8 Frequency Supporting Elements9 Staff Board Stakeholders
1. Develop Every 5 years
  • Planning Calendar
  • Five-Year Financial Model
  • Draft Summary of Five-Year Operating Plan
  • Strategic goals with corresponding Key Performance Indicators, dependencies, five-year phasing, and list of portfolios
Develop    
2. Consult Every 5 years Public comment and other engagements   Consult Consult
3. Update Each year

Annual Reporting

  • Performance as compared to
  • plan for prior Fiscal Year, starting with FY16
  • Explanation of variances
  • Required changes to Five-Year Operating Plan if warranted
Update based on consultations    
4. Approve Each year Final Summary Five-Year Operating Plan   Approve  

Fiscal-Year Operating Plan and Budget Process

  Community Roles and Responsibilities
Fiscal-Year Operating Plan and Budget10 Frequency Supporting Elements11 Staff Board Stakeholders
1. Consult Each year
  • Draft Revenue Model
  • Draft list of Initiatives and Engagements
  Consult Consult
2. Develop Each year
  • Draft Fiscal-Year Operating Plan
  • Draft Fiscal-Year Budget
Develop/update based on Five-Year Operating Plan, consultations and recent history of events    
3. Consult Each year Public comment and other engagements   Consult Consult
4. Approve Each year Final Fiscal-Year Operating Plan and Budget Update based on consultations Approve  

ICANN Fiscal-Year Operating Plan Current Calendar


1 The next Strategic Planning effort for FY21 – FY25 is scheduled to begin in FY19

2 The Five-Year Operating Plan is updated each year to reflect actual performance and recent events. Changes are made for the remaining years in the planning cycle. Adopted Plans are published on the ICANN Planning Process page.

3 The Five-Year Strategic Plan for FY16–FY20 is linked to the Five-Year Operating Plan, which informs the Fiscal-Year Operating Plan and Budget

4 Five-Year Strategic Plan for FY16–FY20 is linked to the Five-Year Operating Plan, which informs the Fiscal-Year Operating Plan and Budget. The next Strategic Planning effort for FY21 – FY25 is scheduled to begin in FY19.

5 All documents are posted and publically available.

6 The next planning cycle is scheduled to begin in FY19 to allow sufficient time for key planning steps.

7 Environmental analysis is an important aspect of strategic planning. It includes assessment of strengths and weaknesses (internally focused) and opportunities and threats (externally focused).

8 The Five-Year Strategic Plan for FY16–FY20 is linked to the Five-Year Operating Plan, which informs the Fiscal Year Operating Plan and Budget. The Five-Year Operating Plan is updated each year to reflect actual performance and recent events. Changes are made for the remaining years in the planning cycle.

9 The Five-Year Operating Plan will be updated, when appropriate, for the rest of the cycle. No changes to the Five-Year Strategic Plan for FY16 – FY20 are anticipated. They would be made if a critically significant event or development is observed.

10 Strategic Plan for FY16–FY20 is linked to the Five-Year Operating Plan, which informs the Fiscal-Year Operating Plan and Budget.

11 All documents are posted and publically available

Domain Name System
Internationalized Domain Name ,IDN,"IDNs are domain names that include characters used in the local representation of languages that are not written with the twenty-six letters of the basic Latin alphabet ""a-z"". An IDN can contain Latin letters with diacritical marks, as required by many European languages, or may consist of characters from non-Latin scripts such as Arabic or Chinese. Many languages also use other types of digits than the European ""0-9"". The basic Latin alphabet together with the European-Arabic digits are, for the purpose of domain names, termed ""ASCII characters"" (ASCII = American Standard Code for Information Interchange). These are also included in the broader range of ""Unicode characters"" that provides the basis for IDNs. The ""hostname rule"" requires that all domain names of the type under consideration here are stored in the DNS using only the ASCII characters listed above, with the one further addition of the hyphen ""-"". The Unicode form of an IDN therefore requires special encoding before it is entered into the DNS. The following terminology is used when distinguishing between these forms: A domain name consists of a series of ""labels"" (separated by ""dots""). The ASCII form of an IDN label is termed an ""A-label"". All operations defined in the DNS protocol use A-labels exclusively. The Unicode form, which a user expects to be displayed, is termed a ""U-label"". The difference may be illustrated with the Hindi word for ""test"" — परीका — appearing here as a U-label would (in the Devanagari script). A special form of ""ASCII compatible encoding"" (abbreviated ACE) is applied to this to produce the corresponding A-label: xn--11b5bs1di. A domain name that only includes ASCII letters, digits, and hyphens is termed an ""LDH label"". Although the definitions of A-labels and LDH-labels overlap, a name consisting exclusively of LDH labels, such as""icann.org"" is not an IDN."