Workforce scenario planning software: what it is and what it isn't
Three weeks before a board meeting, a People Analytics Lead at a 900-person logistics company gets a message from the CFO: "We need to model three headcount scenarios for next year — flat, minus 8%, and a restructure around automation. Can the org-design tool do that?" The org chart platform the company already owns can move boxes around and recalculate reporting lines. It cannot tell her which roles are structurally exposed to AI-driven task automation in the first place. She has scenario modeling without a baseline to model from.
This is the gap that trips up most buyers evaluating workforce scenario planning software. Scenario tools are built to answer "what happens if we change X" — headcount, structure, location, cost. They are not built to answer "where is X already exposed." Getting a useful answer to the CFO's question requires both pieces, in the right order. This guide walks through what workforce scenario planning software actually does, where AI exposure scoring fits ahead of it, and how to evaluate vendors — including where enterprise platforms like Orgvue and Faethm sit relative to a mid-market budget.
The category, defined narrowly
Workforce scenario planning software lets an organization model alternative future states of its workforce — different headcount levels, different org structures, different skill mixes — and compare projected cost, capacity, and risk across them. The strongest platforms in this category do three things well: maintain a structured model of the current organization (the "digital twin" of headcount and reporting lines), let planners branch that model into multiple named scenarios, and surface side-by-side comparisons of cost and capacity across those branches.
What the category does not typically do — and this is the part that catches mid-market teams off guard — is originate the exposure or risk data that makes a scenario meaningful. A scenario tool can tell you what a 15% reduction in a department costs. It generally cannot tell you which roles in that department carry disproportionate AI task exposure and are therefore the more defensible candidates for review versus the roles that are not.
Gartner's 2024 research found that 86% of HR leaders have not implemented strategic workforce planning, and a related Gartner survey found 66% of organizations that do plan say their efforts are limited to basic headcount planning and that they struggle to demonstrate ROI on the exercise. Scenario software alone does not close that gap — it needs a substantive input to plan against.
Why exposure data has to come before the scenario
Strategic workforce planning with AI works best as a two-layer process, and skipping the first layer is the most common reason scenario planning initiatives stall at the "headcount planning" level Gartner describes. The two layers:
- Baseline exposure layer. Map the organization's actual roles to standardized occupational data and score how much of each role's task content is routine-cognitive, routine-physical, judgment-dependent, or creative. This produces a defensible, role-by-role starting picture.
- Scenario layer. Take that baseline and model alternative futures against it — what changes if the company invests in upskilling the highest-exposure department, or redeploys instead of backfilling in a given function, or holds headcount flat while task mix shifts.
Trying to run the scenario layer without the baseline layer is what produces the CFO's unanswerable question. Trying to run the baseline layer without ever moving to scenarios is what produces a report that sits in a folder. Both layers matter, and they are typically different tools.
How exposure scoring actually works: a worked example
WorkforceAnalysis builds the baseline layer specifically. The methodology starts from the U.S. Department of Labor's O*NET database — a public occupational classification system covering 1,016 occupational titles across 923 data-level occupations, representing more than 55,000 individual jobs, described by roughly 277 standardized descriptors and updated on a regular cycle with a primary annual refresh. (This site incorporates information from O*NET. Used under the CC BY 4.0 license. O*NET is a trademark of USDOL/ETA.)
Every role a customer uploads is mapped to its closest O*NET occupation. Each task associated with that occupation is then scored across four dimensions, each on a 0–100 scale:
- Cognitive routine — how repeatable and rule-based the thinking involved is
- Physical routine — how repeatable and rule-based the physical actions involved are
- Social/judgment — how much the task depends on negotiation, persuasion, or contextual human judgment
- Creative — how much the task depends on original synthesis or novel problem-solving
Here is a simplified worked example, using round numbers to illustrate the method rather than an actual customer output. Suppose a "Financial Analyst" role maps to an ONET occupation with three core tasks, weighted by ONET's own task-importance ratings: preparing standard variance reports (importance weight 0.4, cognitive-routine score 80), building ad hoc models for a board presentation (importance weight 0.35, creative score 65), and presenting findings to department heads (importance weight 0.25, social/judgment score 70). Weighting each task's relevant dimension score by its importance and summing gives a role-level exposure profile rather than a single flattened number — the variance-reporting task pulls the cognitive-routine dimension up, while the board-modeling and presentation tasks keep the creative and judgment dimensions meaningfully present. That profile, not a single "risk score," is what feeds into a Monitor / Review / Redeployment Candidate categorization — a triage label for where HR should look first, never a verdict on the role or the person in it.
This is the input a scenario planning exercise actually needs: not a guess about which departments "feel" exposed, but a task-level, O*NET-grounded profile for every role in the org chart.
Enterprise platforms vs. a self-serve baseline: what to expect at each level
Two enterprise-grade platforms come up often in scenario planning searches, and it is worth understanding what each is actually built for.
Orgvue is an enterprise workforce and org-design platform built around scenario modeling and a workforce "digital twin," with an AI automation-potential capability layered in. It is aimed at large organizations running complex, multi-scenario restructuring exercises, and it does not publish pricing publicly — evaluation happens through a sales process.
Faethm, now part of SAP, is positioned as an enterprise workforce and future-of-work scenario tool. Like Orgvue, it does not publish standalone self-serve pricing; it is typically evaluated and deployed as part of a broader enterprise HR technology stack.
Neither structural fact is a knock on either platform — they are built for organizations with the internal analytics capacity and budget to run a sales-led enterprise evaluation, and they do a great deal that a lighter tool does not attempt, including full scenario branching and cost modeling. The structural gap for a mid-market buyer is different: a 200–5,000 employee organization often needs the O*NET-grounded exposure baseline described above, produced quickly and self-serve, before it is ready to justify — or afford — an enterprise scenario platform at all. The market reflects that split. Workforce planning software as a category was estimated at $2.8 billion in 2024, projected to reach $5.3 billion by 2031 at an 8.7% CAGR, according to a 2024 6Wresearch/Verified Market Research estimate — a category broad enough to include both the enterprise scenario-modeling tier and the lighter, more targeted exposure-analysis tier underneath it.
A buyer's checklist for evaluating workforce scenario planning software
Before signing a demo request for any platform in this category, a buyer should be able to answer:
- Does this tool generate a baseline, or does it require one as an input? Many scenario platforms assume you already have exposure or risk scores loaded — confirm which layer you are actually buying.
- Is the underlying occupational data standardized and public, or proprietary? O*NET-grounded scoring can be explained line-by-line to a board or a CFO; a proprietary black-box score is harder to defend under scrutiny.
- Does the vendor publish pricing, or is evaluation sales-led? This alone is a strong proxy for whether the platform is scoped for a mid-market budget or an enterprise one.
- Does the tool stop at "at-risk" labeling, or does it connect to a redeployment or upskilling pathway? A scenario tool that only flags roles without suggesting where those people or budgets could go next leaves the harder half of the work undone.
- Can the same underlying data support both a one-time board briefing and an ongoing quarterly review? Point-in-time consulting engagements answer the first question well but are not repeatable; a self-serve platform should support both.
For deeper comparisons across specific product categories, see the guides on AI org design tools, enterprise workforce planning software, and a full AI workforce planning tools comparison.
Where WorkforceAnalysis fits
WorkforceAnalysis is built for the baseline layer, not the full enterprise scenario-modeling layer. It maps an organization's role list to O*NET occupations, produces the four-dimension exposure profile described above at the role and department level, and surfaces Monitor / Review / Redeployment Candidate categorizations that a People Analytics team can then carry into whatever scenario or planning tool they already use — or into board materials directly. It is priced and packaged for a mid-market team running this exercise itself, self-serve, without a sales-led enterprise procurement cycle. Full tier details are on the pricing page. For a deeper look at how this fits into a broader strategic workforce planning practice, see our guide to strategic workforce planning with AI.
Getting started: baseline first, then scenarios
The order matters. Before evaluating a full scenario platform, most mid-market teams get more immediate value from establishing the exposure baseline — it is faster to stand up, it does not require a sales-led procurement cycle, and it gives the board or CFO conversation something concrete to react to. To help structure that first pass, we've put together a Workforce Scenario Planning Workbook — a downloadable template for organizing role data, exposure inputs, and scenario assumptions before you bring in (or build out) a full modeling tool.