Certificate goals
A certificate goal sets how many people should hold a valid certificate, for example the number of certified consultants a vendor partnership requires. A goal applies either to your whole company or to a subgroup of it, such as the consultants of one business unit. decídalo compares the goal with the people who hold the certificate today and projects, from the expiration dates on their profiles, when the number will fall below it. That lets you plan re-certifications before the gap opens, and remind the people concerned to renew.
Each certificate in your company’s catalog can have one company-wide goal, which applies to everyone, and any number of subgroup goals, each for a group of people described by their profile fields. Certificates themselves are described in Managing and using certificates.
Opening the certificate goals page
Open Certificates in the Skill and CV menu section and click Goals above the certificates table. The Certificate goals page lists every goal, company-wide and subgroup goals alike. Click Back to certificates to return to the catalog.
The page, including the development drawer of each goal and the renewal reminders, requires the ‘Manage skills, certificates and roles’ permission; without it, the Goals button is not shown. See the Permission concept.
How holders are counted
A holder is a person who has the certificate on their profile. The goal counts follow the same validity rule as the rest of decídalo:
- A certificate is valid until the end of its expiration month, or until the end of the year if only a year is set.
- A certificate without an expiration date never expires, so its holders count as valid.
- Only the expiration dates entered on the profiles are used. Nothing is estimated.
- A person stops counting once their exit date has passed. In the chart, a holder counts in a month only if they are still employed at the end of it: someone whose last working day is 15 March no longer counts in March, someone leaving on 31 March counts in March and no longer in April. The current month counts the holders employed today, the same number as Valid now; hovering over it also shows the projected number at the end of the month.
- Deleted profiles no longer count. In the recorded months of a company-wide goal, a deleted person counts until their exit date, or until the deletion if that came first or no exit date was set. A deleted person belongs to no subgroup, so subgroup goals do not count them in any month.
A subgroup goal counts only the holders who belong to its subgroup, by the same rules.
Subgroup goals
A subgroup goal applies to the people whose profiles meet a set of conditions, for example everyone in the Consulting business unit who works in Germany or Austria. Use it when a requirement concerns only part of your company, such as a partnership that asks for a number of certified consultants in one country. Each subgroup has a name that no other subgroup in your company has, and goals for several certificates can use the same subgroup, for example to track both a cloud and a security certificate for the same consultants. Subgroups are shared with skill goals, so the same consultants can also get a goal for a skill. A subgroup is neither a team nor a resource group, and it is deleted together with the last goal that uses it, whether that is a certificate or a skill goal.
Each condition names a profile field and the values a person must have in it:
- A person meets a condition if their profile has any of the condition’s values.
- A person belongs to the subgroup if they meet all of its conditions.
The conditions can use the fields that the ‘Profiles’ page can be filtered by, including your company’s custom fields and fields that name a person, a team or a company, such as a manager. Some fields are not offered:
- fields in the restricted data section, which only users with the ‘View restricted fields’ permission may see;
- fields that identify a single person: the name and its parts (first, middle and last name), the email address, the office and mobile phone numbers, the LinkedIn profile, the external user ID and the private address;
- fields whose values decídalo calculates rather than stores;
- date fields, with or without a time, and paragraph fields.
Fields that name another person, such as the manager, are not affected and can be used.
decídalo checks every profile when calculating subgroup membership, including profiles outside your viewing permissions. It reuses the result for up to five minutes, so when someone moves to another business unit, for example, the figures of the goal follow within a few minutes. The number of matching people shown while you edit the conditions is always current. The values you can choose for a condition come from the profiles you may view.
Field names and option labels follow your display language. Translated profile text is matched in your company’s default language, so the text values offered in a condition use that language too.
Note: decídalo does not record who belonged to a subgroup in the past. The recorded months of the development drawer therefore count today’s members in every month: a holder who joined the subgroup recently counts in earlier months as well, and a holder who has left it no longer counts in any month.
Conditions that need review
A condition depends on its field. If the field is deleted or deactivated, is moved to the restricted data section, or changes its type, the condition can no longer be applied. decídalo then skips it and counts the goal without it, so more people may be counted than intended; if none of the conditions can be applied, the goal counts everyone. In the goals table, the goal is marked with a warning icon and Conditions need review, and its development drawer shows a warning. Wherever the conditions are listed, a skipped condition appears as Field no longer available, followed by its values.
To fix such a goal, edit it: the drawer lists the conditions that are no longer applied, and saving the goal removes them from the subgroup. If other goals use the subgroup too, for other certificates or for skills, decídalo names them and asks you to confirm, because the subgroup changes for them as well; to change only this goal, give it a subgroup of its own under a new name instead. Add new conditions in their place if the subgroup still needs them.
Deleting one of a field’s options does not mark the goal: the field is still available, but the option is removed from every profile that had it (see Customizing Data Fields in decídalo). A condition that uses the deleted option therefore no longer matches anyone through it, and the goal may count fewer people than intended.
The goals table
The table shows one row per goal, so a certificate with subgroup goals appears in several rows. The figures of a subgroup goal cover the subgroup’s members only. Narrow the table down with the column filters, and show or hide columns with the column settings. Your choice, and the column widths, are remembered.
| Column | Description |
|---|---|
| Certificate | The certificate the goal is set for. Click the name to open the development drawer. |
| Applies to | Everyone for a company-wide goal, otherwise the name of the subgroup. Hover over a subgroup’s name to see its conditions. A warning icon and Conditions need review mark a goal whose conditions need review. |
| People | How many people the goal applies to: everyone in your company for a company-wide goal, otherwise the members of the subgroup. Unlike the holder figures, it includes people who have left the company, just like the number of matching people shown while you edit the conditions. |
| Goal | How many people should hold a valid certificate. |
| Goal status | Goal held: enough holders are valid today, and the projection stays at or above the goal for the next 24 months. Falls below goal: the goal is met today, but the projection falls below it within the next 24 months. Below goal: fewer holders are valid today than the goal requires. |
| Below goal from | The first month in which the projection falls below the goal. For a goal that is already below goal, this is the current month. Empty while the goal is held. |
| Valid now | Holders whose certificate is valid today, including those without an expiration date. |
| All holders | All holders who have not left the company, whether their certificate is valid or not. |
| Expired | Holders whose certificate has expired. |
| No expiration date | Holders without an expiration date on their profile. |
| Expiring within 6 months | Holders whose certificate is valid today and expires within the next 6 months: the same people as in the drawer’s renewal list. |
Adding, editing and removing goals
Click Add next to the table title, or Add goal while the table is still empty. A pop-up opens:
| Field | Description |
|---|---|
| Certificate | Search for the certificate in your company’s catalog. For a company-wide goal, certificates that already have one are marked Already has a company-wide goal and cannot be selected. A subgroup goal can be added to any certificate. |
| Goal | The number of people who should hold a valid certificate: a whole number of at least 1. |
| Why this matters | Optional. Up to 1,000 characters on why the goal exists, for example the partnership or contract that requires it. It is shown in the development drawer. |
| Applies to | Everyone for a company-wide goal, Subgroup for a subgroup goal. If the certificate already has a company-wide goal, Everyone is not available, Subgroup is selected and a note says why. |
| Subgroup | Subgroup goals only. Pick a subgroup that other goals already use, including skill goals, or type a name and click Add “…” to define a new one. A new subgroup’s name has up to 100 characters and is shown in the Applies to column, for example “Consultants Germany”; typing the name of an existing subgroup, whatever its capitalization, picks that subgroup. Subgroups the certificate already has a goal for are marked Already has a goal for this subgroup and cannot be selected. |
| Conditions | Subgroup goals only. Who belongs to the subgroup, as described below. An existing subgroup is used as it is: its conditions and the number of people they match are shown, but cannot be changed here. |
To add a condition, click Add under Conditions and click a field in the list that opens: the field is added straight away as a row of its own. Click the button in its Values column to choose the values, as in a column filter. The trash icon at the end of a row removes the condition. A subgroup goal needs at least one condition and can have up to 20. Every condition needs at least one value and can have up to 50: while a condition has no value, a note below the conditions names its field and the goal cannot be saved.
Below the conditions, the pop-up shows how many people currently match them, for example “12 people currently match”, whether they hold the certificate or not. The number updates shortly after you change a condition. If no one matches, a warning says so; you can still save the goal, for example for a group that is still being built up.
Save is always available. If a required field is empty or a value is not valid, clicking it saves nothing and shows an error message at each field that needs attention.
You can also start from the certificates table: the Add goal action in a certificate’s row opens the same pop-up with that certificate already selected. For a certificate that has a company-wide goal, Remove company-wide goal removes that goal after a confirmation. Its subgroup goals stay; remove them on the goals page.
To change a goal, click the three vertical dots at the end of its row and select Edit. A side drawer opens with the same fields; only the certificate cannot be changed there. Under Applies to, you can turn a company-wide goal into a subgroup goal, and a subgroup goal into the company-wide goal of its certificate. If the certificate already has a company-wide goal, Everyone is not available and a note says why. The goal keeps its number of people and Why this matters.
For a subgroup goal, the Subgroup field shows the goal’s subgroup, and you can change its conditions:
- If no other goal uses the subgroup, the changes apply to this goal alone, and typing a new name and clicking Add “…” renames the subgroup.
- If other goals use the subgroup too, whether for certificates or for skills, a note names them. Changes to the conditions apply to those goals as well, so when you save, decídalo names them again and asks you to confirm. To change the conditions for this goal only, type a new name and click Add “…”: the goal gets a subgroup of its own under that name, starting with the same conditions, and the other goals keep theirs. The new name must differ from every existing subgroup’s name, whatever its capitalization, including the subgroup the goal used so far.
- To count the members of another existing subgroup instead, pick it or type its name. It is used as it is.
A subgroup that no goal uses any more is deleted. If no other goal uses the goal’s subgroup, picking another subgroup or Everyone therefore deletes it, and decídalo asks you to confirm that when you save. If some of the subgroup’s conditions are no longer applied, the drawer lists them with a notice; see Conditions that need review. To remove a goal, select Remove in the same menu and confirm; for a subgroup goal, the confirmation names the certificate and the subgroup, and says that the subgroup is deleted as well if no other goal uses it. Removing a goal changes nothing on the certificate or on the profiles.
When a certificate is deleted, all its goals are deleted with it, and so are the subgroups no other goal uses. When two certificates are merged, the company-wide goal of the duplicate moves to the target certificate, unless the target already has a company-wide goal of its own: then the target keeps its goal. The subgroup goals of the duplicate move to the target certificate in the same way: a subgroup goal moves unless the target already has a goal for the same subgroup, which it then keeps.
The development drawer
Click a certificate name in the goals table to open the development drawer of that goal. It shows how the number of valid holders has developed and how it will develop if nobody renews.
At the top, the drawer repeats the Goal, Valid now, Goal status and Below goal from of the table, followed by Why this matters when it has been filled in. If holders with a valid certificate will leave the company within the next 24 months, a note says how many.
For a subgroup goal, the subgroup’s name and conditions appear above these figures, with a warning if some of the conditions need review. The figures, the chart and the renewal lists then cover the subgroup’s members only, and the recorded months count today’s members (see Subgroup goals).
The chart shows the goal month by month:
| Element | Description |
|---|---|
| Valid holders | The number of valid holders. In the past months it is the recorded number, in the coming months it is projected. The current month shows both: the recorded number counts the holders employed today, the projected number those still employed at the end of the month. |
| All holders, including expired certificates | The recorded number of all holders, whatever the validity of their certificate. |
| Goal | A horizontal line at the goal. |
| Today | A marker at the current month. |
| Below goal | The shaded area from the month in which the projection falls below the goal. |
Hover over a month to see its figures. The recorded part covers up to the last 24 months. decídalo has kept the history needed for it only since a certain point, so the recorded part can be shorter, and the chart then starts where the data does. Holders of certificates that were merged into this one count in the recorded months as well.
The projection covers the next 24 months by default. It follows the known expiration dates and exit dates, and assumes that nobody renews and that no new holders are added, as the note under the chart says. Two controls above the chart change only the chart, never the saved goal or the figures in the table and the drawer summary:
- The button with the calendar icon shows the period on display. Click it to choose the months to show, from the start of the recorded history up to ten years ahead. A period that ends after the next 24 months extends the projection accordingly.
- Standard validity: a what-if for holders without an expiration date. By default they stay valid (Unlimited). Select 12, 24, 36 or 60 months, or enter a number of months from 0 to 600, to see how the projection would look if these certificates expired that long after their issue date (or, without one, after the date they were added to the profile).
Reminding holders to renew
Below the chart, the drawer lists the holders who need to renew the certificate, in two lists:
- Expired: holders whose certificate has expired, the most recently expired first. This list is open when the drawer opens.
- Expiring within 6 months: holders whose certificate is still valid but expires within the next 6 months, the soonest first. This list is collapsed.
People who have left the company are not listed, and for a subgroup goal, neither are people outside the subgroup. Each list shows how many people it contains and the first five of them; click Show all to see the rest. Each entry shows the person’s name, which opens their profile, the month in which the certificate expired or expires, and, if someone has sent one, the date of the last reminder. People whose profile you may not view are listed anonymized, without a link.
Click Send reminder to send the person an email, in their language, asking them to renew the certificate and then update it on their profile. The email names you as the person asking and links to their profile. Once it is sent, the entry shows Reminder sent. In a list with at least two people who can be reminded, Send reminder to all reminds all of them at once after a confirmation.
A reminder can only be sent:
- to people whose profile you may open, who are active and have a login;
- once every 24 hours per person and certificate, whichever goal of the certificate it is sent from. Until then, Send reminder is disabled, and hovering over it shows when the last reminder was sent and when the next one is possible;
- while the person has not turned the reminder off. Users can only do so if an administrator has made the notification optional; hovering over the disabled button then says so.
The reminder is the email notification ‘Certificate renewal reminder’, which is active by default. If an administrator switches it off, no reminder buttons are shown and a note above the lists explains that an administrator has to turn it on again. See Notifications for how email notifications are configured. If a reminder cannot be sent, for example because someone else has just reminded the same person, a message appears above the lists and they are refreshed.
Note: The reminder is independent of the automatic ‘Certificate expiration approaching’ email, which decídalo sends on its own 90 days before a certificate expires.