# Outputs

Key outputs are the immediate results of the organization's activities. These outputs are essential milestones that serve as indicators of progress towards achieving the desired outcomes. By documenting these outputs, the ToC provides a tangible basis for monitoring and evaluation, ensuring that each step in the process is contributing effectively to the ultimate goals. 

We have grouped these outcomes under 4 key service dimensions:

<details>

<summary>Circle Dimensions</summary>

Outputs include:

* Multi-stakeholder service evaluation measures the social climate, individual well-being and quality of life of Circle members.
* Circles recruit locally to support locally.
* Key roles for circles to start and support teams are shared amongst circle members as " Circle Hats".
* Circles resource teams with local volunteers.
* Circles resource teams with local volunteers.
* Circles connect teams to local resources and community networks that can enrich the quality of lives of team members.
* Circles connect teams to local resources and community networks that can enrich the quality of lives of team members.
* Teams are started, supported and ended through local circles.
* Teams are started, supported and ended through local circles.
* Circles operate semi-autonomously from the wider coop with distributed decision-making authority.
* Key roles or "Circle Hats" are nominated by circle members sociocratically<br>

</details>

<details>

<summary>Platfrom Dimensions</summary>

Outputs include:

* People receiving support and their families can see and interact with their care data.
* Communication and coordination tools enable collaboration between formal and informal care and support.
* Platform clarifies relationships, roles & responsibilities with Teams and Circles i.e. "Hats"
* The platform facilitates giving and receiving informal support through a Care Coin system (gift, save, spend).
* Care Plans "Supportive Conversations" identify the relationships that promote people's well-being and meet their quality of life needs.
* The platform helps teams and circles access local resources that enrich quality of life.

</details>

<details>

<summary>Team Dimensions </summary>

Outputs Include:

* Teams collaborate with the social workers and/or other social care professionals supporting the people they care for.
* People receiving care build their own team, choosing friends, family members, local volunteers and vetted Equal Care workers as team members.
* Key operational roles for each team to self-manage shared amongst team members as "Team Hats".
* Teams operate semi-autonomously from the local circle with distributed decision-making authority.
* Care workers choose what their hours are and where they will work.
* Peer learning communities, observation, training, and coaching are team-specific.
* Care workers are paid more.
* Key roles or "Team Hats" are nominated by team members sociocratically.&#x20;
* Multi-stakeholder service evaluation measures the social climate, individual well-being and quality of life of Team Members.&#x20;
* People giving and getting support consent to each other in a mutual match.

</details>

<details>

<summary>Commons Dimensions</summary>

Outputs include:

* Commons resource circles with volunteers
* People gift time, skills, and resources to teams and circles.
* Commons connects circles to local resources and community networks that can enrich the quality of lives of team members.
* Local circles have diverse and representative memberships, including other organizations with common values.
* Circle establishes partnerships with local community hubs and anchor organisations to expand service offerings.
* Service evaluation measures cooperative connections between teams, circles and local community networks.

</details>

See the interactive ToC map below highlighting these four key service dimensions and their respective outputs.&#x20;

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


---

# Agent Instructions: 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:

```
GET https://play.equal.care/boneyard/copy-of-scope/outputs.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.