Workflow timing

Process Lead Time Calculator

📋
Request
⚙️
Process
🔍
Review
📤
Complete
No sign-up requiredBusiness days & holidaysDays, weeks & date formats100% private
Process setup

Calculate lead time across internal process stages

Use this page when you want a structured estimate for workflows that behave like a staged process rather than a single simple task.

Calculator Configuration

Enter values for each stage below

📅
📝?Days from initiation to formal request submission
days
⏳?Days spent waiting in queue before processing
days
✅?Days for review and approval
days
⚡?Days for the actual work to be performed
days
🔍?Days for final review and quality assurance
days
🤝?Days for handoff and process closure
days
🎉?Number of non-working holidays in the period
days
📆Including weekends
📊

Ready to Calculate

Enter values on the left to see your lead time breakdown and delivery estimate.

Process Timing Guide

How to Measure Process Lead Time

Four steps to map the elapsed time of an internal workflow from start to finish.

Process lead time is the elapsed time from a process being triggered to it being complete. It applies as much to an invoice approval or a support ticket as to a machined part, and in every case it is dominated by the same thing: waiting between steps rather than working within them.

The single most useful measurement is the ratio of the two. Process cycle efficiency — value-adding time divided by total elapsed time — tells you whether your process is slow because the work is slow, or slow because the work sits still. Those need opposite fixes, and teams routinely apply the wrong one.

Worked example

Worked example: where a two-week process actually spends its time

A quotation process takes an average of ten working days end to end. The team is asked to make it faster and proposes hiring another estimator. Before agreeing, someone measures where the time goes.

  • Enquiry logged and qualifiedThen waits 1 day
    30 min work
  • Technical reviewThen waits 3 days in a queue
    2 hours work
  • Pricing and margin approvalThen waits 4 days for sign-off
    1 hour work
  • Quote drafted and issuedThen waits 1 day for review
    1 hour work
  • Total working timeAcross 10 elapsed days
    ~4.5 hours
Process cycle efficiency~6%

Four and a half hours of work spread across eighty working hours. Hiring a second estimator addresses the 6% and changes the total by hours at best. The four days waiting on margin approval is nearly half the lead time and costs nothing to fix — raise the threshold, or delegate it. Measuring efficiency before choosing a solution is what separates the two options, and it takes an afternoon.

Process efficiency benchmarks

Process cycle efficiency is value-adding time divided by total elapsed time. It is unusual for any unimproved process to exceed 15%, which is why the headroom is almost always in the waiting.

MeasureTypicalWhat it tells you
World-class discrete manufacturing MCE5–15%Even best-in-class is mostly waiting
Unimproved office or service processunder 10%Handoffs and approvals dominate
Lean batch production targetunder 5 daysElapsed, not working time
Value-adding share of a typical process5–15%The number improvement targets
Waiting, queue and handoff share85–95%Where the available days actually are

Published lean and manufacturing efficiency benchmarks, cited below. These are ratios rather than durations, so they travel across industries better than lead time figures do.

Where process lead time goes

Four sources of delay, ordered by how much time they usually hold and how cheap they are to remove.

1

Approvals and sign-off thresholds

Frequently the largest single block of waiting, and the cheapest to remove. Work sits complete, waiting for one person to agree. Raising a threshold or delegating authority costs nothing and often returns more days than any amount of process redesign.

2

Handoffs between people or teams

Every handoff adds a queue, and queue time scales with how busy the receiver is rather than how long the task takes. Reducing the number of handoffs shortens lead time more reliably than speeding any individual step, because it removes waiting rather than compressing work.

3

Batching

Processing requests weekly instead of daily adds an average of half the batch interval to every item, whether or not anyone is busy. Weekly approval meetings are the most common example, and they are also the easiest to change.

4

Rework loops

Work rejected at a late step returns to the start of an earlier queue, so a single rework loop can add more elapsed time than the original pass. Moving quality checks earlier costs some throughput and usually returns far more in lead time.

The Process Lead Time Calculator produces an estimate. Real lead times move with supplier capacity, congestion, customs and weather — confirm any committed date with your suppliers and logistics partners before acting on it.

Process FAQs

Process lead time FAQs

Questions for teams measuring the elapsed time of internal or service-based workflows.

Process lead time is the total elapsed time from the beginning of a workflow to the point where the work is completed and ready to hand off.
Yes. The staged structure also works for approvals, internal operations, service requests, onboarding, and other process-driven workflows.
They drift because waits, handoffs, review queues, and inconsistent response times accumulate even when the actual work effort seems unchanged.
Operations leaders, project managers, service teams, and process-improvement specialists can all use it to understand timing more clearly.
Cycle time is how long one unit takes to be worked on. Lead time is how long it waits in total, including every queue between steps. A process with a two-hour cycle time can easily have a two-week lead time, and the ratio between them — process cycle efficiency — is usually the most useful number you can calculate about a process.
Add up the time each step spends actively working, divide by the total elapsed time, and the answer is almost always under 15%. The remaining 85% is queue, handoff and rework. Improving the working time attacks the small number; removing handoffs and waiting attacks the large one.