> 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-pour-le-parametrage/affecter-les-moniteurs-selon-leurs-competences.md).

# Assign monitors according to their skills

### The question

"I've assigned skills (tags) to my instructors, and I'd like Yoplanning to only suggest instructors with the required skill for that product. For example, a dive exploration requires the "DP" skill. I can't seem to make the connection, how do I do that?"

***

### The short answer: you have to reason in the opposite direction.

Yoplanning **does not manage a skills repository** that would be automatically compared to a requirement entered on the product. There is no "required skill" field on a product.

The reasoning is reversed:

* You do not leave **not** from the monitor (“he has the DP, so suggest it on the explos”).
* You start **from the product** ("for this product "Explo diving", here is the list of instructors who can supervise it").

This list is called **potential staff**. You only include instructors who actually possess the necessary skills. **This list is what matches sessions with instructors.**

{% hint style="info" %}
In summary: competence is not a property that the software reads from the monitor; it's a **decision you express on a product-by-product basis**, by choosing who appears in your potential staff.
{% endhint %}

***

### So what is the purpose of the staff tags then?

The tags placed on the staff profiles ("Diving", "DP", "English", "Senior Coach"...) are a **visual sorting and filtering tool**. They help you quickly find the right people in the staff list and on the schedule.

On the other hand :

* a tag **does not restrict** the assignments;
* a tag **does not trigger any automatic monitor suggestions** on a product;
* A tag is **never compared** to the content of a product.

Tags remain very useful as **support for your settings**: filter your staff on the "DP" tag to know exactly who to add as potential staff on your exploration products.

To create and manage these tags, see [Sort and classify staff on the schedule](/en/yoplanning-academy/yoplanning-parametrage/gestion-staffs/trier-et-classer-les-staffs-sur-le-planning..md).

***

### How to do it, in practice — diving example

Objective: that the "Explo diving" product is only supervised by instructors holding the DP qualification.

1. **Identify your competent instructors.** In **Menu > Administration > Staff**, filter by the tag "DP" (if you have set this tag). You will get the exact list of people to retain.
2. **Open the relevant product.** **Menu > Administration > Products**, then "Explo Dive".
3. **Complete the "Potential Staff" section.** Add only the monitors identified in step 1. **Do not add anyone else:** any monitor on this list is considered suitable to supervise this product.
4. **Record**, then repeat for each product with a specific requirement.

A monitor can obviously be a potential staff member on several products. A monitor without the DP will simply remain absent from the list of "exploit" products.

The detailed procedure, as well as the reverse method (starting from a monitor and assigning all its products to it at once), are described in [Defining the potential staffs of a product](/en/yoplanning-academy/yoplanning-parametrage/parametrage-produit/les-produits-qui-seront-utilises-sur-votre-planning/definir-les-staffs-potentiels-dun-produit.md).

***

### What this setting brings you next

Potential staff are the driving force behind the [**AI Planning**](/en/yoplanning-academy/yoplanning-parametrage/le-planning-ia.md), meaning **potential** sessions offered for sale but not yet scheduled. Once your lists are complete:

* **Availability of potential sessions:** The sale of a potential session is calculated based on the availability of the declared potential instructors. If none of them are available during that time slot, the activity is no longer offered online — you never sell an activity that no one can lead.
* **Automatic allocation**: When a potential session is booked, it is automatically assigned to an available potential monitor, according to the priority order you have defined in the staff list.
* **Number of simultaneous sessions**: The number of explosions you can sell in parallel depends directly on the number of potential monitors declared on the product.

***

### Points to be aware of

{% hint style="warning" %}
**Potential staff do not lock in assignments.** They indicate who is *in principle* qualified to lead a product; they do not restrict what you can enter on the schedule. Assigning a monitor to a session who is not listed among the product's potential staff is perfectly possible, **and it's common practice** — last-minute replacement, team arrangement, or a constraint of the day. Therefore, competency-based control relies on the quality of your lists, not on a software lock.
{% endhint %}

{% hint style="info" %}
**A session placed on the standard schedule has a life of its own.** Once it is created on the schedule and made available for online booking, it remains sellable **regardless of the staff assigned to it** — including an instructor who is not part of the potential staff, or a subsequent instructor change. The potential staff only manage the availability of **potential** sessions, those that are not yet scheduled.
{% endhint %}

* A product with no potential staff does not appear in the AI ​​Planning. See [Resolution of the problem of products not displayed in the AI ​​Planning](/en/faq/faq-pour-le-parametrage/resolution-du-probleme-des-produits-non-affiches-dans-le-planning-potentiel-sur-yoplanning.pro.md).
* **Keep the lists up to date**: a new qualified instructor, a departure, a qualification obtained during the season must be reflected in the products concerned (or, more quickly, from the staff sheet).
* **The tag filter works in "OR" mode:** selecting "DP" and "English" displays staff members who have one **or** the other, not both. Filter tag by tag to build your lists.

***

### In summary

| What you want                                              | The Yoplanning tool                                                       |
| ---------------------------------------------------------- | ------------------------------------------------------------------------- |
| Find/filter instructors with a qualification               | The **tags** on the staff profile                                         |
| Determine who can supervise a given product                | The **potential staff** of the product                                    |
| Only offer online time slots that can actually be managed. | Potential Staff + **AI Planning**                                         |
| Automatically assign a monitor to a potential session      | Potential staff + **order of priority** of staff                          |
| Place whomever you want on a pre-scheduled session         | The **assignment** from the schedule, free and without effect on the sale |


---

# 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://docs.yoplanning.support/en/faq/faq-pour-le-parametrage/affecter-les-moniteurs-selon-leurs-competences.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.
