What Is a Logframe? A Plain-English Guide for NGO Program Staff

If you’ve worked in the NGO sector for more than a few months, you’ve almost certainly encountered the word “logframe” — usually in a donor template you’re expected to fill in without much explanation of what it’s actually for. A logframe (short for logical framework) is one of the most widely used project design and monitoring tools in international development, required in some form by nearly every major institutional donor. Yet surprisingly few program staff are ever formally taught how to build one well.

This guide breaks the logframe down in plain language: what it is, why donors require it, its four core levels, a worked example, and the mistakes that most commonly undermine an otherwise strong project design.

What a Logframe Actually Is

A logframe is a one-page (or sometimes two-page) matrix that summarizes a project’s design logic: what you plan to do, what you expect to achieve as a result, how you’ll know if it worked, and what assumptions your plan depends on. It was originally developed by USAID in the late 1960s and has since been adapted, with minor variations, by virtually every major donor — the EU, FCDO, the UN system and most private foundations all use some version of it.

At its core, a logframe answers four questions for each level of your project: What are we trying to achieve? How will we measure it? Where will that evidence come from? And what has to hold true outside our control for this to work?

The Four Levels, Explained

Each level should causally lead to the one above it: activities produce outputs, outputs contribute to outcomes, and outcomes contribute to the goal alongside other factors you don’t control. This causal chain is the actual “logic” in logical framework — and it’s also where most logframes break down.

A Worked Example: The Full Matrix

Here’s how the WASH example from earlier looks as a complete logframe matrix, including indicators, means of verification and assumptions — the full structure donors actually expect to see, not just the narrative levels.

Notice that each “Assumption” cell names something specific and checkable — not a vague statement like “no major problems arise.” This specificity is what makes the assumptions column useful as an actual risk-monitoring tool during implementation, rather than boilerplate nobody ever revisits.

The Mistake That Undermines Most Logframes

By far the most common error is collapsing outputs and outcomes into the same thing. “500 people trained” is an output — it tells you what you delivered. It is not an outcome, because it doesn’t tell you whether anything actually changed as a result. A logframe that only tracks outputs can report 100% delivery on every activity while the project fails to produce any real change — and donors increasingly catch this during review.

A second common mistake is writing indicators that aren’t actually measurable with the resources available. An indicator like “improved community resilience” sounds appropriate at the outcome level, but if you have no realistic way to measure resilience within your budget and timeline, it’s not a usable indicator — it’s an aspiration. Good indicators are specific enough that two different people, given the same data, would reach the same conclusion about whether the target was met.

A third mistake is treating the “assumptions” column as boilerplate rather than a genuine risk log. Assumptions should name the specific external conditions your project logic depends on — political stability, continued government cooperation, no major weather disruption — not generic statements that add no real information.

Using the Logframe During Implementation, Not Just at Design Stage

A logframe’s value doesn’t end once the proposal is approved. Teams that treat it as a living document — revisiting it at each reporting cycle, checking whether assumptions still hold, and flagging where the causal logic isn’t playing out as expected — get far more value from it than teams that file it away after the grant is signed. If your project’s actual implementation starts to diverge from what the logframe assumed, that’s useful early-warning information, not something to hide from a donor.

Quick Logframe Self-Check

• Does every output clearly lead to the outcome above it, with a stated assumption connecting them?
• Could two different people, given the same data, agree on whether each indicator’s target was met?
• Is there a documented baseline for every outcome and goal-level indicator, not just a target?
• Have you distinguished ‘what we delivered’ (outputs) from ‘what changed as a result’ (outcomes) at every level?
• Are the assumptions specific and checkable, rather than generic placeholder statements?

Building a logframe is one of the core modules in our Monitoring and Evaluation Course, where you’ll design a full logframe for a real or simulated project rather than just reading about the theory.

Frequently Asked Questions

Is a logframe the same as a results framework?

They’re closely related and often used interchangeably, though some donors distinguish a results framework as a narrative diagram and the logframe as the full matrix with indicators, means of verification and assumptions.

Do I need special software to build a logframe?

No — a logframe is typically built in a spreadsheet or word processor table. The skill is in the thinking behind each cell, not the software used to build it.

How detailed should indicators be at the activity level?

Activity-level indicators are usually just completion milestones (e.g., “training curriculum finalized by month 2”) rather than full impact indicators, which are reserved for the outcome and goal levels.

What’s the difference between a means of verification and a data collection tool?

The means of verification names the source of evidence (e.g., “household survey”), while the data collection tool is the actual instrument used to gather it (e.g., a specific survey questionnaire). Donors generally want the source named in the logframe itself.

Who Should Own the Logframe Inside Your Organization

A recurring source of confusion is who actually owns the logframe once a project starts — the program manager, the M&E officer, or whoever wrote the original proposal. In practice, shared ownership works best: the program manager should own the activities-to-outputs logic, since they’re closest to delivery, while the M&E officer owns the indicator design, data collection and the means-of-verification columns. Treating the logframe as “the M&E person’s document” tends to produce exactly the kind of outputs-outcomes confusion covered above, since the people with the deepest understanding of what’s actually changing on the ground aren’t the ones reviewing whether the indicators capture it. Build in a joint review at least once per reporting cycle, not just at the design stage, so both perspectives stay connected to the document throughout implementation.

About Strategia Netherlands

Strategia Netherlands is a training provider based in Rotterdam, the Netherlands, focused specifically on the humanitarian and development sector. We work with NGOs, UN agencies and government partners across Europe, Africa and the Middle East, and every course we run is built and updated by facilitators with direct field, donor or policy experience rather than academic staff alone. This blog draws on the same practitioner-informed approach we bring to our courses — practical, specific guidance you can apply directly, not general theory.

We publish guides like this one for the same reason we built our course curricula the way we did: most of the available material on these topics is either too academic to apply directly, or too generic to account for the specific constraints NGOs actually work under — limited budgets, small teams, and donors with real compliance expectations. If you found this guide useful, our related course goes several steps further, with individual feedback on your own project rather than general examples.

Related Reading

• 5 Signs Your NGO’s M&E System Isn’t Working
• SMART Indicators Explained: Examples by Sector
• MEAL vs. M&E: What’s the Difference
• How to Build a Donor-Ready M&E Report
• Why Your NGO’s Last Grant Proposal Got Rejected
• How to Write a Theory of Change That Convinces Donors
• A Beginner’s Guide to NGO Budgeting for Grant Proposals
• Country-Based Pooled Funds (CBPF) Explained
• 10 Donor Organizations NGOs Should Know in 2026