> For the complete documentation index, see [llms.txt](https://play.equal.care/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://play.equal.care/evaluation-framework/the-toolbox/theory-of-change/what-is-a-theory-of-change.md).

# What is a Theory of Change?

A way to map how change happens - and how we know if it’s working

A **Theory of Change (ToC)** is a structured way of describing how and why a particular change is expected to happen. It maps out the steps between what a service or project *does* and the change it *wants to see*. It shows the links between activities, outputs, outcomes, and longer-term impacts — so we can track whether we’re on the right path and adapt when we’re not.

That might sound quite formal, but it’s actually something we all do, often without realising.

***

## Everyday theories of change

Think of the last time you tried to set yourself up for a good start to your morning. You possibly did something like this:

* Set your alarm early
* Planned time for a stretch or a walk
* Made space for breakfast before leaving the house

Why? Because over time, you’ve developed a theory (even if unspoken) that says:\
**“If I get up early and have time to ease into the day, I’ll feel more grounded and less rushed.”**

That’s a theory of change.

It’s based on past experience, a sense of cause and effect, and a belief that one thing leads to another. But it’s also not guaranteed. Some mornings, that alarm rings… and things don't go to plan!

***

## Why a ToC needs testing, too

A good Theory of Change recognises that things don’t always go as expected. It invites us to ask:

* Are our assumptions holding true?
* Did our action (setting the alarm) lead to the output (getting up early)?
* Did the output lead to the outcome (starting the day feeling calm and in control)?
* What other factors got in the way (e.g. traffic jams, sudden responsibilities, a bad night’s sleep)?

By mapping this out in a transparent way, a Theory of Change gives us a shared starting point for learning, helping teams reflect, adapt, and make better decisions as they go.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://play.equal.care/evaluation-framework/the-toolbox/theory-of-change/what-is-a-theory-of-change.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
