> 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/boneyard/copy-of-scope/mapping-outputs-to-outcomes.md).

# Mapping Outputs to Outcomes

A  ToC outlines the sequence of outputs and activities required to achieve desired outcomes. This structured mapping clarifies how outputs and activities are measured and how they contribute to overall goals. It establishes a clear connection between actions (outputs and activities) and their results (outcomes). To highlight theses connections we have separated out these causal chains into distinct service dimensions and their associated outputs and outcomes. 

Our interactive ToC enables users to focus on each the sequence of outputs and outcomes of each dimension of our service.

{% hint style="info" %}
You can use the filters and functions of our interactive ToC to explore these ToC's by following the guidance [here](/evaluation-framework/the-toolbox/theory-of-change/how-to-use-our-interactive-toc/orientation-to-toc-tool-the-kumu-platform.md). You can alsoclick and drag elements into space in order see their connections more clearly.  
{% endhint %}

### The Circle ToC

{% embed url="<https://embed.kumu.io/ecf76f9320531c99f61cacc695d1357b>" %}

### The Platform ToC

{% embed url="<https://embed.kumu.io/035d6087a049670fffda6ff8aada76b1>" %}

### The Teams ToC&#x20;

{% embed url="<https://embed.kumu.io/89a067da57eb8f11c803f8b9df2eb105>" %}

## Commons ToC

{% embed url="<https://embed.kumu.io/642b6a3ad30ab03e05df11c33c63e3ac>" %}


---

# 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/boneyard/copy-of-scope/mapping-outputs-to-outcomes.md?ask=<question>&goal=<endgoal>
```

`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.