> 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/es/academia-de-planificacion-yo/yoplanning-parametrage/pour-creer-votre-planning-pour-la-future-saison-dans-yoplanning.md).

# Para crear tu agenda para la próxima temporada en Yoplanning

### Planificación avanzada de sesiones

Tienes la libertad de planificar sesiones futuras y prepararte para una temporada con mucha antelación, incluso antes de que concluya la temporada actual. Para ello, es necesario navegar por el cronograma y crear las sesiones en el lugar deseado.

#### Modificación de Precios

Si está considerando cambiar las tarifas, consulte el párrafo siguiente para obtener más información.

Si modificas tus precios, especialmente en productos, ten cuidado después de guardar de no pulsar en "Actualizar futuras sesiones" para no afectar a la temporada actual. Luego podrá crear sesiones en cualquier lugar en el futuro con los precios correctos. Esto es particularmente importante para mantener la integridad de los compromisos financieros con los asistentes y garantizar la coherencia de los precios en las diferentes sesiones programadas.


---

# 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/es/academia-de-planificacion-yo/yoplanning-parametrage/pour-creer-votre-planning-pour-la-future-saison-dans-yoplanning.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.
