-
Notifications
You must be signed in to change notification settings - Fork 156
Checkin Checkout Workflow
Bill Wagner edited this page Feb 27, 2015
·
1 revision
The Checkin / Checkout process for a volunteer can go through a few states.
The 'success' path for an onsite volunteer would follow this workflow:
- A cluster coordinator would request volunteers for a site.
- Volunteer creates a commitment on the site, and schedules travel.
- Once onsite, the volunteer 'checks in', changing her status to onsite.
- When the volunteer leaves, she 'checks out', indicating that her commitment is done.
There are two other volunteer states that need to be managed in the software as well:
Delayed: This state represents a volunteer that was scheduled to be on site, but has been delayed. This might be flight delays, or problems with customs and equipment, or visa issues.
Unavailable: This state represents a volunteer that is on site, but unavailable. Examples might be a surgeon with an open laceration, quarantine, or just some much needed rest.
The offsite volunteer path is more simple, but remember that a remote volunteer may be in a different timezone than the disaster site:
- A cluster coordinator would request volunteers for the site.
- Volunteer creates commitment on the site.
- Each day, the volunteer checks in at the beginning of work.
- Each day, the volunteer checks out at the end of the work day.