RSSAC041 was published on 5 October 2018. All RSSAC publications can be found at https://www.icann.org/groups/rssac/documents.
| Recommendation | Description | Current Phase |
|---|---|---|
| Recommendation 1 | The ICANN organization should, with sufficient detail, define an ICANN organizational review. This definition should be documented and available to the community. Details should be crisp and tight in order to ensure complete clarity of scope. | Phase 5 | Close |
| Recommendation 2 | The ICANN organization should document the intent of the organizational review, what information it hopes to obtain, and how that information will be used. | Phase 5 | Close |
| Recommendation 3 | The ICANN organization should continue to use its RFP process to select the IE. The process should be modified to ensure that the IE are experts in assessment frameworks and methodologies and that they are not from the ICANN community. | Phase 5 | Close |
| Recommendation 4 | When an organizational review begins, the ICANN organization should ensure there are actionable checkpoints in place to ensure that the organizational review is meeting contractual obligations. Depending on the outcome of each checkpoint, the ICANN organization should take appropriate action to ensure contractual compliance. | Phase 5 | Close |
| Recommendation 5 | At the conclusion of any organizational review, the ICANN organization should report on how the process transpired. If there are any lessons learned from the organizational review, the ICANN organization should demonstrate how the process will be modified. | Phase 5 | Close |
