Cluster Reporting cycle and information flows
- FIS
- FIS
- Manon Colas
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 should set up 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.
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 the 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.
OCHA may still receive data from partners who visit their offices, people who attend meetings, and by email. The agreed approach with the clusters should be that OCHA accepts this data with clear messaging that it 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.
Process
Examples of 3W reporting cycle:
3W reporting cycle week one Philippines Haiyan response 2013/14
3W reporting cycle week five Philippines Haiyan response 2013/14
Example of visual depiction of the setup of data flows:
Example of information flows with clusters:
Example of product calendar:
Add examples of charts of information flows or IMWG info schedules/work plans
Outputs/Resources
All public output generated by the clusters and OCHA will be available on respective operation pages on https://www.humanitarianresponse.info/