You are a senior MEAL specialist designing an end-to-end monitoring system for "program name" (from the material, if given) operating across "scale" (from the material, if given).
The system must connect data capture to data use, not just data storage.
Requirements:
- Scope and indicators. Define what is being monitored (outputs, intermediate outcomes, process/quality indicators). Tie each to a level in the results framework.
- Data capture. Specify capture tools and points (e.g., service register, mobile form, partner monthly report, the attached or pasted document). Define who captures what, when, and how.
- Data flow. Describe how data moves from capture to aggregation to analysis (frequency, format, responsible roles). Identify the storage location of the source of truth for each indicator.
- Data quality. Build in routine data quality checks (e.g., "DQA step" (from the material, if given)) and validation rules at the point of capture.
- Analysis and review. Specify the regular analysis products (e.g., monthly dashboard, quarterly report) and the meetings or routines where they are reviewed.
- Use. Connect each analysis product to a specific decision or action. Avoid building reports nobody uses.
- Roles and capacity. List the roles (data clerk, MEL officer, program manager) with time allocations and required skills. Identify capacity gaps.
Output Format:
Produce:
- A 1-paragraph framing.
- A system overview describing the major components and how they connect.
- A monitoring matrix: indicator, capture method, capture point, frequency, aggregation, analysis, review forum, decision use.
- A roles and responsibilities matrix.
- A short risks and mitigations section (data quality, partner reporting reliability, system underuse).
Quality bar: The result must meet these criteria. It will be reviewed against them afterwards.
- Indicator Coverage & Quality: Whether the plan includes SMART indicators at each results level that directly measure stated outcomes, with targets and disaggregation.
- Data Collection Systems: Whether collection tools, methods, frequency, and responsible parties are specified per indicator - not just listed in the logframe.
- Data Quality Assurance: Whether the plan addresses validity, reliability, and verification - including how data quality will be checked before it is used.
- Roles & Responsibilities: Whether data ownership, collection responsibilities, analysis roles, and reporting lines are assigned to named positions.
- Learning & Adaptive Management: Whether the plan includes mechanisms for using data to inform decisions - including review cycles, feedback loops, and who acts on findings.
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.