What is a Program Logic?

A program logic maps visually what will be done (activity), with what resources (inputs), producing what outputs towards progressional outcomes (short, medium and long term outcomes). Essentially it provides a program of ‘actions’ for the achievement of the ‘theory of change’ goals.

It provides greater detail on the activity that will be undertaken to produce the required outputs than the Theory of Change by breaking down the larger programs of works into smaller implementable components. It maps this activity showing how it is shaped by inputs such as resources, and connects up to outputs such as course completions. It also details any limitations and/or assumptions around the activity, its inputs and outputs, and their relationship to producing the outcomes intended.

The Program Logic map may need to change and adapt as more is learnt about the relationships between the project’s inputs, activity, outputs and outcomes. As the project is implemented further limitations may arise that were not predicted and/or assumptions may need to shift as new knowledge about the relationships across the program logic components emerge.

How do you develop a program logic?

The program logic should be developed in partnership with key stakeholders who have an interest in the proposed activity to drive the outputs and outcomes. It may be developed with some or all of the stakeholders who were part of the development of the Theory of Change (ToC) depending on the type of project being implemented and the complexity of activity mapping and level of required identification of any limitations and or underlying assumptions related to the achievement or not of outcomes. The program logic should reflect the ToC and show how the activity and outcomes will answer the key evaluation questions. Did [activity A] produce [output A] leading to change(eg. Increase or decrease) to [outcome A] among the target participant [Group A].

Your program logic should be able to assist your monitoring and evaluation to determine, for instance:

  • If Activity A is the right activity to produce Output A?
  • If Output A actually causes change to Outcome A?
  • If there are other activities and/or Outputs that were not initially anticipated which need to be built into the program logic as they are ‘causally’ important to Outcome A?
  • If Outcome A is not changing as expected how might Activity A need to be adapted?
  • Is participant Group A being effectively targeted and participating in the project to experience Outcome A? Why not? Does Activity A need to change to better engage Group A?
  • Are other Groups being targeted by the project activity who were not intended to be participant groups? And what effect are they having on the project and its outcomes?

The key evaluation questions will depend on the interests of stakeholders and the ToC so shaping them together with the program logic supports stakeholder readiness for the results of the monitoring and evaluation. Further, stakeholder understanding of how the Project Logic maps execution of the project/program better supports the utilisation of the evidence to support the project/program’s success.

Program logic examples

For a brief visual introduction, take a look at this video here which introduces Program Logics used in a health service provision context.

An example of a simple program logic. Depending on the complexity of the project/program and the complexity of activity and outcomes being monitored and evaluated, a more complex program logic may need to be developed. For instance, where activity and outcomes need to be visually separated in some parts of the program, and connected up to show causality in others, you may detail these differing connections in your program logic. See an example of a more complex program logic here.

Developing a program logic for the first time can be challenging and the information on this page is only intended to provide an introduction to program logics. For further reading and guidance in developing a program logic please take a look at this guide and/or this video to assist you to go through the steps.

ACE Program Logic template

Diagram sourced from the Australian Centre for Evaluation | Templates, tools and resources | Template 2: Program logic [docx]

Developing your program logic outcomes

The outcomes should be measurable, tangible achievements directly connected to the Theory of Change outcomes. The Theory of Change provides a macro perspective of the types of achievements necessary to evidence the required changes are occurring in the ways needed (causality) to achieve the project/program goals. In contrast, the program logic outcomes provide much greater detail around what the various achievements looks like operationally.

The program logic outcomes essentially describe to readers how outcomes can be measured (indicator/metric) and what the target point (metric/indicator) is which will signal each outcome is ‘achieved’. The program logic outcomes provide greater granularity compared to ‘ToC’ outcomes, so the complexity of different achievements (short, medium and long term) and associated indicators to measure them, along with measurement targets, can be monitored and evaluated.