Logical Frameworks Explained Simply

The logical framework — the "logframe" — intimidates many municipal teams, but
its idea is simple: it is the project's chain of cause and effect, written so a
stranger can audit your reasoning. Donors require it because it forces you to
prove that your activities will actually produce the change you promise.

THE FOUR LEVELS

ACTIVITIES → OUTPUTS → OUTCOMES → IMPACT

- ACTIVITIES are what you DO: train, build, equip, organise.
- OUTPUTS are what you DELIVER, the direct products of activities: "300 youth
trained," "1 market constructed." They are within your control.
- OUTCOMES are the CHANGE that results: "220 trainees employed within 6 months,"
"vendor incomes up 25%." You influence these but do not fully control them.
- IMPACT is the long-term GOAL you contribute to: "reduced youth unemployment,"
"a more resilient local economy." Many actors contribute; you claim a share.

WORKED EXAMPLE
Activity: deliver a 4-month tourism-skills course → Output: 300 youth trained
(40% women) → Outcome: 220 placed in formal jobs → Impact: lower youth
unemployment and reduced out-migration.

THE TWO COLUMNS PEOPLE FORGET
A logframe is not just the results chain. Each level also needs:
- INDICATORS, BASELINES, AND TARGETS — how you will measure each result.
- MEANS OF VERIFICATION — where the proof comes from (payroll records, training
registers, a tracer survey).
- ASSUMPTIONS — the external conditions that must hold for the logic to work
(e.g., "the tourism sector continues hiring"). Naming assumptions shows mature
risk thinking, not weakness.

THE COMMON MISTAKE
Confusing outputs with outcomes. "Trained 300 youth" is an output; if your
proposal lists it as the outcome, reviewers conclude you are measuring effort,
not change — and effort is not what they are buying. Always push one level
further: trained for WHAT result?

Build the logframe BEFORE you write the narrative. If the chain holds together
in the table, the proposal almost writes itself.