What is a logframe?
A logframe, or logical framework matrix, summarizes what a project intends to achieve, how progress will be measured, where evidence will come from and which assumptions must hold. It brings the results hierarchy and the measurement plan into one table.
A common format uses four result levels—goal, purpose, outputs and activities—and columns for the description, indicators, means of verification and assumptions. Funders may use different labels or add baseline, target and milestone columns. Use the required format without losing the reasoning behind it.
The logframe matrix: rows and columns
| Result level | Indicator | Means of verification | Assumption |
|---|---|---|---|
| Goal: improved employment prospects | A defined employment measure at a suitable follow-up point. | Follow-up records and an appropriate contextual comparison. | The local labor market offers suitable opportunities. |
| Purpose: participants gain and use relevant skills | Proportion demonstrating competence and reporting application. | Assessed task, rubric and follow-up evidence. | Participants can access opportunities to use the skills. |
| Outputs: training and practice delivered | Completed sessions, assessed tasks and participation coverage. | Delivery and assessment records. | Trainers and facilities remain available. |
| Activities: recruit, teach, assess and support | Implementation milestones or resource measures required by the format. | Workplan, attendance and expenditure records. | Recruitment reaches the intended group. |
Each row should be understandable without guessing what a label means. “Participants supported” needs a service definition. “Skills improved” needs a measure and timing. Keep the table concise and put detailed definitions in an accompanying indicator dictionary.
Vertical and horizontal logic
Vertical logic asks whether the sequence makes sense: if the activities happen and the relevant assumptions hold, are the outputs likely to follow? If those outputs are delivered, are they sufficient to support the purpose?
Horizontal logic asks whether each claim can be examined: does the indicator measure the intended result, and can the stated verification source provide that information? A satisfaction survey cannot, by itself, verify demonstrated skill.
Test one row in both directions. If the purpose is sustained use of a skill, a completion register only verifies an output. Add suitable follow-up evidence or narrow the claim.
Logical Framework Approach vs logframe matrix
The Logical Framework Approach is a planning process. It can include stakeholder analysis, problem analysis, objectives, choices about strategy and the development of a monitoring plan. The matrix is one output of that process.
Completing a table is not a substitute for discussing the problem with people affected by the project. If partners disagree about the purpose, resolve that disagreement before polishing indicator wording.
How to write an objectively verifiable indicator
An objectively verifiable indicator, often shortened to OVI, describes how a result will be observed or assessed. “Objectively verifiable” does not mean judgment disappears; it means the definition and evidence can be examined rather than relying on an unexplained assertion.
| Weak wording | More usable wording | Still needed |
|---|---|---|
| Participants are job-ready | Proportion meeting the agreed task-assessment standard at course completion. | Task, rubric, assessors, denominator and baseline. |
| Partners report on time | Proportion of required quarterly submissions received by the agreed deadline. | Which partners, what constitutes a complete submission and the calendar. |
| Service quality improves | Change in the defined quality measure over the reporting period. | Measure, collection method, comparison and missing-data treatment. |
Set a baseline, a target with a rationale and intermediate milestones where useful. A target is a planning commitment, not evidence. The UK’s revised logframe guidance separates indicator, baseline, target and milestone information to make these distinctions clear. Read the guidance.
Means of verification: name an actual source
The means of verification column explains where the evidence will come from. “Project report” is often too vague. Name the underlying record, survey, assessment or document and specify who collects it and when.
- For an assessment: retain the task, rubric, score and assessment date.
- For a survey: retain the question wording, response options, population and collection period.
- For partner evidence: define the reporting period, metric version and supporting document requirements.
- For an external source: check whether the population, geography and timing match the indicator.
Check feasibility early. A sophisticated indicator that no partner can collect reliably may be less useful than a narrower measure with a clear source.
What belongs in the assumptions column?
Assumptions are conditions needed for the pathway to work that are not fully under the project’s control. They should be specific enough to monitor. “Stakeholders remain supportive” is weaker than naming the particular partner commitment the next stage needs.
Distinguish an assumption from a delivery task. If the team is responsible for arranging transport, that belongs in the workplan. If participation depends on an external transport service remaining available, the dependency belongs in the assumptions and risk discussion.
Give important assumptions an owner, a review date and a signal that would trigger action. When an assumption fails, record the consequence for the project logic and the response. Do not quietly rewrite the original plan.
How to build a logframe step by step
- Define the purpose: state the change the project can plausibly support for a specified group.
- Connect it to the goal: explain the wider change without claiming the project controls it.
- Work backward to outputs: identify what must be delivered.
- Choose activities: connect the workplan and resources to those outputs.
- Write indicators and verification: make measurement feasible before agreeing targets.
- Check assumptions: test the links with delivery partners and people affected.
- Review the whole matrix: remove contradictions and assign responsibility for updates.
Use a theory of change alongside the matrix when the explanation needs more space, several pathways or feedback between stages.
A blank logframe template to use with your team
| Project description | Indicator, baseline and target | Verification source and timing | Assumptions |
|---|---|---|---|
| Goal: [wider change] | [what would indicate progress?] | [source and reporting period] | [conditions beyond the project] |
| Purpose: [change for whom?] | [measure, baseline, target and date] | [collection method and owner] | [what must hold for outputs to lead here?] |
| Outputs: [deliverables] | [quantity, quality and coverage] | [delivery records and checks] | [dependencies affecting delivery] |
| Activities: [work to deliver outputs] | [milestones or inputs, as required] | [workplan and resource records] | [preconditions] |
Keep supporting definitions outside the main matrix so it stays readable. Link each indicator to its definition rather than copying a different version into every quarterly report.
Logframe, theory of change, logic model or results framework?
Use a logframe when a compact management and reporting matrix is needed. Use a theory of change to explain the causal reasoning and context. A logic model provides a results sequence; a results framework organizes objectives and measures, often across a wider program. The names overlap in practice, so agree what each document must do.
These tools are not competing software categories. Keep their definitions aligned and avoid maintaining conflicting outcome statements in separate files.
Keep quarterly reporting consistent
When several partners report against the same framework, keep their original submissions and map them to agreed definitions. A financial document, narrative report and indicator table should retain the same partner identity and reporting period.
AI-assisted review can help flag missing information or conflicting descriptions for a human to check. It should not silently normalize unlike indicators or invent a value where evidence is missing. Freeze the version used for a submitted report, then record subsequent corrections separately.
Continue learning in the Academy
Use these existing Academy guides for the practical next step. They are suggested companion readings; follow each guide’s course navigation for the full sequence.
Use the practical guides to connect the model to a collection plan, review new evidence and decide what to improve.
Frequently asked questions
What are the four columns of a logframe?
A common format uses the result description, indicators, means of verification and assumptions. Some funders separate baseline, target and milestone fields.
What is the purpose row?
It usually states the main change the project intends to support, between its delivered outputs and the wider goal. Check the funder’s terminology.
Can a logframe change during implementation?
Yes, when justified and agreed through the appropriate process. Preserve the earlier version, the reason for revision and any effect on comparability.
How many indicators should each result have?
Use enough to examine the result without creating an unmanageable collection burden. Coverage, quality and distribution may need different measures.
Does a completed logframe prove impact?
No. It organizes the plan and evidence requirements. Causal claims still need an appropriate evaluation design and analysis.
