Historical Resolution Tracking Feature » Ombudsman FY20 At-risk Compensation

Important note: The explanatory text provided through this database (including the summary, implementation actions, identification of related resolutions, and additional information) is an interpretation or an explanation that has no official authority and does not represent the purpose behind the Board actions, nor does any explanations or interpretations modify or override the Resolutions themselves. Resolutions can only be modified through further act of the ICANN Board.

Ombudsman FY20 At-risk Compensation


Resolution of the ICANN Board
Meeting Date: 
Thu, 9 Jul 2020
Resolution Number: 
2020.07.09.02 – 2020.07.09.03
Resolution Text: 

Whereas, the Compensation Committee recommended that the Board approve payment to the Ombudsman of his FY20 at-risk compensation.

Resolved (2020.07.09.02), the Board hereby approves a payment to the Ombudsman of his FY20 at-risk compensation component.

Resolved (2020.07.09.03), this action by the Board shall remain confidential as an "action relating to personnel or employment matters", pursuant to Article 3, section 3.5b of the ICANN Bylaws.

Rationale for Resolution: 

Annually the Ombudsman has an opportunity to earn a portion of his compensation based on specific performance goals set by the Board, through the Compensation Committee. This not only provides incentive for the Ombudsman to perform above and beyond his regular duties, but also leads to regular touch points between the Ombudsman and Board members during the year to help ensure that the Ombudsman is achieving his goals and serving the needs of the ICANN community.

Evaluation of the Ombudsman's objectives results from both the Ombudsman self-assessment as well as review by the Compensation Committee, leading to a recommendation to the Board with which the Board agrees.

Evaluating the Ombudsman's annual performance objectives is in furtherance of the goals and mission of ICANN and helps increase the Ombudsman's service to the ICANN community, which is in the public interest.

While there is a fiscal impact from the results of the scoring, that impact was already accounted for in the FY20 budget. This action will have no impact on the security, stability or resiliency of the domain name system.

This is an Organizational Administrative Function that does not require public comment.