Using O*NET Occupation Data for Nursing Workforce Planning

What O*NET Is — and Why Wage Data Alone Leaves a Gap

Picture a Director of Nursing preparing for a budget conversation about a chronic vacancy on the med-surg unit. She has the BLS median wage figure — the RN median annual wage of $93,600 (BLS Occupational Outlook Handbook, May 2024) — and she can show where her posted pay band sits relative to that number. What she cannot easily answer is a quieter, more structural question: do we have anyone internal who could move into this role with targeted support, or are we starting from zero every time we post?

That gap — between knowing what a role pays and knowing what a role requires — is where ONET occupational data becomes useful. ONET is a publicly accessible database maintained by the U.S. Department of Labor's Employment and Training Administration. It publishes structured profiles for hundreds of occupations, including Registered Nurses (ONET-SOC 29-1141.00) and Licensed Practical and Vocational Nurses (ONET-SOC 29-2061.00). Each profile describes the skills, tasks, knowledge areas, abilities, and work activities the occupation involves, along with a Job Zone rating that summarizes the typical education, experience, and on-the-job training a worker needs to perform the role competently.

On its own, an O*NET profile is rich but static — a detailed job description without a wage signal. On its own, a BLS OES wage row is precise but thin — a pay figure without occupational context. The practical value comes from joining the two by their shared SOC code. This article explains how that join works, what it surfaces for nursing workforce planning, and how nurse leaders can begin applying it to internal-transfer and reskilling decisions.

Occupational data in this article is sourced from ONET, licensed under CC BY 4.0. O*NET® is a trademark of the U.S. Department of Labor, Employment and Training Administration. Source: https://www.onetcenter.org/*

The SOC-Code Join: How O*NET and BLS Wage Data Connect

The Standard Occupational Classification (SOC) code is the shared key that links the two datasets. BLS Occupational Employment and Wage Statistics (OEWS) publishes median and percentile wages by SOC code — national, state, and metropolitan-area — on a regular release cycle. ONET structures its occupational profiles using ONET-SOC codes, which are either identical to or derived from the BLS SOC taxonomy.

For nursing, the alignment is direct:

• Registered Nurses → SOC 29-1141 / O*NET-SOC 29-1141.00. BLS May 2024 data: median annual wage $93,600; 10th percentile below $66,030; 90th percentile above $135,320.
• Licensed Practical and Vocational Nurses → SOC 29-2061 / O*NET-SOC 29-2061.00. BLS May 2024 data: median annual wage $62,340; 10th percentile below $47,960; 90th percentile above $80,510.

When you join a BLS OES wage row to its corresponding O*NET profile, you get a single enriched record: what the occupation pays and what it involves. For a nurse manager or HR director reviewing internal talent, that enriched record makes it possible to ask structured questions — not just "is our pay competitive?" but "how far is an LPN/LVN from the skill and knowledge profile of an RN, and what would a reskilling pathway look like?"

See our BLS nurse wage benchmarking guide for a deeper walkthrough of how to read and apply the BLS OES percentile structure to your internal pay bands.

What O*NET Profiles Contain: Skills, Tasks, and Job Zone

An O*NET occupational profile for a nursing role is organized into several scored dimensions. The most relevant for workforce planning are:

Skills — rated by importance and level. For RNs, the profile captures both technical nursing competencies and the social/cognitive skills — critical thinking, active listening, coordination, monitoring — that distinguish experienced clinical nurses from newer graduates. Skills ratings allow a meaningful comparison between two occupations: where an LPN/LVN's skill profile overlaps significantly with an RN's, a lateral or upward internal transfer is more feasible than a ground-up external hire.

Tasks — specific work activities performed in the role. The RN task list includes clinical decision-making, patient assessment, care planning, and collaboration with the care team. The LPN/LVN task list covers a narrower clinical scope, generally under the supervision of an RN or physician. Reviewing task overlap helps identify how much of an internal candidate's daily work already maps to the target role.

Knowledge areas — the domains of knowledge the occupation draws on. Both RN and LPN/LVN profiles include medicine, psychology, customer and personal service, and English language, among others. The degree of overlap between a current employee's occupational knowledge profile and the target role's requirements is a practical proxy for reskilling distance.

Work Activities and Work Context — how the work is organized and where it happens. For nursing, this dimension captures the physical demands, the degree of decision-making authority, the pace and variability of tasks, and the interpersonal intensity. These dimensions matter when evaluating whether an internal candidate who has been working in a lower-acuity setting is genuinely prepared for the demands of, say, a telemetry unit.

Job Zone — a summary rating on a 1–5 scale that captures the typical education, related experience, and on-the-job training associated with competent performance. RNs are commonly associated with Job Zone 4 (substantial preparation needed — typically a Bachelor's degree plus experience), while LPN/LVNs are commonly associated with Job Zone 3 (medium preparation — typically a vocational certificate or Associate's degree). Verify current Job Zone values against the ONET database at https://www.onetcenter.org/ before using them in formal workforce documents.*

The Job Zone difference between LPN/LVN (3) and RN (4) is not a ceiling — it is a measure of the preparation gap. For facilities running LPN-to-RN bridge programs, O*NET Job Zone is a useful, neutral way to frame that gap for finance or operations stakeholders who are less familiar with clinical credentialing.

Applying O*NET to Internal-Transfer and Reskilling Decisions

The practical payoff of O*NET nursing data is in workforce-planning decisions that would otherwise be made on intuition alone.

Mapping internal-transfer pathways. When a unit has a persistent vacancy, the instinctive response is to post externally. But the national average time-to-fill for an experienced RN is 78 days (NSI 2026 Report, via Kahuna Workforce, 2026) — nearly three months of operating below capacity. O*NET skill and task profiles give a nurse manager a structured basis for evaluating whether an existing LPN/LVN, nursing assistant, or clinical support role has enough skill overlap with the open RN role to support an accelerated internal pathway. This is not a guarantee of success; it is a way to make the evaluation more systematic and less dependent on who happens to come to mind.

Scoping reskilling investments. When a facility is considering funding an LPN-to-RN bridge program or a CNA-to-LPN pathway, O*NET profiles help scope the gap. The difference in knowledge areas, skill levels, and work activities between two adjacent occupations gives education or HR leadership a content-grounded brief for selecting or evaluating a training program. It is worth noting that the BLS projects RN employment to grow approximately 5% from 2024 to 2034, generating roughly 189,100 annual openings (BLS Occupational Outlook Handbook, 2024–2034 projection) — a projection that makes internal reskilling pipelines more strategically valuable than a one-time external hire.

Grounding compensation conversations. When a facility promotes an LPN/LVN into an RN role, the O*NET skill and Job Zone profiles provide an objective reference point for the compensation conversation: the new role carries a meaningfully different scope of practice, a higher knowledge requirement, and a higher credential threshold — and the BLS OES percentile structure for SOC 29-1141 gives the external market signal for what that difference is worth. Our RN vs. LPN wage difference guide covers the BLS percentile spread between these two roles in detail.

Supporting multi-facility planning. Regional HR directors managing nursing FTEs across multiple facilities can use ONET profiles to standardize how they classify roles, compare skill gaps across sites, and identify which locations have the deepest internal bench for reskilling. Without a shared occupational framework, cross-facility talent analysis tends to collapse into inconsistent job title comparisons. ONET SOC codes provide a stable, publicly defined taxonomy.

For a broader framework on building these decisions into a repeatable planning process, see our nursing workforce analytics guide and our HR director nurse compensation resource.

O*NET in Practice: What to Watch For

A few practical notes for nurse leaders and HR directors beginning to work with O*NET data:

The profiles describe occupations, not individuals. ONET ratings are population-level summaries of what the occupation typically requires — not an assessment of any specific employee. Internal-transfer decisions still require individual performance data, credentialing review, and manager judgment. ONET gives the structural frame; facility-level data fills it in.

Skill importance scores are ordinal, not absolute. A skill rated "very important" in the RN profile and "important" in the LPN/LVN profile does not mean the gap is fixed or uniform. The ratings inform direction, not distance.

Job Zone is a preparation summary, not a ceiling. An employee currently performing in a Job Zone 3 occupation who holds a Bachelor's degree is already closer to the Job Zone 4 preparation threshold than the occupational label suggests. Cross-reference O*NET data with your facility's actual credential records.

O*NET updates on a rolling schedule. Profiles are revised periodically as occupational data is refreshed. Always link to and cite the current O*NET release — particularly for Job Zone values and skill importance ratings — rather than reproducing static figures in internal documents.

Bringing It Together: O*NET as a Planning Layer, Not a Stand-Alone Tool

ONET nursing occupations data does its best work as a layer on top of, not a replacement for, wage benchmarking and turnover analytics. A facility that already tracks rolling 12-month RN turnover, monitors internal pay bands against BLS OES percentiles, and models the cost of a departure — NSI 2026 puts the average RN departure cost at $60,090 — has the operational context to make ONET's occupational profiles immediately actionable.

Each percentage-point increase in RN turnover costs the average hospital approximately $295,000 per year (NSI 2026 National Health Care Retention & RN Staffing Report, via Becker's Hospital Review, 2026).

When the turnover cost is visible and the occupational skill gap is structured, the case for investing in an internal reskilling pathway — rather than defaulting to a 78-day external search or costly agency coverage — becomes a quantifiable comparison, not a qualitative argument.

Nursing Workforce Planner integrates BLS OES wage benchmarking with ONET occupational enrichment, alongside rolling turnover tracking, retention risk scoring, and 6-month vacancy forecasting. The platform is built for nurse managers, Directors of Nursing, and CNOs at 50–300-bed facilities who are ready to move beyond spreadsheets — and self-serve pricing starts at $199/month. You can explore the full feature set at /features or start a 14-day free trial to see how the ONET–BLS join surfaces in your own workforce data.

Occupational data sourced from O*NET, licensed under CC BY 4.0. O*NET® is a trademark of the U.S. Department of Labor, Employment and Training Administration. https://www.onetcenter.org/