Skip to content
ENExplore Calculators

Lead Time for Changes Calculator

Calculate the DORA lead time for changes from commit to production deployment.

About Lead Time for Changes Calculator

Lead Time for Changes is a core DORA metric measuring the time from code committed to code successfully running in production: lead_time = deploy_time − commit_time, averaged across a sample of recent deployments. DORA performance tiers classify this as Elite (under 1 hour), High (under 1 day), Medium (between 1 day and 1 month), and Low (over 1 month) — shorter lead times indicate a more efficient, less risky delivery pipeline.

Formula

leadTimeDays = avgCommitToDeployHours / 24

L_h
Average commit-to-deploy time in hours
L_d
Lead time for changes in days

Worked example

With the default values below, Lead Time for Changes Calculator returns Lead Time for Changes of 8.00. Change any input above and every figure here is recalculated in your browser.

Inputs used

Avg Commit-to-Deploy Timeaccepts 0–100,000 hours
8 hours
Number of Deployments Sampledaccepts 1–1,000,000 deployments
20 deployments

Results

Lead Time for Changes
8.00 hours
Lead Time for Changes
0.33 days
DORA Category
High (less than one day)
Sample Size
20 deployments

Step by step

  1. 1Lead time in minutes= 480 min
  2. 2Lead time in days= 0.33 days
  3. 3DORA classification= High (less than one day)

Assumptions and limits

  • The result is derived only from the 2 inputs listed above. Anything not among them is not part of the calculation.
  • In particular, this calculator does not take inflation, tax, fees or charges or compounding frequency into account.
  • Figures are rounded for display to 2 decimal places, so totals built from several rounded parts can differ slightly from the unrounded arithmetic.

How these calculators are built and tested is described on the Methodology page. If a figure looks wrong, please report it.

Frequently Asked Questions

Should lead time start from the first commit on a feature branch or the merge to main?

DORA's definition specifically measures from merge to main (i.e. code committed to the trunk/main branch) to production deployment — time spent on a long-lived feature branch before merging isn't counted.

How is lead time for changes different from cycle time?

Cycle time often includes the full development process starting from work beginning (e.g. ticket picked up); DORA's lead time for changes starts specifically at commit-to-main, a narrower and more consistently measurable window.

What drives most of the lead time in slow pipelines?

Commonly: slow or flaky CI pipelines, manual approval gates, batch/scheduled deployment windows instead of continuous deployment, and large batch sizes that require more testing and review before shipping.

Why average across many deployments instead of using one sample?

Individual deployments can vary widely due to one-off circumstances (a hotfix vs. a large feature); averaging over a rolling window of recent deployments gives a more representative and stable metric.

Related Calculators

Lead Time for Changes Calculator | Calcrivo