Gallagher 2026: Revenue Plans and Headcount

Short answer

Gallagher’s 2026 survey is a planning prompt, not a staffing forecast. Its revenue and headcount figures are separate aggregate results, so they do not identify the same employers or quantify a workforce shortfall. Convert your own growth plan into demand units, qualified hours, timing, and available capacity before choosing whether to hire, redesign work, outsource, or automate.

What Gallagher’s benchmark says

On September 9, 2026, Gallagher published findings from its US Workforce Trends Report. The survey covered 3,717 US employers and collected responses between January and March 2026. Gallagher reported that 61% anticipated revenue growth by 2027, while 50% expected workforce headcount to increase. Gallagher’s release

The comparison is a useful planning prompt, but it is not a capacity forecast. The percentages are separate aggregate results. The release does not show how many employers selected both responses, the expected scale of either change, or whether the plans concern the same functions and periods.

The 11-percentage-point difference therefore cannot be interpreted as a staffing shortage of any fixed size. Revenue can grow through price, volume, customer or product mix, acquisitions, outsourcing, lower rework, or process changes. Each mechanism can produce a different workload implication.

Translate growth into operational demand

Before selecting recruitment, outsourcing, redesign, or technology, make the business plan operationally legible:

1. Identify the growth mechanism. Separate volume, price, mix, retention, acquisition, new products, outsourcing, and process changes.
2. Choose a demand unit. Use orders, projects, cases, deliveries, service calls, production runs, or another item that generates work.
3. Estimate work per unit. Include operating time, review, handoffs, management attention, and specialist input.
4. Locate demand. Record when and where the work occurs, including peaks, shifts, launches, and local constraints.
5. Define required capability. Specify skills, credentials, authorizations, access rights, language coverage, or local knowledge.
6. Calculate usable capacity. Adjust scheduled hours for leave, vacancies, training, ramp time, supervision, and role-specific limits.

The resulting question is not simply “Do we need more people?” It is “Which work needs which qualified capacity, where and when, and how confident are we in that estimate?”

Original practical framework: the Growth Plan to Work Test

The following is an original proposed planning artifact for this article, not a conclusion or method taken from Gallagher’s survey. Copy it into a working document and complete one row for each distinct growth mechanism.

Planning period: [Enter dates]
Business area and location: [Enter scope]
Decision owner: [Enter name or role]
Review date: [Enter date]

Do not combine price, volume, and product changes in one row. Their workload implications may differ. For each input, record the source date and explain the confidence rating. Low confidence should lead to an earlier review, stronger evidence, or a reversible commitment rather than false precision.

Use these checks:

Required qualified hours = demand units × hours per unit, adjusted for timing and required capability.

Available qualified hours = scheduled capacity minus known unavailable time and role-specific constraints.

Record the decision after reviewing the completed rows:

• Constraint currently supported by evidence: [Enter finding]
• Selected response and reason: [Enter response]
• Action owner and due date: [Enter owner and date]
• Next review trigger: [Enter event, threshold and reviewer]

Diagnose the constraint before responding

Treat a reported capacity problem as a hypothesis. Test which condition applies:

• Aggregate capacity: Required qualified hours exceed available qualified hours in the relevant period.
• Schedule: Capacity exists overall, but not on the required shift, date, or location.
• Skill or authorization: People are available, but too few meet the work requirements.
• Vacancy and ramp: Roles are unfilled, or new starters cannot yet contribute as assumed.
• Process: Rework, handoffs, approvals, or unclear ownership consume unexpected capacity.
• Evidence quality: Forecasts, time estimates, or staffing records are incomplete, stale, or inconsistent.

A persistent qualified-hours gap may support recruitment. A schedule problem may require roster changes. A capability constraint may call for training, authorization planning, or work redesign. Process pressure should be investigated before additional capacity is assumed to be necessary.

Fictional example: one plan, two workload effects

Illustrative example, not customer evidence: A regional service business expects revenue growth while keeping total headcount flat. Its plan combines a price change with a premium service launch.

The price change is recorded separately because it creates no assumed increase in service volume. The launch generates additional appointments in two locations and requires a specific authorization. The relevant constraint is therefore qualified local coverage, not company-wide headcount.

The plan assigns an owner to confirm coverage four weeks before launch. If coverage is not confirmed, the response options are to sequence the launch, authorize or train existing staff where appropriate, obtain approved external support, or recruit for the named capability. Hiring remains possible, but it is connected to evidence and a defined trigger.

For implementation, Anticipating Hiring Needs: A Trigger and Scenario Worksheet provides a deeper process for scenario ranges and review triggers. Workforce Planning Tools: What Headcount Data Misses explains how to compare demand hours with usable capacity.

Use turnover and AI findings conditionally

Gallagher’s release also reports findings about turnover, intended AI adoption, and concerns about trust. These provide attributed context, not evidence that any factor caused the difference between revenue and headcount expectations.

Include turnover only when local vacancy, replacement, retention, or ramp assumptions change available qualified capacity. Include AI only when a documented workflow change affects task hours, review work, training, governance, or exception handling. Do not count expected productivity as available capacity before accountable people have tested the relevant work and reviewed the results.

Method and interpretation limits

The evidence used here is a Gallagher-issued release carried by PR Newswire, not independent validation of Gallagher’s conclusions. It describes expectations reported by surveyed US employers, not observed future outcomes or a measurement of all employers.

The supplied release does not provide the sampling frame, response rate, weighting, respondent roles, industry and organization-size distributions, exact question wording, or cross-tabulation of the revenue and headcount answers. It does not establish causal relationships among turnover, AI, management practices, revenue, and workforce capacity. Review the full report methodology and original tables before making additional numerical claims.

Glossary: practical working definitions

Available qualified capacity: Work time that people can actually contribute to a defined activity during a named period. It adjusts scheduled capacity for planned absence, vacancies, training, ramp time, supervision, access, skills, authorizations, and other known limits. It is narrower than total scheduled time.

Capacity constraint: The specific limit preventing a plan from being delivered as assumed. It may involve total hours, timing, location, shift coverage, supervision, credentials, systems, suppliers, or another dependency. Naming the constraint helps prevent a generic staffing response to a more specific problem.

Demand unit: A measurable item that generates work, such as an order, project, customer case, delivery, production run, or service appointment. A useful demand unit connects a business assumption to operational activity. It should not be selected only because it is easy to count.

Evidence confidence: A stated assessment of how dependable a planning input is. Confidence may reflect source quality, recency, agreement with observed operations, sample size, and the range of plausible outcomes. A confidence label communicates uncertainty but does not turn a forecast into a fact.

Headcount: The number of people employed or planned within a defined population. It can support budgets and governance, but it does not show available hours, workload, timing, location, capability coverage, productivity assumptions, or whether people can perform a particular activity.

Qualified hours: Hours provided by people who meet the requirements for a defined activity. Requirements may include training, authorization, experience, local knowledge, language capability, system access, or supervisory coverage. Qualified hours are not necessarily interchangeable across roles, locations, or periods.

Review trigger: A pre-agreed event or threshold that prompts reconsideration of an assumption or action. Examples include a delayed launch, demand outside the scenario range, a sustained vacancy, or unexpectedly high exception work. A useful trigger identifies the evidence, reviewer, and review timing.

Scenario range: A bounded set of plausible planning cases, commonly expressed as low, base, and high demand. Its purpose is to reveal which assumptions drive the decision and which responses remain sensible under uncertainty, not to claim that one case will occur.

Workload implication: The expected operational effect of a business assumption. It can include changed demand units, hours per unit, timing, handoffs, quality requirements, exception work, or capability needs. A revenue change is a commercial outcome and is not automatically a workload implication.

Workforce deficit: A conclusion that should be used only after comparing required qualified capacity with available qualified capacity for a named period, role, and location. It cannot be inferred from separate aggregate percentages concerning expected revenue and headcount growth.

FAQ

Does a 61% revenue-growth figure versus 50% headcount-growth figure prove a staffing gap?

No. It is a difference between two aggregate survey shares. It does not show which employers expected both outcomes, the scale of their changes, or the work needed to generate revenue growth.

What should a workforce plan measure besides headcount?

Measure demand units, hours per unit, timing, location, required skills or authorizations, available qualified hours, vacancy and ramp assumptions, and confidence in each input. Review them against defined scenario ranges and triggers.

Should automation be treated as extra capacity in a workforce plan?

Treat it as an assumption requiring evidence. Identify tasks that may change, the review or exception work that remains, when the change could take effect, and who is accountable for evaluating the result.