> 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/equal-cares-model/teams/team-starting/6.-building-a-team.md).

# 6. Building a team

<figure><img src="/files/65F6L3s2fvMfkIqmNsbv" alt="" width="563"><figcaption></figcaption></figure>

Support needs change, lives shift, and people move on. One of the strengths of the Teams model is its flexibility: it allows for new team members to be welcomed in when needed: always by consent, and always with the team’s values and dynamics at heart.

This stage builds on the trust and clarity already established. Adding someone new to the team isn’t just a logistical step, it’s a relationship-building one. The way that person is found, introduced and welcomed can make all the difference to how well the team continues to work together.

In this section, we explore how new members are identified and brought in, including:

* How teams search for new members through the platform or their networks
* Who gets involved in that decision and how consent is handled
* The importance of introductions, shadowing and warm welcomes
* How trial periods work and why they matter
* What happens when someone new *isn’t* a good fit, and how to manage this with care

{% hint style="info" %}
Each team handles this slightly differently, and that’s okay! The aim is to offer a consistent framework that still gives space for the unique context and preferences of each team.
{% endhint %}


---

# 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/equal-cares-model/teams/team-starting/6.-building-a-team.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.
