OSCA occupation classification and your workforce plan

Open the occupation code field in your HRIS and you will probably find an ANZSCO code against every position, set when the position was created and untouched since. That field feeds your establishment reports and the labour market comparisons in your workforce plan, and it now describes your jobs in a classification Australia has retired.

Put your establishment report next to the ABS figures you benchmark against, and from September 2026 the two columns count jobs differently. The ABS reports on OSCA, the Occupation Standard Classification for Australia it released in December 2024, while your positions still carry ANZSCO codes.

The fix is smaller than it sounds, as long as you treat the occupation change and the skills change as two separate jobs with two very different levels of certainty.

Occupations have a timeline, but skills still have no date

The ABS released OSCA version 1.0 on 6 December 2024 and said it would appear in official labour market statistics from September 2026, then in the 2026 Census outputs. So before you compare a recent ABS release with your own position data, check which classification each one uses.

OSCA will also keep changing. The ABS consulted on an OSCA 2027 update from 11 March to 24 April 2026, has a draft due for further feedback and plans the release for March 2027. The ABS describes the changes as minor and at the 6-digit occupation level (new occupations, skill levels, titles and tasks), and the 6-digit level is exactly where your individual positions sit.

On skills, the old reference has gone and the new one has no date. Jobs and Skills Australia's Australian Skills Classification (ASC) described occupations through 10 core competencies, specialist tasks and technology tools. According to JSA, its final update was in December 2023 and it has since been decommissioned. JSA is developing a National Skills Taxonomy without a confirmed release date, and in May 2026 Universities Australia was among the stakeholders asking JSA for a clear 2026-27 implementation timeline.

Be firm on occupations and loose on skills

Most commentary bundles all of this into one story about national skills reform, and that framing pushes organisations towards one of two mistakes. Some wait for everything to settle and lose a year of comparable data. Others rebuild their capability model around whatever looks closest to the coming taxonomy, then rebuild it again when the real thing arrives.

The two layers deserve different treatment because they carry different amounts of certainty. OSCA has a version number, an ABS date for the statistics and a planned 2027 update, which is enough to code against today. The skills layer has none of those things yet. So the response that fits is firm on occupations and deliberately loose on skills, and the next sections take them in that order.

Why your occupation codes will drift from official data

Occupation codes rarely live in one place. They sit in the HRIS, in position descriptions, in recruitment templates and in the reports that go to the executive or to central agencies. Each copy was set at a different time by a different person, which is why they often disagree with each other already.

Once ABS series run on OSCA, a headcount coded in ANZSCO is being compared against a different structure. Where an occupation has been retitled, split or given a different skill level, your numbers and the market's numbers stop describing the same group of jobs, and few people reading the board paper have any reason to check. The gap widens after March 2027, because the ABS will keep updating OSCA while codes nobody owns stay frozen at whatever they were when the position was created.

Map your roles to OSCA this financial year

With the ABS series moving from September 2026, the mapping is worth doing now, before the next system upgrade swallows it. It is mostly careful desk work, and it goes faster when one named person owns the data. These are the steps in the order they build.

The flagged list is the most useful thing the exercise produces. It shows where your job design is ambiguous, and that is often where your capability questions have been hiding.

• Find every place an occupation code lives: HRIS fields, position description templates, recruitment forms and any recurring report that groups people by occupation.
• Code each position as designed, whoever currently fills it, so the mapping survives turnover and acting arrangements.
• Record a reason and a confidence level for each mapping, and flag positions that sit across two occupations or whose ANZSCO occupation has been split or retitled in OSCA.
• Keep the ANZSCO code beside the OSCA code for a transition period, so historical trend lines still run while new reporting lines up with the ABS.
• Put the OSCA 2027 draft and the planned March 2027 release in the calendar, then recheck only the flagged positions, since the ABS expects the changes at the 6-digit level.

Keep your skills language loosely coupled to the National Skills Taxonomy

With the ASC decommissioned and the National Skills Taxonomy still in development, any skills framework you build today has to survive a change of reference point. The practical way to do that is to keep your own skill names as the primary language, written the way your managers talk, and to hold any national reference in a separate mapping field.

That separation lets you map to the new taxonomy when it lands instead of rebuilding twice. The ASC's shape of core competencies, specialist tasks and technology tools is still a reasonable way to organise your own thinking, but JSA has not said whether the National Skills Taxonomy will keep that shape, so treat it as scaffolding you can take down. Be sceptical of any product or adviser claiming alignment with a taxonomy that has not been released. Our skills taxonomy consulting page explains how we approach the internal side.

APS agencies and their suppliers will feel it first

The ABS and Jobs and Skills Australia are both Commonwealth bodies, and APS workforce plans lean on their data more than most private sector plans do. When an agency makes a budget case, explains a recruitment shortfall or reports capability gaps upwards, it usually points to national labour market evidence. Once that evidence is published on OSCA, an agency still reporting in ANZSCO has to translate every comparison by hand or quietly stop making them.

Suppliers sit downstream of that. Firms that provide contractors, labour hire or project teams to government should expect role descriptions and workforce reporting requests to move towards OSCA language over time, and the ones that have mapped their own roles will find those conversations easier. Our strategic workforce planning work covers how to keep the wider plan current while this happens.

How one mismatched code ends up in an executive pack

Picture a mid-sized agency preparing its annual workforce plan. The workforce analyst pulls the agency's digital roles from the HRIS by occupation code and charts them against the national labour market series, to show leadership how hard those roles will be to fill. The internal codes are ANZSCO, set when each position was created, and the national series is now on OSCA.

For most roles the comparison roughly holds. For a few, the OSCA occupation has a different title, task list or skill level, so the agency is comparing its people against a group defined differently. The chart looks authoritative, goes into the executive pack and supports a hiring decision. Had the analyst worked from a mapping table with a flag column, those few roles would have carried a footnote or been left out, and the hiring case would have rested on comparisons that hold.

Tie every classification to a decision

Classification work expands to fill the time available. You can spend months debating which OSCA occupation a hybrid role belongs in while the real workforce question (do we have the people to deliver next year's priorities?) goes unanswered. Mapping is never perfectly one-to-one, and some roles will always be a judgement call, which is fine as long as the judgement is written down.

A useful test is to ask which decision each classification supports. If an OSCA code helps you compare against the market, justify a hiring case or spot a capability gap, it earns its place; if it only exists for tidiness, record it and move on. Skills work the same way: build the part your managers will use for staffing and development decisions, and fill in the national mapping later. A strategic workforce plan starts from the organisation's goals and uses classifications as evidence, not as the destination.

Where Propellion Labs can help

The mapping table, the flagged list and the separate skills field are each a modest piece of work, but they tend to land on a workforce team already busy with budget season. That is the gap our people advisory work fills. It is led by co-founder Aarti Tandon, who has more than 15 years in recruitment, strategic HR and project management, including end-to-end recruitment for government, non-profit and private organisations in Australia.

We start by listening to your priorities and looking at your data, then map roles to OSCA, design skills language your managers will use and connect both to a plan leadership can act on. Where you need a live picture of skills, we use MuchSkills, built by our partner studio team. You can read more about our HR advisory and transformation work.

What to do before OSCA 2027 lands

For this financial year, map positions to OSCA with the ANZSCO code kept beside it, flag the roles that do not map cleanly, put the OSCA 2027 draft and release in the calendar, and keep your skills language in your own words with room for a national mapping later.

The national changes also hand you a free audit. The roles that will not sit neatly in an OSCA occupation are usually the ones your organisation has never quite defined, and those are often the roles carrying your biggest capability risk. Start the mapping with that list in mind, and if you would like a second pair of eyes on it, get in touch.