> 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/using-toc-tool-to-see-how-we-measure-outcomes.md). # Using ToC tool to see how we measure outcomes Our Theory of Change (ToC) doesn’t just help us understand what we’re working towards—it also supports us in checking whether we’re getting there. In this view of the ToC, you can explore the **indicators** we use to evaluate progress across the three outcome domains: * Growth * Systems Maintenance & Co-production * Well-being, Relationships & Belonging In the interactive Kumu maps embedded below, **indicators are represented as small pale blue dots** connected to each outcome. These indicators describe the specific things we look at to understand whether change is happening, and how we know. Clicking on any outcome will reveal the indicators linked to it. Clicking on an individual indicator opens up a side panel with more detail on how we define and measure it. *** ## Systems Maintenance & Co-production Outcome Indicators {% embed url="" %} Clicking on an outcome within this domain (e.g. “Stronger community networks and partnerships”) highlights the indicators that tell us how we’re tracking that change. ***
## Growth Outcome Indicators
{% embed url="" %} These indicators relate to people’s security, control, and development over time—for both care workers and people receiving support. *** ## Well-being, Relationships & Belonging Outcome Indicators {% embed url="" %} These indicators focus on connection, trust, and emotional and social quality of life. This domain includes the highest number of indicators, as many of our outcomes cluster here. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://play.equal.care/evaluation-framework/the-toolbox/theory-of-change/using-toc-tool-to-see-how-we-measure-outcomes.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.