- Event management
- Volunteer matching or "brokering"
- Skill building
- "Go Veg" has a table at a festival which they hope to use to distribute pro-vegetarian literature. From 10am to 1pm, they need one staffer and two volunteers at the table; from 1pm to 4pm, when traffic is heavier, they need one staffer and four volunteers at the table.
- "Go Veg" needs four volunteers in the office each Tuesday from 4pm to 6pm to stuff envelopes.
- "Help Now" operates a hotline on the weekends and needs volunteers to answer calls and serve as receptionist.
Volunteer Matching or "Brokering"
This sounds interesting. The use-cases I hear about most frequently are is situations where there are a lot of "tasks" that need one or more people to fill each task time slot. Typically these are not connected to any event. Such as the organizer needs:
5 people at 8am to prepare food
3 people at 10:30 to pack boxes of meals/supplies
10 people who can drive, make deliveries of food/supplies to various destinations
So the organizer needs a really simple way to set up all the "tasks/needs" at the various times/locations. I think ease of use/setup needs to be paramount, as the organizer is often NOT a regular user of CiviCRM, and just needs to get their setup of the tasks done very quickly, without needing to be trained in the intricacies of the system.
Then the people who may be interested in helping need a simple way to see all the options available, and indicate which tasks they want to do.
An example of a website that is handles this kind of use case nicely is at: http://www.volunteerspot.com
Thanks for sharing this service. I've poked around it a bit and will take a closer look at its strengths and shortcomings to make sure we incorporate and leave them out, respectively. The wizard does a pretty good job of hand-holding, which I think is an important part of what we're trying to do with CiviVolunteer. A lot of the functionality for volunteer management is already in core, but the CiviCRM admin screens can be a little daunting to newcomers -- one CiviVolunteer's primary concerns is to package the pieces in such a way that results in a centralized, easy-to-use interface.
Have you looked at Crew Connect? http://drupal.org/project/om_crew_connect
While this currently isn't tied to CiviCRM, most of the groups already using it are building on http://drupal.org/project/cm_starterkit_moderate which includes the same version of CiviCRM included in http://drupal.org/project/civicrm_starterkit.
Crew Connect is basically a collection of Profile 2 fields, Views, and some JQuery that turns multiselect form fields into sliders making it much easier to search for a person who's rated themelves or been rated a 3 or higher in a specific skill. The functionality in Crew Connect is largely Views driven. The default filter for including a user in a volunteer search is a single checkbox for users to volunteer, but using fields and views you can easily customize this for a variety of use cases.
Views Send allows users with the approporiate permission to contact each other directly.
We've already discussed tracking the emails exchanged as CiviCRM Activites. The skill ratings could also be done as CiviCRM profile fields, but I'd push for the type of syncronization we do w/ http://drupal.org/project/civicrm_multiday_event over only storing the data in CiviCRM.
Here in England GMCVO & Circle Interactive are talking to YouthNet who run the national volunteering website and supply volunteer brokerage software to all the local volunteer centres. A number of the volunteer centres already run CiviCRM alongside the software supplied by YouthNet and the addition of a brokerage module to CiviCRM would mean they could then run all their work through CiviCRM only.
Currently we are in inital discussions and looking for a partnership agreement. If we can get the agreement we will then start to put together a project plan, speak to other people who are interested / blog our progress.
A good use case for us is with teams for activities specifically Peer Review. Where people fill out qualifications sheet (check list and open-ended statements) and then are teamed up/ paired together based on skillset and previous work completed. They are also broken down into distance the reviewer is to the reviewee in hopes of controlling/mitigating travel related expenses/issues. We have traditionally done this manually but see this module and the Case module overlapping to provide the solution we need. Just some prelim thoughts about our use.
Your scenario aligns more or less with our "Skill Building" use case, I think.
In some version of CiviVolunteer -- it's unclear to us at this point whether this feature should be considered a requirement for a viable release -- we'd like to tie roles to requirements or qualifications. When defining a role for an event or volunteer activity, the admin could optionally identify requirements (e.g., in order to serve as a lifeguard, a volunteer must be CPR certified). Only contacts who meet the requirements could be assigned to (or sign up for) that role.
Additionally, the admin would be presented with a list of candidates for a shift. This list would be generated in a way not unlike the "Advanced Search" in core, taking into account the skillset or qualifications required by the role. To meet your use case better, you could alter the search criteria to filter based on geography as well.
Thank you for your feedback. Please continue to follow our posts on the CiviCRM blog and continue to weigh in!
One of the most important features for my organization is the ability to track the number of volunteer hours an individual has contributed. We use the total number of hours to demonstrate part of our value as an organization. In addition, we award volunteers with certain benefits at various milestones (100 hours, 250 hours, 1000 hours, etc.).
Individual volunteers should be able to record their own hours contributed and certain admins should be able to enter hours by event for other individuals. For example, a regular volunteer would enter their hours each week. Whereas, for a large volunteer day, one person should be able to enter volunteer hours for a large number of contacts at once.
Referencing the "tree" scenario above:
Any thoughts about integration with CiviCase to handle that workflow mentioned within the Skill Building scope. Such that case workflow might flag the person who has taken the quiz or maybe has been assigned to a leader for first two plantings and the leader can then record that for each planting. So that when all assigned activities are completed that the person can then register as a particular volunteer type?
I really tried to adapt this concept from my own thoughts about peer review use case that I have, where it is almost a hybrid between this and CiviCase, due to the fact that people submit all sorts of paperwork along the way and leaders clear others to lead and/or new skills they have acquired along with recording of the "event" (a peer review) and the participants "reviewers".
Just some mroe thoughts on this.