Disaster tech support for NGOs
Jump to navigation Jump to search
Revision as of 00:53, 21 November 2017 by Josh (Created page with "=Scenario:= * Earthquake, subsequent tsunami. * 5-10% of nonprofit org buildings collapse. * Computer/technology/platform are down. * Time period of 2nd day post crisis eve...")
- Earthquake, subsequent tsunami.
- 5-10% of nonprofit org buildings collapse.
- Computer/technology/platform are down.
- Time period of 2nd day post crisis event through several weeks of recovery.
- Not focused on preparation for orgs, instead focused on those who are not prepared.
- Mobilizing those inclined and qualified to help.
Needs for Success
- Must work in low-bandwidth.
- Must have non-internet or computer based resources (ex: laminated guides, etc).
- Triage process that works for volunteer lay-people, non-technical to evaluate most urgent cases.
- OUTBOUND: who needs help
- OUTBOUND: who can help
- incoming requests for aid
- incoming offers to help
- go through triage (below)
Triage Questions: Prioritization of Need
(Automate triage questions if possible, Twillio, etc, have option to talk to people)
- Will lives be threatened if technology is not restored?
- Power out? Internet out?
- Damaged equipment? Type, how many, etc.
- Building damaged/flooded/no access? Do you need to relocate?
- Do you have other resources that can help you?
- Are you the person normally in charge of this?
- Is there an IT person?
- Are they okay, can help?
- Can you get in touch with them to assess your needs?
- This could be routed through tech industry orgs, building out their own versions of a disaster response program set up in advance of a crisis, and deploy technical employees to respond.
- There are issues of liability, HIPAA data, etc.
- Ticket systems for assigning people are needed in order to avoid duplication of efforts, appropriately escalate, indicate resolution.
- Leverage existing frameworks and tools to achieve goals: A reworking of Facebook’s “I’m Safe feature, Google’s disaster/crisis maps, etc).