Logical Framework Approach
- Introduced by
- Leon Rosenberg / Practical Concepts Inc. for USAID; later NORAD, GTZ, European Commission
- Year
- 1969
- Type
- Project planning, monitoring and evaluation framework
- Family
- Objectives-oriented project planning
What does it do?
The Logical Framework Approach (Logframe) is a structured planning, monitoring, and evaluation method that distils an intervention into a single four-by-four matrix linking a hierarchy of objectives to the indicators, evidence, and external conditions on which success depends.
Originated by Leon Rosenberg of Practical Concepts Incorporated for USAID in 1969 and elaborated by agencies such as GTZ, NORAD, and the European Commission, it forces planners to make explicit the causal logic by which activities are expected to produce outputs, outcomes, and ultimately a development goal.
The intuition behind the method
Imagine writing the whole theory of a project on a single page, then stress-testing it for hidden cracks. Reading the matrix bottom-to-top you tell a story of 'if we do these activities, then we get these outputs; if we get these outputs, then we achieve this purpose; if we achieve this purpose, then we contribute to this goal'. Reading across each row you ask: how will we know it happened, where is the proof, and what must hold true in the world for the next rung of the ladder to bear weight? The assumptions column is the project's risk register written as conditions the logic silently depends on.
History
The Logical Framework was developed in 1969 by Leon Rosenberg of Practical Concepts Incorporated under contract to the United States Agency for International Development (USAID), which faced difficulty appraising and evaluating projects with vague objectives. Through the 1980s and 1990s it was adopted and adapted by bilateral and multilateral agencies: GTZ in Germany embedded it within its participatory ZOPP method, NORAD published an influential objectives-oriented planning handbook, and the European Commission, DFID, AusAID, and UN agencies made it a standard requirement of the project cycle. It remains a near-universal donor planning instrument, increasingly used alongside theory-of-change and results-based management approaches.
When to use it
Use the Logframe when a project or programme needs a concise, shared summary of its intervention logic for appraisal, contracting, monitoring, and evaluation, particularly where a donor requires it as part of the funding cycle. It is strongest at the design stage for clarifying objectives, indicators, and risks and at the evaluation stage as a reference against which results are judged. It is weaker for highly complex, emergent, or politically contested interventions where the causal chain cannot be specified in advance, and it should be the product of a participatory process rather than a form filled in retrospectively.
Limitations and considerations
- The fixed four-by-four matrix imposes a linear, predictable causal model that fits poorly with complex, adaptive, or emergent interventions.
- Once approved it can become a rigid contract that discourages adaptation and learning as conditions change during implementation.
- Filled in mechanically or retrospectively to satisfy a donor, it becomes a bureaucratic ritual divorced from the project's real logic.
- It privileges what is easily measurable and can crowd out attention to unintended effects, power relations, and processes that resist indicators.
Source conditions do not replace independent scientific review or validation by an analysis engine.
Strengths
- Compresses a project's entire logic, evidence base, and risk profile into a single, comparable one-page matrix that aids appraisal and communication.
- Forces explicit statement of the causal hypotheses linking activities to outcomes, exposing gaps and unrealistic leaps in the intervention logic.
- Couples each objective with verifiable indicators and named data sources, building the monitoring and evaluation system into the design from the outset.
- The assumptions column institutionalises risk thinking, requiring planners to identify external conditions that could derail the causal chain.
Applications
- Structuring a donor-funded project proposal so that goal, purpose, outputs, indicators, verification sources, and assumptions are presented coherently for appraisal.
- Designing the monitoring and evaluation plan of an intervention by deriving data-collection requirements directly from the indicators and means of verification.
- Serving as the reference document for mid-term and final evaluations that judge whether outputs, outcomes, and goal-level changes were achieved.
- Facilitating participatory planning workshops (such as GTZ's ZOPP) in which stakeholders jointly build the problem tree, objectives tree, and matrix.
- Coordinating multi-partner programmes by giving all parties a shared, explicit statement of the causal logic and division of responsibilities.
How it works
How it works
The approach opens with an analysis phase: stakeholder analysis to identify who is affected and who has influence, problem analysis to build a cause-and-effect 'problem tree', objectives analysis that mirrors the problem tree into a 'means-ends' tree, and analysis of alternative strategies to choose the intervention scope. This participatory diagnosis grounds the matrix in the actual problem rather than a predetermined solution.
The chosen strategy is arranged into the vertical logic of the matrix — the first (narrative summary) column — across four levels: Goal (the higher-order development objective the project contributes to), Purpose or Outcome (the change expected once outputs are used), Outputs or Results (the deliverables under the project's direct control), and Activities (the tasks undertaken). Each level is connected to the one above by an if-then causal hypothesis, so the column is a testable chain rather than a wish list.
The horizontal logic is completed for each level by specifying Objectively Verifiable Indicators (OVIs) — quality, quantity, and time-bound measures of achievement — and the Means of Verification (MOVs), the data sources and methods (surveys, records, reports) that will supply evidence for each indicator. This pairing makes objectives measurable and forces planners to confront, early, whether the data needed to prove success can actually be collected affordably.
The fourth column records the assumptions: external conditions outside the project's control that must hold for the causal jump to the next level to occur. Read with the vertical logic, the full statement becomes 'if Activities are carried out and Assumptions hold, then Outputs are delivered', and so on up the hierarchy. Assumptions judged both important and unlikely are 'killer assumptions' that may require redesign; this column is the bridge between the logframe and risk management.
Common pitfalls
- Treating the matrix as a fixed contract rather than a living management tool, so it is never revisited as assumptions prove false.
- Confusing levels of the hierarchy — labelling deliverables (outputs) as outcomes — which breaks the if-then logic and inflates claims of impact.
- Specifying indicators with no realistic, affordable means of verification, so the monitoring system collapses during implementation.
- Omitting or downplaying 'killer assumptions' to make the project appear feasible, hiding the very risks most likely to cause failure.
Frequently asked questions
What is the difference between vertical and horizontal logic in a logframe?
Vertical logic runs down the first column through the objective hierarchy — Goal, Purpose, Outputs, Activities — and expresses the if-then causal chain that connects them, read together with the assumptions. Horizontal logic runs across each row: for every objective it specifies the Objectively Verifiable Indicators that define success and the Means of Verification that supply the evidence. Vertical logic tests whether the strategy is coherent; horizontal logic tests whether achievement can be measured and proven.
What are OVIs and MOVs?
OVIs are Objectively Verifiable Indicators — measures stated in terms of quality, quantity, and time so that different observers would agree whether an objective has been met. MOVs are Means of Verification — the specific data sources and collection methods (project records, household surveys, official statistics, field reports) that will provide the values for each indicator. Pairing them ensures that every indicator chosen can actually be measured at acceptable cost and effort.
How does the Logframe relate to Theory of Change?
Both make a project's causal logic explicit, but a Theory of Change is typically a richer, more flexible narrative-and-diagram that maps multiple pathways, preconditions, and assumptions and is well suited to complex change. The Logframe is a more compact, tabular summary optimised for management, contracting, and measurement. In modern practice the two are often used together: a Theory of Change articulates the broader pathway, and the logframe operationalises a selected pathway into measurable objectives, indicators, and assumptions.
Related methods
Sources
NORAD (1999). The Logical Framework Approach (LFA): Handbook for Objectives-Oriented Planning (4th ed.). Norwegian Agency for Development Cooperation, Oslo.
Open publication referenceCopied.European Commission (2004). Aid Delivery Methods, Volume 1: Project Cycle Management Guidelines. EuropeAid Cooperation Office, Brussels.
Open publication referenceCopied.