Calculator
Example data table
A simple snapshot for one process instance (minutes). Replace these with your observed values.
| Step | Time (min) | Notes |
|---|---|---|
| Setup | 6 | Open tools, gather inputs |
| Processing | 18 | Complete core work |
| Waiting | 25 | Queue for review |
| Move | 4 | Handoff to next owner |
| Inspection | 7 | Check and approve |
| Rework | 9 | Fix issues found |
| Downtime | 5 | System interruption |
Formula used
- Total Cycle Time = Setup + Processing + Waiting + Move + Inspection + Rework + Downtime
- Cycle Time per Unit = Total Cycle Time ÷ Batch Size
- Value-Add Time = Setup + Processing
- Value-Add % = (Value-Add Time ÷ Total Cycle Time) × 100
- Throughput (units/hour) = 60 ÷ Cycle Time per Unit
- Takt Time (minutes/unit) = Available Time ÷ Customer Demand
- Capacity (units) = Available Time ÷ Cycle Time per Unit
- First-Pass Yield = (Good Units ÷ Batch Size) × 100
How to use this calculator
- Observe one full process run, from start to finish.
- Break time into components: setup, work, waiting, and checks.
- Enter each component using a consistent unit.
- Set batch size when one run produces many units.
- Optionally add available time and demand to estimate takt.
- Click Calculate cycle time and review KPIs above.
- Export CSV or PDF to share results and track changes.
Operational article
Cycle time as a controllable metric
Process cycle time is the elapsed time from the first action to the final deliverable. In service teams, it can be measured per ticket, per approval, or per request. A baseline cycle time enables trending, such as week-over-week reductions, and supports predictable delivery planning.
Separating value-add from delay
This calculator treats setup and processing as value-add, while waiting, movement, inspection, rework, and downtime are delay drivers. If total cycle time is 120 minutes and value-add is 30 minutes, the value-add percentage is 25%. That gap directs improvement work toward queues and rework.
Batching effects on throughput
Batch size changes how cycle time is experienced per unit. A 90-minute run producing 6 units yields 15 minutes per unit. Using the throughput estimate, 60 ÷ 15 = 4.00 units per hour. Smaller batches often reduce waiting and rework exposure.
Capacity planning with available time
When planned available time is entered, the calculator converts it to minutes and estimates capacity. For example, 7.5 hours equals 450 minutes. With 18 minutes per unit, capacity becomes 25.00 units. This supports daily staffing, shift targets, and realistic service-level commitments.
Takt alignment for demand stability
Takt time indicates the pace needed to meet demand. If available time is 450 minutes and demand is 30 units, takt is 15 minutes per unit. When cycle time per unit exceeds takt, backlog growth is expected unless work is redistributed, simplified, or automated.
Quality and first-pass yield signals
First-pass yield uses good units divided by batch size. If 18 out of 20 units are good, yield is 90.00%. Low yield usually raises rework time and inflates cycle time. Use the component chart to confirm whether rework or inspection is dominating your lead time.
FAQs
What is the difference between cycle time and lead time?
Cycle time is the elapsed time to complete the process itself. Lead time often includes upstream waiting before work starts, such as intake queues, approvals, or scheduling delays, depending on how your organization defines it.
Which components should I measure first?
Start with processing and waiting. Processing shows hands-on effort; waiting reveals bottlenecks and queues. Add rework and downtime next, because they often explain why delivery becomes unpredictable during busy periods.
How do I choose the right batch size?
Use the number of units produced per run. If one review meeting approves ten items, batch size is ten. If each request is handled independently, keep batch size at one for a clearer per-item cycle time.
What does value-add percentage tell me?
It shows how much of the total cycle is productive work versus delay. A low percentage usually means queues, handoffs, or rework dominate. Improving the largest delay component typically improves delivery speed fastest.
How is takt time used in daily operations?
Takt time sets the pace needed to meet demand within available time. Compare takt with cycle time per unit. If cycle time is higher, expect backlog growth unless you reduce work, add capacity, or smooth demand.
Why does the chart use minutes even if I enter hours?
All inputs are normalized to minutes internally to keep calculations consistent across units. The displayed unit label reflects your selected time basis, while the plotted values remain comparable and precise across runs.