Training (Courses), Development (skill map), and Qualifications are now connected around skills. Previously, the Skill Map required manual entry while reviewing Training and Qualification records. Now it updates automatically based on achievement data.

① Skill levels automatically increase from course completion, qualification acquisition, and SOP performance

There are three paths for automatic skill level increases:

Completing a Training course (when you pass an Assessment test if the course has one, or complete all SOPs in the course if there is no test)
Acquiring a Qualification (when it is registered and approved)
Completing all linked Related procedures independently (using the Solo completion judgment: completed with no errors)

The third path assumes questions are used as field verification, not tests. The fact of completion with no errors matches the evaluation criteria of "can do it alone".

Skill level does not increase from just viewing. We distinguish between "seeing" and "doing".

● Conservative safeguards

Automatic updates never lower levels. Users who already meet or exceed the level stay unchanged
No entries are written to users marked "Not target" for that skill
Nothing happens with skills that have no links set. Operations remain unchanged until configuration is set
The evaluator is recorded in the history as "Dive (Automatic evaluation)". You can later confirm who evaluated it

● Team-wide settings

Switch this setting in [Development (skill map)] → [Common settings] → [Automatic evaluation]. The default is On, and levels are automatically confirmed. If auditing is a priority, you can change the setting to only record development activity without changing levels.

The third path, "Related procedures", requires both the completion condition in Team settings and the Target level for each skill. Nothing happens if either is unconfigured.

② You can now configure how to gain skills

You can link Courses where this skill is gained, Qualifications that prove this skill, and Related procedures to each skill. Links can be set from either screen, and the same relationship updates.

From the "Skills gained" field in the Course edit screen, specify the skill and Target level
From skill definition (Group skill / Team-common "Common settings"), specify "Courses where this skill is gained" and "Qualifications that prove this skill"

We added "How to gain this skill" to individual Skill Details. Users and administrators can now see on the spot which courses to take, which qualifications are needed, and how far they have progressed.

The "Renewal training" (courses to take to earn or renew this qualification) on the qualification side and the links on the skill side are separate things. The former is configured on the qualification page, the latter on the Skill Map.

③ You can now see which skills, courses, and required qualifications are linked to an SOP

Previously, links were only visible from the skill side. Opening an SOP didn't tell you where it was used.

The Procedure list (both table and card view) in the folder shows count badges for skills / courses / required qualifications. Hover to see names
We added "Linked skills and courses" to the "Basic information" tab of SOPs (display only). The count also appears in the collapsed heading
When you hover over the Related procedures icon on the Skill Map and Personal page, the SOP name now appears

Qualifications shown on an SOP are only "required qualifications for this task" (Required qualification set on the SOP). We do not show qualifications linked through skills, as they may conflict with the SOP settings.

④ We added "Not target" to Evaluation Criteria

We responded to requests to "add non-applicable items to evaluation criteria" by formally treating "target / not target" as the bottom level of the evaluation axis, while keeping the number of levels (Lv1–Lv4) the same.

A "Not target" row has been added to the Evaluation Criteria edit screen (Team-common / Group-specific / Skill-specific), and you can edit the text
"Not target" is now an option when changing levels. The level value is retained if you select it, so when you return to target, it reverts to the previous level. This is not a level confirmation, so no supporting comment is required (Self-evaluation cannot select this)
On the Personal page, from the "Not target N items" toggle, you can also view skills marked as not target (default is hidden as before)

The population for achievement rate, Export to Excel, saved snapshots, and qualification verification remains only target skills as before.

⑤ Skill Map screen refinements

When skill names are long, they now wrap, and you can drag the column width to resize (width is remembered on the device). When operating with behavior-based evaluation text like "can do ~", the list remains readable
The toolbar has been streamlined from 4 rows to 2 rows. Filter is now a single button, and you can also filter by the presence or absence of course / qualification links
We renamed "[Skill Catalog]" to "[Common settings]". The catalog was only one of three items inside, and the name was narrower than the content
We expanded saving Team-common evaluation criteria from "Enterprise plan only" to "Core plan and above". Group-specific evaluation criteria can be freely edited, so it was inconsistent to restrict only the team default
Teams without groups can now open Common settings. We also added a navigation path from the Skill Map creation screen to group creation
The Development tab on the Personal page now reflects Team-common and Group-specific evaluation criteria. Previously fixed text was displayed, so the same level had different meanings on the Skill Map screen
Development plan (schedule for reaching level) now also gets deadline reminders
Skill Details changed from an always-visible panel to a collapsible one, fixing layout issues when screen width is narrow

Impact on existing use

At the time of release, no team has links between skills and courses, qualifications, or SOPs. Automatic updates do not work, and past evaluations will not change, until links are configured.

"Not target" retains the same treatment as skills previously marked as not target. No data migration is needed.

Related information

We look forward to your continued use of Dive◎