How to Calculate Workforce Capacity: From Headcount and Productive Hours to Required FTE

A team has 20 employees.

How much work can it complete?

The answer is not simply:

20 employees × target output

because total headcount is not the same as productive capacity.

Some employees may be:

• On leave
• In training
• Attending meetings
• Working partial periods
• Supporting non-production activities
• New to the process
• Operating below full proficiency

And even when everyone is available, capacity depends on how quickly the work can reasonably be completed.

A better capacity model connects:

Workload

↓

Working Days

↓

Available FTE

↓

Productive Hours

↓

AHT or CPH

↓

Expected Capacity

↓

Required FTE

This gives operations leaders a much stronger basis for staffing decisions.

What Is Workforce Capacity?

Workforce capacity is the amount of work a team can reasonably complete during a defined period using the resources and productive time available.

For transaction-based operations, capacity may be measured in:

Claims

Cases

Applications

Verifications

Requests

Transactions

or another unit of work.

For example:

Daily Capacity = Available FTE × Productive Hours per FTE × Cases per Hour

If:

Available FTE = 10

Productive hours per FTE = 7

CPH = 5

then:

10 × 7 × 5 = 350 cases per day

This provides a basic capacity estimate.

But there are several assumptions hidden inside that calculation, so each component needs to be understood.

Headcount Is Not the Same as FTE Capacity

Suppose a department has:

20 employees

That is the total headcount.

But today:

2 are on approved leave

1 is in training

1 is unavailable for another activity

The operationally available workforce may therefore be closer to:

16 employees

Even that does not tell us how many productive hours will actually be available.

This is why capacity planning should distinguish between:

Total Headcount

Scheduled Headcount

Available Headcount

Productive FTE

and:

Effective Capacity

These measures answer different questions.

Step 1: Determine the Workload

Capacity planning starts with demand.

Suppose expected monthly volume is:

50,000 cases

That is the workload the operation must process.

But management should also ask whether this represents:

Incoming demand only

or:

Incoming demand + existing backlog reduction

This distinction matters.

If 50,000 cases are expected to arrive next month and management also wants to reduce backlog by 5,000 cases, the real processing requirement is:

50,000 + 5,000 = 55,000 cases

The staffing requirement should be calculated against 55,000, not 50,000.

Step 2: Determine the Working Days

Do not automatically assume:

1 month = 4 weeks = 20 days

Calendar months differ.

For example, depending on weekends and holidays, a month might contain:

19 working days

20 working days

21 working days

22 working days

or more under another operating schedule.

If capacity is being calculated monthly, use the actual applicable working calendar wherever practical.

For example:

Monthly requirement = 55,000 cases

Working days = 22

Average daily requirement:

55,000 ÷ 22 = 2,500 cases per working day

That becomes the daily throughput requirement.

Step 3: Determine Productive Hours per FTE

An employee may be scheduled for eight or nine hours but not spend every minute processing transactions.

Time may be used for:

• Breaks
• Meetings
• Training
• Coaching
• Administrative activity
• System downtime
• Other non-production work

Therefore:

Scheduled Hours ≠ Productive Hours

Suppose an employee is scheduled for:

8 hours

but expected productive processing time is:

6.5 hours

Capacity should normally use the 6.5 productive hours if CPH is defined against productive processing time.

Using eight hours would overstate capacity.

Step 4: Determine CPH

CPH means:

Cases per Hour

A basic formula is:

CPH = Completed Cases ÷ Productive Hours

Suppose:

Completed cases = 42

Productive hours = 7

Then:

42 ÷ 7 = 6 CPH

If this is a reasonable expected processing rate for the Worktype, it can be used in capacity planning.

For example:

Productive hours per FTE = 7

Expected CPH = 6

Daily capacity per FTE:

7 × 6 = 42 cases

If 10 FTE are available:

42 × 10 = 420 cases per day

For more detail on these measures, read CPH, AHT, Productivity and Utilization: A Practical Guide for Operations Teams.

Step 5: Calculate Capacity per FTE

The basic transaction-based formula is:

Capacity per FTE = Productive Hours × CPH

Suppose:

Productive hours per day = 7.5

Expected CPH = 5

Then:

7.5 × 5 = 37.5 cases per FTE per day

Over 22 working days:

37.5 × 22 = 825 cases per FTE per month

One productive FTE can therefore theoretically support approximately:

825 monthly cases

under these assumptions.

Step 6: Calculate Required FTE

Now reverse the capacity formula.

Required FTE = Required Volume ÷ Capacity per FTE

Suppose:

Required monthly volume = 50,000

Capacity per FTE per month = 825

Then:

50,000 ÷ 825 = 60.61 FTE

Operationally, you cannot schedule 0.61 of a full employee unless partial allocation is possible.

So the planning requirement may be rounded according to the organization's staffing approach.

For example:

Approximately 61 productive FTE

This is the productive capacity requirement, not necessarily the total payroll headcount required.

That distinction becomes important when shrinkage and availability are included.

A Full Worked Example

Assume:

Monthly volume = 50,000 cases

Working days = 22

Productive hours per FTE per day = 7

Expected CPH = 5

Daily workload

50,000 ÷ 22 = 2,272.7 cases per day

Daily capacity per FTE

7 × 5 = 35 cases

Required productive FTE

2,272.7 ÷ 35 = 64.94

Therefore:

Approximately 65 productive FTE

The same result can be obtained monthly:

Monthly capacity per FTE:

22 × 7 × 5 = 770 cases

Required FTE:

50,000 ÷ 770 = 64.94

The daily and monthly calculations reconcile because the assumptions are consistent.

Calculate your workforce capacity with your own numbers

Use the free Praevexa Workforce Planner to model monthly volume, AHT or CPH, productive hours, shrinkage, working days, backlog, current HC and future hiring.

The planner shows your required headcount, effective productive capacity, staffing surplus or deficit, backlog trend and SLA risk month by month.

Open the Free Workforce Planner

Link that text to:

https://www.praevexa.com/WorkforcePlanner.aspx

Calculating Capacity Using AHT

Sometimes an operation has a reliable AHT rather than CPH.

AHT means:

Average Handling Time

Suppose:

AHT = 12 minutes per transaction

The theoretical number of cases per processing hour is:

60 ÷ 12 = 5 CPH

This can then be used in the previous formula.

Alternatively, required workload hours can be calculated directly.

Required Processing Hours = Volume × AHT in Minutes ÷ 60

Suppose:

Volume = 50,000

AHT = 12 minutes

Then:

50,000 × 12 ÷ 60 = 10,000 processing hours

If one FTE provides:

22 working days × 7 productive hours = 154 productive hours

Required FTE:

10,000 ÷ 154 = 64.94

Again:

Approximately 65 productive FTE

CPH and AHT Should Reconcile

If the measures refer to the same productive processing time and the same type of work:

Theoretical CPH = 60 ÷ AHT in minutes

For example:

AHT = 10 minutes

Theoretical CPH:

60 ÷ 10 = 6

AHT = 15 minutes

Theoretical CPH:

60 ÷ 15 = 4

However, actual reported CPH may differ if its denominator includes activities that are not included in measured handling time.

Therefore, before using AHT or CPH for staffing, verify that both metrics are defined consistently.

Why Small AHT Changes Can Have a Large Capacity Impact

Suppose:

AHT = 10 minutes

Capacity per productive hour:

6 cases

Now AHT increases to:

15 minutes

Capacity becomes:

4 cases per hour

That is a reduction of:

2 cases per hour

or:

33.3% lower theoretical throughput

If demand remains unchanged, required staffing increases considerably.

This demonstrates why operations leaders should monitor changes in handling time when building staffing plans.

Capacity Should Be Calculated by Worktype When Possible

A common mistake is using one average CPH for a process containing very different work.

Suppose monthly volume is:

Using a simple average CPH would be misleading.

Instead, calculate required processing hours separately.

Simple

20,000 ÷ 10 = 2,000 hours

Standard

20,000 ÷ 5 = 4,000 hours

Complex

10,000 ÷ 2 = 5,000 hours

Total required processing hours:

11,000 hours

Notice something important:

Complex work is only:

20% of volume

but consumes:

5,000 ÷ 11,000 = 45.5% of required processing hours

Volume alone would hide that workload.

This is why Worktype mix can significantly change staffing requirements.

Use Weighted AHT Carefully

A blended AHT can be useful when Worktype mix is stable.

Suppose:

Simple work = 40%

Standard = 40%

Complex = 20%

AHT values are:

Simple = 6 minutes

Standard = 12 minutes

Complex = 30 minutes

Weighted AHT:

(40% × 6) + (40% × 12) + (20% × 30)

= 2.4 + 4.8 + 6

= 13.2 minutes

That can support a blended capacity model.

But if next month's work mix changes materially, the same blended AHT may no longer be appropriate.

Include Backlog Reduction in Required Capacity

Suppose:

Incoming monthly volume = 50,000

Current backlog = 15,000

Management wants to reduce backlog by:

6,000 cases next month

Required production becomes:

50,000 + 6,000 = 56,000

If capacity per productive FTE is:

770 cases per month

then:

56,000 ÷ 770 = 72.73

Required productive FTE:

Approximately 73

If management staffed only for incoming demand:

50,000 ÷ 770 = 64.94

the team may stabilize backlog but will not achieve the intended reduction.

For more on backlog planning, read How to Manage Backlog, Aging and SLA in Case-Based Operations.

Backlog Burn-Down Formula

A useful operational measure is:

Net Burn-Down = Completed Volume − Incoming Volume

For example:

Daily incoming = 2,000

Daily completed = 2,300

Net burn-down:

300 cases per day

If backlog is:

6,000 cases

Approximate clearance period:

6,000 ÷ 300 = 20 working days

This assumes demand and capacity remain reasonably stable.

If completions are equal to or below incoming volume, backlog will not decline.

Productive FTE vs Paid FTE

So far, our calculations have estimated productive FTE requirement.

But suppose an employee is not productively available 100% of paid working time.

This is where shrinkage becomes relevant.

Shrinkage represents paid or scheduled capacity that is unavailable for the defined production activity due to factors included in the organization's shrinkage definition.

Examples might include:

• Leave
• Training
• Meetings
• Coaching
• Other approved non-production activities

Organizations define shrinkage differently, so the definition should be documented.

Converting Productive FTE to Required Headcount

Suppose:

Required productive FTE = 65

Expected availability for production = 85%

In other words:

Shrinkage = 15%

Required gross FTE can be estimated as:

Gross FTE = Productive FTE ÷ (1 − Shrinkage)

Therefore:

65 ÷ 0.85 = 76.47

Planning requirement:

Approximately 77 gross FTE

This illustrates why:

65 productive FTE

does not necessarily mean:

65 employees on payroll

The operation needs enough total capacity so that approximately 65 productive FTE remain available after expected shrinkage.

Do Not Add Shrinkage Incorrectly

A common mistake is:

Required productive FTE = 65

Shrinkage = 15%

Incorrect calculation:

65 × 1.15 = 74.75

The more appropriate availability adjustment is:

65 ÷ 0.85 = 76.47

Why?

Because 85% of 76.47 is approximately 65.

This distinction becomes larger as shrinkage increases.

Planned and Unplanned Shrinkage

For management purposes, it can be useful to separate:

Planned

• Approved leave
• Training
• Meetings
• Coaching
• Scheduled administrative activity

Unplanned

• Unexpected absence
• System disruption
• Other unforeseen loss of productive time

This helps explain why planned capacity differed from actual capacity.

The same principle applies to workforce attendance reporting.

Read How to Calculate Attendance Rate, Absenteeism and Planned vs Actual Working Hours.

Do Not Double-Count Shrinkage

This is an important modelling issue.

Suppose your assumption of:

7 productive hours per day

already excludes expected meetings, breaks and other non-production time.

If you then apply another shrinkage factor for those same activities, capacity will be understated.

Likewise, if leave has already reduced available FTE for the month, do not automatically deduct the same leave again inside another availability factor.

Every capacity model should document:

What is already included in productive hours?

What is included in shrinkage?

What has already been deducted from available FTE?

This prevents double counting.

Skill Availability Can Be More Important Than Total FTE

Suppose an operation has:

50 available employees

But only:

8 can process Worktype X

Worktype X requires:

12 productive FTE

The organization has a shortage of:

4 skilled FTE

even though total headcount appears sufficient.

This is a critical workforce-planning concept.

Capacity should therefore sometimes be calculated at:

Process

Queue

Worktype

Skill

rather than only at department level.

New-Hire Training Does Not Create Immediate Full Capacity

Suppose management hires:

10 employees

It may be tempting to add:

+10 FTE

to the capacity plan immediately.

But new employees may require:

Training

followed by:

Ramp-up

For example, an illustrative productivity ramp might look like:

Week 1 — 20%

Week 2 — 40%

Week 3 — 60%

Week 4 — 80%

Week 5 onward — 100%

Under such a model, 10 new employees do not contribute the equivalent of 10 fully productive FTE immediately.

Their effective productive capacity needs to be adjusted during the ramp period.

Effective FTE During Ramp

Suppose:

10 employees

Expected ramp productivity = 60%

Then effective capacity is:

10 × 60% = 6 fully productive FTE equivalents

If each full FTE provides:

35 cases per day

the new-hire group provides approximately:

6 × 35 = 210 cases per day

rather than:

10 × 35 = 350

This makes hiring forecasts much more realistic.

Training Time Should Also Be Accounted For

If new employees spend two weeks in training before entering production, their production capacity during those weeks may be zero or substantially reduced.

A hiring plan should therefore distinguish:

Hire Date

↓

Training

↓

Ramp

↓

Steady State

This is especially important when hiring is intended to solve a near-term backlog problem.

Hiring 20 people this month does not necessarily create 20 productive FTE this month.

Releases Need the Same Treatment

Capacity models should also account for planned employee releases.

Suppose:

Current productive FTE = 70

5 experienced employees leave at month-end.

10 new employees join.

If the 10 new employees are still ramping, the operation may temporarily have less effective capacity even though gross headcount increased.

A good workforce model therefore forecasts:

Opening FTE

Hiring

Training

Ramp

Attrition / Releases

Effective FTE

rather than headcount alone.

Capacity Planning Should Include Quality

Increasing throughput does not automatically mean the operation has more sustainable capacity.

Suppose:

Target CPH = 5

Actual CPH rises to:

6

But quality falls significantly.

If the additional errors generate rework, effective capacity may be lower than it appears.

For example:

10,000 completed cases

1,000 require rework

The operation generated additional workload for itself.

A balanced capacity model should therefore monitor:

Throughput

alongside:

Quality

Rework

SLA

This prevents speed from becoming the only staffing assumption.

Occupancy, Utilization and Productivity Are Different Concepts

These terms are often used interchangeably, but they should be defined separately.

Attendance

How much scheduled working time was attended?

Utilization

How much available time was used for the defined productive activity?

Productivity

How much output was achieved relative to expectation?

Capacity

How much work can the available workforce reasonably process?

An employee can have:

100% attendance

but:

80% productive utilization

while also achieving:

110% productivity

depending on the organization's definitions.

These measures should not be merged casually.

Use Historical Performance, Not Only Targets

Capacity can be calculated using:

Target CPH

but management should compare the result with historical performance.

Suppose:

Target CPH = 6

Actual stable CPH over six months = 4.8

Building the staffing model on 6 CPH may systematically underestimate the workforce requirement.

Management should understand why the target and actual differ.

Possible reasons include:

• Work complexity
• System limitations
• Incorrect target
• New employee mix
• Nonproductive activity
• Process inefficiency

A staffing plan should use assumptions that are both challenging and operationally credible.

Scenario Planning Is Better Than One Forecast

Instead of one staffing requirement, consider several scenarios.

For example:

Assumptions:

22 working days

7 productive hours per FTE per day

This immediately shows that staffing risk can come from either:

higher demand

or:

lower productivity

Scenario planning is much more useful than pretending one forecast will be exact.

Calculate Over- or Under-Staffing

Once required FTE is calculated, compare it with available effective FTE.

A simple formula is:

FTE Variance = Available Effective FTE − Required FTE

Suppose:

Available effective FTE = 68

Required FTE = 65

Variance:

+3 FTE

The model indicates approximately three FTE of capacity above the requirement.

Now suppose required FTE increases to:

73

Variance:

68 − 73 = -5 FTE

The operation now has an estimated shortage of five productive FTE.

The result should be interpreted alongside uncertainty in workload and productivity assumptions.

Translate an FTE Gap into Volume Impact

An FTE variance is useful.

But a volume impact may be even easier for managers to understand.

Suppose:

FTE shortage = 5

Daily productive hours per FTE = 7

CPH = 5

Daily capacity shortage:

5 × 7 × 5 = 175 cases

Over 22 working days:

175 × 22 = 3,850 cases

If the gap is not addressed, the model suggests approximately 3,850 cases of monthly capacity shortage, assuming the other inputs remain stable.

That can help quantify potential backlog impact.

A Practical Monthly Capacity Model

A good operational planning model might contain:

This gives management a clear chain from:

Demand

to:

Capacity

to:

Staffing Gap

Forecast Monthly Capacity Properly

Avoid converting weekly capacity into monthly capacity using:

Weekly Capacity × 4

unless the reporting period genuinely contains exactly four operational weeks.

A better monthly calculation is based on actual working days.

For example:

Daily capacity = 350 cases

September working days = 22

Monthly capacity:

350 × 22 = 7,700 cases

Another month may contain 20 working days:

350 × 20 = 7,000 cases

Same workforce.

Same productivity.

Different calendar capacity.

Capacity Should Be Dynamic

A strong capacity model should allow management to change assumptions such as:

Volume

Working Days

Headcount

Leave

Productive Hours

CPH

AHT

Training

Ramp Rate

Hiring

Releases

and immediately see the effect on:

Capacity

Required FTE

Over / Under Staffing

Backlog

This is much more useful than creating a static staffing number once a year.

What Should a Workforce Capacity Dashboard Show?

A useful management view may include:

Demand

Forecast Volume

Actual Volume

Backlog

Required Output

Workforce

Total HC

Available HC

Productive FTE

New Hires

Training FTE

Ramp FTE

Efficiency

AHT

CPH

Productive Hours

Utilization

Capacity

Daily Capacity

Monthly Capacity

Required FTE

Available Effective FTE

FTE Gap

Risk

Expected Backlog Change

SLA Exposure

Skill Gaps

This connects workforce planning directly to operational performance.

Common Workforce Capacity Mistakes

Using headcount as capacity: Employees are not always fully productively available.

Assuming every month has four weeks: Calendar capacity becomes inaccurate.

Using scheduled hours instead of productive hours: Capacity is overstated.

Double-counting shrinkage: The same lost time is deducted more than once.

Using one CPH for very different Worktypes: Work complexity is hidden.

Ignoring backlog targets: Staffing only covers incoming demand.

Counting new hires as fully productive immediately: Ramp-up is ignored.

Ignoring skills: Total headcount looks sufficient while one Worktype remains understaffed.

Using target productivity without checking actuals: Required FTE is understated.

Ignoring rework and quality: Apparent capacity may not represent first-time-right output.

A Practical Capacity Planning Checklist

Before approving a staffing model, ask:

1. What workload are we planning for?

2. Does it include backlog reduction?

3. How many actual working days are available?

4. What productive hours can one FTE reasonably provide?

5. What CPH or AHT assumption are we using?

6. Is that assumption supported by historical performance?

7. Do Worktypes have materially different handling times?

8. Have leave and shrinkage been included once—and only once?

9. Are new hires adjusted for training and ramp?

10. Are planned releases included?

11. Do we have enough people with the required skills?

12. What happens under higher-volume or lower-productivity scenarios?

13. What is the effective FTE gap?

14. What volume or backlog impact does that gap create?

If those questions can be answered clearly, management has a much stronger basis for staffing decisions.

From Headcount Planning to Capacity Intelligence

A basic workforce report says:

We have 70 employees.

A better report says:

We have 62 effective productive FTE this month.

A stronger capacity model says:

We require 68 productive FTE to meet incoming demand and the backlog target, leaving an estimated shortage of six FTE. At current CPH, that gap represents approximately 4,620 cases of monthly capacity.

Now management has actionable information.

The evolution is:

Headcount

↓

Availability

↓

Productive Hours

↓

Effective FTE

↓

Capacity

↓

Required FTE

↓

Staffing Gap

↓

Operational Impact

That is the difference between counting people and planning capacity.

How Praevexa's MIS Approach Supports Better Capacity Decisions

Praevexa's MIS and operations focus is centered on helping businesses turn operational data into management information.

Capacity planning becomes much stronger when managers can connect:

Work Volume

Productivity

AHT / CPH

Backlog

Quality

and:

Workforce Availability

Praevexa's applications address different parts of this operating environment:

Want to move beyond a one-time capacity calculation? Praevexa Workforce Planner lets you build a month-by-month staffing plan with forecast and actual volume, backlog, automation, attrition, hiring, training and ramp-up.

Build your workforce plan →

https://www.praevexa.com/WorkforcePlanner.aspx

Praevexa CaseFlow supports structured case-based operations and visibility into work allocation, backlog, processing activity and operational performance.

Praevexa QualityFlow provides structured QA information that can help management understand quality and rework risk.

Praevexa HRMS supports employee, roster, attendance and leave management, providing workforce context around planned and actual availability.

These are separate applications, but the management information they produce can contribute to a broader understanding of operational capacity.

The objective should not simply be:

“How many people do we have?”

It should be:

“Do we have enough effective capacity to handle the work we expect to receive?”

Related Reading

From Raw Data to Management Decisions: How to Build an Effective Operations MIS Dashboard

CPH, AHT, Productivity and Utilization: A Practical Guide for Operations Teams

How to Manage Backlog, Aging and SLA in Case-Based Operations

How to Calculate Attendance Rate, Absenteeism and Planned vs Actual Working Hours

Workforce Scheduling, Attendance and Leave Management