Framework for Board Liaisons to Community Groups: Difference between revisions
Created page with "The '''Framework for Board Liaisons to Community Groups''' is a set of guidelines outlining how to choose a board liaison and detailing the role.<ref>[https://www.icann.org/en..." |
m added Category:Frameworks using HotCat |
||
| (One intermediate revision by the same user not shown) | |||
| Line 5: | Line 5: | ||
# Keep the Board/caucus informed of their appointed projects' progress; | # Keep the Board/caucus informed of their appointed projects' progress; | ||
# Identify potential challenges that could be mitigated by the ICANN Board and/or give the board early warning; | # Identify potential challenges that could be mitigated by the ICANN Board and/or give the board early warning; | ||
# Convey Board input to inform project deliberations ; | # Convey Board input to inform project deliberations; and | ||
# Indicate whether recommendations are unlikely to be approved by the ICANN Board, without attempting to dictate a preferred | # Indicate whether recommendations are unlikely to be approved by the ICANN Board, without attempting to dictate a preferred | ||
outcome. | outcome. | ||
==References== | ==References== | ||
[[Category:Frameworks]] | |||
Latest revision as of 15:04, 7 March 2022
The Framework for Board Liaisons to Community Groups is a set of guidelines outlining how to choose a board liaison and detailing the role.[1]
Overview
Board Liaisons provide an interface between the ICANN Community and the ICANN Board. The framework indicates that liaisons should:
- Keep the Board/caucus informed of their appointed projects' progress;
- Identify potential challenges that could be mitigated by the ICANN Board and/or give the board early warning;
- Convey Board input to inform project deliberations; and
- Indicate whether recommendations are unlikely to be approved by the ICANN Board, without attempting to dictate a preferred
outcome.