View all glossary terms

Work and processes

FTE Reduction Explained: The Metric That Shows Automation Value, Complete Guide

Korea Deep LearningPublished

FTE reduction means comparing before and after automation by converting the staff needed to handle the same workload into full-time equivalents (FTE). It is the figure most often requested when explaining the effect of an investment in an approval review.

Why convert to headcount instead of time

A different unit is needed for the approval.

The first numbers that come out when summarizing automation results are usually time. Processing time per case dropped to a fraction, or monthly work hours fell sharply. On the ground, these numbers communicate well.

But when the matter goes up to an investment review, the question changes. The question becomes how many people's worth of work it is. Time is calculated differently by each department and is hard to compare with other projects. Converting to full-time equivalents links directly to labor costs and makes it possible to compare with other investments on the same basis. FTE is closer to translating the outcome into another language.

The exact definition of FTE reduction: how it differs from time reduction

Three axes of difference between time reduction and FTE reduction

First, the units differ. Time reduction looks at time per case or per month. FTE reduction divides that time by the annual working hours of one full-time staff member.

Second, what is reflected differs. Time reduction reflects only work time. FTE reduction becomes accurate only when actual available working hours and variation in volume are reflected too. No one spends all eight hours of a day on document work.

Third, where each is used differs. Time reduction is used when explaining on-site improvement. FTE reduction is used when explaining the effect relative to investment. In practice, there are cases where workforce savings were confirmed through efficiency gains in document processing work.

The two metrics are not substitutes. Without actual time measurement, headcount conversion cannot be produced. Measure time first, then convert that value.

Five criteria for a reliable conversion

Five criteria used in the calculation

First, measure time before adoption. If you start with estimates, the results will also be estimates. Divide document review and classification, extraction and entry, and cross-checking and verification by stage, and measure each one.

Second, fix the scope of the target work. Including work that is not subject to automation in the calculation produces an inflated value.

Third, do not subtract review time. Even after automation, review time for exception cases remains. Only by including this time does the actual reduction come out.

Fourth, use actual available working hours. The division must reflect annual working days, leave, and the share of other work for the headcount conversion to be correct.

Fifth, look at variation in volume too. For work that piles up at month-end or at particular times, the average alone does not reveal the actual staffing need.

Practical ways to explain FTE reduction

Present it divided by stage

Showing only one overall reduction rate invites doubts about the basis. Showing how much was reduced in each stage makes the case far more persuasive.

In a real summary, the method used is to present how many hours were cut in document intake and classification, how many in item extraction and entry, and how many in system integration, and then total them. It is natural for the reduction rate to differ across stages.

Also organize how the freed time is used

The freed time must also be explained in terms of what it turns into. Sometimes the aim is reducing headcount, but more often the same staff increase throughput or move people to work that requires judgment.

Especially in work with a statutory deadline, shortening the lead time itself is the outcome. As in the case where payment lead time fell from three business days to one, value separate from headcount reduction needs to be explained as well.

FTE calculation in a domestic environment

In Korean organizations, document work is often not concentrated in a specific job group but spread a little across several staff. In this case, explaining it as reclaiming each person's work time fits reality better than reducing headcount.

Public institutions cannot freely adjust authorized headcount, so presenting increased throughput and shorter waiting times as outcomes is easier to accept than headcount cuts. Express the same data differently depending on which organization you are explaining to.

Define the measurement stages first

The value of a headcount metric changes greatly depending on which stages are counted. To compare before and after adoption, the same stages must be measured in the same way.

In practice, we measure intake and classification, value checking and entry, and cross-checking and verification separately. In one card issuer's credit review work, time was split across document review and classification, information extraction and entry, and document matching and verification. In retirement pension review, the burden in the same stages was heavier.

Dividing the stages this way makes it possible to confirm which stage actually decreased after automation. Comparing only total time gives no clue as to where to focus further.

Frequently asked questions

We did not measure time before adoption.

Even now, set a sample and measure it. Measuring just a few days' worth of work from several staff members can create a baseline.

How should review time be reflected?

It must be included in the post-automation time. Review of exception cases is still time spent by people, so leaving it out makes the reduction appear much larger than it is.

Is it still a result if we don't cut headcount?

Yes. Increasing throughput with the same staff or reducing waiting time is also a result. Choose the wording that fits the organization's situation.

How far can the reduction rate go?

It varies greatly by work. Work with a high share of repetitive entry shows large reductions, while work with a high share of judgment shows relatively small ones.

How do we measure it?

Divide the work into intake and classification, value checking and entry, and cross-checking and verification, and measure time per case. Before and after adoption must be measured the same way for the comparison to hold.

Is it enough to look at the monthly average?

Please also look at how work concentrates at peak times. The processing capacity during periods when volume piles up determines the actual operational burden.

If you share processing time by work stage, we will also estimate the possible range of reduction with you.

Contact us