A board meeting question that starts with tasks, not titles
A People Analytics Lead building a workforce exposure briefing for a board or a PE sponsor usually starts by pulling job titles. That's the wrong unit of analysis. A "Financial Analyst" and a "Senior Financial Analyst" can share a title family but spend their weeks on entirely different task mixes — one buried in recurring variance reports, the other running scenario models for the CFO. Scoring the title produces a number nobody can defend under questioning. Scoring the tasks that make up the title, and weighting them by how much each one actually matters to the job, produces a number that survives the follow-up question: "how did you get this?"
That's what ONET task importance ratings are for. This article explains what they measure, how they differ from other ONET task attributes, and why importance-weighting is a load-bearing part of any task-based AI exposure methodology — including the four-dimension rubric WorkforceAnalysis uses to score roles.
What O*NET task importance ratings actually measure
ONET — the U.S. Department of Labor's Occupational Information Network — maintains a database covering 1,016 occupational titles and 923 data-level occupations, representing more than 55,000 individual jobs across the U.S. economy (ONET Resource Center, USDOL/ETA, 2019). Each occupation in that database is described by roughly 277 standardized descriptors, refreshed on a regular update cycle with the primary annual update typically landing in the third quarter (U.S. DOL, 2025).
Within that descriptor set, O*NET occupational analysts don't just list the tasks a worker in a given occupation performs. They also rate how important each task is to doing that job well — on a numeric scale running from tasks that are incidental to the role to tasks that are central to it. This is the Importance rating, and it exists precisely so that analysts, researchers, and (in our case) exposure-scoring tools don't have to treat a occupation's fortieth listed task as equal in weight to its first.
That distinction matters more than it sounds. A Customer Service Representative's task list includes both "resolve customer complaints regarding service" and "greet visitors at the front desk." Both are real, both appear on the O*NET task list for the occupation — but they are not remotely equal in importance to the job, and they are not remotely equal in AI exposure. Treating them as equal weight in a scoring model manufactures a number that looks precise and means very little.
Importance versus frequency and level — a distinction worth holding onto
O*NET's Task Ratings data captures more than one dimension of a task, and it's worth being precise about which one you're using and why. Importance answers "how much does this task matter to doing the job?" It is a distinct question from frequency ("how often is this task performed?") and from the skill or education level a task requires. A task can be performed rarely and still be extremely important — a Financial Controller's quarter-end audit reconciliation, for instance. A task can be performed constantly and be relatively unimportant to the core value of the role — routine status-update emails, for example.
For AI exposure scoring specifically, importance is the more defensible weighting variable of the two. Frequency tells you how much of the employee's calendar a task occupies; importance tells you how much the organization's outcome depends on that task being done well. A model built to help HR leaders make redeployment and reskilling decisions should weight toward tasks that matter to the business, not simply toward tasks that consume the most hours. That's the rationale behind importance-weighted task exposure scoring as a methodology choice rather than a default.
Why an unweighted exposure score misrepresents a role
Here's the failure mode importance-weighting is designed to prevent. Imagine scoring every task on a role's O*NET task list against a cognitive-routine exposure rubric, then simply averaging the results. A role with twelve minor administrative tasks and three high-importance judgment tasks would get an average score dragged toward whatever the twelve minor tasks look like — even though the three judgment tasks are the reason the role exists and the reason it's paid what it's paid.
An unweighted average also produces a number that changes depending on how many low-importance tasks happen to appear on the occupation's task list, which is an artifact of how O*NET documents that occupation, not a fact about AI exposure. That's not a defensible board-ready metric. It's noise dressed up as a score.
Importance-weighting corrects for this by making each task's contribution to the final role score proportional to how much that task matters to the job — so three high-importance judgment tasks can outweigh twelve incidental administrative ones, which matches how the actual work of the role is understood by the people who do it, manage it, and would have to redesign it.
A worked example: weighting exposure by task importance
Here's a simplified, illustrative calculation — round numbers, chosen only to show the mechanism, not drawn from any real occupation's O*NET record.
Suppose a role has four O*NET-listed tasks, each already scored on a 0–100 cognitive-routine exposure scale, and each carrying a relative importance weight (weights sum to 1.0 for simplicity):
| Task | Exposure score | Importance weight |
|---|---|---|
| A | 80 | 0.10 |
| B | 30 | 0.45 |
| C | 65 | 0.30 |
| D | 90 | 0.15 |
A simple average of the four exposure scores is (80+30+65+90) / 4 = 66.25.
The importance-weighted score is (80×0.10) + (30×0.45) + (65×0.30) + (90×0.15) = 8 + 13.5 + 19.5 + 13.5 = 54.5.
The gap between 66.25 and 54.5 is not rounding error — it's the difference between treating four tasks as equally significant and recognizing that Task B, the largest share of the role's actual importance, happens to carry a relatively low exposure score. An unweighted approach would have overstated this role's exposure by more than ten points. That's the kind of gap that changes whether a role lands in Monitor or Review on an executive-facing heatmap.
Where importance-weighting fits inside a four-dimension exposure rubric
This same importance-weighting logic runs across all four dimensions WorkforceAnalysis scores for every mapped role: cognitive routine, physical routine, social/judgment, and creative, each scored 0–100. Each dimension score is built from the role's ONET task list, weighted by ONET's task-importance data before it's rolled up. The result is a role-level exposure profile, not a single alarm number — and it's explicitly an input to a Monitor, Review, or Redeployment Candidate designation, not a verdict about whether a specific person's job will disappear. The full mechanics of that scoring pipeline — how tasks are mapped from a client's role list to O*NET occupations, and how the four dimensions are combined — are covered in task-based AI exposure methodology and in what is O*NET and how it works.
It's also worth noting where this data sits within the broader ONET framework. The occupations WorkforceAnalysis maps roles into ultimately trace back to the 2018 Standard Occupational Classification system, which organizes the U.S. labor market into 867 detailed occupations, 459 broad occupations, 98 minor groups, and 23 major groups (U.S. BLS). Understanding how ONET's task and work-activity descriptors sit above that classification structure is a useful next step — see the O*NET work activities list guide for how generalized work activities relate to occupation-specific tasks.
Turning this into a board-ready methodology, not a black box
The value of importance-weighting isn't academic. It's what lets an HR strategy team stand in front of a board or a PE sponsor and answer "how did you get this number?" with a specific, auditable answer: this task, this importance weight, this exposure score, combined this way. That answer is the difference between a credible workforce risk briefing and a slide that gets picked apart in the first five minutes.
If you're building or reviewing an exposure methodology internally, the O*NET Task-Mapping Methodology Handbook walks through the full task-to-occupation mapping and importance-weighting workflow in template form, so your team isn't reconstructing this logic from scratch. And if you'd rather see the weighting applied automatically across a full role list, pricing for the self-serve exposure analysis is a reasonable next stop.
This site incorporates information from ONET. Used under the CC BY 4.0 license. ONET is a trademark of USDOL/ETA.