Field entry, published 2026-11-03, updated 2026-11-03. Group: Job, occupation, and unit group

What is a task, and why does it matter more than a title?

A task is a discrete piece of work that a person carries out as part of a job: an action with a purpose, performed with particular tools, knowledge, or interaction. Tasks matter more than titles in ISCO-08 because tasks describe what is actually done, while a title only names a role, and names can be chosen freely by employers. When classification must decide which family a job belongs to, it turns to the task evidence, because that evidence is the closest available record of the work itself.

What counts as a task, and what does not?

A task is specific enough to picture. Preparing a report, repairing a component, advising a client, supervising a team, entering data, and cleaning a room are all tasks, because each names an action and an object of that action. Vague qualities are not tasks. Being hardworking, being a team player, or having a positive attitude may be valued at work, but they do not describe what a person does. Likewise, a workplace, a department name, or a product name is not a task. The useful test is whether a stranger could understand, from the description alone, what the worker spends time doing. If yes, you have a task. If no, you have context or praise, not a task.

How do tasks combine into a job?

A job is rarely a single task. It is a bundle of tasks held together by a purpose: serving customers, producing a good, maintaining a system, teaching learners, or administering an organisation. Within that bundle, some tasks are main tasks, the ones that define the job and take a substantial share of time or importance. Others are supporting tasks, necessary but not defining. Classification weighs the main tasks most heavily. A job that includes a small amount of bookkeeping is not thereby a bookkeeping job, if bookkeeping is only a supporting task. A job whose main purpose is bookkeeping is a different matter. The distinction between main and supporting tasks is therefore central, and good job descriptions make it visible.

Why are titles such weak evidence?

Titles are weak for three reasons. First, they are not standardised: the same work carries different titles in different firms, sectors, and countries. Second, they are chosen for purposes other than description, including recruitment, retention, and internal status. Third, they age badly: a title can survive long after the work it named has changed, or a new title can appear for work that has not changed at all. Tasks, by contrast, change more slowly and can be described in ordinary words that travel across firms and countries. A coder who reads a task description can compare it with task profiles in the classification, while a coder who reads only a title must guess what the title means in that particular workplace.

How can you write a task description that classification can use?

Start with verbs and objects: what do you do, and to what or for whom? Then add purpose: why does that action matter, and what result does it produce? Then add the knowledge or tools involved, briefly, where they help distinguish the work. Keep the main tasks first and the occasional tasks last, and give a rough sense of time or importance where you can. A description built that way lets a reader see the shape of the job at a glance, and it avoids the trap of listing every minor duty as if all duties weighed equally.

What happens when two jobs share some tasks but not their main ones?

Shared minor tasks do not make jobs equivalent. Many jobs involve answering messages, attending meetings, or completing records, yet those shared supporting tasks do not place them in the same family. What places jobs together is similarity in their main tasks, the defining core. Imagine two jobs that both involve some advising, but in one job advising is the main purpose and in the other it is a small aside to a mainly manual job. The shared word advising hides a real difference in the balance of work. Classification follows the balance, not the shared word, which is why task descriptions must show weight as well as content.

Can tasks reveal skill better than qualifications?

Tasks and qualifications tell complementary stories. In classification, tasks come first, because a person can hold a qualification and work in a job that does not use it, or can perform skilled work built on experience rather than formal study. For grouping jobs, however, the performed tasks are the primary evidence, since the grouping aims to describe work as done, not credentials as held.

Why does this task-first habit help outside statistics?

It helps anyone trying to understand, compare, or change work. A hiring manager who writes a task based advert attracts applicants who understand the job. A worker who describes tasks clearly can show transferable experience across titles and sectors. A student choosing a path can compare the daily work of different families, rather than comparing glamorous titles. In each case, tasks cut through branding and fashion to the work itself. That is the habit ISCO-08 embodies: look at what people do, weigh what they mainly do, and let titles stay in their place as useful but unreliable labels.

Sources checked

1. ILO: ISCO-08 structure

Back to the Job, occupation, and unit group group or browse all occupations.