Project goal

Every well-run project needs a reason for existing that is bigger than any single activity. Logical Framework Analysis calls that reason the project goal.

The workbook's definition: the project goal is the "ultimate vision or the long-term impact the project seeks to achieve." It reflects the biggest change hoped for in a community, region, or issue — not the narrower, nearer-term change a single project cycle can finish.

Because it sits at the top, a goal is deliberately broad and aspirational. It answers three questions: what major challenge is being addressed, what long-term improvement is wanted, and how the project adds to the wider well-being of the people it serves.

A goal does not change from year to year. It stays fixed through the whole project, even across several project cycles, and even if no single cycle fully achieves it.

The project goal is the first of the Logical Framework Analysis's key components (Chapter 4, section 4.2.1), and it sits at the top of the workbook's logic-model chain:

Impact (linked to the goal) → Outcome → Output → Activities → Inputs

In the workbook's own worked case study — "Economic Empowerment of Rural Women Through Financial Literacy" — the project goal is stated as "Improved Economic Empowerment of Rural Women," measured with its own indicators, means of verification and assumptions, just like every other level of the logframe:

• Indicators: pre- and post-intervention surveys, economic data analysis
• Means of verification: surveys conducted before and after the intervention
• Assumptions: continued community support and political stability

Because a goal "may not always be fully achieved within a single project cycle," the workbook treats it as a direction to work towards across the project's whole life, not a single deliverable due on a fixed date.

Following the workbook's own case study; figures are illustrative.

A financial-literacy project for rural women sets its project goal as "Improved Economic Empowerment of Rural Women" across 40 villages over 5 years.

In year 1, the project trains 2,000 women in basic banking and budgeting (an output). By year 2, 1,600 of them (80%) report using a bank account regularly (an outcome). By year 5, household savings and income data across the 40 villages show a genuine rise in women's financial control — the impact, and the closest evidence yet of the project goal being realised.

Even at year 5, project staff cannot say the goal is "done" — the workbook's own case study treats the goal as an ongoing direction, verified by comparing household income and savings data before and after, rather than a box that gets ticked once.

Chapter 4 (Understanding Logic Model in Social Programs for Social Impact Assessment), section 4.2.1, defines the project goal and gives the three questions it must answer. Section 4.5's worked case study shows the goal stated, with its indicators, means of verification and assumptions. Expect a question distinguishing the project goal (broad, long-term) from the outcome (specific, immediate) in the same logframe.

• A goal is broad and aspirational; an outcome is specific and measurable. Confusing the two is a common error in logframe questions.
• Goals may not be fully achieved within a single project cycle — this is expected, not a sign of project failure.
• The project goal, like every other logframe level, needs its own indicators, means of verification and assumptions.
• Do not confuse the project goal with impact — the goal is the stated aim in the logframe design; impact is the enduring, evidenced consequence measured later, sometimes years afterward.