> For the complete documentation index, see [llms.txt](https://docs.yoplanning.support/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yoplanning.support/en/yoplanning-academy/yoplanning-au-quotidien/planning-et-indisponibilites-avec-yoplanning/definir-une-indisponibilite-pour-un-membre-de-lequipe/scinder-les-indisponibilites.md).

# Split unavailability

### What is the "Split Unavailability" feature for?

This feature allows you to insert a session in the middle of a staff unavailability period. This automatically splits the unavailability into two, before and after the added session.

It is useful when, even if a staff member is noted as unavailable (for example, for a whole day), they exceptionally agree to provide a session at a specific time.

### How to use the "Split Unavailability" feature?

#### Detailed steps

1. **Access the schedule**:
   * From the **Graphic Planning**.
2. **Identify unavailable staff**:
   * A gray area appears on their schedule at the time they are unavailable.
3. **Drag a session onto this gray area**:
   * Create a new session or move an existing one within the downtime period.
4. **Confirmation window**:
   * Yoplanning displays an alert indicating that the staff is unavailable.
   * You are offered to **split the unavailability** to insert the session.
5. **Validate the action**:
   * By confirming, the unavailability is automatically split:
     * There is still unavailability before the session.
     * Another one is created after the session.
   * The session is successfully assigned to the selected staff.

### Best practices

* Use this function only if you have received confirmation from the staff.
* Add a comment to the session to keep track of this exception.
* Check that the remaining unavailability does not cover other slots that the staff may have accepted.

### In summary

The "Split Unavailability" feature is a smart, automatic tool in Yoplanning for managing exceptional cases. It facilitates organization while ensuring data consistency across the schedule. This feature can only be used when dragging and dropping on the schedule.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.yoplanning.support/en/yoplanning-academy/yoplanning-au-quotidien/planning-et-indisponibilites-avec-yoplanning/definir-une-indisponibilite-pour-un-membre-de-lequipe/scinder-les-indisponibilites.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.