# data[].attributes.body
The current format of the volunteer sensitisation, though making sense, is a little too much information for the volunteers.
Also the facilitators for these smaller components needs to be better prepared.
-Millesh

# data[].attributes.body
Induction after 3-4 weeks doesn't make sense. Its purpose is lost. How to deliver we can think about it but finish mandatory induction related stuff in 1-2 weeks of vol being recruited

# data[].attributes.body
Utilize ZHs for onboarding by involving the city team, the continuing volunteers and the new volunteers (who are a few weeks into the system) in welcoming and inspiring  the newly un-inducted volunteers. @SO team, something to think about maybe?
-Lavanya

# data[].attributes.body
Conducting Induction & Onboarding along with CPP signing  within 2 weeks post recruitment and encouraging class visits only if they have been onboarded in the respective role.

# data[].attributes.headline
Use the ACT evaluation Sheet for Designing the sessions 

# data[].attributes.subject
Use the ACT evaluation Sheet for Designing the sessions 

# data[].attributes.body
For skills that they wanted/learned & obstacles they faced. Would be great if each vertical can be given a list of skills that their volunteers thought would have been good to have for designing the training session - Anne :)

# data[].attributes.body
A lot of volunteer that I spoke about did not have clarity of different roles - Mentor/Fellow/Strat. Which meant volunteers miss out on potential people to reach out for help.
-Millesh

# data[].attributes.body
The manner of first vertical training was not effective. Relook at how this can be more effective.
_Millesh

# data[].attributes.body
Onground induction. This stays with volunteers as it’s the first interaction they have

# data[].attributes.body
Divide onboarding into
1. Mandatory pre session (even if its only couple of hrs)
2. On job onboarding and training

Hold the first bit strongly and ensuring folks don't start classes without that

# data[].attributes.body
Too many gateways before first class. Can the design be more integrated into the first class

# data[].attributes.body
Self learn and CFU after recruitment and immediately before first class or mid way

# data[].attributes.body
CPP signing can happen just before every class. Needn’t on,y happen at the Induction. Would be good to redesign when sensitisation occurs and how - a lot of volunteers did not the escalation model or what’s right and wrong
- Sarika

# data[].attributes.headline
Keeping some parts as self-learn for onboarding

# data[].attributes.subject
Keeping some parts as self-learn for onboarding

# data[].attributes.body
Better data tracking and usage of tools.
(It was difficult to get data and using sheets was not easy.)

# data[].attributes.body
Keep the shelter visit before induction as volunteers show more involvement.

# data[].attributes.body
I am adding this as a question for the design team to think about if we should keep induction as an important gateway before entering the classes our not
- Yashashri

# data[].attributes.headline
Keeping onboarding attendance mandatory before the first class for Academic support volunteers

# data[].attributes.subject
Keeping onboarding attendance mandatory before the first class for Academic support volunteers

# data[].attributes.body
It did not add the value or the connect that was intended and having it every month online again did not work out as well as expected.

Recommendations:
1. Conduct on-ground inductions as and when the FTEs / strats visit the city, which anyway happens once a month or once every 6 weeks.
2. Combine the inspire bit with CC and have an induction along with that (Needs more design)
- Lavanya

# data[].attributes.body
Our culture that we have org wide (things like standing in circles, finger snapping, and other tiny things) should be something that needs to be passed on to the new set of people during the onboarding - Anne :)