This Workspace has been created to assist the ALAC/At-Large community in developing FY19 Additional Budget Request proposals. The Finance and Budget Sub-committee (FBSC) will review all proposals submitted and will agree on which to submit to ICANN on behalf of the ALAC.
FY19 Draft ALAC Criteria for Additional Budget Requests:
- Outreach should not be a major focus. Activities to improve engagement with existing members is encouraged.
- If any request is made on outreach, it should probably go through the CROP program and not this special request process.
- Proposals should include ways in which will make the ALAC and/or the At-Large community more effective and develop the At-Large community.
- RALO requests must go through a bottom up process within their RALO prior to being submitted for consideration by the FBSC.
- They must be explicitly supported by the RALO representative on the FBSC.
- Staff is currently expecting that basic resources for community communications/printing will be supported through the core ICANN budget, but that community proposals for printing , etc. will be accepted as a back-up in case expectations change. Specific proposals for communications resources beyond simple printing and editing functions should be prepared and submitted.
Important Documents and Resources from ICANN Finance:
TBD
FY19 Additional Budget Request Timeline
FY19 Community Additional Budget Request Timeline | Start | End |
Kick off and Submission Period | 15/12/2017 | |
FBSC representatives and/or staff to send notice of opening of FY18 additional budget request process to RALOs | ||
RALOs to review any ALS request or complete a template on behalf of the RALO and send requests to | ||
Discussion of Proposals with Finance Staff and FBSC | ||
Revised proposals to be sent to the FBSC for final review. | ||
The FBSC to review all the RALO requests. | ||
Submission Deadline (Staff will send the FBSC approved requests to Finance by 1/30/2017.) | ||
Preliminary review of requests by ICANN staff | ||
SO/AC consultations at ICANN 58 (by request, during Constituents’ Day) | ||
Final assessments and recommendations by ICANN staff | ||
ICANN Board Review and approval at May Board meeting |