BDESE settings

Two settings weigh on the BDESE calculations: the statistical confidentiality threshold, which protects anonymity in breakdown tables, and how your workspace’s exit and absence types are mapped to BDESE reasons, on which the departure and absenteeism indicators depend. This article explains the Settings tab: setting the threshold, checking and correcting the mappings, and knowing when these settings take effect. It is aimed at the module’s administrators.

Before you start #

• The BDESE module is installed in your workspace.
• The tab requires the BDESE module settings right. At Access level, you read the settings; at Execute level, you change them. Among the roles provided, only the Administrator role carries this right.
• The settings apply to the whole workspace, and therefore to every database.
• Exit and absence types come from your workspace: the termination reasons in the list of exit types, and the absence types defined in your workspace. Their labels are shown in the screen’s language.

Opening the settings #

In the menu, open BDESE › Settings. The tab shows three cards: Statistical confidentiality, Exit types and Absence types.

Without Execute level, the threshold is shown as text (for example “5 people”) and the reasons are shown without a drop-down list.

Setting statistical confidentiality #

In the BDESE breakdown tables, a cell counting fewer people than the threshold is hidden, so that no one can be identified. The total stays exact. The default threshold is 5 people.

1. In the Statistical confidentiality card, enter the new value in the Threshold (people) field: a whole number between 3 and 50.
2. Click Save. The button stays greyed out while the value is not valid or has not changed.
3. The message “Threshold saved.” confirms.

A higher threshold hides more cells: it protects anonymity better, at the cost of less detail for the CSE. A lower threshold shows more detail in small populations.

Mapping exit types to departure reasons #

The BDESE presents departures by reason (art. R2312-9). Each exit type in your workspace must therefore be filed under one of the BDESE reasons: Resignation, Redundancy, Dismissal on other grounds, Mutual termination, End of fixed-term contract, End of probation, Transfer, Retirement, Death or Other.

1. In the Exit types card, find the row of the type to set in the Workspace type column.
2. In the BDESE reason column, choose the reason from the drop-down list.
3. The choice is saved at once: the message “Mapping saved.” confirms.

Mapping absence types to absenteeism reasons #

Likewise, the BDESE presents absenteeism by reason. Each absence type in your workspace is filed under one of the reasons: Illness, Work accident, Commuting accident, Occupational disease, Maternity, paternity, Authorised leave, Paid holidays or Other.

1. In the Absence types card, find the row of the type to set.
2. Choose the reason in the BDESE reason column.
3. The message “Mapping saved.” confirms.

If the workspace has no type in a family, the card states “No type defined in the workspace.”

The “Suggested” badge #

As long as no one has set a row, Illizeo suggests a reason based on the type’s label: a type whose label refers to a resignation is suggested under Resignation, a retirement under Retirement, an illness under Illness. A sick leave type is suggested under the reason matching its nature (illness, work accident, maternity). Anything that matches nothing falls under Other.

A suggestion is already used by the calculation. Check it and correct it if needed: as soon as you choose a reason, the badge disappears and your choice prevails.

Where these mappings are used #

The mappings feed the departure and absenteeism indicators in the Data tab. They are also used to calculate the gender equality index and to determine the population used for the remuneration indicators.

When settings take effect #

A setting applies from the next calculation. The statistical confidentiality threshold and the mappings are read when the indicators are calculated: values already calculated do not change.

1. Change the threshold or the mappings in the Settings tab.
2. Open the Data tab and choose the database and the fiscal year.
3. Run the indicator calculation again to see the effect of your settings.

A fiscal year that has already been published is not changed by a new setting: what CSE members received stays as it is. To reflect the change, an update of the fiscal year must be published.

Good to know #

• The threshold protects anonymity in breakdown tables; totals stay exact.
• The threshold can be set between 3 and 50 people; it is 5 by default.
• A “Suggested” mapping is already used by the calculation: check it.
• The settings apply to every database in the workspace.
• Every change to the settings is logged.
• The module’s full export is requested in the BDESE databases tab, not here.

Frequently asked questions #

Why are some cells hidden in the Data tab? #

They count fewer people than the statistical confidentiality threshold (5 by default). The row or column total stays exact.

Can the threshold be lowered to 1? #

No. The threshold can be set between 3 and 50 people.

I changed a reason, but the indicators did not move. Why? #

The setting applies from the next calculation. Run the indicator calculation again in the Data tab.

A new exit type has been created. What should I do? #

It appears in the Exit types card with a suggested reason. Check the suggestion and choose another reason if it does not fit.