Lead Time & Cycle Time Calculator
Measure lead time, cycle time and wait time for a work item from its request, start and completion dates.
How it works
lead time = completed − requested · cycle time = completed − started · wait time = started − requested · flow efficiency = cycle ÷ lead
Lead time is what the customer feels: the whole span from raising a request to receiving it done. Cycle time is the subset during which the item was actively being worked, starting when someone picked it up. The gap between them is queue or wait time — often the single biggest lever for going faster, since most items spend far longer waiting than being worked. Flow efficiency (cycle ÷ lead) puts a number on that; teams are frequently surprised to find it under 25%.
Worked example
A ticket requested September 1, picked up September 4 and finished September 12 has an 11-day lead time, an 8-day cycle time and a 3-day wait. Flow efficiency is 8 ÷ 11 ≈ 73%.
Frequently asked questions
What is the difference between lead time and cycle time?
Lead time is measured from the moment work is requested; cycle time from the moment work actually starts. Lead time always includes cycle time plus any waiting before work begins.
What is a good flow efficiency?
Many teams measure 15–25% — items wait far more than they are worked. Anything above ~40% is strong. Low efficiency points to queues, handoffs and blocked work rather than slow individuals.
Why show working days too?
Calendar days include weekends, which can inflate the numbers for work that only happens Monday–Friday. The working-day figures strip weekends out so you can compare items started on different days of the week fairly.
Related calculators
This calculator is for educational purposes. Double-check important results before acting on them.