Chained Check-in's as task lists for volunteers helping post-disaster

[Erioldoesdesign]

Please describe the problem.

When there are typhoons/hurricanes in Taiwan, the farms receive help from various volunteers that can be difficult for NGO's managing the volunteer to manage due to various factors like:

• Not knowing what the volunteer is skilled in doing (e.g. Can they operate large machinery)
• Not knowing how long they will volunteer for.
• Not knowing whether the critical work on the farm is completed and the volunteers are ready to move on.
• Not knowing whether the farm has more needs that are less critical than other farms and they have asked volunteers to stay to help on non-critical issues.

Linked to issue #140 'Chained Check-Ins'

Who are we designing for?

We are designing for at least two user groups primarily after a disaster

1 -NGO Leads or people managing a TenFour organization. Otherwise referred to as an 'admin'
Typically have the role types of Owner and Admin in TenFour. The owner of the TenFour organization could be the farm owner. These users program, manage and send out the check-ins/tasks

2 - The volunteers or TenFour check-in responders that are receiving check-ins/tasks to complete who need to be able to respond clearly and update information easily when asked via check-in.

Describe what the user needs to do

As an admin/NGO lead of a TenFour organization I want to:

1. Be able to send a check-in (or know via the location of that volunteer) when a volunteer/field worker arrives at a specific location to support a disaster/crisis.

2. I want to then be able to 'program' or 'pre-populate' a series of check-ins that operate like 'task list' for that individual and/or group of individuals.

3. After the program of check-ins is completed by the individuals/group of volunteers I want to send a check-in that does not require a response on where each individual volunteer should re-locate to next.

e.g.
Check-in = 'Have you arrived at Shuai's organic farm in Yilan?'
Check-in answer options = 'Yes' 'No' 'I'm on my way' 'I cannot make it'
Answer = Yes

Check-in = 'Your first task is to report to the farm HQ'
Check-in answer options = (no response required)

Check-in = 'Have you reported to farm HQ?'
Check-in answer options = 'Yes' 'No' 'I cannot find HQ'
Answer = Yes

Check-in = 'Please complete x task and check-in when finished'
Check-in answer options ='I'm finished' 'I will not complete this today' 'I need support'
(time elapses)

Answer = I'm finished

The system could be programmed with a number of tasks until the volunteer is 'discharged' and returns under the care of themselves and is no longer the responsibility of the TenFour organization managing volunteers.

A way of indicating a task is complete and how to review those are useful for the admin of TenFour Organisation.

A way of 'downloading' or 'saving' the work status for that farm for a day so it can be added to a report.

Describe alternatives you've considered

This could be done by a series of templated or scheduled check-ins but we want the system to be intelligent enough to follow a programmed sequence of check-ins and tasks.

What is success for our user

• The NGO admin can clearly see which volunteers have complete what tasks/check-ins.

• The NGO can share that information with farmers/government/document that time period easily.

• The NGO's are not overwhelmed by communications and responses for large groups are still visually simple and easy to understand.

• Critical information that changes a situation is prioritised.

• Volunteers can easily and quickly update and edit responses/information when replying to check-in or completing a task.

What are our design constraints?

Requires:
Mobile telecom connection or internet connection.
Uses/already logged onto a TenFour org
On the TenFour system as a ‘person’.