---
title: "Role-Level vs Task-Level Assessment: 923 Occupations, 19,000 Tasks, and Which Unit to Score"
description: "Role-level assessment predicts overall job performance; task-level assessment tells you which activities a person can do. A comparison of what each unit buys, what it costs, and how to choose when AI is recomposing work inside stable job titles."
canonical: https://www.assessall.com/blog/role-level-vs-task-level-assessment-923-occupations-19-000-tasks-and-which-unit
published: 2026-11-21
updated: 2026-11-21
author: "AssessAll Editorial"
source: AssessAll
---

# Role-Level vs Task-Level Assessment: 923 Occupations, 19,000 Tasks, and Which Unit to Score

Role-level assessment predicts overall job performance; task-level assessment tells you which activities a person can do. A comparison of what each unit buys, what it costs, and how to choose when AI is recomposing work inside stable job titles.

Role-level assessment scores a person against a whole job — one composite meant to predict overall performance. Task-level assessment scores specific work activities separately. The choice is a bandwidth decision: broad predictors forecast broad criteria better, narrow predictors forecast narrow ones. Pick the unit that matches the decision you are about to make.

Most assessment programmes never make that choice explicitly. They inherit it. A competency framework arrives with eight role-level dimensions, the test gets built to match, and the unit of measurement is settled before anyone asks what decision the scores will inform. That was tolerable when jobs changed slowly. It is less tolerable now, because the thing being disrupted is the task, not the job title.

## The two units, defined

**Role-level measurement**

- Scores a candidate or employee against a whole occupation or job family.
- Produces a small number of broad scores — a composite, a competency profile, an overall fit index.
- Is validated against a broad criterion: supervisor ratings of overall performance, retention, promotion.

**Task-level measurement**

- Scores performance on specific work activities — drafting a dispute response, reconciling a ledger, triaging a support queue.
- Produces many narrow scores, each tied to one activity.
- Is validated against a narrow criterion: did the person do that activity acceptably?

The US Department of Labor's [O*NET](https://www.onetcenter.org/about.html) database makes the granularity gap concrete. It covers 923 data-level occupations and more than 19,000 task statements, which roll up into over 2,000 detailed work activities, then 325 intermediate activities, then 41 generalised ones. The same work can be described at five levels of resolution. Your assessment picks one, whether or not you noticed.

## Why the question is live now

Task exposure to AI is not evenly distributed inside a job. Eloundou and colleagues, writing in *Science* in June 2024, estimated that around 80% of the US workforce could have at least 10% of their work tasks affected by large language models, and roughly 19% could see at least half their tasks affected ([doi:10.1126/science.adj0998](https://www.science.org/doi/10.1126/science.adj0998); [preprint](https://arxiv.org/abs/2303.10130)). That is an exposure estimate, not a displacement forecast — the authors are explicit that exposure measures potential overlap, not realised job loss.

Employer expectations point the same way. The World Economic Forum's [Future of Jobs Report 2025](https://www.weforum.org/publications/the-future-of-jobs-report-2025/in-full/3-skills-outlook/) finds employers expect 39% of workers' core skills to change by 2030 — down from 44% in the 2023 edition — against projected churn equal to 22% of today's jobs, 170 million created and 92 million displaced.

Early payroll evidence suggests the effect lands unevenly by task type. The Stanford Digital Economy Lab's [*Canaries in the Coal Mine?*](https://digitaleconomy.stanford.edu/publications/canaries-in-the-coal-mine/), revised in August 2026 using ADP administrative data through June 2026, reports that employment of 22–25 year olds in the most AI-exposed occupations sits about 19% below where it would be had it tracked less-exposed peers — operating through reduced hiring rather than layoffs, and concentrated where AI substitutes for tasks rather than complementing them. The authors frame these as descriptive indicators, not causal estimates.

The practical consequence for assessment is narrow and specific: when the composition of a role changes faster than the role's title does, a score attached to the title ages faster than a score attached to the activity.

## What each unit actually buys you

This is not a new psychometric problem. It is the bandwidth–fidelity dilemma, set out for selection by Ones and Viswesvaran in the *Journal of Organizational Behavior* (1996, vol. 17, pp. 609–626): broad predictors match broad criteria, narrow predictors match narrow criteria, and mismatching them costs you validity in both directions.

**Role-level gives you**

- Fewer scores to interpret and defend.
- Better prediction of broad outcomes — overall performance, tenure, promotion — because work performance is itself multidimensional and composite criteria need composite predictors ([Campbell and Wiernik, 2015](https://doi.org/10.1146/annurev-orgpsych-032414-111427)).
- Stability: the score survives small changes in how the job is done.

**Task-level gives you**

- Diagnostic information. You learn what to train, not just whom to reject.
- Faster obsolescence detection: when a task stops mattering, you retire one measure, not the instrument.
- Portability. A result attached to an activity travels to another role that shares it; a result attached to a job title does not.

**What each costs you**

- Role-level buys stability at the price of diagnosis. A single composite cannot tell you which part of the job the person cannot do.
- Task-level buys diagnosis at the price of reliability per score and testing time. Narrow measures built from few items are less reliable individually, and a battery of twenty of them is a long assessment.

## When role-level is the right choice

Role-level is the better unit when the decision itself is broad.

1. **You are making a yes/no hiring decision at volume** and the criterion you care about is overall performance or early attrition.
2. **You have criterion data** linking scores to that broad outcome, and the role is stable enough that the linkage will still hold next year.
3. **The work is highly interdependent**, so performance is not decomposable into separable activities.
4. **Defensibility is the binding constraint.** A single validated composite with a documented job analysis is easier to defend than twenty narrow measures each needing its own evidence.

If those conditions hold, splitting into task scores adds length and noise without adding decision value.

## When task-level is the right choice

Task-level is the better unit when the decision is about *which part* of the work someone can do.

1. **You are redeploying people internally** and need to know what transfers.
2. **The role is being actively recomposed** — AI is taking some activities, humans keeping others — so the job title has stopped being a stable container.
3. **The output is a development plan**, not a reject decision.
4. **You need evidence that travels** across roles, employers or borders.

AI-graded scenarios are natural task-level instruments, because a scenario is already shaped like a work activity rather than like a job. On AssessAll, where results sit in a candidate's Skill Passport, that shape matters: an activity-level result keeps its meaning when the surrounding role changes, and pay-as-you-go credits at ₹30 / US$0.50 mean adding one narrow measure to a battery is a marginal cost decision rather than a licence renegotiation.

## What does not change either way

The unit of measurement is a design choice. The evidence obligation is not.

- **Job analysis still comes first.** Both the [SIOP Principles](https://www.cambridge.org/core/journals/industrial-and-organizational-psychology/article/principles-for-the-validation-and-use-of-personnel-selection-procedures/730C076329F88919D5C81C6E7D304FE2) (5th edition, 2018) and the EEOC's [Uniform Guidelines Q&A](https://www.eeoc.gov/laws/guidance/questions-and-answers-clarify-and-provide-common-interpretation-uniform-guidelines) require that a content-based claim rest on an analysis of important work behaviours. Task-level scoring does not exempt you from that; it makes the linkage more visible.
- **Reliability is reported per score, not per battery.** If you publish twenty task scores, you owe twenty reliability estimates — or you aggregate and report the composite you actually use.
- **Adverse impact is assessed on the decision**, not on each component. A battery of narrow measures combined into a pass/fail still produces one selection rate per group.

A reasonable middle path exists and is often the right answer: measure at task level, report at role level. Score the activities separately so the data stays diagnostic and portable, then combine them into the composite you validate and defend. That requires deciding the combination rule in advance — compensatory or multiple-hurdle — rather than discovering it in a spreadsheet after the fact.

## The takeaway

The unit of measurement should be chosen from the decision, not inherited from the competency framework. If the decision is "hire or not", measure broad and validate broad; if the decision is "what can this person do, and what changed", measure at the task and keep the scores separable.

---

Source: https://www.assessall.com/blog/role-level-vs-task-level-assessment-923-occupations-19-000-tasks-and-which-unit
