Process Cycle Time
Definition
Process Cycle Time
Process cycle time is the total elapsed time one item takes to travel through a process from start to finish. It is the clock a customer experiences, and it is almost always longer than the simple sum of the working steps inside it.
The distinction between elapsed and working time is the whole subject. A form that takes four minutes to complete can take nine days to clear.
Teams that only measure handling time are measuring their own effort — customers are measuring the calendar.
Once both figures sit side by side, the improvement conversation changes completely. The question stops being who is slow and becomes where the item is sitting still.
Key takeaways
- Process cycle time runs from the first step to the last, in elapsed time.
- It includes queues, handoffs, and non-working hours, not just active handling.
- Measuring handling time alone hides most of what the customer waits for.
- Batch sizes and approval gates usually dominate the total more than staffing does.
How it works
Timestamp each item as it enters and leaves the process, then take the difference across a representative sample. Average those durations for the headline figure and keep the distribution, because the tail matters as much as the mean.
Definitions have to be fixed first. Start points, stop points, and how to treat rework loops all change the answer materially.
| Choice | Common options | Effect |
|---|---|---|
| Start point | Request received or work allocated | Allocation delay disappears if the later point is used |
| Stop point | Work completed or customer notified | Notification delay can add hours |
| Rework | New cycle or continuation of the first | Continuation lengthens the tail sharply |
| Calendar basis | Elapsed hours or working hours | Working hours can halve the reported figure |
Batch size is the single biggest lever in most office processes. Work released once daily carries an average half-day wait before anything begins.
Mapping tools make the delays visible. The American Society for Quality lists flowcharts, failure analysis, and spaghetti diagrams among the methods used to understand how work actually moves.
Public services face the same arithmetic — the federal customer experience programme at Performance.gov treats the time people spend waiting on government processes as a measurable service quality problem, not an administrative detail.
Examples
Cycle times behave differently depending on how work is released, approved, and handed between teams. Four cases show which structural choice sets the number in each setting.
A supplier onboarding process. Active work totals three hours across six people, while elapsed cycle time runs nineteen days. Five separate approval gates account for most of it.
A mortgage application desk. Cycle time dropped from twelve days to five when document checks moved from sequential to parallel — and staffing did not change at all.
A Manila back-office team. Nightly batch release added an average of eleven hours per item. Moving to hourly release cut cycle time by a third within a month.
An IT change process. Weekly change windows meant a two-hour job could wait six days. Daily windows removed most of the wait without adding any risk controls.
Related terms
Process cycle time connects to the mapping, management, and automation work that shortens it. The terms below cover the structures around the clock and the measures that sit next to it.
- Process Mapping: the method that identifies the steps and the waits.
- End to End Process: the boundaries the clock runs between.
- Business Process Management (BPM): the discipline governing the workflow.
- Average Handle Time (AHT): the contact centre equivalent of handling time.
- Resolution Time: the service desk version of the same elapsed measure.
- Business Process Automation (BPA): the tooling that removes cycle-stretching handoffs.
- Key Performance Indicator (KPI): the reporting family it belongs to.
FAQ
What is the difference between cycle time and handling time?
Handling time counts only active work, while cycle time counts every hour from start to finish. The gap between them is queue time.
Should cycle time use elapsed or working hours?
Report elapsed hours as the primary figure because that is what customers experience. A working-hours version is useful internally but flatters the result.
How does batch size affect cycle time?
Larger batches mean longer average waits before work starts. Halving batch frequency roughly halves the queue portion of the cycle.
What is takt time compared with cycle time?
Takt time is the rate at which output must be produced to meet demand. Cycle time is how long the process actually takes.
Why report a distribution instead of an average?
Because the slow tail drives complaints and escalations. A median of two days with a tail of fourteen tells a very different story from a flat average.
What reduces cycle time fastest?
Running steps in parallel and releasing work more often. Both remove waiting rather than demanding faster work.
Explore process improvement partners at Outsource Accelerator.
Independent
