Job category taxonomy for recruitment advertising reports

A recruitment reporting taxonomy should group vacancies by stable, agreed business categories while preserving their original titles and identifiers. Start with the decisions the report must support, then define role families, levels and locations separately so a naming variation does not distort campaign comparisons.

Key facts

• A readable job title and a reporting category serve different purposes.
• Keep original vacancy identifiers when adding categories.
• Unknown classifications should remain visible rather than being forced into a convenient group.
• Taxonomy changes need a version and a mapping so historical reports remain explainable.

Why do recruitment reports need a job taxonomy?

Campaign exports often inherit local vacancy names. One branch may use “warehouse operative”, another “fulfilment colleague” and another an internal abbreviation. Those titles can be accurate for candidates while making a cross-branch report difficult to read.

A taxonomy adds a consistent reporting layer. It should help answer a real question, such as which role families need more hiring support or whether one location’s candidate journey differs from another’s. It should not erase meaningful differences simply to make a smaller chart.

Avoid using the taxonomy as the vacancy identity. Two roles can share a category while representing different hiring decisions. The duplicate-job control guide explains why campaign identity needs its own stable mapping.

Which dimensions should be kept separate?

Choose a small set of dimensions that the organisation can maintain reliably. Role family describes the type of work. Level describes responsibility where that distinction is useful. Location describes the workplace. Contract or schedule can matter when those conditions affect the candidate decision.

Do not combine all of these into one uncontrolled label. A category such as “North temporary evening warehouse senior” becomes difficult to maintain when any single element changes. Separate fields allow the report to filter each dimension without inventing a new role family every time.

Dimension	Example structure	Common mistake to avoid
Role family	Operations, transport, customer service	Using every title as a separate family
Role group	A defined subdivision where useful	Creating detail no one uses
Responsibility level	Agreed levels with definitions	Inferring seniority from one word
Workplace	Stable site or location identifier	Mixing headquarters with job location
Working pattern	Approved schedule category	Treating missing information as flexible
Vacancy identity	Original requisition and source	Replacing identity with the category

The example categories are illustrative. Use definitions that match your organisation rather than adopting a generic hierarchy that nobody can apply consistently.

How should the team map existing vacancies?

Export the current titles and identifiers, then group a manageable sample with the people who understand the work. Write a definition for each category and record borderline examples. These examples make the mapping usable by someone who did not attend the original workshop.

Keep “unclassified” as a visible state with an owner. Forcing a role into the nearest category hides the fact that the taxonomy or source information needs improvement. Track recurring unknowns so the team can decide whether to add a category or clarify a definition.

If software proposes a category, retain a review route for ambiguous cases. Do not assume that a title alone reveals duties, credentials or seniority. Review the underlying vacancy when the category affects an important operational decision.

For new locations, use the site-opening plan to ensure the source information exists before expecting a reporting taxonomy to classify it accurately.

What would a practical mapping exercise look like?

Consider a hypothetical business with nine vacancy titles across three sites. Six describe similar warehouse work, two describe driving roles and one combines supervision with operational duties. The team maps the six related titles into one role family while retaining the original titles and sites.

It keeps the driving roles separate because the work and requirements differ. The mixed supervisor role receives a reviewed category and an explanatory note rather than being classified by the first word in its title. The team records the rule so future mixed roles receive consistent treatment.

The resulting report can compare warehouse recruitment across sites without pretending that all nine vacancies are interchangeable. The example demonstrates classification, not improved campaign performance or a validated industry standard.

Before applying the mapping broadly, have another reviewer classify a different sample using only the written definitions. Disagreement identifies where the instructions need more precision.

How should historical changes be handled?

Version the taxonomy and record when a mapping changed. If two categories are merged, preserve the relationship between old and new codes. If one category is split, state whether historical records can be reliably reassigned or must remain under the old grouping.

Do not silently rewrite history when the source evidence is insufficient. A report can show the old classification for earlier periods and the new classification later, with an explicit break. Alternatively, use a common broader category for a comparable trend if that aggregation is defensible.

Keep title changes distinct from category changes. Renaming a vacancy for clarity does not always mean the underlying role family changed. Likewise, a familiar title can hide a substantive change in duties that warrants a different classification.

How can the taxonomy improve campaign decisions?

Use it to create comparable groups and reveal where a headline result is driven by changing role mix. If a period contains more difficult specialist vacancies, a combined campaign average may change even when each established role group behaves similarly. The taxonomy makes that question inspectable; it does not answer it automatically.

For international reporting, combine the taxonomy with the cross-market comparison checklist. Consistent role groups are only one requirement; periods, currency handling and outcome definitions also need alignment.

Adway publishes an ATS and CRM integration directory. Ask how your chosen source fields and reporting identifiers would be represented in the proposed configuration. Directory inclusion alone does not prove that a custom taxonomy will pass through unchanged. Bring a small mapping sheet to the discussion and Book a demo.

Sources

• Adway integrations, directory checked 2 November 2026.
• The taxonomy structure and nine-vacancy example are original reporting recommendations. They do not replace an organisation’s job architecture.

Keep local job language useful and reporting categories consistent.