You are a senior MEAL specialist designing the data flow diagram and accompanying narrative for the MEL plan of "program name" (from the material, if given).
The diagram must make explicit who collects what, where it lives, how it moves, and who acts on it.
Requirements:
- Entities and roles. Identify the actors in the data flow (e.g., "actors" (from the material, if given)).
- Capture stages. Describe each capture stage: point of contact (e.g., service delivery, household survey), tool (paper form, mobile app, registry), and responsible role.
- Aggregation stages. Describe how raw records are aggregated up the chain (site, partner, region, national) and where the system of record sits for each indicator.
- Validation and quality. Show where validation steps occur (auto-checks at entry, supervisor review, monthly DQA, "quality step" (from the material, if given)).
- Storage and access. Identify the platform for each stage (e.g., paper file, Excel, KoBo, DHIS2, partner system) and access permissions.
- Use points. Indicate where data is reviewed and used (program meetings, quarterly reviews, donor reports), tying use back to specific roles.
Output Format:
Produce:
- A 1-paragraph framing.
- A structured description of the diagram, organized as nodes (capture, aggregation, storage, use) and arrows (data movement), so the diagram can be rendered visually.
- A roles and tools table (role, tool, action, frequency).
- A short narrative explaining how the diagram ensures end-to-end data integrity.
- A list of key risks (data loss, version conflict, delayed transmission) and mitigations.
Quality bar: The result must meet these criteria. It will be reviewed against them afterwards.
- Completeness of Flow: Whether the diagram covers the full path from data source to decision-maker, including every collection, entry, storage, analysis, and reporting step in between.
- Role Assignment Clarity: Whether responsible positions are named at every transition point, so it is clear who owns the data at each step and who hands it off to whom.
- System Specification: Whether the tools and platforms used (specific forms, databases, dashboards, file shares) are named at every storage and transfer point, not described in generic terms.
- Quality Gates and Verification: Whether validation, cleaning, and review steps are explicit in the flow, with named checks placed before data is used for analysis or reporting.
- Feasibility and Context Fit: Whether the flow is realistic given the program staffing, field connectivity, device availability, and reporting cycles described elsewhere in the MEL plan.
Where the material is silent, write "Not in the material" rather than guessing.
Source material: Attached, or pasted below. Base everything above on it and do not invent details that are not in it.