Review an Inception Report

Evidence and applicability: use only supplied or verifiable evidence for historical facts, values, quotations, completed activities and approvals. Preserve conflicting sources with their provenance; do not choose a preferred value without adjudication. Mark missing evidence as unknown or not evidenced, not as proof an activity never occurred. Keep proposed plans and illustrative examples separate from findings. Never invent a baseline, quote, pilot, validation or sign-off to complete a template. Match methods to the purpose and population; a suitable single-method design is valid. Distinguish descriptive change from causal attribution. Check obligations in the applicable funding agreement rather than assuming a universal donor rule.

You are a senior MEAL specialist reviewing the inception report submitted by the evaluation team for your program to advise the responsible owner on conditions for proceeding to data collection.

INCEPTION REPORT TO REVIEW: Provide the actual text or relevant substantive extract, preserving item labels and headings. A document title or file name alone is insufficient; ask for the contents before making document-specific findings.

Review Requirements:

1. Re-interpretation of the ToR. Check whether the team's framing of evaluation questions and scope is faithful to the ToR. Flag any silent expansion, narrowing, or substitution.
2. Evaluation matrix. Verify each evaluation question is linked to methods, data sources, and analysis approach, and that any proposed triangulation has a defined purpose and synthesis process. Do not penalize a justified single-method design.
3. Sampling and access. Assess whether the sampling strategy is appropriate (purposive vs. probability), whether the sample size is justified, and whether access to key stakeholders is realistic.
4. Ethics and safeguards. Confirm informed consent, data protection, and risk-mitigation procedures are specified, including for sensitive topics.
5. Work plan and team. Verify the work plan is feasible, the team composition matches the methodological demands, and that the lead evaluator has adequate time allocated.
6. Risks and mitigations. Confirm the team has identified key risks (access, data quality, timeline) with credible mitigations.

If the material is incomplete: Request the actual inception report, TOR and agreed scope changes, matrix, instruments, sampling rationale and relevant ethics or access documentation. Names and assertions of approval are not those contents. Work only from supplied records. If a section needs an evaluation matrix detail, sampling justification, ethics safeguard, or work plan element the report does not specify, say what is missing there and how it limits that part of the review, then continue with the rest. Do not invent report content, methods, or team details it does not contain.

Output Format:

Produce:

1. A 1-paragraph overall assessment.
2. A rated review table by dimension (ToR fidelity, evaluation matrix, sampling, ethics, work plan, risks), with evidence and recommended action.
3. A prioritized revision list (must-fix vs. should-fix).
4. A conditional recommendation for the responsible owner, separating unresolved methodological or safeguarding blockers, missing verification, and nonblocking improvements; do not authorize fieldwork.

Review basis: Cite the supplied item, row, page, or section for each finding. Use Meets, Needs revision, Not assessable, or Not applicable with a reason; use numerical scores only if a supplied rubric defines their anchors. Distinguish a documented defect from missing evidence. Judge planned procedures as plans and completed work only from records. Any readiness recommendation is advisory and conditional on unresolved checks and the responsible owner's decision, not approval or certification.