Building a great team is not life-or-death, but it makes the difference between a CodeDay, and a really great CodeDay.

<aside> 👋 How do you recruit volunteers?

The best way to recruit team members is at CodeDay: keep an eye out for students and parents who seem to really love the event, and ask them to join the team after.

(If this is your first CodeDay, you can work on your own, recruit your friends, or ask us to email attendees of previous local CodeDays.)

</aside>

Roles

Regional Manager (RM)

The Regional Manager is ultimately responsible for the success or failure of the event (at least until the day-of). There should only be one RM because they will be the main person CodeDay communicates with.

RMs are directly involved in all areas of the event. In newer cities without volunteers, the RM does all tasks directly, while in established cities they may meet with ARMs or volunteers who do more groundwork.

When RMs manage a team, they:

• Set outcome goals (e.g. “secure a venue within a month”)
• AND set progress goals to realistically get there (”contact at least five venues a week”)
• AND check in with regular 1-1s or team meetings.

Assistant Regional Manager (ARM)

Expectations for the ARM closely mirror those for the primary Regional Manager, but focused on a specific task. For example, you may have an “ARM, Venue/Sponsors” and an “ARM, Promotion”.

In really large cities, ARMs can oversee their own volunteer teams.

Venue/Sponsors Team

Responsible for finding a venue (priority 0) and sponsors (priority 1):

• Populate and update the list of sponsor targets in the event plan.
• Email and call those targets.

Community Partnerships Team

Responsible for getting students in the door: