NGO & Project Management

How to Write a Logframe: A Practical Guide for NGO Project Teams

November 18, 2026 7 min read
African colleagues drawing a project chart on a whiteboard

A young project officer in Kano once told me she was afraid of the logframe. Her donor had sent a template with four rows, four columns and a lot of unfamiliar words. She stared at it for three days.

If you are in the same place, relax. Learning how to write a logframe is not a talent. It is a method. Once you see the logic behind the boxes, the template stops being a threat and becomes a tool that protects your project.

Let’s walk through it step by step.

What a logframe is and why donors insist on it

A logframe, short for logical framework, is a one page summary of your project. It shows what you want to change, what you will do to get there, how you will measure progress and what could go wrong.

Donors love it for one reason. It lets them see your whole thinking at a glance. Staff love it for another reason. It keeps the team honest about what the project is really trying to achieve.

Most logframes have four rows and four columns. The rows are the levels of your project. The columns describe each level, how you will measure it, where the evidence will come from and what assumptions you are making.

The four rows, in plain language

Goal

This is the long term change you hope to contribute to. For example, improved household income among smallholder farmers in a state. Your project alone will not achieve it. You are one contributor among many.

Outcome

This is the change your project is directly responsible for. For example, two thousand farmers adopt improved cassava planting methods and increase yields by thirty percent within three years. Notice how specific it is. Notice that it describes a change in people, not an activity.

Outputs

These are the products and services your project delivers. Farmers trained. Demonstration plots established. A seed multiplication group formed. Outputs are things you can count and you control directly.

Activities

These are the tasks your team performs to deliver the outputs. Recruit trainers. Prepare materials. Hold forty sessions. Visit each plot monthly.

Read the rows from bottom to top and you get the logic. If we do these activities, we will deliver these outputs. If we deliver these outputs, we will achieve this outcome. If we achieve this outcome, we contribute to this goal.

How to write a logframe in six steps

Step 1: Start with the problem, not the template

Before you open any document, write one paragraph describing the problem and who suffers from it. Use real data. If the problem is unclear, the logframe will be unclear.

Step 2: Write the outcome first

Most people begin at activities because they are easy. Do the opposite. Write the outcome in one sentence. Ask yourself, what will be different for these people if the project succeeds? If you cannot answer in one sentence, your project is trying to do too much.

Step 3: Work backwards to outputs

Ask what must exist for the outcome to happen. List three to five outputs. Keep them concrete. If an output is vague, such as “improved awareness”, rewrite it as “one thousand households reached with three radio messages”.

Step 4: Add the activities

List the main tasks for each output. Do not list every small action. A logframe is a summary. Your detailed workplan is a separate document.

Step 5: Choose indicators that you can actually measure

An indicator tells you whether you are on track. Good indicators have a number, a group of people and a time frame. For example, percentage of trained farmers using row planting by month twelve.

Be realistic. A beautiful indicator that costs a million naira to measure is useless to a small team. Ask who will collect the data, how often and with what tool.

Step 6: Name your assumptions and risks

Assumptions are things outside your control that must hold true. Rainfall is normal. The state government keeps the extension office open. Farmers have access to seed. Write them down. When one fails, you will have already warned the donor.

Common mistakes that weaken a logframe

Confusing outputs with outcomes is the most common one. Training twenty teachers is an output. Teachers using new methods in class is an outcome.

The second mistake is too many indicators. Two or three strong ones for each level are enough. More than that and nobody will track them.

The third mistake is writing the logframe alone. Sit with field staff, finance and your monitoring officer. They will spot what is unrealistic before the donor does.

The fourth mistake is filing the logframe after approval. It is a living tool. Review it every quarter. If the context changes, adjust it and tell your funder.

A simple check before you submit

Read your logframe aloud to someone who does not know the project. Ask them to explain it back to you. If they cannot, simplify it. A good logframe is clear enough for a community leader and rigorous enough for a donor reviewer.

Test the logic with the words “if” and “then”. If we do this, then that will happen. If a link feels weak, you have found the gap to fix.

Take the next step

A logframe is the backbone of every well run project. When it is built properly, your reporting becomes easier, your team becomes clearer and your funder becomes more confident.

If your organisation needs help designing logframes, building monitoring systems or training project teams, I can support you. Learn more on the services page and let’s strengthen your next proposal.

← All Articles
MU
Written by
Michael Ukwuma

Capacity development consultant working with nonprofits, NGOs and donor-funded organisations across Africa. Tony Elumelu Foundation coach and HundrED Nigeria country lead.

Full Bio →
Start Your Journey

Get the free book that started everything.

Download Free →