Workforce Planning 2027

Workforce Planning 2027 connects business demand, work design, AI, usable capacity, residual roles and reversal exposure to the workforce commitment that reaches the financial plan. The workforce number is the residual after those operating claims have been reconciled.

City Shift Finance thanks the contributors to this report for sharing firsthand operating evidence on workforce capacity, work design, technology, and workforce decisions.

Frank U. Hess

Former Global Intelligent Asset Management Leader, Accenture; Chairman of Vysr

Oscar Lovera

Chief Operating Officer, Xometry

Kathryn MacMillan

Founder & CEO, CircleHR

Ben Wieder

Founder & CEO, Level 6 Incentives

Pranav Dalal

Founder & CEO, Office Beacon

Workforce planning for 2027 is becoming a reconciliation problem. Business demand creates work, while process design, technology and role composition determine how much human capacity that work ultimately requires. Similar operating pressure can therefore produce very different labor decisions.

Vacancies, overtime, queues and repeated requests for staff can reflect genuine demand growth, but they can also reflect duplicated handling, accumulated approvals, poor deployment or work that no longer belongs in the process. AI adds another distinction because faster tasks do not automatically create usable capacity when review, exceptions, controls and human judgment remain.

City Shift Finance treats the workforce number as the residual of an evidence reconciliation, placing the burden of proof on the operating evidence before labor enters the financial plan. The 2027 commitment is the requirement that remains after demand, necessary work, process-added work, demonstrated technology effects, proven usable capacity, residual roles and reversal exposure have been reconciled.

Workforce pressure becomes economically meaningful before it becomes a headcount decision. Vacancies, overtime, service delays, management intervention, fatigue and repeated requests for additional staff can all signal a capacity problem, yet the same symptoms can also come from duplicated handling, fragmented systems, work performed below the right skill level, concentrated knowledge or process load that has accumulated around unchanged demand.

The distinction matters because the workforce response changes with the cause. Additional labor can relieve genuine demand growth, while the same hiring decision can preserve avoidable work when paid time is being consumed by repeated reviews, rework, administrative effort or poor deployment.

Capacity before headcount: genuine workload growth and paid time already consumed by vacancies, repeated handling, administrative work and poor deployment produce different labor economics, and the distinction changes the case for additional headcount.
Work before technology: AI can make an existing task faster while surrounding approvals, exceptions, controls and human judgment continue to consume paid time, leaving expected time savings financially different from usable capacity.
Role before reduction: removing task hours changes the work left behind. Judgment, accountability, customer context, coordination and specialist knowledge can become a larger share of the residual role even when routine execution falls.
Reversal before savings: a payroll reduction remains economically exposed when the underlying capacity is still required and later has to be recreated through overtime, recruitment, onboarding, ramp time or restored roles.

These conditions connect the operating evidence to the financial plan. Demand creates work, process design changes the labor attached to that work, technology changes what capacity may be released, residual work changes the role that remains, and reversal exposure changes the value of removing capacity too early.

The resulting workforce number is the residual of the operating evidence. City Shift Finance treats the 2027 commitment as the labor requirement that remains after legitimate work, process load, demonstrated technology effects, usable capacity, residual roles and reversal exposure have been reconciled.

CITY SHIFT FINANCE

The Workforce Reconciliation

The workforce number carries assumptions about business activity, work design, technology and human capacity even when those assumptions are not visible in the budget. A headcount total can remain unchanged while the operation underneath it moves through higher demand, vacancies, overtime, process friction, new technology, role redesign and changing skill requirements.

Demand establishes the activity baseline, while the labor requirement emerges from the work attached to that activity. Revenue, transactions, service volume and customer commitments create tasks, decisions, exceptions and service obligations, and product mix, complexity and operating standards determine how much work sits behind the same unit of demand. The workforce number becomes financially meaningful only after that work has been reconciled with the capacity the organization can actually use.

Business demand. Revenue, transactions, orders, customers and service volume establish the activity the business expects to carry. Forecast growth changes the demand signal, while the labor requirement depends on the work attached to that demand.
Necessary work. Business activity becomes tasks, cases, decisions, production requirements, service hours and exceptions. Changes in mix, complexity and service expectations can increase the work attached to the same unit of demand without changing the headline forecast.
Process-added work. Handoffs, duplicated reviews, rework, approvals and administrative activity consume labor inside the process. Paid hours can rise because the business has more work, because each unit carries more work, or because the route through the operation has become more labor intensive.
Technology effect. AI and automation can remove, compress or change parts of the work. Expected time savings remain economically different from released capacity until the live process shows what human work has disappeared, what new work has appeared and where the saved time has gone.

Global employment exposure

Generative AI Exposure

One in four workers globally are in occupations with some degree of generative AI exposure; the measure describes work that may change and makes no forecast that one in four jobs will disappear.

CITY SHIFT FINANCE

Proven usable capacity. The work left after elimination, redesign and technology determines the amount and type of human capacity still required. Routine execution can fall while judgment, accountability, customer context, coordination and specialist expertise become a larger share of the residual role.
Workforce commitment. The remaining requirement reaches the financial plan through headcount, compensation, contractors, overtime, technology spend and management capacity. Hiring, redeployment, holding vacancies, reskilling and reducing roles become financial responses to the evidence that survives the reconciliation.

Employer workforce responses

Changing Skill Needs

Employers expect a mix of hiring, internal movement and role reduction, with several labor actions occurring at the same time.

CITY SHIFT FINANCE

Operating experience shows where workforce pressure reflects genuine capacity limits and where additional labor would simply reproduce existing friction.

Frank U. Hess

Former Global Intelligent Asset Management Leader, Accenture; Chairman of Vysr

“The earliest signs are usually visible in operational behavior long before they appear in the financial statements.”

Oscar Lovera

Chief Operating Officer, Xometry

“Before approving any headcount increase, we audit the ratio between high-value tasks and administrative overhead within the requesting team. In fast-growing organisations, teams often feel overstretched because their daily workflow is bogged down by legacy manual processes or fragmented systems.”

Kathryn MacMillan

Founder & CEO, CircleHR

“All of these issues can stem from one fundamental problem: staffing levels no longer match the actual demand and workload of the business.”

Ben Wieder

Founder & CEO, Level 6 Incentives

“Here at Level 6 Incentives, I first want to know what is consuming people's hours.”

Pranav Dalal

Founder & CEO, Office Beacon

“Headcount tells me how many people I have. Capacity tells me what the organization can actually get done.”

Frank U. Hess

Operational Knowledge

Operational knowledge and decision-making are often highly dependent on particular individuals. An experienced supervisor may understand which asset presents the greatest risk, which intervention can safely be postponed, or why a recurring failure continues to return; however, that knowledge may never become part of a shared decision process.

When the individual is absent, moves into another role, or retires, the organization loses both expertise and consistency.

Technology And Decisions

Technology improves performance when it makes a relevant decision easier, faster, or more accurate; it adds complexity when it creates more data, interfaces, alerts, and administrative work without improving what people ultimately decide or do.

It provides the necessary context, presents meaningful alternatives, makes trade-offs explicit, and supports action within the existing workflow; the strongest operating effect is a lower cognitive burden without another layer of complexity for employees to manage.

Early Operating Signals

The earliest signs are usually visible in operational behavior long before they appear in the financial statements.

One of the clearest signals is a growing level of reactivity. More planned work is interrupted, priorities change more frequently, and teams spend increasing amounts of time responding to emergency requests. Each intervention may appear manageable when considered separately; taken together, they indicate that the organization is losing control of its workload.

Other early indicators include increasing schedule instability, more last-minute expediting, repeated planning changes, declining compliance with the maintenance plan, rising overtime, unavailable materials, aging work orders, and growing dependence on a small number of experienced individuals.

Decision-making also becomes more subjective as escalation, negotiation, and organizational influence begin to determine priorities while explicit operating criteria recede.

Oscar Lovera

Headcount Evidence

Before approving any headcount increase, we audit the ratio between high-value tasks and administrative overhead within the requesting team.

In fast-growing organisations, teams often feel overstretched because their daily workflow is bogged down by legacy manual processes or fragmented systems. When an account management team spends a large portion of the day on manual data entry or supplier tracking, additional headcount can simply expand the cost attached to an existing inefficiency.

We look for evidence that distinguishes physical human capacity limits from process friction that can be reduced through workflow automation.

Central, Regional And Local Roles

When scaling across diverse European markets, the division of central and local responsibilities comes down to separating shared data systems from local human context.

We centralise decisions that benefit directly from network scale, such as our pricing algorithms, software infrastructure, supplier matching, and core quality standards. These functions belong centrally because consistency drives operational efficiency.

At the same time, business development, key account management, and hands-on engineering support stay strictly regional. Manufacturing procurement relies heavily on local trust, language, and cultural understanding, making regional proximity indispensable for long-term customer relationships.

AI And Automation

AI and automation have fundamentally shifted our workforce strategy from simple headcount expansion toward role transformation.

In digital manufacturing, we use technology to reduce repetitive tasks such as manual CAD drawing analysis, quoting back-and-forths, and order tracking. The hiring profile then moves away from volume-based execution and toward work that depends on specialist judgment.

We invest in specialised talent such as Application Engineers and Strategic Account Managers where human expertise remains essential.

By embedding automated workflows into our operations, we scale transaction volume while directing investment toward the work that adds the most value to our customers and partners. Technology sets the baseline for operating speed, while our team focuses on complex problem-solving and client strategy.

Kathryn MacMillan

Pressure Appears Before Cost

When dealing with people often the symptoms of situations are apparent well before the financial impact.

When staffing levels or hiring plans stop matching actual demand, fatigue can surface before the financial effect becomes visible. Economic pressure may already be present through rising operating costs, high interest rates, expensive electricity and overheads, increasing compliance obligations, and strong competition; in business-to-business settings, client financial pressure can add another constraint as customers reduce spending.

The business effectively becomes a pressure cooker, with the operating pressure continuing to rise.

Management may keep the team lean as employees leave, roles are merged, processes are compressed and the remaining employees absorb more work.

Sometimes this works. If demand for the organisation's products or services has genuinely reduced, a leaner workforce may be able to comfortably manage the workload.

In other cases, fatigue rises even as the workforce becomes leaner.

The Early Operating Signals

Absenteeism begins to increase. Employees start taking the occasional day off simply because the pressure has become too much and they need a break. Burnout starts to appear, reducing people's capacity to work effectively and efficiently. Resentment can develop towards the employer because employees feel they are continually being asked to work beyond what they consider normal and reasonable expectations.

Fatigue follows. With prolonged fatigue and excessive workloads comes an increased risk of psychological injury and workers compensation claims. Employees become more likely to consider leaving, and suddenly the organisation has a retention problem as well.

All of these issues can stem from one fundamental problem: staffing levels no longer match the actual demand and workload of the business.

The Financial Effect Follows

The difficulty is that these early warning signs are not always recognised by busy managers. The business may initially believe it is saving money by operating with fewer employees. Before long, however, the financial consequences begin to emerge.

Personal/carer's leave costs increase as absenteeism rises, while productivity and efficiency decline as employees become fatigued or burnt out. Resentment can reduce discretionary effort; employees may still report for work while contributing less beyond the minimum requirement, which then affects productivity, service and overall business performance.

Psychological injury claims can increase workers compensation costs and premiums, while extended absences create an additional operating burden. The remaining team then carries more workload, potentially creating further fatigue and continuing the cycle.

Finally, when employees decide they have had enough and leave, the business faces recruitment costs, onboarding and training costs, lost knowledge and the inevitable reduction in productivity while new employees learn their roles.

What initially appeared to be a sensible cost-saving strategy can therefore become a significant and ongoing business expense.

The economics remain favorable while staffing levels match the work that needs to be done; once that relationship breaks, apparent savings can move into absence, turnover and operating disruption.

Ben Wieder

Headcount Evidence

Here at Level 6 Incentives, I first want to know what is consuming people's hours.

One client handled commissions through a manual process, and automation removed about 40 hours of work per pay cycle while reducing payout errors by 94%. The result shows that employee busyness can reflect process load as much as staffing shortage.

We look for repetitive data entry, verification, corrections, handoffs, and administrative work that keeps moving between people. When those hours fall through technology or better process design, another hire would simply add labor to a crowded workflow.

Process Before Headcount

We have encountered versions of this problem in incentive-program operations.

Submissions, reward fulfillment, participant support, reporting, tax administration, and verification can become scattered across departments or vendors. More people may temporarily keep everything moving, yet the underlying process stays tangled.

Here at Level 6 Incentives, we centralize much of that work through our Program HQ and automate repeatable tasks. My preference is to untangle the wires first because a cleaner process produces a more credible read of the remaining labor requirement.

AI And Automation

Our investment in AI automation company Aprendio has made this especially relevant for us.

I look at AI from the workflow upward like identifying repetitive work, determining what can reliably be automated, implementing it, and then measuring how much human capacity was genuinely released.

I wait until automation is functioning reliably before treating a role as removable because expected software capacity can count savings before they exist. Once the operating result is proven, hiring, redeployment, and future-role decisions rest on stronger evidence.

Pranav Dalal

Capacity Before Headcount

I've been doing this long enough to know that when a manager asks to add headcount, there is usually a legitimate operating signal behind the request: the team is busy, work is slipping, customers are waiting, deadlines are moving, or a specialist gap has emerged.

That pressure alone does not establish a headcount problem.

I look underneath the request at where the team's time is going, who is working below their skill level, where the same piece of work is touched two or three times, and whether the workload itself is rising or the existing process is making it harder to carry.

I've seen very talented people become the bottleneck simply because too much low-value work accumulated around them. If I add another person at that point, I may solve the symptom, but I've also made the bad process more expensive.

There are absolutely times when the answer is to hire. We've grown Office Beacon from five people to more than 5,500, so clearly I believe in adding people when the work supports it. But I want to see that we've addressed deployment and process first.

That's why I tend to think in terms of capacity: headcount tells me how many people I have, while capacity tells me what the organization can actually get done.

AI And Automation

I think we're still very early in understanding what AI will ultimately mean for workforce planning.

I begin the AI conversation with the work itself and look at the tasks technology can change before making any judgment about roles.

I look at which work is repetitive, what technology can handle better, where AI can make somebody faster or provide information they did not have before, and what that person can do with the capacity created.

I've spent my career building a people business. What I've seen again and again is that when you take lower-value work away from capable people, they don't suddenly become unnecessary. Very often they become more valuable because they can spend their time solving problems, dealing with customers, making decisions or doing the work that actually requires experience.

AI changes the economics of certain roles, and I think it will absolutely change hiring plans. I would be very careful about removing people based on capacity an organization only expects AI to create; proven capacity is the stronger basis for the workforce decision.

Removing the person before the work has actually disappeared counts capacity before it exists.

For me, AI is ultimately about extending what strong employees can accomplish. Better tools can materially increase what a capable person gets done, and that changes the economics of the role.

Scaling Across Locations

Going from five employees to thousands taught me that what works when you're small can become a problem surprisingly quickly when you scale.

In the early days, I could know what was happening everywhere. You can talk to everyone. Decisions come back to a very small group of people, and it works because the organization is small. You simply can't operate that way at 5,500 people across multiple countries.

At some point, the operating decision becomes the division between what I control centrally and what I leave with the people closest to the work.

Consistency in standards, systems and accountability is part of operating as one company, while local decisions often depend on people who understand the employees, market and day-to-day reality better than headquarters can from thousands of miles away.

Strong local leaders matter when they carry real authority over the decisions closest to their operations.

The mistake is adding management layers as a substitute for trust. Every new layer may look like additional control, but it can also mean another meeting, another approval and another place for a decision to get stuck.

I've found that ownership becomes more explicit as the organization grows; consistency adds value in some decisions, while local knowledge and speed make proximity to the work more valuable in others.

Scaling changes both the size of the workforce and the way the company itself operates.

Continue Reading

Continue into the work audit, AI capacity, productivity, residual roles, reversal economics and the final workforce commitment.

Existing activity can survive in a workforce plan simply because it is embedded in today's operating process, even when obsolete tasks, duplicated reviews, unnecessary handoffs and administrative effort continue to consume paid time.

The workforce audit therefore acts as a planning gate, with only work that retains a defensible operating purpose creating a headcount requirement.

Current State

Busy teams can appear capacity constrained even when employee time is being consumed by repetitive administration, duplicated reviews or work that no longer creates enough value to justify the labor attached to it.

Headcount requests can preserve the current process by adding labor before the organization separates genuine workload growth from poor deployment, unnecessary approvals, rework or avoidable process friction.

AI can magnify the same problem when it is applied to existing work too early. Task automation leaves the underlying work claim unresolved, and expected automation leaves usable capacity unproven.

Transformed State

Work With A Defensible Operating Purpose Becomes Headcount

Work Identified: recurring tasks, exceptions, approvals, corrections, reporting, administrative work and handoffs establish the employee time currently consumed by the process.

Work Removed: activity without sufficient operating or economic value leaves the labor requirement even when it has been embedded in the process for years.

Process Redesigned: ownership, approvals, handoffs and control points change around the work that remains, and the operating process can continue changing as technology is tested in live use.

Technology Applied: AI operates against work that has already been tested while the workflow continues to change through implementation; capacity enters the workforce plan after the operating result has settled and the released time remains usable.

CITY SHIFT FINANCE

AI can change the labor requirement, but the capacity assumed at the start rarely survives unchanged through task selection, process redesign, deployment, adoption and day-to-day operating use. Only demonstrated net capacity can change the 2027 workforce requirement.

The columns show the evidence required before capacity reaches the workforce plan. Process and deployment can loop until the live workflow settles.

1. Work Selected

Task selection begins with whether the work still belongs in the operating requirement.

Work that leaves the operating requirement carries no remaining automation case.

2. Process Baseline

The live workflow provides the baseline for any labor saving attributed to AI.

Reviews, approvals and handoffs remain part of the baseline when AI gains are measured.

Demand-created work and process-added work remain separate in the baseline.

3. AI + Workflow

AI performance is tested inside the live workflow, with process design changing as operating evidence changes.

Integration, data preparation, maintenance and other operating costs remain inside the economics.

Process portability limits the amount of work that has to be rebuilt when AI providers change.

4. Human Adoption

Day-to-day employee use establishes adoption, while license counts measure deployment.

Human review, judgment and exception handling remain part of the post-AI workload.

Partial adoption reduces the amount of capacity that can credibly enter the workforce plan.

5. Capacity Proven

Released capacity is evidenced by employee hours that disappear from the live workflow.

New AI-related work is deducted from released time, and persistence determines whether the capacity remains usable.

Sustained net capacity is the amount that can change hiring, redeployment or workforce-reduction decisions.

CITY SHIFT FINANCE

AI time savings matter financially through the destination of the released capacity, which can support more output, better work, redeployment, or a lower labor requirement.

Assumption

Time saved by AI is the productivity gain.

What matters

Time saved becomes economically meaningful through the destination of those hours; they may be absorbed by new work, used to improve quality, held as slack, or redeployed elsewhere. The destination of the released capacity determines the value.

Assumption

Released capacity automatically becomes more output.

What matters

Released capacity can increase output, shorten cycle time, improve a decision, reduce errors, or expand the scope of a role. Productivity is the operating effect created by the released capacity across those possible destinations.

Assumption

Released capacity automatically lowers the workforce requirement.

What matters

A workforce reduction is only one possible outcome. Capacity can support growth, absorb demand, reduce overtime, avoid hiring, or be redeployed. Only capacity that remains unused after those choices can support a lower labor requirement.

CITY SHIFT FINANCE

Task removal does not equal role removal

Same hours removed

Equal time savings can leave very different work behind.

Different residual work

The residual mix determines what the role becomes.

Residual role after AI or process change

Routine execution removed

Low

Residual effect

High

Judgment retained

Low

Higher concentration

High

Review and control added

Low

Added work

High

Work transferred elsewhere

Low

Transfer effect

High

Workforce consequence

Work Removed

Task hours genuinely leave the role.

Residual Work

Judgment, accountability, coordination, and review remain.

Role Outcome

The remaining work changes the shape, level, or combination of the role.

Workforce Decision

Same role · Combined role · More senior role · No longer a full role

CITY SHIFT FINANCE

Workforce reductions can create immediate payroll savings while leaving economic exposure behind when the underlying capacity is still required. City Shift Finance treats that saving as provisional until the capacity is proven unnecessary or rebuilt.

100 Pre-reduction

Reduce −30

Payroll leaves the plan before all work disappears.

Cost base 70

Absorb +10

Remaining work moves into overtime, cover, or delay.

Cost base 80

Rebuild +15

Recruiting and ramp costs return capacity to the business.

Cost base 95

95 Post-reversal

Only 5 index points of the original 30 remain.

CITY SHIFT FINANCE

The workforce number closes the planning chain. It reflects the labor requirement that remains after the work, capacity, role structure, and financial exposure have been reconciled.

Demand establishes the work requirement. Volume, service expectations, growth commitments, and operating obligations determine the amount of work the business still has to carry.

Necessary work and process-added work are economically different. Work created by demand remains part of the requirement, while duplicated handling, rework, approvals and administrative effort can increase paid time without increasing the underlying demand.

Technology changes the plan only when capacity is proven. AI and process gains affect labor requirements when released capacity is sustained, usable, and no longer absorbed by new review, exception, or control work.

The work left behind determines the role that remains. Removed task hours can leave the original role intact, create a combined role, increase the experience required, or leave too little coherent work to support a full position.

Removal carries a second price when capacity may have to return. Reversal exposure changes the economics of workforce reductions because payroll savings can later be offset by operating substitution, recruitment, compensation, onboarding, and ramp costs.

The workforce commitment is the residual. Headcount enters the financial plan after these operating conditions have been reconciled, leaving the number as the consequence of evidence at the end of the planning chain.

Learn More About Workforce

The financial plan ultimately records a number, but that number carries every unresolved assumption that preceded it. Capacity booked too early, work left untested, roles reduced before their remaining responsibilities are understood, and savings recorded before reversal exposure is known all survive inside the final workforce commitment.

Headcount therefore appears at the end of the operating evidence. Demand establishes the requirement, necessary work defines the obligations the business continues to carry, process-added work changes the labor attached to those obligations, technology changes the capacity available, and residual roles determine the human work that remains.

Reversal exposure then changes the economics of removing capacity that may have to return. The workforce number is the financial residual after those operating claims have been reconciled.

About This Report

Workforce Planning 2027 treats the workforce commitment as the financial residual of the operating evidence that precedes it. The report connects business demand, necessary work, process-added work, technology effects, usable capacity, residual roles, and reversal exposure to the labor requirement that ultimately reaches the financial plan.

The analysis combines international labor-market and workforce research with firsthand operating evidence from executives who have made decisions involving staffing capacity, process design, automation, organizational structure, and workforce change.

About The Authors

Tyler W. led the editorial development of the report, with research and analytical support from the City Shift Finance analyst team.

The authors thank the contributors whose operating experience informed this report:

Frank U. Hess: Former Global Intelligent Asset Management Leader, Accenture; Chairman of Vysr.

Oscar Lovera: Chief Operating Officer, Xometry.

Kathryn MacMillan: Founder & CEO, CircleHR.

Ben Wieder: Founder & CEO, Level 6 Incentives.

Pranav Dalal: Founder & CEO, Office Beacon.

Planning Under Pressure

Operating Significance

Workforce plans are usually expressed through approved roles, hiring targets, or headcount limits. Operating pressure can develop on a different timetable. A team can experience rising workload, vacancies, overtime, backlogs, or increased management intervention before any formal staffing decision changes.

Operating Evidence

The useful comparison is between the demand entering the operation, the capacity currently available, and the cost commitments already made. A persistent gap between those three conditions can indicate that the workforce plan no longer represents the operating requirement.

Financial Consequence

The cost can surface through more than payroll. Delayed hiring can move expense into overtime or external labor, while premature hiring can commit recurring cost before demand is established. The timing of the response therefore matters alongside the eventual headcount decision.

Workforce Planning 2027

The Workforce Reconciliation

Generative AI Exposure

Changing Skill Needs

Frank U. Hess

Oscar Lovera

Kathryn MacMillan

Ben Wieder

Pranav Dalal

Continue Reading

Current State

Transformed State

1. Work Selected

2. Process Baseline

3. AI + Workflow

4. Human Adoption

5. Capacity Proven

About This Report

About The Authors

Outcomes Defined by Impact

Sign in

Create your account

Verify your email

Sign in

Contact us

Contact us

Contact

What we do

Recent work

Who we are

Featured

Sign up to download