Lead Time for Changes Calculator
Add each stage from commit to deploy and instantly see your total lead time, DORA band, and exactly where the hours go.
Delivery stages
Illustrative estimates - edit to match your team.
Result
DORA: EliteTotal lead time
20h
~0.83 days
Commit-to-deploy under a day. Protect this with fast, reliable CI and small batches.
Where the time goes
- Commit -> PR open2h · 10%
- PR open -> first review8h · 40%
- Review -> merge6h · 30%
- Merge -> deploy4h · 20%
Biggest wait: PR open -> first review at 40% of total lead time.
What lead time for changes measures
Lead time for changes is the elapsed time from a code commit to that change running safely in production. It is one of the four DORA metrics and the clearest signal of how quickly your team turns work into value. A long lead time usually is not a coding problem - it is a queue problem, with changes sitting idle waiting for review, merge or a deploy window.
This calculator splits lead time into the stages you define, so a single number becomes a map of where the hours actually go. The DORA band - Elite under a day, High under a week, Medium under a month - is directional and based on published research; your own baseline and trend matter far more than the label. To go deeper, read our guide on lead time for changes and what DORA metrics are.
Lead time pairs naturally with cycle time and delivery throughput. Once you have an estimate here, compare it with the cycle time calculator, check your full DORA picture with the DORA metrics calculator, or move from estimates to continuous tracking with the Measure product.
Frequently asked questions
Measure what you ship
FeatureFactory plans the work, builds it with AI, and measures the outcome - so lead time for changes updates itself from real commit and deploy data instead of a hand estimate.
Get early access