Instructions:
1. You must be logged in to the Community Wiki with a valid Username and Password in order to complete forms within CROP.
2. Your organization must first complete and get approval for the Outreach Strategic Plan before any CROP trip could be processed.
3. To fill out the the form, click
(top of the screen).4. Answer each of the questions that appears within the form. Use the scroll bar (right) to reveal all contents. Click here to read the full instructions
Strategy Status |
APPROVED |
Person Completing Form: | Lawrence Olawale-Roberts |
---|
FY23 Outreach Strategy | |||||||||
---|---|---|---|---|---|---|---|---|---|
Outreach Goals: | The Commercial and Business Users' Constituency [also known as the ICANN GNSO Business Constituency (BC)] FY23 Outreach Strategy seeks to fulfill the BC’s mission [1] as described in the BC’s approved Charter. The BC Outreach goals support the engagement of business users in gTLD policy development and in ICANN’s overall governance. The BC Outreach Strategy aligns with ICANN strategic objectives, and includes collaborative efforts between the BC and ICANN’s Engagement teams and ICANN org, effective use of CROP funds, as well as activities that are funded from the BC’s membership fees. | ||||||||
Strategies: | The BC’s Outreach Strategy is focused on growing the BC visibility and engagement in ICANN meetings and in selected and related events where business executives and others from the business user communities participate, as well as engaging with other stakeholders who may influence ICANN’s stability. The BC Outreach strategy is described in this document, with specific reference on the use of ICANN’s Community Regional Outreach Program (CROP) funds, and other special funds [some of which are not only supported by ICANN funding], including BC’s membership funds to increase the engagement of business user companies and business associations and to support the broader BC Outreach Strategy. The BC Outreach Strategy aims to: CROP FY23 Activities: The BC Outreach activities will draw on ICANN FY23 CROP travel support for three travellers as defined in the ICANN CROP, overseen by the BC Vice-Chair Finance and Operations and approved by the BC ExCom [and consistent with CROP guidelines] and in keeping with the BC’s regional and other focus priorities. CROP events will benefit from full support from the BC membership in the meeting region. BC members are encouraged to submit proposals for events at a national or sub regional/regional level where the BC can broaden awareness of the BC’s mission, and recruit new members. For FY23, the BC’s Vice-Chair for Finance and Operations has encouraged early submission of ideas for the full fiscal year. Proposals are preferred for external events but are also welcomed for maximizing outreach support during ICANN meetings. Reports are required, and those funded then write an article about their event/participation activities for the BC Newsletter. BC Leadership Program seeks to ssponsor business executives by ICANN and BC Funding to each public meeting of the BC. Key objectives of the BC overall: Reporting: All BC funded travellers attending or organizing an outreach event are required to provide a detailed report on the event. Enhanced visibility of BC’s Outreach engagement are promoted via the BC Newsletter whenever required. Those funded by CROP and BC funds are required to submit reports, and encouraged to draft an article for the BC newsletter, and potentially, for their own community’s newsletter or website upon their return from their participation. Previous BC Newsletters are available on www.icannbc.org/newsletter COMMUNITY REGIONAL OUTREACH PROGRAM (CROP) – THE BC’S USE OF CROP FUNDS CROP funds will support travelers to events that are primarily focused on companies/associations that fit the definition of Business Users. The BC presence and participation at events will be further reinforced by materials and presentations developed for BC outreach. All materials will reflect the BC official policy positions, in discussions about ICANN policy topics/or other governance topics. Normally, CROP will primarily support the engagement in or be associated with external to ICANN events where business users can be easily reached, rather than creating unique events, in order to avoid additional organizing costs, other than those that CROP covers. On some occasions, CROP will support bringing members from the region of the ICANN meeting who can support the outreach efforts during the ICANN meeting. The BC Executive Committee will evaluate/approve funding requests from BC members to attend an event, and specifically evaluate the effectiveness of the use of CROP funds to augment BC funding participation. Such BC expenditures may include printing of brochures or fact sheets for use, which will not be covered by CROP. Responsibility for making recommendations for use of funding lies with the BC Outreach Committee, with budgetary review by the BC Financial Committee and final approval resting with the BC ExCom. Selected events might require sponsorship or registration fees. Ultimately, approval is also required by the ICANN staff and support from the regional VPs/business VP of ICANN. For CROP and other BC supported funding, priority for funding will be given to BC experienced members who have a speaking role at an approved event, where the speaker has the ability to directly promote the work of the BC (versus speaking on another topic). Where a unique relationship exists between a BC member and an organization [including ICANN regional teams] organizing an outside event that has high visibility within a region/sub-region with low BC membership, CROP can be considered to bring a BC member as a special “recruiter”. Given the limited funding from CROP, priority will be given to proposals that are well documented regarding high opportunity for new BC member(s) and enhancing ICANN visibility over the longer term. As an exception and due to the limitations of CROP funding for FY23, CROP funding could be used to support participation and the active engagement of a BC member who could not otherwise attend an ICANN meeting or another major ICANN-related event where a BC Outreach event is organized, and a particular BC member brings unique contacts in that region. In these cases, the member’s engagement must augment the legitimacy of the BC’s role and effectiveness of BC outreach within that region. This would be an exception and would be assessed on a case-by-case basis, looking at the needs of the BC and the parameters of the CROP program. Documentation: A written proposal, and documented plans are required for consideration of CROP, as well as any BC funding for Outreach and Awareness/Recruitment. A written report that assesses the effectiveness of a particular event, direct and indirect outcomes is required. | ||||||||
Expected Activities and Outcomes: | Outcomes: Through our outreach efforts, the BC expects to: Goals: | ||||||||
Other Details: |
| ||||||||
Date Submitted: | 12-Mar-2023 |
Note: To be completed by a Program Coordinator (PC) designated by this organization/structure.
Acknowledgements | Confirmed? | Who Confirmed? | Date of Confirmation | Notes |
---|---|---|---|---|
The detailed Outreach Strategic Plan has been properly completed per CROP requirements. | Yes | Ozan Sahin | 16-Mar-2023 |
|
The ICANN Organization / Structure's leadership has authorized this Outreach Strategic Plan. | Yes | BC Vice Chair of Finance, Lawrence Olawale-Roberts | 12-Mar-2023 | Confirmation email sent to bc-excomm@icann.org mailing list on 12 March 2023. |
The Outreach Strategic Plan has been concurred by the Stakeholder Engagement V.P. | Yes | Ozan Sahin | 29-Mar-2023 |
|
=============== | =========== | ============================== |
CROP Outreach Strategic Plan Template (June 2018)