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

CPH, AHT, Productivity and Utilization are some of the most commonly used performance metrics in transaction-processing and back-office operations.

They are also some of the most frequently misunderstood.

A team may have high utilization but poor productivity.

An employee may have an excellent AHT but still process fewer transactions than expected.

Two teams may achieve the same CPH while requiring very different amounts of effort.

This happens because each metric measures a different aspect of operational performance.

Understanding those differences is essential when setting targets, forecasting headcount, measuring employee performance or determining whether an operation has enough capacity.

What Is CPH?

CPH stands for Cases Per Hour, although organizations may also use terms such as Transactions Per Hour, Claims Per Hour, Applications Per Hour or Orders Per Hour depending on the process.

The basic formula is:

CPH = Completed Transactions ÷ Productive Hours

For example, if an employee completes 40 transactions during 8 productive hours:

CPH = 40 ÷ 8 = 5

The employee therefore processed an average of 5 transactions per productive hour.

CPH is primarily an output-based metric.

It answers the question:

How much work are we completing for each hour of productive capacity?

This makes CPH particularly useful for capacity planning.

If forecast volume is 60,000 transactions per month and expected productivity is 5 CPH, the organization can estimate how many productive hours will be required to process that volume.

However, CPH alone does not explain why productivity is high or low.

For that, Average Handling Time becomes important.

What Is AHT?

AHT stands for Average Handling Time.

It measures the average amount of handling time required to complete a transaction.

The basic formula is:

AHT = Total Handling Time ÷ Number of Completed Transactions

For example, if 30 transactions require a total of 360 minutes of handling time:

AHT = 360 ÷ 30 = 12 minutes

The average transaction therefore requires approximately 12 minutes of handling time.

If every available minute could be used for processing, an AHT of 12 minutes would theoretically allow:

60 ÷ 12 = 5 transactions per hour

This creates an important relationship:

Theoretical CPH = 60 ÷ AHT in minutes

However, real operations rarely work this perfectly.

Employees may spend time on meetings, system delays, documentation, research, training, administrative activities, breaks and other tasks.

That means actual CPH may differ from the theoretical CPH calculated from AHT.

CPH and AHT Are Related — But They Are Not the Same Metric

CPH measures output.

AHT measures the time required to process each transaction.

Suppose two employees both process 40 cases during an eight-hour shift.

At first glance, both appear to have:

CPH = 5

But their working patterns may be very different.

Employee A may spend almost the entire day processing transactions.

Employee B may process transactions much faster but spend significant time on meetings, administrative activities or other responsibilities.

Both employees can therefore produce the same CPH while having different AHT and utilization levels.

This is why operational performance should rarely be evaluated using a single metric.

What Is Productivity?

Productivity measures how efficiently output is being generated relative to an expected standard or available productive capacity.

Organizations calculate productivity differently, so the definition should always be documented clearly.

One common method is:

Productivity % = Actual Output ÷ Expected Output × 100

Suppose an employee is expected to process 6 transactions per productive hour.

During 6 productive hours, the expected output would be:

6 × 6 = 36 transactions

If the employee actually completes 30 transactions:

Productivity = 30 ÷ 36 × 100

Productivity = 83.3%

This tells management that the employee produced approximately 83% of the expected output during the time available for processing.

Another organization may define productivity using standard minutes, workload units or earned hours.

The exact methodology may vary.

What matters is that the organization uses a consistent definition and ensures managers understand what the metric actually represents.

What Is Utilization?

Utilization generally measures how much available working time is being used for productive activity.

A common formula is:

Utilization % = Productive Hours ÷ Available Hours × 100

Suppose an employee has 7.5 available working hours during the day.

If 6 hours are spent performing productive processing activities:

Utilization = 6 ÷ 7.5 × 100

Utilization = 80%

This does not tell us whether the employee worked efficiently during those six hours.

It only tells us how much of the available time was spent on productive activity.

That distinction is extremely important.

An employee could have 95% utilization while processing work inefficiently.

Another employee could have 75% utilization but perform extremely well during the time spent processing.

Utilization therefore should not be treated as a substitute for productivity.

Productivity vs Utilization

These two metrics are often confused.

Utilization asks:

How much of the available time was used productively?

Productivity asks:

How efficiently was output produced during that time?

Consider an employee with:

Available hours: 7.5
Productive hours: 6
Cases completed: 30
Target CPH: 6

Utilization is:

6 ÷ 7.5 = 80%

Actual CPH is:

30 ÷ 6 = 5

Expected output during six productive hours is:

6 × 6 = 36 cases

Productivity against target is:

30 ÷ 36 = 83.3%

We therefore have three different measures of the same working day:

Utilization = 80%

CPH = 5

Productivity = 83.3%

Each tells management something different.

A Practical Operations Example

Consider a claims-processing operation.

An analyst works 7.5 available hours during the day.

Of those 7.5 hours:

6 hours are recorded as productive processing time.

During those six hours, the analyst completes 36 claims.

Total recorded handling time across those claims is 330 minutes.

We can now calculate several performance metrics.

Utilization:

6 ÷ 7.5 = 80%

CPH:

36 ÷ 6 = 6 CPH

AHT:

330 ÷ 36 = 9.17 minutes

Theoretical CPH based purely on AHT:

60 ÷ 9.17 = approximately 6.54 CPH

The analyst therefore completed 6 claims per productive hour even though the recorded handling-time performance suggests a theoretical capability of approximately 6.5 claims per hour.

That difference may be caused by small amounts of processing-related time not captured directly in handling time, system delays, case transitions, documentation or other operational factors.

This is exactly why looking at only one metric can produce misleading conclusions.

What Happens When AHT Increases?

AHT has a direct impact on capacity.

If average handling time increases, fewer transactions can generally be processed during the same number of working hours.

For example:

At 10 minutes AHT:

60 ÷ 10 = 6 theoretical cases per hour

At 15 minutes AHT:

60 ÷ 15 = 4 theoretical cases per hour

A 50% increase in AHT has reduced theoretical throughput from 6 CPH to 4 CPH.

If transaction volumes remain unchanged, additional capacity may therefore be required.

This is particularly important during workforce planning.

A process may receive exactly the same number of transactions next month, but if complexity increases and AHT rises, required headcount can still increase significantly.

Why Volume Alone Is Not Enough for Headcount Planning

Organizations sometimes forecast staffing requirements simply by looking at transaction volumes.

This can be misleading.

Two months may each contain 100,000 transactions, but the workload could be very different if average handling time changes.

For example:

Month A:

100,000 transactions × 10 minutes = 1,000,000 processing minutes

Month B:

100,000 transactions × 15 minutes = 1,500,000 processing minutes

Transaction volume has not changed.

Workload has increased by 50%.

This is why stronger capacity models usually consider both volume and workload complexity.

Using CPH for Capacity Planning

Once a reliable productivity assumption has been established, CPH can be translated into capacity.

Suppose:

Expected CPH = 5

Productive hours per employee per day = 7.5

Working days = 21

Monthly capacity per employee would be:

5 × 7.5 × 21

= 787.5 transactions per month

If expected monthly volume is 15,000:

15,000 ÷ 787.5

= approximately 19.05 FTE

The operation would therefore require approximately 20 productive FTE before considering additional requirements such as shrinkage, training, absence, ramp-up, management coverage or workload variation.

This is where operational metrics begin connecting directly with workforce planning.

Turn your productivity assumptions into a staffing plan

Use the free Praevexa Workforce Planner to convert your AHT or CPH assumptions into monthly capacity and required headcount.

You can also include working days, shrinkage, backlog, current HC, hiring, training, ramp-up and automation to see the real staffing surplus or deficit over time.

Open the Free Workforce Planner

Link it to:

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

Do Not Ignore Shrinkage

A common capacity-planning mistake is assuming every paid hour will be available for production.

Employees also spend time on activities such as meetings, coaching, training, breaks, system downtime, leave and administrative work.

These activities reduce the amount of productive capacity available.

If an employee is paid for 8 hours but only 6.4 hours are realistically available for production, productive availability is:

6.4 ÷ 8 = 80%

Capacity models therefore need to distinguish between:

Paid Hours

Available Hours

Productive Hours

and sometimes:

Handling Time

Without these distinctions, staffing requirements can easily be underestimated.

Avoid Using One Metric as the Entire Performance Score

No single operations metric provides a complete picture.

High CPH could be achieved by rushing transactions and creating quality problems.

Low AHT could indicate efficiency — or insufficient investigation.

High utilization could simply mean employees remained busy, not that they produced enough output.

High productivity could also become misleading if targets have not been adjusted for differences in case complexity.

A stronger performance framework considers productivity together with quality, SLA, accuracy, workload complexity and other relevant operational outcomes.

Speed without quality is not operational excellence.

Neither is quality without sufficient throughput.

The goal is balanced performance.

Segment Metrics by Work Type Where Necessary

Another common problem occurs when organizations calculate one CPH or AHT target across very different transaction types.

Suppose Work Type A typically requires 5 minutes.

Work Type B requires 20 minutes.

An employee processing mostly Work Type B will naturally produce fewer cases per hour than someone processing Work Type A.

Comparing their raw CPH numbers would therefore be unfair and analytically incorrect.

Better approaches may include separate productivity targets, complexity weights, standard minutes or workload units.

The performance metric should reflect the work being performed.

Build Clear Metric Definitions

Before publishing dashboards or employee scorecards, every important metric should have an agreed definition.

For each KPI, document:

• Metric name
• Business definition
• Calculation formula
• Data source
• Inclusion and exclusion rules
• Reporting frequency
• Target
• Owner
• Treatment of exceptions

This prevents different departments from calculating the same KPI differently.

It also reduces one of the most common reporting problems in organizations:

Multiple versions of the truth.

How These Metrics Work Together

A mature operations reporting framework might use the metrics in this way:

AHT measures transaction effort.

CPH measures throughput.

Productivity measures performance against expected output.

Utilization measures how much available time is being used productively.

Quality measures whether the work was completed correctly.

SLA or TAT measures whether the work was completed within the required timeframe.

Volume and backlog measure workload demand.

Together, these metrics provide a much more complete picture of operational health than any one KPI could provide independently.

From Metrics to Management Decisions

The purpose of operational reporting is not simply to calculate percentages.

Metrics should help management answer practical questions.

Why has productivity declined?

Is the issue caused by higher AHT?

Has workload complexity changed?

Are employees spending less time in productive activity?

Is additional training required?

Is one work type creating most of the backlog?

Do we have enough capacity for forecast demand?

Are employees meeting productivity targets at the expense of quality?

Once metrics begin answering these questions, reporting becomes a management system rather than simply a collection of numbers.

How Praevexa Can Help

Praevexa MIS Technologies helps organizations build practical operational reporting, productivity measurement and workforce-planning frameworks.

This can include KPI design, MIS reporting, productivity and utilization measurement, capacity models, dashboards, reporting automation and Business Intelligence solutions.

Our objective is to help businesses move from disconnected operational numbers toward reporting systems that provide managers with clear, consistent and actionable information.

Learn more about our MIS Reporting & Business Intelligence Services:

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

CPH and AHT are most useful when they are connected to real workforce decisions. The Praevexa Workforce Planner helps you move from productivity metrics to capacity, backlog and headcount planning using your own operational assumptions.

Build your capacity plan →

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