EvalCompassEvalCompass
Design & theoryInternational developmentProject managementPDMIndicatorsExternal conditions

Logical Framework (Logframe / LFA)

Logical Framework (Logframe / LFA)
Also known as: Logframe、LFA、Project design matrix (PDM)、Project cycle management (PCM)

A planning and monitoring table linking each level of objectives to indicators, verification sources and external conditions. It identifies what is needed to move from activities to outcomes. [1]

Project design matrix (PDM) worksheet — openReferences and checked sections
Difficulty
Intermediate
Cost
Low
Duration
Illustrative estimate (adjust for scale and staffing): 1–3 days (PDM development workshop)
Content updated: 2026-09-13Source checked: 2026-09-13 (includes AI cross-checking)No documented human reviewIncludes fictional examples

How it works at a glance

A logframe distinguishes activities, direct outputs, changes for participants and broader objectives, alongside indicators, information sources and the external conditions needed. Formats and terminology vary by organization. [1]

During preparation, read links between levels as conditional statements and monitor changes in assumptions during implementation. Completing the table does not establish causation; plan the necessary observations and analyses separately. [1]

Narrative summaryIndicatorMeans of verificationExternal conditionsOverall goalProject purposeOutputsActivitiesVertical logic: activities → outputs → purpose → goal+ external conditions → next level
A 4 × 4 matrix with four levels of objectives vertically and indicators, means of verification, and external conditions horizontally. Read the vertical logic together with the external conditions in a zigzag.

When to use it and when it is unsuitable

When to use it

  • Throughout planning, consensus building, monitoring and evaluation of ODA and international development projects
  • When a recipient organization requires a logframe or PDM. Check its specific format and definitions before use.
  • Agreeing on a shared hierarchy of objectives in projects involving multiple donors or implementing agencies
  • As a reference document for monitoring plans, midterm evaluation and final evaluation after project approval

When it is unsuitable

  • Fixing objectives and indicators without updating them. Revise them as circumstances require.
  • Imposing excessive documentation on a program that needs only a brief check. Choose a format and level of detail suited to its purpose.
  • Estimating causal effects requires a design for examining causation in addition to preparing the table.

Participants, roles, and deliverables

Participants and roles

Program officers, evaluation officers and key stakeholders. Include people who can verify the plan’s assumptions.

Main deliverables

  • Project design matrix (PDM)
  • Problem and objective trees
  • Plan of operations (PO)

Implementation steps

  1. Problem analysis (problem tree)
    Brainstorm current problems and challenges and visualize cause-and-effect relationships in a problem tree. Roots represent causes, the trunk the central problem and branches the consequences.
  2. Objective analysis (objective tree)
    Convert each element of the problem tree into a positive state to create an objective tree. Resolved problems become the objectives.
  3. Analyze alternatives
    Select the parts of the objective tree the project will address (its scope), and compare and select alternative approaches.
  4. Enter the PDM hierarchy of objectives
    Enter the overall goal, project purpose, outputs and activities in their respective rows. State each objective in terms of who does what and to what level.
  5. Set objectively verifiable indicators (OVIs)
    Set objectively verifiable indicators for each objective. Following SMART criteria, specify quantity, quality and deadlines.
  6. Identify means of verification
    Record the data source and means used to verify each indicator, such as survey reports, administrative statistics and site visit records. Check cost and feasibility.
  7. Record external conditions
    Record the assumptions needed to achieve each objective level (necessary conditions outside the project). Link high-risk conditions to the risk management plan.
  8. Check the logic
    Check both vertical logic (if–then) and horizontal consistency (whether indicators measure objectives correctly). Revise the PDM periodically after its initial preparation.

Strengths and limitations

Strengths

  • Brings objectives, indicators, information sources and assumptions together in a common table for stakeholder discussion.
  • Provides an overview of objectives, indicators, means of verification and external conditions from which a monitoring plan can be developed directly
  • Established procedures from problem analysis to PDM preparation enable beginners to proceed systematically

Limitations

  • An overly rigid format cannot reflect changing circumstances. Review it regularly and record reasons for changes.
  • Focusing only on indicator achievement rates may miss unintended changes and benefits that are difficult to measure.
  • A concise table alone cannot easily show multiple pathways or cycles. Add explanatory diagrams or text as needed.

Common pitfalls

  • Confusing the project purpose with the overall goal: the purpose is the situation the project should achieve; the overall goal is the broader objective beyond it
  • Using only counts of activities as indicators, without measuring changes for participants (outcomes)
  • Avoiding real risks by listing external conditions that are too obvious, such as “no war,” or too optimistic, such as “strong government commitment”
  • Assuming one PCM workshop is sufficient and not revising the PDM after midterm evaluation

Conditions of use and evidence

  • Logframe formats vary by organization; there is no single universally fixed template. [1]
Fictional example; not actual results

Setting out counseling outcomes and external conditions

The following fictional example illustrates the design of a 1-year community project combining counselor training and counseling accompaniment.

Hierarchy of objectivesIndicators (OVI)Means of verification for indicatorsExternal conditions (assumptions)
Overall goal: improved access to needed supportProportion of people able to use support for their difficultiesFollow-up records based on consentThe relevant scheme continues
Project purpose: residents who wish to apply proceed with applicationsNumber of the 20 interested residents who proceed with applicationsCounseling and application status recordsA service meeting scheme requirements is available
Output: counseling and accompaniment provided20 first-time counseling users; accompaniment sessions for those requesting themImplementation records with duplicates removedThe individual wishes to participate
Activities: counselor training and accompaniment coordination2 training sessions and staff assignmentsTraining records and rostersCounselors are available to participate

Common errors in judgment

Common mistake

Writing “staff make an effort” as an external condition

How to revise

Place staffing in activities or inputs, and service intake conditions under external conditions

ReasonThis distinguishes actions under management control from external influences.

Common mistake

Imposing the same 4-row, 4-column format on every program

How to revise

Check the commissioning organization’s format and specify outcome levels and definitions

ReasonLogframes have multiple formats.

Organize your thinking by writing

Project design matrix (PDM) worksheet

A practical template is available to fill in and print on A4 paper.

Open worksheet

Related methods

Logic ModelTheory of ChangeIndicator DesignEvaluation Design Matrix

References and checked sections

  1. Logframe
    BetterEvaluation
    Section consulted
    Main text; Advice for using this method
    How it relates to the text
    Logframe formats vary by organization; there is no single universally fixed template.
    Source checked: (includes AI cross-checking)

Editorial and checking information

Content updated: Source checked: (includes AI cross-checking)No documented human reviewIncludes fictional examplesEditorial policy and scope of checkingCite this pageReport a correction

How to cite this page

EvalCompass Editorial Team. “Logical Framework (Logframe / LFA)”. EvalCompass, updated 2026-09-13. https://evalcompass.jun-nakatani.com/en/methods/logical-framework/
Add the date you accessed the page. Text created by this site is available under CC BY 4.0. Quotations, external materials, and bundled fonts have their own terms of use. When reusing content, credit the source, link to the license, and indicate any changes.

Suggest a correction or improvement to this page

Change history
  • — Updated explanations to correspond to the sources and added method-specific fictional completed examples, judgment examples and a change log.