reporting needs 01/11/2010 – revinge training acaps/natf
TRANSCRIPT
REPORTING NEEDS
01/11/2010 – Revinge Training ACAPS/NATF
Process• Start with the ‘Who’:
• Identification of end user’s (HCT, Cluster leads, Government, NGO, HC/RC, Donors, etc..)
• Move to the ‘What’: •Decision making and information needs (Qualitative and Quantitative)•Analysis plan
• Finally, consider the ‘How’:• Final product: Assessment report, Sitrep, dashboard, Flash appeals,
etc…
•Build a reporting strategy:•Reporting timeline•Target audiences
Common reporting timelineReporting Flow - Sudden onset disaster
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 1 2 3 4 5 6 7
Disaster
Sitrep #1 - 13
Reporting needs
Reporting Needs - Sudden onset disaster
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 1 2 3 4 5 6 7
Disaster
Sitrep #1 - 13
Preliminaryscenario definition
MRA report In depth sectoral report
Main Coordinated assessment products
•Preliminary Scenario Definition•Multi cluster Rapid Assessment report•Appeal (IFA/RFA, CERF)•Sitrep•Key messages(HC/RC, ERC)•Dashboard•Response and operational plan•Assessment findings summary
Assessment report• Briefly explain methodology and constraints• Report should be thorough but concise. Ideally, it should not exceed 30 to 40 pages (additional details in ) annexes).• The executive summary should be no longer than four pages.• The sections of the report should be interlinked, the analytical process must be evident.• Findings and conclusions should be illustrated by tables, graphs, and maps, when relevant• Cross cutting issues should be mainstreamed into the sectoral analysis as well as pre-disaster information
Issues...•Manage expectations vs. be responsive to the information needs•Be clear on final product and what information will or will not be included (HoO, IM, Clusters, etc..)• Consider timeframe for results communication. How to share early results when the pressure is to prepare the report•Raw data•Preliminary findings•Draft report•Final report
• Consider data expiration date....• Consider data volume (graphs/page)•Who does the report represent, who owns the report
Template 1/2•Acknowledgment•List of annexes•Acronyms•Introduction•Executive summary
•Key findings•Most affected areas and groups•Assessment key recommendations and priorities•Information gaps and needs
• MRA Background and objectives•Purpose and scope of the assessment•Objectives•Methodology•Sampling•Limitations•Data access
Template 2/2• Needs analysis:
Information Analysed by:
1. Affected area(s)
Most affected areasKey issues (priorities)
Information gaps and needs
Number and type of affected areas (rural,
urban, coastal, montaneous)
Effects on affected areas (crops , infrastructure
damage,..)
N of afffected pop &Type of affected groups
in the affected area
Sectoral needs & risksper affected area
2.Affected group(s)
Most affected groupsKey issues (priorities)
Information gaps and needs
Number and type of affected groups (IDPs, returnees, residents,
etc..)
Impact on affected group ("affected"
definition and classification)
Localisation of affected groups
Sectoral needs & risks per affected group
3.Affected sector(s)
Most affected sectorkey issues (priorities)
Information gaps and needs
Number & type of affected sectors (WASH, LFS, Health, Shelter, ..)
Effects and impact on affected sectors (human
and infrastructure)
N of afffected pop, sectoral needs & risks
per affected areas
N of afffected pop , Sectoral needs & risks
per affected groups
Remember
•Use your analysis plan for designing the structure of your final report, adapt according to end user’s feedback
•Let also the data speak to you...