Français 
Deutsch 
Українська 
Across major donor reports, between 60% and 80% of grant applications are rejected not because the idea is weak, but because the project logic is opaque. The reviewer reads the proposal and cannot see how the listed activities will produce the promised change. The Logical Framework — known as the LogFrame or Logical Framework Approach (LFA) — is the tool that answers that question in ten minutes of reading. It is required, or implicitly expected, by virtually every major funder: the European Commission, USAID, UN agencies, the World Bank, Sida, and GIZ.
What the LogFrame Actually Is
A LogFrame is a 4×4 matrix that condenses the project's skeleton onto a single page. The rows describe four levels of results, from the long-term goal down to specific actions. The columns describe each level along four dimensions: the result statement, indicators, means of verification, and assumptions or risks.
The vertical logic answers "if–then": if we carry out the activities, then we deliver outputs; if outputs are delivered, then outcomes follow; if outcomes are achieved, then we contribute to the goal. The horizontal logic answers a different question: how will we prove it?
Matrix Structure
| Level | What it describes | Example (youth digital-skills project) |
|---|---|---|
| Goal / Impact | Long-term change the project contributes to | Reduced youth unemployment in the region |
| Outcome / Purpose | Behavioral change in the target group caused by the project | 500 graduates employed in IT within one year of training |
| Outputs | Concrete products delivered by the project | 1,000 course graduates; 30 certified trainers |
| Activities | Actions that produce the outputs | Curriculum design, recruitment, training, examinations |
How to Fill It In — Order of Operations
- Start at the top, work down. Begin with the Goal. This forces an early check: does your project actually align with the donor's strategic priorities? That alignment is the first filter every evaluator applies.
- Outcome is the field that matters most. The most common weakness is conflating Outcomes with Outputs. An Output is "training delivered." An Outcome is the change — "participants apply the new skills in their work." Funders pay for outcomes; outputs are how you get there.
- Make indicators SMART, with a baseline. Each level needs at least one quantitative and one qualitative indicator. Always include the baseline and target: "from 12% to 35% by project end."
- Be specific about means of verification. Not "reports," but "semi-annual M&E report following the donor's template; alumni survey six months post-graduation."
- Treat assumptions as risks in reverse. What must remain true in the external environment for your logic to hold? "The IT labor market remains in growth," "partner companies maintain their internship pipelines."
Three Mistakes That Cost Proposals at Evaluation
- Activities not mirrored in budget and workplan. Reviewers cross-check the matrix against the financial annex and Gantt chart. Any mismatch is an immediate red flag.
- Vague indicators. "Increased awareness" with no number and no measurement instrument is a wish, not an indicator.
- Assumptions that are actually internal risks. If the factor is under your control, it belongs in your risk-management plan, not in the assumptions column.
When the LogFrame Is Mandatory
For EU programmes (Horizon Europe, NDICI, IPA III, Erasmus+ KA2 Capacity Building) the LogFrame is a standard annex. USAID requires a Results Framework — a related but distinct tool built around Strategic Objectives and Intermediate Results. Private foundations (Mott, Open Society, Ford) rarely impose a fixed template, but reviewers still read your proposal through the same lens.
The honest test is simple: if your matrix holds together, you already have the skeleton of every other section — methodology, workplan, budget, and M&E. If it falls apart, the answer is to revisit the concept, not to rephrase the cover letter.