How BLS occupational data forecasts analytics demand across US metros

What to take away

• Business analytics and intelligence hiring plans should start from two BLS occupation lines: management analysts and data scientists.
• The Occupational Outlook Handbook gives the national direction, but OEWS metro tables give the local wage and employment base you actually hire against.
• Metro demand is not national demand scaled down: San Jose, Austin, Boston, Seattle, and New York each carry different industry mixes and pay floors.
• The BLS release schedule sets the calendar for when a forecast should be refreshed, not the other way around.
• A demand dashboard works when it tracks three layers: national projection, metro estimate, and your own requisition pipeline.
• BLS projections are a planning input, not a local verdict; treat them as one signal among several.

What the BLS Occupational Outlook Handbook projects for analysts

The BLS Occupational Outlook Handbook is the starting point for any defensible analytics hiring plan in the United States. It publishes occupation profiles with employment totals, projected openings, and the education and work experience employers typically require.

Two lines matter most for analytics teams. Management analysts cover the broad business analysis and consulting layer that sits inside banks, insurers, hospitals, and government agencies. Data scientists cover the modeling and quantitative layer that sits closer to engineering and product.

Management analyst projections describe an occupation that is large, widely distributed, and present in nearly every metro with a corporate or public sector base. That breadth makes it a good proxy for general analytics demand.

Data scientist projections describe a smaller occupation with sharper geographic concentration. Demand clusters where technology, finance, biotech, and research employers already sit.

Compare the two together. A metro can be strong in management analyst roles and thin in data scientist roles, or the reverse. That split changes what you recruit for and what you pay.

The Handbook also states typical entry requirements. Management analyst roles often accept a bachelor's degree plus prior business experience. Data scientist roles more often expect a quantitative graduate degree or equivalent applied experience.

Those entry paths affect your pipeline. If your metro has strong business schools but few quantitative programs, management analyst hiring will be easier than data scientist hiring.

Use the Handbook for direction, not for a local number. It answers what the occupation is and where it is heading nationally. It does not tell you what a Denver or Atlanta employer will pay next quarter.

For the career side of this, the distinction between analysis, analytics, and data science roles matters more than the job title. See analytics careers for how those tracks separate in practice.

What each occupation line tells you

BLS line	What it covers	Planning use
Management analysts	Business process, strategy, and operations analysis	Broad demand proxy across corporate and public employers
Data scientists	Statistical modeling, machine learning, quantitative research	Narrower, higher-pay demand concentrated in tech and finance metros

The table is deliberately small. Adding more occupation lines invites double counting, because analytics work is spread across many SOC codes.

Pulling OEWS metro and state wage tables into a demand model

The OEWS metro and state wage and employment estimates for management analyst roles give you the local base that the national projection cannot. OEWS reports employment counts and wage percentiles by occupation and area.

That means you can compare a metro's management analyst employment level against its total employment, then compare wages at the 10th, 25th, 50th, 75th, and 90th percentiles. The median tells you the market rate. The spread tells you how hard the top of the market is to reach.

OEWS tables for comparing analytics pay across metros let you line up several areas on one screen. This is where a national average stops being useful and a local number starts being useful.

Build the model in four steps.

1. Pull the management analyst and data scientist rows for each target metro from the OEWS tables.
2. Divide each occupation's employment by total metro employment to get a location quotient.
3. Pull the median and 75th percentile wages for the same rows.
4. Multiply your planned headcount by the 75th percentile wage to get a realistic budget, not an optimistic one.

A location quotient above one means the metro has more of that occupation than the national average. That usually signals an established hiring market with recruiters, job boards, and competing employers already active.

A location quotient below one means you may be creating the market rather than joining it. Budget for longer time to fill and for relocation or remote premiums.

State tables matter when your hiring radius crosses a metro boundary. Northern Virginia, for example, draws from both the Washington metro and statewide Virginia data, and the two do not tell the same story.

Wage data also anchors pay equity work. If your posted range sits below the metro median, your pipeline will thin before you notice, because candidates self select out early.

Keep the OEWS vintage visible in the model. OEWS estimates are annual and lag the current market, so a 2026 hiring plan built on the latest published tables is always working from a slightly older picture.

That lag is manageable if you label it. It is dangerous if you present the number as current.

For a fuller treatment of which measures deserve attention, see the best business intelligence tools 2027 comparison.

Translating national projections into metro hiring plans

National projections set direction. Metro plans set headcount. The translation step is where most workforce plans fail, because it treats the country as one labor market.

Start with the national projected growth rate for management analysts and data scientists. Then adjust it for the metro using three local signals: industry mix, employer concentration, and wage pressure.

Industry mix is the strongest signal. Austin and San Jose carry large technology and semiconductor employer bases. Boston and Raleigh Durham carry biotech and research. New York and Chicago carry finance and insurance. Seattle carries cloud and retail technology. Atlanta carries logistics, payments, and media.

Employer concentration is the second signal. A metro with three dominant employers behaves differently from one with three hundred mid sized employers. Concentration means fewer openings but also fewer competing offers.

Wage pressure is the third signal. If the metro's 75th percentile wage for data scientists is already near the top of your band, adding headcount will require either a band change or a different metro.

Here is a worked example. Suppose your national plan calls for twenty analytics hires next year. Your metro carries a location quotient of 1.4 for management analysts and 0.8 for data scientists.

That mix suggests you can hire management analysts at or near market rate, but data scientists will be harder. Shift the plan toward twelve management analyst hires and eight data scientist hires, and attach a longer time to fill to the data scientist slots.

Do the same exercise for each metro you hire in, then compare. The comparison is the plan. A single national number hides the constraint that actually binds.

If your organization hires across California, Texas, and New York, run three separate plans. State labor law, pay transparency rules, and remote work norms differ enough that one plan will misprice at least two of the three.

For the mechanics of building a repeatable process rather than a one off spreadsheet, see business intelligence 2027.

Reading Monthly Labor Review articles for hiring-cycle context

Monthly Labor Review articles on labor market trends relevant to analytics hiring add the context that tables cannot. The articles explain why a number moved, which matters when you are deciding whether to accelerate or pause hiring.

Mine them for three things: occupational composition changes, industry employment shifts, and methodological notes on how BLS measures the labor market.

Occupational composition articles help when a job title in your requisition system does not map cleanly to a SOC code. Analytics work is often split across management analysts, data scientists, statisticians, and computer occupations.

Industry employment articles help when your metro's demand depends on one sector. If finance employment in your metro is flat, management analyst demand there will likely be flat too, regardless of the national projection.

Methodological notes help you avoid overreading a single release. Revisions happen. A month that looks like a slowdown may be revised away.

Assign the reading. One analyst should own Monthly Labor Review each month and write a short note on anything that changes the hiring plan. That note is more useful than a dashboard nobody interprets.

The publication is also a good source of long run framing. Articles on remote work, occupational licensing, and wage growth all touch analytics hiring indirectly but materially.

Keep a running list of articles that changed a decision. Over a year, that list becomes the institutional memory your next plan needs.

For more on which trend signals are worth tracking, see this business intelligence case study.

Timing forecasts against the BLS release schedule

The BLS release schedule tells you when new data lands, and a forecast that updates on the wrong week is a forecast that argues with itself. Use the schedule to set your refresh calendar.

The Employment Situation release, usually the first Friday of the month, gives the headline labor market picture. It sets the tone for hiring conversations even though it is not occupation specific.

OEWS estimates arrive annually and feed the metro wage tables. When they land, your wage assumptions and location quotients need to be recomputed.

Occupational Outlook Handbook projections update on their own cycle, typically every two years. When they update, your national growth assumptions need a review.

Monthly Labor Review publishes continuously, so it does not have a single release date. Treat it as a monthly reading task rather than a scheduled data drop.

Build the calendar in four steps.

1. List every BLS release that touches your model: Employment Situation, OEWS, Occupational Outlook Handbook, and any state or metro series you use.
2. Mark each release date on the planning calendar at least a quarter ahead.
3. Assign an owner to each release who must confirm whether the model inputs changed.
4. Freeze the hiring plan between releases so it is not revised on rumor.

That last step matters more than it sounds. Plans revised weekly are not plans. They are reactions.

If your fiscal year starts in January, the December and January releases will land right when you are finalizing headcount. Decide in advance which release you will wait for and which you will not.

For a companion view on which forecast measures deserve the effort, see these business intelligence examples.

Building a business analytics and intelligence demand dashboard

A business analytics and intelligence demand dashboard should show the forecast and the evidence behind it on one page. If a reader cannot see why the number moved, the dashboard is decoration.

Keep the layout to three bands: national, metro, and internal.

The national band holds the BLS Occupational Outlook Handbook projection for management analysts and data scientists, plus the latest Employment Situation headline.

The metro band holds OEWS employment, median wage, 75th percentile wage, and location quotient for each metro you hire in. This band is where the dashboard earns its keep.

The internal band holds your own requisitions: openings, time to fill, offer acceptance rate, and attrition. Without this band, you cannot tell whether a hiring problem is market wide or specific to you.

Use a small number of tiles. Six to ten is enough. A dashboard with forty metrics gets one look.

Label every tile with its source and vintage. A wage tile without a vintage will be trusted long after it is stale.

Add a short written note each month. Two sentences on what changed and what you are doing about it. That note is what executives actually read.

The geography dimension deserves care. BLS geography statistics form the basis for metro level demand forecasts, and the metro definitions change over time as commuting patterns shift. Check the definition before comparing two years.

Keep the dashboard separate from the hiring plan. The dashboard reports; the plan decides. Mixing them produces a document that is neither.

Limits of BLS projections for local hiring decisions

BLS projections are national, model based, and lagged. Each of those three properties limits what they can tell you about a single metro.

National scope means the projection is an average across very different local markets. A metro with one dominant employer can move in the opposite direction from the national trend for several quarters.

Model based means the projections rest on assumptions about GDP growth, productivity, and labor force participation. Change an assumption and the projection changes.

Lagged means the data describe a labor market that has already moved. In fast hiring cycles, the gap between the reference period and today can span a full recruiting season.

Occupation coding is another limit. Analytics work is spread across several SOC codes, so any single occupation line undercounts the total. Management analysts alone do not capture every business analytics role.

Wage data has its own limits. OEWS wages are annual and do not capture equity, bonus, or remote pay adjustments that many analytics offers include.

Use BLS data to set the frame and your own pipeline data to set the decision. When the two disagree, trust your pipeline for the next two quarters and watch whether BLS catches up.

Document the disagreement. A note that says the national projection and local pipeline diverged, and what you did about it, is worth more than a clean chart.

Finally, remember that projections are not targets. A growing occupation does not obligate you to hire into it, and a flat one does not forbid it. The projection informs the plan; it does not write it.

Common questions

How often should I rebuild an analytics demand forecast? Rebuild the wage and employment inputs when OEWS publishes, review national assumptions when the Occupational Outlook Handbook updates, and refresh your internal pipeline data monthly. Anything more frequent usually adds noise.

Which BLS occupation line best represents business analytics hiring? Management analysts cover the broadest share of business analytics roles, while data scientists cover the quantitative modeling layer. Most teams need both lines, plus a check against statisticians and computer occupations.

Can I use national projections for a single metro? Only as a starting direction. Adjust for local industry mix, employer concentration, and wage pressure. A metro with one dominant sector can diverge from the national trend for several quarters.

What is a location quotient and why does it matter? It compares an occupation's share of local employment to its national share. Above one means the metro has an established market for that role; below one means you may be creating the market yourself.

Where do I find metro wage data for analytics roles? The OEWS tables publish employment and wage percentiles by occupation and area. Use the median for market rate and the 75th percentile for budgeting competitive offers.

How should I handle BLS data revisions? Keep the vintage on every input, note revisions when they land, and avoid changing a hiring plan on a single release. Wait for the next scheduled update before acting.