How to Write a Theory of Change That Actually Convinces Donors

A theory of change is where many NGO proposals lose a reviewer’s confidence before they even reach the budget. Done well, it’s the clearest, most persuasive part of a proposal — a plain statement of why your specific approach will produce the change you’re promising. Done poorly, it reads as a list of activities with no real argument behind it. This guide walks through the components and a worked example.

The Core Components

A complete theory of change includes five elements: the problem you’re addressing and its root causes, the activities you’ll implement, the outputs those activities produce, the outcomes (behavior or condition changes) those outputs should lead to, and the longer-term impact those outcomes contribute to. Crucially, it also needs the assumptions connecting each stage — the conditions that have to hold true for your logic to work.

A Worked Example

Problem: Smallholder farmers in the target district have low crop yields, driven partly by limited access to improved seed varieties and partly by lack of training in modern agronomic techniques.

Activities: Distribute improved seed varieties; deliver agronomic training; establish farmer demonstration plots.

Outputs: Farmers equipped with improved seeds; farmers trained in new techniques; functioning demonstration plots.

Assumption linking outputs to outcomes: Farmers who receive both seeds and training will actually adopt the new techniques, assuming no major disruption (drought, input price shocks) prevents adoption.

Outcome: Increased adoption of improved agronomic practices among target farmers.

Assumption linking outcome to impact: Adoption of improved practices, combined with reasonable weather conditions, will translate into measurably higher yields.

Impact: Improved household food security and income among smallholder farming households in the district.

Notice that the assumptions do real work here — they’re not boilerplate, they name the specific conditions (“no major disruption,” “reasonable weather conditions”) that a reviewer needs to believe are plausible for your logic to hold.

What Makes Reviewers Doubt a Theory of Change

The most common weakness is skipping the assumptions entirely — presenting the pathway from activities to impact as if it will simply happen, with no acknowledgment of what has to go right along the way. A second common weakness is a theory of change that doesn’t match the root cause analysis: if the stated problem is about access to markets, but all the activities are about training, a reviewer will reasonably ask how the activities address the actual bottleneck identified. A third is failing to distinguish outputs from outcomes — the same confusion that undermines logframes undermines theories of change for the same reason.

Common Categories of Assumptions to Consider

Strong theories of change usually draw assumptions from several distinct categories rather than focusing on just one type of risk:

• Political/institutional: continued government cooperation, stable policy environment, local authority buy-in
• Economic: no major price shocks, continued household purchasing power, stable exchange rates for multi-year budgets
• Environmental: no major weather disruption, seasonal timing assumptions for agricultural projects
• Social/behavioral: target population’s willingness to adopt new practices, community acceptance of the intervention approach

Reviewing your theory of change against each of these categories, rather than relying on whatever risks happen to come to mind first, usually surfaces assumptions a single pass would miss.

Theory of Change vs. Logframe: How They Work Together

These two tools are often confused because they describe similar causal chains, but they serve different functions in a proposal. The theory of change is the persuasive narrative argument — it convinces a reviewer your approach makes sense. The logframe is the operational tracking tool — it specifies exactly how you’ll measure whether that logic actually played out. A strong proposal uses the theory of change to make the case and the logframe to make it measurable; using only one without the other leaves either the logic or the accountability mechanism underdeveloped.

Using the Theory of Change Beyond the Proposal

A theory of change shouldn’t be written once for the proposal and then forgotten. Referring back to it during implementation — checking whether the assumptions are actually holding, and whether outputs really are translating into outcomes as expected — turns it into a genuine management tool rather than a one-time donor-facing document.

Our Funds for NGOs course includes a dedicated module on theory of change and proposal structuring, built around your own real project.

Frequently Asked Questions

Is a theory of change the same as a logframe?

They’re related but serve different purposes: a theory of change is the narrative argument for why your approach will work, while a logframe is the structured matrix with indicators used to track it. Many strong proposals include both.

How long should a theory of change section be?

Most effective ones run half a page to one page of narrative plus a simple diagram — reviewers want clarity, not length.

Can a theory of change be revised mid-project?

Yes, and it often should be if implementation reveals the original assumptions didn’t hold. Document the revision and the reason for it rather than quietly abandoning the original logic.

Do donors ever ask to see the theory of change updated during reporting?

Some do, particularly for longer multi-year grants, as part of assessing whether the original project logic is still holding up — treating it as a living document rather than a one-time submission puts you ahead of this expectation.

Testing Your Theory of Change Before You Submit

Before finalizing a theory of change for submission, it’s worth stress-testing it with someone outside the project team — ideally someone unfamiliar with the specific intervention. Walk them through the pathway from problem to impact and ask them to identify any step where the logic isn’t obvious to them. If an outside reader needs the connection between two stages explained verbally that isn’t clear from the document itself, a reviewer reading it cold will have the same gap. This kind of outside read often catches logical leaps the original drafters, who already understand the project intimately, don’t notice are missing from the written version.

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

• What Is a Logframe? A Plain-English Guide for NGO Program Staff
• 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
• A Beginner’s Guide to NGO Budgeting for Grant Proposals
• Country-Based Pooled Funds (CBPF) Explained
• 10 Donor Organizations NGOs Should Know in 2026