Build a Theory of Change with AI

A 5-step prompt workflow that produces a complete Theory of Change with causal pathways, assumptions, risks, and an indicator framework. Run all prompts in a single AI conversation.

30-45 min6 stepsIntermediatePlanning

What you'll build

A complete Theory of Change with problem statement, causal pathway (activities to impact), assumptions table, risk register, and indicator mapping.

Before you start

  • Your program description or concept note
  • Target population and geographic context
  • Donor framework or strategic objectives the program aligns with (if applicable)
1Analyze the Problem

Start with the problem your program addresses. A strong problem analysis grounds the entire Theory of Change and prevents the common mistake of jumping straight to activities.

Step 1: Analyze the Problem

You are a senior M&E specialist. I need to build a Theory of Change for my program, starting with the problem analysis. Based on the program description I provide, produce: 1. **Problem statement** (2-3 sentences): What is the core problem? Who is affected? What are the consequences of inaction? 2. **Root causes** (4-6 causes): What drives this problem? Distinguish between immediate causes, underlying causes, and structural causes. Present as a simple causal chain, not a flat list. 3. **Affected population**: Who experiences this problem? How are different groups affected differently? 4. **Existing responses**: What is already being done about this problem (by government, other organizations, communities)? Where are the gaps? Here is my program description: [Describe your program, its goals, target population, and context]

If the root causes feel generic ("lack of awareness," "limited access"), push the AI to be more specific. Ask: "What specifically limits access? For whom? Why?"

2Map the Causal Pathway

Build the core logic: how your program activities lead to outputs, outcomes, and ultimately impact. This is the spine of the Theory of Change.

Step 2: Map the Causal Pathway

Based on the problem analysis, map the causal pathway for this program. Present it as a structured results chain: **Impact** (1 statement): The long-term change this program contributes to. **Outcomes** (2-4): The medium-term changes in behavior, practice, or conditions that the program expects to achieve. These should be measurable and time-bound. **Outputs** (3-6): The direct products or services the program delivers. Each output should logically lead to at least one outcome. **Activities** (5-10): The key activities that produce the outputs. For each level, explain the causal logic: WHY does this activity produce this output? WHY does this output lead to this outcome? Make the "because" explicit. Present the pathway as a structured table with columns: Level, Statement, Causal Logic ("because...").

The "because" column is the most important part. If you cannot explain why an activity leads to an output, the causal link is probably weak or missing a step.

3Identify Assumptions and Risks

Every causal link in your Theory of Change rests on assumptions. Making them explicit is what separates a useful ToC from a wishful one.

Step 3: Identify Assumptions and Risks

Review the causal pathway and identify the assumptions and risks at each level. **Assumptions table:** For each causal link (activity to output, output to outcome, outcome to impact), identify: - The assumption (what must be true for this link to hold) - Current evidence for or against this assumption - How you will test or monitor this assumption during implementation - What happens to the program logic if this assumption fails **Risk register:** Identify 5-8 risks that could prevent the program from achieving its outcomes. For each: - Risk description - Likelihood (high, medium, low) - Impact if it occurs (high, medium, low) - Mitigation strategy - Who is responsible for monitoring this risk Focus on risks that are specific to this program and context, not generic risks that apply to any development program.

The most useful assumptions are the ones you are least sure about. If you are certain an assumption holds, it is not adding analytical value to the ToC.

4Map Indicators to the Pathway

Assign at least one indicator to each level of the results chain so you can actually measure whether the Theory of Change is playing out as expected. This is a preliminary mapping. If you plan to build a full MEL plan, the Indicator Development and MEL Plan workflow guides go deeper on operational definitions and targets.

Step 4: Map Indicators to the Pathway

For each level of the causal pathway (outputs, outcomes, impact), propose SMART indicators. Present as a table with columns: - Results level (output/outcome/impact) - Result statement - Proposed indicator - Data source - Collection frequency - Baseline status (known, needs collection, or not applicable) Include 1-2 indicators per output, 1-2 per outcome, and 1 for the impact level. Prioritize indicators that are: - Feasible to collect with typical program resources - Sensitive enough to detect change within the program timeframe - Clearly linked to the causal pathway (not generic sector indicators) Also propose 2-3 assumption-monitoring indicators: indicators that track whether key assumptions are holding, not just whether results are being achieved.

Assumption-monitoring indicators are what make a ToC a living document instead of a one-time planning exercise. If an assumption fails, you want to know early.

5Write the Narrative Summary

Pull everything together into a coherent narrative that explains the Theory of Change to stakeholders, donors, and the program team.

Step 5: Write the Narrative Summary

Write a Theory of Change narrative summary (800-1200 words) that synthesizes everything we have built. Structure it as: 1. **Context and problem** (150-200 words): The problem, who it affects, and why it persists. 2. **Program logic** (300-400 words): How the program intervenes, the causal pathway from activities to impact, and the key "because" logic at each transition. 3. **Assumptions and risks** (200-250 words): The critical assumptions the logic depends on, the biggest risks, and how they will be monitored. 4. **Measurement approach** (150-200 words): How the program will know whether the ToC is working, including the role of assumption-monitoring indicators. Write for a mixed audience of program staff, donors, and partners. Be direct and specific. Avoid jargon where plain language works. The narrative should be understandable to someone who has not seen the diagram.

A good ToC narrative reads as a convincing argument, not a list of boxes. If you remove the headings and it still makes logical sense, the narrative is strong.

Score Your Theory of Change

Use MEStudio's scoring rubric to check the quality of what you just built. Send this prompt in the same conversation to get a scored assessment with specific revision suggestions.

Open the scoring rubric

If any dimension scores below 4, go back to the relevant step and ask the AI to strengthen that section. The rubric tells you exactly what to fix.

Not sure which AI tool to use?

Try the AI Tool Selector to find the best tool for your specific M&E task, or browse 130+ M&E-specific prompts.

Related Resources