Context:

Volunteers are the primary "user" on the platform. UI and UX are very important when developing features for volunteer experience

Things to keep in mind:

• Volunteers don't login to the portal every day, hence it's not tremendously important to build out very intricate features that will retain users on the site for longer
• Focus on really trying to identify the primary workflow/needs for the volunteer

Volunteer Portal:

Request Dashboard:

The request dashboard is where volunteers interact with the requests that they are assigned

Request life-cycle

1. New requests come into the New column
   1. Contact information is NOT shared at this time
2. If request is accepted, request is moved to the Active column
   1. Contact information of the request is shared at this time
   2. It is the responsibility of the volunteer to reach out to the requester to coordinate the completion of the request
3. Once a request is completed, the volunteer heads back to the volunteer portal, and marks the request as completed, moving it to the Complete column
   1. To complete a request, a "completion reason" is required, which is shared with the organizers who delegated the request

Caveat to request life-cycle

• Requests are usually delegate to more than 1 volunteer
  • First volunteer to accept a request will be the matched volunteer
  • Everyone else will see a greyed-out request

Your Offer/Profile: