M&E Plan Template: How to Build a Monitoring & Evaluation Plan for NGO Projects

A Monitoring and Evaluation (M&E) plan is the operational document that turns a project’s logframe indicators into an actual data collection, analysis and reporting system. Without one, even a well-designed logframe fails in practice because no one has defined who collects what data, how often, and how it gets used.

Core Sections of an M&E Plan

1. Indicator Matrix

Each indicator from the logframe, with its definition, disaggregation requirements (sex, age, location), baseline value, and target.

2. Data Collection Methods and Tools

The specific tool (survey, checklist, focus group guide, administrative records review) and method used to collect data for each indicator.

3. Frequency and Responsibility

Who collects each data point, and how often (monthly, quarterly, at baseline/midline/endline).

4. Data Quality Assurance

The procedures for checking data accuracy, completeness and consistency before it’s used for reporting or decision-making.

5. Data Use and Reporting

How data flows into internal management decisions, donor reports, and adaptive programming — the step most M&E plans neglect in practice.

Building an M&E Plan That Actually Gets Used

The most common M&E plan failure is treating it as a compliance document rather than a management tool. Build review points into the plan itself — e.g. a quarterly data review meeting where programme staff actively discuss what the data shows and what to change.

Related Resources

• Logframe Template
• Indicator Library
• Evaluation Template

Related ATI Training

ATI’s Diploma in Monitoring and Evaluation covers full MEAL (Monitoring, Evaluation, Accountability, Learning) system design, including data quality assurance and adaptive management.

Frequently Asked Questions

What’s the difference between an M&E plan and a logframe?

A logframe defines what to measure; an M&E plan defines how, when, and by whom it gets measured, plus how the data gets used.

How often should an M&E plan be updated?

At minimum annually, and whenever project design changes significantly — an outdated M&E plan drifts out of sync with actual project activities.