Causal pathway

A project team usually has a rough idea of why their work should lead to change. A causal pathway is what happens when that rough idea is written down as a proper chain of cause and effect.

The workbook describes the Theory of Change as "a structured thinking process that allows project teams to turn their theories about what needs to change and why into a 'causal pathway.'"

It is not a general theory of how change happens in the world. The workbook is explicit that a Theory of Change "is not a general theory of how change happens. It is specific to the project initiatives" — so a causal pathway is always built for one particular project, not borrowed wholesale from another.

The workbook ties the causal pathway to two design features of a Theory of Change:

1. It runs backwards from the goal. Building the pathway is described as "a step-by-step, backwards mapping process through which all project activities determine all the preconditions necessary to reach an ultimate vision." The starting point is the destination, not the first activity.
2. It rests on explicit assumptions. A Theory of Change "explicitly highlights the causal links between program activities, intermediate outcomes, and long-term outcomes. It involves identifying and testing the assumptions underlying these causal pathways." The pathway is not just a sequence of steps — each link in the chain carries an assumption about why that step should lead to the next.

Contrast this with a Logic Model, which the same workbook table describes as depicting causal relationships "but it may not delve as deeply into the underlying theories and assumptions. It tends to present a more straightforward cause-and-effect sequence." A causal pathway is the Theory of Change's deeper, assumption-explicit version of that same basic idea.

Illustrative example.

A rural non-profit builds a causal pathway for its youth-employment programme:

Ultimate vision: 80% of rural youth aged 18–25 secure stable, well-paying jobs within five years. Working backwards: Jobs secured ← Employers willing to hire ← Youth hold in-demand skills ← Youth complete a technical training programme ← Youth are motivated to enrol and stay enrolled ← Financial support from donors and local business partnerships exist.

Each backward step names a precondition, and each precondition carries an assumption — for instance, that "young individuals are motivated to attend and complete the training programmes." If that assumption turns out to be false in practice — say, enrolled youth drop out because the stipend is too small to offset lost daily-wage income — the causal pathway itself tells the project team exactly which link broke, rather than leaving them only with the fact that the final jobs target was missed.

Chapter 6 (Social Impact Assessment Frameworks, Techniques and Standards), section 6.1.1 (Theory of Change), introduces the causal pathway as the product of the ToC's backwards-mapping process. Expect a question distinguishing a causal pathway's assumption-driven depth from a Logic Model's more linear cause-and-effect sequence.

• A causal pathway is built for one specific project, not as a general theory of social change — the workbook states this distinction explicitly.
• It is constructed working backwards from the final goal, identifying preconditions at each step — do not describe it as being built forwards from activities, which is closer to how a Logic Model is typically read.
• Assumptions are an integral part of the causal pathway, not a separate afterthought — testing those assumptions is described as part of building the pathway itself.
• Do not confuse causal pathway with backwards mapping as a standalone term — backwards mapping is the process used to build the causal pathway; the causal pathway is the result of that process.