> 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/dealing-with-conflict-and-change/how-to-leave-a-team-well.md).

# How to leave a team well

Supporting teams through departures in ways that honour relationships, ensure continuity, and offer opportunities for reflection

<figure><img src="https://1956200314-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MN8VA8CjNRwZEdN7ikK%2Fuploads%2F2SEvwfyvU2E96uLAHSiM%2FArm%20around%20rainbow.png?alt=media&amp;token=1beb7398-8d88-4af5-a51d-6d0c41ff328e" alt="" width="563"><figcaption></figcaption></figure>

Teams form through trust and shared purpose and like all relationships, they change over time. People leave for many reasons, and while the departure can feel significant, it doesn’t have to be difficult. When handled with openness and care, endings can reinforce the strength of the team rather than disrupt it.

## Common reasons for leaving a team

* A shift in personal circumstances or availability
* Changes in health, energy or wellbeing
* Stepping into a new role or responsibility
* A sense that the fit or focus isn’t quite right
* Unresolved tensions or dynamics that haven’t improved over time

In most cases, leaving marks the next stage of a journey: not a failure, but a transition.

## Helpful practices when someone is preparing to step back

* **Sharing the decision early**: Where possible, the intention to leave is shared in advance so the team can make plans. This reduces disruption and offers time to reflect or adapt.
* **Notifying the Team Owner**: Ideally, the news is communicated directly to the Team Owner. If this feels difficult, another team member or a Coach can help.
* **Using the chat for farewells**: A message in Team Chat often provides a helpful point of closure, where appreciations can be shared and the contribution acknowledged.
* **Offering insight**: Reflections about what’s worked well, and what could be improved, are welcomed - especially if shared constructively.
* **Handover of responsibilities**: If team roles or hats are held by the person leaving, these can be reviewed and reallocated before departure. The Circle or Coach can support this process.

## Supporting the wider team

A departure can raise feelings of sadness, disappointment - even relief. When recognised and spoken about with compassion, these emotions can strengthen a team’s sense of trust. In some cases, a facilitated check-in or reflection can help the group move forward with clarity and care.

## When things are unresolved

If a departure follows conflict or an unresolved issue, extra support may be offered by the Circle or Coach to help ensure the handover is respectful and the remaining team feels steady.

## Keeping the door open

Leaving a team well helps maintain goodwill and connection. Many people go on to support others through the co-operative, or return to the team at another stage. The emphasis is always on learning, mutual respect and continuing the wider work of care.


---

# 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/dealing-with-conflict-and-change/how-to-leave-a-team-well.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.
