Logical Framework (Logframe): From Theory to Action Plan
Transform your Theory of Change into a structured, funder-ready planning framework with clear objectives, measurable indicators, and realistic assumptions.
🎯 What You’ll Learn
By the end of this lesson, you will be able to:
✅ Structure your project logic in the standard logframe format
✅ Write SMART objectives at goal, outcome, and output levels
✅ Select appropriate indicators that demonstrate progress and impact
✅ Identify realistic assumptions and potential risks
✅ Create funder-ready documentation that meets proposal requirements
🌟 Why Logical Frameworks Matter
The Challenge with Loose Planning
- Unclear accountability → Hard to demonstrate results
- Confused stakeholders → Different people have different expectations
- Weak proposals → Funders can’t assess feasibility and impact
- Poor monitoring → No systematic way to track progress
What Logframes Provide
- Structured clarity that everyone can understand
- Measurable commitments that demonstrate accountability
- Risk management through explicit assumption testing
- Communication tool that works across cultures and organizations
- Monitoring framework built into your project design
📊 Understanding the Logframe Structure
The Four-Level Hierarchy
GOAL (Impact) ←→ Impact Indicators ←→ Sources of Verification
↑
OUTCOMES (Purpose) ←→ Outcome Indicators ←→ Sources of Verification
↑
OUTPUTS (Results) ←→ Output Indicators ←→ Sources of Verification
↑
ACTIVITIES (Actions) ←→ Input Indicators ←→ Sources of Verification
ASSUMPTIONS (External Factors Needed for Success)
The Four Columns Explained
Column 1: Intervention Logic
- Goal: Long-term impact your project contributes to
- Outcomes: Changes that your project will directly achieve
- Outputs: Products/services your project will deliver
- Activities: Tasks your project will implement
Column 2: Indicators
- Specific, measurable evidence of achievement
- Quantitative and qualitative measures
- SMART targets with baselines and timeframes
Column 3: Sources of Verification
- Where you’ll find evidence for each indicator
- Who will provide the data
- How data will be collected and when
Column 4: Assumptions
- External factors beyond your control
- Conditions that must hold for your logic to work
- Risks that could derail your project
🎯 Writing Strong Objectives
GOAL Level (Impact)
Characteristics:
- Addresses the broader problem from your Problem Tree
- Long-term (5-10 years)
- Your project contributes but doesn’t single-handedly achieve
- Often shared with other organizations
Good Goal Examples:
- “Improved livelihoods for smallholder farmers in Region X”
- “Reduced maternal mortality in underserved communities”
- “Enhanced educational outcomes for marginalized youth”
Poor Goal Examples:
- “Train 500 farmers” (This is an output, not impact)
- “Reduce poverty” (Too broad, not specific enough)
- “Our organization becomes well-known” (About you, not beneficiaries)
OUTCOME Level (Purpose)
Characteristics:
- Direct changes your project will achieve
- Medium-term (1-3 years)
- Changes in knowledge, behavior, conditions, or policies
- Measurable and attributable to your intervention
Good Outcome Examples:
- “Smallholder farmers adopt climate-resilient farming practices”
- “Community health workers provide quality maternal care services”
- “Youth develop job-relevant skills and find employment”
OUTPUT Level (Results)
Characteristics:
- Direct products of your activities
- Short-term (3-12 months)
- Completely under your control
- Quantifiable deliverables
Good Output Examples:
- “Farmers trained in climate-resilient techniques”
- “Community health workers certified in maternal care”
- “Youth complete vocational training programs”
📏 Selecting Quality Indicators
Types of Indicators
Quantitative Indicators:
- Numbers, percentages, ratios
- Easy to measure and compare
- Clear targets and thresholds
Examples:
- “80% of trained farmers adopt at least 3 new techniques”
- “Maternal mortality rate decreases by 25%”
- “70% of program graduates find employment within 6 months”
Qualitative Indicators:
- Changes in quality, perception, or satisfaction
- Descriptive evidence of change
- Often captured through stories and case studies
Examples:
- “Farmers report increased confidence in trying new methods”
- “Community members express satisfaction with health services”
- “Youth demonstrate improved communication skills”
Indicator Quality Criteria
SMART-ER Indicators:
- Specific: Clear and well-defined
- Measurable: Quantifiable or clearly observable
- Achievable: Realistic given resources and context
- Relevant: Directly related to your objective
- Time-bound: Clear deadline or timeframe
- Evaluable: Data can realistically be collected
- Resourced: You have budget and capacity to measure
Common Indicator Mistakes
Avoid These:
- Activity indicators as outcome indicators: “Number of trainings held” doesn’t show behavior change
- Impossible to measure: “Increased happiness” without defining how to measure happiness
- Too many indicators: Keep to 2-3 per objective level
- Vague language: “Significant increase” instead of specific percentage
📋 Sources of Verification
Primary Sources (You Collect)
Surveys and Questionnaires:
- Baseline and endline surveys
- Regular monitoring surveys
- Participant feedback forms
Observations and Assessments:
- Field visits and observations
- Skills assessments and tests
- Practice demonstrations
Administrative Data:
- Project records and databases
- Attendance and completion records
- Financial tracking systems
Secondary Sources (Others Collect)
Government Statistics:
- National and local government data
- Health, education, economic indicators
- Census and survey data
Partner Organizations:
- NGO and partner reports
- Academic research studies
- Industry associations data
Community Sources:
- Community leader reports
- Local media coverage
- Traditional record-keeping systems
⚠️ Managing Assumptions and Risks
Identifying Critical Assumptions
External Factors Beyond Your Control:
- Political and policy environment remains stable
- Economic conditions don’t deteriorate significantly
- Target communities remain accessible
- Partner organizations maintain capacity and commitment
Beneficiary Behavior Assumptions:
- Participants will attend training sessions
- Community members will adopt new practices
- Local leaders will support project activities
- Beneficiaries have basic prerequisite skills
Assumption Management Strategies
Risk Assessment Matrix:
| Assumption | Likelihood | Impact if False | Mitigation Strategy |
|---|---|---|---|
| Political stability | High | High | Monitor closely, develop contingency plans |
| Community participation | Medium | Medium | Strong outreach, incentive design |
| Partner capacity | High | Medium | Capacity building, backup partnerships |
Mitigation Approaches:
- Monitor: Track indicators of assumption validity
- Influence: Work to make assumptions more likely
- Plan: Develop contingency strategies if assumptions fail
- Accept: Some risks are unavoidable but manageable
🎨 Building Your Logframe Step-by-Step
Step 1: Extract from Theory of Change
- Review your Theory of Change canvas
- Identify the main impact, outcomes, and outputs
- Note key assumptions from your theory
Step 2: Structure the Logic
- Write goal statement (impact level)
- Define 2-3 outcome statements
- List 3-5 output statements
- Plan 5-10 main activities
Step 3: Develop Indicators
- 1-2 indicators per goal
- 2-3 indicators per outcome
- 1-2 indicators per output
- Use mix of quantitative and qualitative
Step 4: Plan Data Collection
- Identify data sources for each indicator
- Plan collection methods and frequency
- Estimate costs and assign responsibilities
Step 5: Test Assumptions
- List critical external factors
- Assess likelihood and potential impact
- Develop monitoring and mitigation plans
📥 Download Resources
🚀 Next Steps
After completing this lesson:
- Build your logframe using the Excel template
- Test with stakeholders to ensure logic makes sense
- Move to Lesson 2.2 on Activity Design to plan implementation
- Use your logframe as the foundation for proposal writing
Remember: Your logframe is a planning tool, not a rigid contract. Update it as you learn and circumstances change.