Overview
In order to make OCHA, clusters and partners’ Information Management activities predictable and to reduce the amount of ad-hoc requests, OCHA or the IMWG can setup a standard IM reporting and product cycle. By using this approach, clusters are given space to do their work between reporting periods and to be predictable with their cluster members (as they define a reporting cycle for their members). Having a calendar will also make the output predictable for management and clients. The tools and examples below show the 3W reporting cycle used in the Philippines Haiyan Response 2013/14 at weeks one and five.
Given that there may be a geographical spread of the emergency and thus multiple coordination hubs, an IM data flow should be agreed upon early in the emergency. In order to provide clarity, it should be proactively decided (with the clusters) that the field clusters are responsible for collecting their own local data, sharing it with their clusters at national level to compile, and then share the data with OCHA. With this approach, products can be generated anywhere along the chain of data movement. The Data Flow tool is a visual depiction of the setup in the Philippines Haiyan Response 2013/14. Adapt this graphic for your context.
Of course, we know that OCHA will continue to receive data from partners who visit our offices, people who attend meetings, and by email. The agreed approach with the clusters should be that OCHA would happily accept this data with clear messaging that we will pass it along to the cluster (at the respective level) for incorporation into their 3W data. In this arrangement, OCHA becomes an extra conduit of information for the clusters.
Text should include: Overview, purpose, when it happens in the the HPC or IM cycle
Process
Text should include: Step by Step, Checklist, SOPs, Tips
Outputs/Resources
Text should include: Essential Reading, Additional Readings, Templates. Examples, Tutorials
Guidance
- text
- text
- text