Once your workforce data has been mapped to occupations, you can explore rich details about each classified role through the Occupation Details panel.
There are two possible views of this screen depending on the type of occupation:
-
Ontology Occupation View – when the role is matched with our proprietary Occupation Ontology.
-
Custom Occupation View – when the role is manually created or imported without sufficient match to our ontology.
Occupation Details Default View
The Occupation Details view provides a breakdown of:
1. Pre-classified data from your organization
-
Headcount – number of employees mapped to this occupation
-
Job Families – high-level functions or domains
-
Job Titles – role labels from your internal data
-
Org Structure – the team, division, or business unit where these roles sit
2. Occupation Classification Metadata
This section includes data drawn from Pearson’s Occupation Ontology or from your custom entries:
-
Occupation name
-
Occupation category (e.g., Financial, Operational, IT)
-
Occupation code – standardized reference code
-
Occupation stream – e.g., Individual Contributors, Leaders
-
Occupation description – a clear, behavioral explanation of what this role does
If the occupation is matched to Pearson’s ontology, this section will be auto-populated with trusted ontology data. If it's a Custom Occupation, this section may contain limited or no data.
Tasks and Skills from Ontology Data
If the occupation is linked to Pearson's Occupation Ontology, the panel will display:
-
Tasks (ranked by time spent) – real-world tasks associated with the occupation, each with an estimated time distribution.
-
Skills (ranked by relevance) – skills required for the occupation, grouped by proficiency levels.
💡 Note: These insights are based on global labor market data, validated by Pearson's data science team, and help benchmark your current workforce.
Custom Occupation Details
If the occupation was created manually or imported as custom:
-
Occupation metadata (e.g., description, stream, category) may be user-defined.
-
Tasks, skills, and role names may not be available unless mapped manually.
-
You will see “Due to limited information, this data is currently unavailable” in place of benchmarked content
This doesn’t mean the data is incorrect—just that the role hasn’t yet been mapped deeply enough to our ontology to surface richer analytics.
💡Tip: When to use Custom Occupations?
Use custom occupations if:
- You have specialized or emerging roles not yet covered in the ontology.
- You’re testing future roles or hybrid functions.
- Your organization prefers internal naming conventions.
To gain access to task and skill data, consider mapping your custom occupations to the closest match in Pearson's ontology using the reclassification tools.
Occupation Details in Employee View
When accessing Occupation Details from the Employee View, the side panel shifts to focus on individual-level context. It provides both mapped occupation information and employee-specific data fields, helping validate classification decisions or uncover anomalies.
Key differences in this view:
-
Job Information: Displays the employee's matched occupation and job family, as well as the organization-specific layers they sit within.
-
Employee Information: Includes key details such as:
-
Employee name and internal ID
-
Email address
-
Internal level (if provided)
-
Location
-
Manager name and ID
-
This view is especially useful for:
-
Spot-checking classification accuracy on an individual level
-
Reviewing edge cases or escalations
-
Cross-referencing internal data with mapped occupation results
Let me know if you want this directly inserted into the canvas or need a meta description next.