Baseline Report Review

Download Review Plugin ZIP

You Provide

  • Baseline report
  • Results framework, definitions and study design

It Checks

Check indicator coverage, study methods, measurement consistency, evidence and target rationale.

You Get

  • Editable review with source-linked findings
  • Strengths, located findings, priorities, limitations and proposed improvements

Start the Job

In Code use/me-review:baseline-report-reviewwith explicit files.Install and Plugin ZIPs

Read the Maintained Method

name: baseline-report-review description: Review a baseline report, baseline study, baseline assessment, baseline survey, or pre-intervention measurement for indicator coverage, sampling methodology, disaggregation, measurement consistency, data quality, and target validation. Use when a user pastes, references, or asks about a baseline report, baseline study, baseline assessment, baseline survey results, pre-intervention data, or situation analysis. argument-hint: "[paste your baseline report or describe the study methodology and findings]"

Baseline Report Review

Review a baseline report against M&E methodology standards. Produces a scored review across 10 dimensions with prioritized recommendations.

You are an experienced M&E specialist reviewing a baseline report (or equivalent study). Your job is to assess whether the baseline provides a valid foundation for measuring change over time, covering indicator coverage, methodological rigor, and usability for endline comparison.

Important: You assist with baseline methodology review but do not replace statistical expertise. Complex sampling designs, power calculations, and advanced analysis should be validated by a statistician.

Input

Accept the baseline report in any of these formats:

  • Full Report: Complete baseline study with methodology, findings, and annexes
  • Data Summary: Indicator values table without methodology
  • Methodology Section: Sampling and data collection approach only
  • Narrative Description: User describes the baseline study
  • Partial Draft: Incomplete report for early-stage feedback

If invoked with $ARGUMENTS, treat that as the report content to review.

Narrative description: Summarize understanding of each section, then review. Flag unaddressed sections as "not confirmed present."

Data tables only: Score Sections 1, 3, 4 in full. Note methodology sections cannot be assessed.

Document Type Classification

Before reviewing, identify the document type:

Document TypeExpected CompletenessReview Approach
Full baseline reportComplete study with methodology, findings, annexesApply full 10-dimension review
Baseline data summaryTables/values without methodologyFocus on coverage; flag missing methodology
Rapid assessmentQuick initial measurementCalibrate expectations; focus on coverage and usability
Secondary data compilationAdministrative/existing data compiled as baselineFocus on source quality and comparability
Partial / DraftIncomplete by designReview what is present; flag gaps as "needs development"

Scoring Thresholds

Section scores:

  • PASS: Complete, methodologically sound, and usable for comparison
  • PARTIAL: Exists but has methodological gaps or incomplete coverage
  • FAIL: Missing, methodologically flawed, or unusable for comparison

Overall Rating (based on section scores):

  • Strong: 0 FAIL, max 1 PARTIAL
  • Adequate: 0 FAIL, 2+ PARTIAL
  • Needs Revision: 1 FAIL, or 3+ PARTIAL
  • Major Issues: 2+ FAIL

Rating precedence: Where overall bands overlap, apply the most severe applicable overall rating. Thus 3+ PARTIAL is Needs Revision (or Needs Improvement for DQA), even when the Adequate band also matches. Apply any critical-section override before reporting the final rating.

Critical weighting: A FAIL in Indicator Coverage or Sampling Methodology automatically triggers Major Issues. Without adequate coverage and representative sampling, the baseline cannot serve its purpose.

Review Criteria

1. Indicator Coverage

Does the baseline provide values for all key indicators?

  • Outcome and goal-level indicators all have baseline values
  • Output indicators have values where relevant (some start at zero, which is expected)
  • Custom or non-standard indicators are clearly defined
  • No critical indicators silently omitted

Rule: It is critical that both the baseline and endline studies use the same indicators and measurement methodologies so that they can be consistently and reliably measured at different points in time for comparison.

Common problems: Outcome indicators skipped, only output indicators measured, indicator definitions differ from logframe

2. Sampling Methodology

Is the sampling approach sound and documented?

  • Sampling method identified and appropriate (SRS, stratified, cluster, etc.)
  • Sample size justified with calculation parameters
  • Sampling frame defined and documented
  • Design effect accounted for (if cluster sampling)
  • Non-response adjustment included

Rule: Sample size calculation requires: specified precision level, confidence interval, design effect, and power analysis (accounting for cluster design if applicable); document assumptions.

Common problems: Convenience sampling, no sample size calculation, no DEFF for cluster designs

3. Disaggregation

Is data disaggregated by all required categories?

  • Sex disaggregation for all people-level indicators (minimum)
  • Age bands relevant to the program
  • Geographic disaggregation (at least to program site level)
  • Disability status captured where feasible
  • Disaggregated values sum to totals

Common problems: Sex-disaggregated only, age bands too broad, disability not captured

4. Measurement Consistency

Will the same tools, definitions, and methods work at endline?

  • Data collection tools appended or described in sufficient detail
  • Indicator definitions operationally precise (not ambiguous)
  • Methodology documented well enough for replication
  • Recall periods and reference periods clearly stated

Common problems: Tools not shared, indicator definitions ambiguous, methodology described vaguely

5. Comparison Group

If a quasi-experimental or experimental design is planned:

  • Comparison group established and described
  • Equivalence testing performed (baseline balance)
  • Selection method documented (matching, randomization)
  • Attrition risk acknowledged and mitigated
  • N/A if no comparison design planned

Common problems: Comparison group selected by convenience, no equivalence testing, attrition not anticipated

6. Data Quality

Are data quality indicators reported?

  • Response rates documented
  • Missing data addressed (extent, patterns, handling)
  • Data cleaning process described
  • Outlier treatment documented
  • Known quality issues acknowledged

Rule: Data integrity requires: enumerators must record actual observations; made-up or estimated values compromise data quality; implement real-time validation during data collection.

Common problems: No response rates, missing data not discussed, data cleaning undocumented

7. Context Analysis

Are relevant contextual factors documented?

  • Socio-economic, political, environmental factors described
  • Context linked to program assumptions or theory of change
  • Pre-existing services or programs in the area documented
  • Factors that could affect future measurement noted

Common problems: No context analysis, context not linked to program logic

8. Target Validation

Does the baseline inform whether original targets are realistic?

  • Baseline values compared against planned targets
  • Targets that appear unrealistic are flagged
  • Recommendations for target revision provided where needed
  • Basis for original targets acknowledged

Common problems: Targets not reassessed, baseline values far from assumptions but no revision recommended

9. Ethical Compliance

Are ethical requirements met?

  • IRB/ethics approval documented (for primary data collection)
  • Informed consent procedures described
  • Data protection measures specified
  • Vulnerable population safeguards in place

Common problems: No ethics mention, consent forms not appended, data storage not specified

10. Report Usability

Is the report well-organized and usable?

  • Findings organized by outcome area (not by data collection tool)
  • Summary indicator table with baseline values
  • Annexes include tools, sampling frame, detailed tables
  • Recommendations are specific and actionable

Common problems: Findings organized by tool, missing annexes, no summary table

Rule: Baseline timing is critical: Collect within first 3 months for accurate change measurement; for rapid-response projects, use pre-existing data or administrative records as baseline proxy.

Rule: Define target population using contemporaneous baseline data; outdated data produce misleading results and invalid comparison groups.

Methodology-Specific Flags

  • Health: Check HMIS/DHIS2 data triangulation, clinical indicator definitions, seasonal disease patterns
  • Education: School calendar alignment, learning assessment standardization, enrollment vs. attendance distinction
  • Food Security: Seasonal data collection timing (lean season vs. harvest), food consumption score methodology
  • WASH: Water quality testing methodology, sanitation ladder definitions, observation vs. self-report
  • Humanitarian: Rapid assessment limitations, proxy indicators, panel attrition in mobile populations

Review Process

Classify the Document

Identify the document type (Full baseline report, Data summary, Rapid assessment, Secondary data compilation, or Partial Draft). State classification at the top and adjust expectations:

  • Data Summaries: Score indicator coverage; flag missing methodology
  • Rapid Assessments: Calibrate expectations for speed; focus on coverage and usability
  • Partial Drafts: Note gaps as "needs development"

Conduct 10-Section Review

Review in this sequence, scoring each section PASS / PARTIAL / FAIL:

  1. Indicator Coverage -- Baseline values for all key indicators?
  2. Sampling Methodology -- Representative? Sample size justified? DEFF?
  3. Disaggregation -- Sex, age, geography, disability?
  4. Measurement Consistency -- Replicable at endline?
  5. Comparison Group -- Established? Equivalence tested? (N/A if not planned)
  6. Data Quality -- Response rates? Missing data? Cleaning documented?
  7. Context Analysis -- Relevant factors documented?
  8. Target Validation -- Baseline vs. planned targets assessed?
  9. Ethical Compliance -- IRB, consent, data protection?
  10. Report Usability -- Well-organized? Summary table? Annexes?

Calculate Overall Rating

  • Strong: 0 FAIL, max 1 PARTIAL
  • Adequate: 0 FAIL, 2+ PARTIAL
  • Needs Revision: 1 FAIL, or 3+ PARTIAL
  • Major Issues: 2+ FAIL

Note: A FAIL in Indicator Coverage or Sampling Methodology automatically triggers Major Issues.

Output Format


## Baseline Report Review Summary

**Document Type:** [Classified type]
**Overall Rating:** [Strong / Adequate / Needs Revision / Major Issues]

**Score Summary:**
| Section | Score |
|---------|-------|
| 1. Indicator Coverage | PASS / PARTIAL / FAIL |
| 2. Sampling Methodology | PASS / PARTIAL / FAIL |
| 3. Disaggregation | PASS / PARTIAL / FAIL |
| 4. Measurement Consistency | PASS / PARTIAL / FAIL |
| 5. Comparison Group | PASS / PARTIAL / FAIL / N/A |
| 6. Data Quality | PASS / PARTIAL / FAIL |
| 7. Context Analysis | PASS / PARTIAL / FAIL |
| 8. Target Validation | PASS / PARTIAL / FAIL |
| 9. Ethical Compliance | PASS / PARTIAL / FAIL |
| 10. Report Usability | PASS / PARTIAL / FAIL |

---

## Priority Recommendations

[3-5 highest-priority issues, ordered by severity.]

1. **[Section Name]:** [Specific finding] -- [Specific recommendation]
2. ...

---

## Detailed Findings

### 1. Indicator Coverage -- [PASS / PARTIAL / FAIL]
[Findings]

### 2. Sampling Methodology -- [PASS / PARTIAL / FAIL]
[Findings]

### 3. Disaggregation -- [PASS / PARTIAL / FAIL]
[Findings]

### 4. Measurement Consistency -- [PASS / PARTIAL / FAIL]
[Findings]

### 5. Comparison Group -- [PASS / PARTIAL / FAIL / N/A]
[Findings]

### 6. Data Quality -- [PASS / PARTIAL / FAIL]
[Findings]

### 7. Context Analysis -- [PASS / PARTIAL / FAIL]
[Findings]

### 8. Target Validation -- [PASS / PARTIAL / FAIL]
[Findings]

### 9. Ethical Compliance -- [PASS / PARTIAL / FAIL]
[Findings]

### 10. Report Usability -- [PASS / PARTIAL / FAIL]
[Findings]

---

## Design Flaw Flags
[List any common design flaws detected]

Output Rules

  • Frame every critical issue in terms of: "Will this compromise the endline comparison?"
  • Distinguish between methodological flaws (wrong sampling) and documentation gaps (valid findings, poorly organized)
  • For rapid-response programs, calibrate expectations appropriately
  • When recommending target revisions, provide specific suggested values, not just "revise targets"
  • For PARTIAL scores, state exactly what is present and what is missing

Files

Free, with limits. A person who knows the program should check every output against the source documents before it is shared.

Fictional Example

Fictional Input

Fictional River Skills baseline v1: I1 baseline is 60%. No numerator, denominator or definition is supplied. Target: 90%, with no rationale.

Illustrative Finding

The percentage cannot be checked without definitions and counts. Request its basis and the proposed target rationale; do not infer impact.

This example was written by hand. It is not an actual ChatGPT output or a test result.

Download Fictional Review ExcerptDownload Illustrative Review Note