Active Processing and Waiting Time in the Office
In one sentence
Separate the time actually spent working on a request from the time spent in a queue or waiting for a reply; do not mix employee effort and the elapsed time of the request in the same total.
By the end of this lesson
- Reconcile 40 min of active processing and 760 min of waiting with an 800 min total on the same time basis.
- Calculate the active processing ratio as 5% and separate it from the value-added time ratio.
- Classify waiting in the approval queue correctly by taking it out of active processing.
- In parallel work, separate the sum of effort time from the active time interval.
Why it matters
In office work, a long lead time does not mean that work of the same length was done. The request is recorded, stays in a queue for a while, is examined, waits again and is finally decided. Active processing time is the interval in which the defined work on the selected request is actually carried out. Waiting is the interval in which the request does not advance but time passes between start and end. An approval task appearing open for two days does not show that the approver worked for two days. If this distinction is not made, capacity need is calculated wrongly and improvement is aimed at the wrong place.
The denominator of the total time is the process boundary set in the previous lesson. The same time basis is used from arrival at the common record to the accepted output. Combining working-calendar minutes with continuous calendar minutes without explanation makes the ratio meaningless. In a working-day calculation, intervals outside work are removed according to the defined calendar; in a continuous calculation they remain inside the waiting. Whichever is chosen, its relation to the customer promise is written down. A blank timestamp in the data table does not mean the waiting time is zero; the unknown interval awaits verification.
Active processing is not automatically value-added processing. Retyping information, correcting a wrong record or rechecking the same document also takes effort. These tasks can be seen within the active time, but they are evaluated separately in terms of producing the result the requester wants right the first time. In this lesson the calculation 40 min ÷ 800 min × 100 = 5% is the active processing ratio. Do not equate this ratio with process cycle efficiency until the activities that count as value-added work are separately defined. The similarity of the denominators does not prove that the indicators mean the same thing.
A time study is not a tool for keeping people constantly busy. A role may speed up its own work while the shared approval queue stays the same. Even preparing more requests early can grow this queue. A correct study investigates under which condition the long wait arises, whether the necessary information is ready and when the decision authority can be used. When short processing times and long waits are visible on the same map, more consistent options can be developed for both capacity and service design. The result is not only lowering the total but explaining where and why the time passes.
Formula
Total time (min) = Active time + Waiting time
Active processing ratio (%) = Active time ÷ Total time × 100
Waiting ratio (%) = Waiting time ÷ Total time × 100
Effort time in sequential work (person·min) = Sum of role times
Unlock the rest of this lesson with an Academy account
Create a free Academy account with your work email address; it can be used once it is approved.
- Step-by-step instructions
- Worked example with real numbers
- Where the method misleads
- Common mistakes