Research

Using BLS Employment Projections to Plan Support Coverage

How to read ten-year occupational projections, separate growth from replacement demand, and use the result as a planning range rather than a headcount promise.

On this page

Outsourced Philippines · 7 min read

Key stats

The U.S. Bureau of Labor Statistics Employment Projections program publishes ten-year projections of employment by occupation and industry, including annual openings that combine projected growth with replacement needs.

Methodology

This note reviews the BLS Employment Projections program, the Occupational Outlook Handbook, the Occupational Employment and Wage Statistics program, and state-level projection resources. It asks how an operations lead can use a long-range projection to plan support coverage without treating it as a forecast for one role, one client, or one hiring market.

Evidence summary

Read the projection as a direction, not a forecast for one role. The Bureau of Labor Statistics publishes a ten-year horizon with assumptions about the economy, and the further the date, the wider the uncertainty. Use it to frame a conversation about demand, not to justify a headcount. Write the horizon and the release date beside the number.

Separate growth from replacement demand. An occupation can have little net growth and still produce many openings because people leave or retire. The annual openings figure combines both. A team planning coverage should care about the total openings in the relevant occupation, not only the growth rate. Record which component the decision depends on.

Check the occupation code against the actual work. A support lane may combine tasks from several occupations, and no single code describes it perfectly. Use the closest code as an anchor and note the mismatch. If the role changes, revisit the mapping. A precise-looking code can hide a broad difference in duties.

Look at the industry projection as well as the occupation. A growing industry may hire more support staff even if the occupation total is flat. The industry view shows where the demand sits. Use both views when the client's sector is narrow. Record which one drove the conclusion.

Use state or metro projections when the hiring market is local. National projections smooth over regional differences that matter for recruiting and wages. If a local projection is unavailable, say so and use the national figure as context. Do not present a national number as a local one.

Compare the projection with current job postings and the team's own funnel. A projection describes a long trend; postings and applications describe the present. If the two disagree, the difference may be a skills mismatch, a schedule problem, or a sourcing issue. Write both readings in the planning note.

Do not convert a projection into a wage. Employment projections do not set pay, and wage data comes from a separate survey with its own definitions. Keep the two sources separate. If the team needs a budget range, use the wage survey and label its geography and period. A projection is not a price list.

Account for automation and task change. The projections include assumptions about productivity and technology, but the effect on a specific support task can be uneven. A task may shrink while a related review or exception role grows. Map the task, not just the occupation title. Record the assumption the plan depends on.

Check the education and training categories. The projections describe the typical entry path for an occupation, and a support role may require different experience. Use the category as context, not as a hiring requirement. A mismatch can explain why a candidate pool looks small. Adjust the requirement or the sourcing plan.

Build a coverage model with ranges. Use the projection to set a low and high expectation for demand, then test both against the team's capacity and the client's service level. A single-point forecast invites false confidence. A range makes the trade-off visible. Record the assumptions behind each end of the range.

Review the model when a new projection is released. The bureau updates the series periodically, and the assumptions can change. Compare the new release with the prior one and note what moved. Do not silently replace the old note. A short change log keeps the planning history readable.

Close with a decision and a review date. State what the team will do differently because of the projection, such as widening a search, changing a training plan, or revisiting a service line. Name the person who will check the result. The projection is useful only when it changes a choice the team can observe.

Use the projection to test a training plan. If the occupation outlook suggests steady replacement demand, a short internal training path may be more useful than a long search for an exact match. Identify the tasks a new hire can learn in the first month and the tasks that need experience. Record the training cost beside the hiring cost. The comparison turns a projection into an operating choice.

Check for overlap between occupation codes before adding their openings. Two codes may describe adjacent work, and summing them can double-count the same labor market. Read the definitions and choose the one that best matches the lane. If the work spans both, present a range rather than a single total. Note the overlap in the planning note.

Record the difference between projected openings and the team's actual applicant flow. A projection may suggest a healthy market while the team sees few qualified applicants. The gap can point to a schedule, a language requirement, or a sourcing channel. Write the observed numbers for a fixed period. Do not dismiss the local evidence because the national trend looks favorable.

Do not use the projection to set a service-level promise. A long-range estimate cannot tell the team how quickly a specific role will be filled. Keep hiring assumptions separate from client commitments. If a client asks for a start date, base it on the current funnel and a named fallback. Review the promise when the funnel changes.

Write a short assumptions page beside the model. List the occupation code, the geography, the horizon, the wage source, and the funnel period. Add the one assumption that would change the recommendation if it were wrong. Ask a colleague to challenge that assumption before the plan is shared. A model with visible assumptions is easier to repair than one that looks authoritative.

Read the projection

Write the occupation code, the horizon, and the release date. Note the headline growth and the annual openings. Check the assumptions. Record which figure the decision uses. Keep the source link.

Separate growth and replacement

Use annual openings to capture both components. Do not read growth alone as hiring demand. Note the replacement share if published. Compare with current postings. Record the difference.

Check the geography

Prefer a state or metro projection when the hire is local. Label a national substitute. Do not present a national figure as local. Note the period. Review the choice with the hiring owner.

Map the tasks

List the tasks in the lane and compare them with the occupation description. Note the mismatch. Use the closest code as an anchor. Revisit the map when scope changes. Record the assumption.

Pair with wages

Keep projections and wage estimates in separate columns. Note each source and period. Do not derive a wage from a projection. Use both to frame a range. Test the range with actual offers.

Write the limit

State what the projection cannot say about one client, one city, or one skill. Put the limit beside the conclusion. Ask whether the decision changes if the limit is material. Collect local evidence before committing. Review the note on the next release.

FAQs

Can a national projection tell me how many support staff to hire?

No. It describes a broad occupational or industry trend over a ten-year horizon. Your lane, client, location, and schedule are more specific. Use the projection as context and test the actual hiring funnel before committing to a headcount.

Why do annual openings exceed projected growth?

Annual openings combine growth with replacement demand, which includes people who leave an occupation or retire. An occupation can have little net growth and still need many new workers. Read both components before drawing a conclusion.

Should I use the occupation or the industry projection?

Use both when the client's sector is narrow. The occupation view describes the work, while the industry view describes where demand sits. Record which one drove your conclusion and note any mismatch.

How often should the projection be reviewed?

Review it when a new release appears and when the role, location, or service line changes. Keep the prior note and record what moved. A short change log is more useful than replacing the old figure without explanation.

Sources

  1. https://www.bls.gov/emp/
  2. https://www.bls.gov/ooh/
  3. https://www.bls.gov/oes/
  4. https://www.bls.gov/cew/

Philippines staffing

Build a clearer work lane.

Share the role, tools, schedule, and approval needs. We will use those details to shape a practical Philippines staffing request.

Contact Us