> 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/faq/faq-generale/comment-massurer-que-la-ligne-non-assignee-soit-vide-pour-le-lendemain.md). # How can I ensure that the "unassigned" line is empty for the next day? ### Introduction To ensure optimal scheduling, it's important to verify that **all sessions have assigned staff**. Leaving a session "unassigned" could lead to oversights or errors in activity management. Here's how to ensure the "unassigned" line is empty for the next day. **Question:** How do I ensure that the "unassigned" line is empty for the next day? ### Checking for unassigned sessions #### **1. Access the session list** * In the **left menu**, click on **"Sessions"**. #### **2. Filter by date** * Select the **start and end date** corresponding to the day to be checked. #### **3. Filter by "Unassigned Staff"** * Enable the filter to only display sessions where **no staff is assigned**. **By following these steps, you ensure that all sessions are correctly assigned and avoid organizational errors.** ### **Important: taking into account active filters** * On the **graphic schedule**, a **security feature prevents hiding an activity containing participants**, even if the staff has been deleted. * **Beware of active filters**: if a staff filter is applied to your schedule, some sessions may appear as **"unassigned"**, making verification ineffective. ### Conclusion By using session filters and regularly checking your schedule, you can ensure that **all sessions the next day have assigned staff**. Consider disabling staff filters for a complete and reliable view. ### Introduction To ensure optimal scheduling, it's important to verify that **all sessions have assigned staff**. Leaving a session "unassigned" could lead to oversights or errors in activity management. Here's how to ensure the "unassigned" line is empty for the next day. **Question:** How do I ensure that the "unassigned" line is empty for the next day? ### Checking for unassigned sessions #### **1. Access the session list** * In the **left menu**, click on **"Sessions"**. #### **2. Filter by date** * Select the **start and end date** corresponding to the day to be checked. #### **3. Filter by "Unassigned Staff"** * Enable the filter to only display sessions where **no staff is assigned**. **By following these steps, you ensure that all sessions are correctly assigned and avoid organizational errors.** ### **Important: taking into account active filters** * On the **graphic schedule**, a **security feature prevents hiding an activity containing participants**, even if the staff has been deleted. * **Beware of active filters**: if a staff filter is applied to your schedule, some sessions may appear as **"unassigned"**, making verification ineffective. ### Conclusion By using session filters and regularly checking your schedule, you can ensure that **all sessions the next day have assigned staff**. Consider disabling staff filters for a complete and reliable view. --- # 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/faq/faq-generale/comment-massurer-que-la-ligne-non-assignee-soit-vide-pour-le-lendemain.md?ask=&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.