Mid-Term Review (MTR): What It Is and What to Include

What Is a Mid-Term Review?

A mid-term review (MTR) is an assessment carried out around the midpoint of a program or project to check progress against plans and results, test whether the design still holds, and recommend corrections for the remaining period. It is usually written by an external reviewer or a small review team for the program's management, its board or steering committee, and the funder. The OECD defines a mid-term evaluation as one "performed towards the middle of the period of implementation of the intervention," and the GEF defines a mid-term review as an assessment of performance and results "carried out for adaptive management purposes at the midpoint" of a project's intended duration.

A final evaluation tells you what happened. A mid-term review tells you what to fix.

MTR, midterm review or mid-term evaluation? Many organizations use these names interchangeably. Where a distinction is made, a "review" is treated as lighter and more management-oriented (progress, delivery, risks, corrective actions), while a "mid-term evaluation" is treated as more independent and more rigorous, with a full set of evaluation questions and criteria and a larger evidence base. Check your funder's guidance: the name in the contract decides what is expected, and the Terms of Reference should say which depth is wanted.

Why It Matters

Funders often require it. The GEF requires a mid-term review for all full-sized projects, and its guidance says the report is submitted at project mid-term. UNDP's guidance for GEF-financed projects calls the MTR mandatory for full-sized projects and describes it as primarily a monitoring tool: it identifies challenges and outlines corrective actions so the project is on track to achieve maximum results by completion.

Even when no one requires it, the midpoint is the last practical moment to act on what monitoring data has been showing. After it, budgets are committed and the remaining time may be too short to change strategy. A good review gives management evidence for hard decisions: revise a target that was set without a baseline, drop an activity that is not working, or reallocate budget. It also confirms that the results framework can actually be measured, which saves months of argument at the final evaluation.

What Does a Mid-Term Review Include?

A mid-term review report typically covers these sections, in roughly this order:

1. Purpose, scope and questions. Why the review is being done, what period and components it covers, and the review questions taken from the Terms of Reference. Usually 4 to 8 questions, written so the findings can answer them directly.

2. Methodology and limitations. Document review, interviews, site visits, and any survey or monitoring data analysis. State who was consulted, who could not be reached, and how this affects confidence.

3. Progress toward results. Each indicator compared with its baseline and its midpoint and end-of-program targets, by outcome and output. Reviewers often rate progress (for example, on a six-point scale from highly satisfactory to highly unsatisfactory) and explain what is driving the gap between planned and actual.

4. Relevance and design. Whether the problem, the theory of change and the assumptions still hold, whether the results framework is clear and measurable, and whether the context has changed since design. This is where weak indicators and unrealistic targets are flagged.

5. Implementation and management. Work planning, spending against budget, staffing, partner coordination, and whether the program has used monitoring data to adapt.

6. Risks and sustainability outlook. Which risks have materialized or grown, whether mitigation is working, and whether benefits are likely to continue after funding ends (financial, institutional, social, environmental).

7. Findings. Evidence-based statements for each review question, each traceable to a data source. Findings describe what was found, not what should be done.

8. Conclusions. The reviewer's judgments drawn from the findings: strengths, weaknesses and the overall picture. They should be balanced and follow from the evidence.

9. Prioritized recommendations. Specific actions, each with an owner and a priority or timeframe. UNDP's guidance recommends no more than 15, summarized in a table in the executive summary.

10. Management response. The program's written reply to each recommendation: accept, partly accept or reject, with the action, owner and deadline. It is usually a separate document prepared after the final report. See Management Response.

Example Outline

A mid-term review report for a three- to five-year program might run 30 to 50 pages:

1. Executive Summary, with ratings and recommendations table (3 to 4 pages)
2. Introduction: purpose, scope, questions (2 pages)
3. Program Description and Context (3 pages)
4. Methodology and Limitations (3 pages)
5. Findings: Progress Toward Results, by outcome with an indicator table (8 to 10 pages)
6. Findings: Relevance and Design (3 to 4 pages)
7. Findings: Implementation and Management (4 to 5 pages)
8. Findings: Risks and Sustainability (3 pages)
9. Conclusions (2 to 3 pages)
10. Recommendations (2 to 3 pages)

Annexes (usually 15 to 30 additional pages): Terms of Reference, evaluation matrix, list of people consulted, indicator tracking table, documents reviewed, interview guides, and the management response.

Mid-Term Review vs. Midline vs. Final Evaluation

These three are often mixed up. They answer different questions and are done by different people.

The midline is data. The mid-term review is judgment. A review without midline data relies on routine monitoring, which may be thin; a midline without a review gives numbers but no explanation. See Midline for the data collection side and Evaluation Report for how final reports are structured. UNDP's guidance adds that the MTR emphasizes adaptive management and supportive recommendations, while the terminal evaluation emphasizes accountability and lessons for future projects.

Common Mistakes

Starting too late. A review that reports at 60 or 70 percent of the timeline leaves little room to act. Draft the Terms of Reference and hire the reviewer well before the midpoint so the report lands while changes are still possible.

Reviewing without usable data. If the baseline is missing or monitoring has not collected indicator data, the reviewer can only report opinions. Run the midline, or assemble the monitoring data, before the review begins.

Writing recommendations nobody can act on. "Strengthen coordination" cannot be assigned or checked. Each recommendation should say what to change, who owns it and by when, and should follow from a stated finding.

Skipping the management response. Without a written response and follow-up, recommendations are filed and forgotten. Put it, with owners and dates, on the steering committee agenda.

Treating it as a mini final evaluation. A review that spends most of its pages proving impact so far misses its job. At the midpoint the useful questions are about delivery, design and risk.

Variation by Program Size and Funder

Large multilateral or donor-required projects. Expect a prescribed process: a standard Terms of Reference, a mandatory inception report, a reviewer mission, specific rating scales and a fixed report template. For example, UNDP's guidance for GEF projects sets four phases and says the process should not exceed 5 months after the consultants are hired. Follow the funder's template exactly, because the report may be submitted to the funder and checked for compliance.

Mid-sized grants and NGO programs. The funder may require a midpoint assessment without a prescribed format. Agree on questions and length early, and ask whether it is a review or an evaluation, because that sets the depth and independence expected.

Small projects. UNDP's guidance says GEF medium-sized projects need not do an MTR, but should when the project is performing poorly, and that the review can then follow a simplified approach. The same logic applies to small awards: a short internal review of 10 to 15 pages, a half-day workshop and an updated work plan may be enough.

Multi-country or multi-partner programs. The review has to sample across sites and partners, which adds time and cost. Say in the Terms of Reference how many sites will be visited and how they are chosen.

The test for any mid-term review: after reading it, can the program manager name three changes to make in the next quarter and who will make them?