Project Lead Time Calculator

Measure total delivery time across approvals and execution stages. Reveal bottlenecks, forecast delays, and improve planning with confidence daily.

Enter Project Details

Example Data Table

Project Request Approval Execution Start Planned Finish Actual Finish Waiting Days Rework Days
Website Redesign 2026-03-01 2026-03-04 2026-03-06 2026-03-28 2026-04-02 5 4
CRM Migration 2026-04-10 2026-04-12 2026-04-15 2026-05-05 2026-05-08 3 2
Mobile App Sprint 2026-05-01 2026-05-02 2026-05-03 2026-05-18 2026-05-20 2 1

Formula Used

Project Lead Time = Actual Finish Date − Request Date

Cycle Time = Actual Finish Date − Execution Start Date

Approval Lag = Approval Date − Request Date

Queue Before Execution = Execution Start Date − Approval Date

Non-Value-Added Days = Approval Lag + Queue + Review + Waiting + Blocked + Rework

Flow Efficiency = Active Work Days ÷ Business Lead Time × 100

Delay Percentage = (Actual Cycle Time − Planned Cycle Time) ÷ Planned Cycle Time × 100

Throughput = Tasks Completed ÷ Business Cycle Time

Lead Time Risk Index = (Waiting × 1.2) + (Blocked × 1.5) + (Rework × 1.3) + (Scope Changes × 2)

How to Use This Calculator

  1. Enter the project name for easy identification.
  2. Provide the request, approval, execution, planned finish, and actual finish dates.
  3. Fill in review, waiting, blocked, and rework days.
  4. Choose the weekend pattern used by your team or region.
  5. Enter planned effort days and completed tasks for deeper analysis.
  6. Press the calculate button to view metrics above the form.
  7. Review the chart, table, and risk band for process insight.
  8. Use the CSV or PDF buttons to export results.

FAQs

1. What does project lead time measure?

It measures the full elapsed time from project request to final delivery. It includes approvals, waiting, execution, review cycles, delays, and rework.

2. How is lead time different from cycle time?

Lead time starts when work is requested. Cycle time starts when active execution begins. Lead time is broader and better for client-facing delivery analysis.

3. Why are waiting and blocked days important?

They expose delivery friction. High waiting or blocked time usually signals approval bottlenecks, missing dependencies, poor handoffs, or weak resource availability.

4. What is flow efficiency?

Flow efficiency compares active work time against total lead time. A higher percentage means more time is spent producing value instead of waiting.

5. Can this calculator support different weekend patterns?

Yes. It supports Saturday-Sunday and Friday-Saturday weekend models, making business-day calculations more practical for global project teams.

6. What does the risk band indicate?

The risk band summarizes delivery pressure using waiting, blocked work, rework, and scope changes. It helps managers spot unstable timelines quickly.

7. Why include scope changes in lead time analysis?

Scope changes often extend reviews, increase coordination, and trigger rework. Tracking them helps explain why actual delivery differs from the baseline plan.

8. When should I use business days instead of calendar days?

Use business days for operational planning, staffing, and internal scheduling. Use calendar days when reporting total elapsed time to clients or stakeholders.

Related Calculators

delivery date predictor

Important Note: All the Calculators listed in this site are for educational purpose only and we do not guarentee the accuracy of results. Please do consult with other sources as well.