Sorry, you need to enable JavaScript to visit this website.

ICANN Resolutions » Ombudsman FY17 At-Risk Compensation

Important note: The Board Resolutions are as reported in the Board Meeting Transcripts, Minutes & Resolutions portion of ICANN's website. Only the words contained in the Resolutions themselves represent the official acts of the Board. 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 FY17 At-Risk Compensation


Resolution of the ICANN Board
Meeting Date: 
Thu, 29 Jun 2017
Resolution Number: 
2017.06.29.06
Resolution Text: 

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

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

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.

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

Scoring the Ombudsman's annual performance objectives is in furtherance of the goals of ICANN and helps increase the Ombudsman's service to the ICANN community. While there is a fiscal impact from the results of the scoring, that impact is already accounted for in the annual 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.