# data[].attributes.body
CE and Devo reviews the rubric

CE and Devo are the first to talk to corporate partner

From rubric reach out to recruit volunteers

Tier 1 - 3 months before the event

Tier 2 - 2 months before the event

Tier 3 - 6 months before the event

Tier 4 - 1 month before event (+ previous volunteers)

Send out catalogue with opportunities that direct them to website to see dates and opportunities; also connect with VE rep to start process

# data[].attributes.body
Evaluate impact of volunteers on student journey via student/staff feedback

Regularly analyze and report out on volunteer satisfaction and feedback given via volunteer surveys

# data[].attributes.body
Provide volunteers with a single point of contact for questions/concerns leading up to event (who?), provide clear instructions on how they can self-change/cancel their registration in HOC if needed

# data[].attributes.body
Important to communicate clear deadlines for tiered partners so they know when their spots will be released, if not filled

# data[].attributes.body
Pre-work: watch volunteer orientation video in HOC; gives overview of YU, the mission and the impact of volunteers for young adults
-review YU volunteer handbook in HOC and acknowledge any policies/photo releases, etc.

# data[].attributes.body
Relationship holder passes corporate partner on to VET to get them prepared for volunteer registration

# data[].attributes.body
CE/Devo relationship holders reach out to corporate partners by Tier to gauge interest in volunteering. Share mission-focused materials about volunteer opportunities at YU (flyer?)

# data[].attributes.body
In virtual event, Ops manages Zoom logistics

# data[].attributes.body
Important to illustrate impact in these reports in addition to numbers

# data[].attributes.body
Does HOC require the user to create an account (username/password) before signing up for an opportunity?

# data[].attributes.body
Partner receives data report on who and how many attended event

# data[].attributes.body
CE can review attendees and see if any HNW or OS members attended. Wonder if we can star people??? Ask HOC.

# data[].attributes.body
volunteer reminder email sent 48 hours prior to event (automatic through HOC)

# data[].attributes.headline
Streamline public transportation, directions, and parking information. 

# data[].attributes.subject
Streamline public transportation, directions, and parking information. 

# data[].attributes.body
It would be helpful to share public transportation, directions, and parking information for each site. So volunteers can plan for parking/travel time.

# data[].attributes.body
CE can review attendees and see if there are any individuals they would like to target (e.g. Redwood Logistics)

# data[].attributes.body
When to arrive - what to expect when they arrive

# data[].attributes.body
thank you email to volunteers includes feedback survey link, photos from event, social media graphic?

# data[].attributes.body
required trainings and pre-work -
role in programming
DEIB

# data[].attributes.body
Devo has access to volunteers and can start the cultivation process

# data[].attributes.body
Volunteers attend training (2 weeks prior to event); training goes over event-specific run of show, guidance/expectations; training is recorded and shared with all volunteers afterwards

# data[].attributes.body
VE and Site Contact verify attendance data in SF before thank you note

# data[].attributes.headline
Streamline orientation and volunteer engagement.

# data[].attributes.subject
Streamline orientation and volunteer engagement.

# data[].attributes.body
Create a standard orientation for volunteers to learn more about YU and site specific details (i.e. what model they are, when the site open etc.). It helps with retention and helps describe the impact volunteers have on our young adults.

# data[].attributes.body
standard confirmation goes to volunteer that has signed up with a concise list of next steps, action items and what to expect (list of comms to expect, training and day of expectations)

# data[].attributes.body
VET sends, Thank you for volunteering with us! Here are other ways to continue involvement.

# data[].attributes.body
Devo hears from partner, we want to volunteer!

CE hears from current or prospective partner, interested in Year Up can we see what's it's about? CE suggests volunteering.

# data[].attributes.headline
Create trainings that are helpful to the each staff members needs

# data[].attributes.subject
Create trainings that are helpful to the each staff members needs

# data[].attributes.body
Create staff training that is helpful for folks to navigate the features they need. So that HOC is helpful and not just another app to use.

# data[].attributes.body
Partner or Individual reviews opportunities (shares with employees if applicable) and sign up for chosen opportunities

# data[].attributes.body
Prospective volunteer goes to YU website and clicks on HOC landing page. Can search for open opportunities by location. Will there be opportunities open for them to see during windows where we are offering to priority partners or after priority partners register? What happens if this volunteer works for a priority partner?

# data[].attributes.body
Corporate Partner is interested in having employees volunteer as part of employee engagement efforts. Informs their CE or Devo Partner.

# data[].attributes.body
VE rep sets up company access (based on tier) and shares access to HOC with Partner Rep. or employee base - how does this change for Individuals

# data[].attributes.headline
Improve descriptions and photos for volunteer page.

# data[].attributes.subject
Improve descriptions and photos for volunteer page.

# data[].attributes.body
List better descriptions of volunteer opportunities and photos or videos to match. So volunteers have a better understanding of what we do, how we do it, and why.

# data[].attributes.body
Volunteer is inspired after hearing Gerald talk or some other intro to YU. Thinks, "I want to volunteer with Year Up." Goes to website.

Note: Devo directs IG to website to sign-up.

# data[].attributes.body
YU Staff vets and approves volunteer in HOC or are they auto-approved upon signing up for an opportunity?

# data[].attributes.body
Event Lead - Prepares students for the event

# data[].attributes.body
Program Lead of the event gives overview of the event and what they'll be doing.

# data[].attributes.body
Ops checks them in at the digital kiosk

# data[].attributes.body
Relationship holder gauges interest and connects to VE rep when interested.

# data[].attributes.body
Ops welcomes them to the site