Processing
This is the time when work is actively being done: supplier production, machine run time, order entry, picking, packing, or inspection.
So what? If processing dominates, the fix usually sits in capacity, batch size, staffing, or method.
Supply chain planning tool
Lead Time Calculator for Procurement, Manufacturing, Fulfillment, and Total Supply Chain Planning
Measure how long supply takes to move from trigger to usable output, then decide what it means for supplier choice, safety stock, and reorder timing. Use the calculator to quantify lead time, spot where delay lives, and act before service slips.
What you calculate
Procurement, manufacturing, order fulfillment, and end-to-end supply chain lead time across the steps that create delay.
What problem it solves
It turns elapsed time into a planning signal so you can size buffers, set reorder timing, and focus improvement work where it matters most.
Who it is for
Planners, buyers, operations teams, warehouse leaders, and supply chain managers who need to protect service without carrying unnecessary inventory.
Calculator: measure lead time and understand the planning impact
How to use it: choose the flow you want to measure, enter the time for each step, and review the result, explanation, and live interpretation. Use the total to decide whether you need earlier reorder triggers, more safety stock, or a faster supply path.
Lead time calculator
Switch between procurement, manufacturing, order fulfillment, and total supply chain views. Each mode keeps the math simple and ties the answer back to a planning decision.
What is lead time?
Lead time is the elapsed time between the moment work is triggered and the moment usable output is available. The trigger could be a purchase order, a production release, or a customer order. The output could be received inventory, a finished unit, or a delivered shipment.
In practical planning, lead time is rarely one block of time. It is a combination of active work, waiting, and movement between steps. That is why good lead time analysis breaks the total into components instead of treating it like one mysterious number.
Waiting
This is the idle time between steps: queue time, approvals, release delays, staging, and other pauses where nothing moves forward.
So what? Waiting time is often the easiest delay to remove because it exposes policy and scheduling friction rather than physical limits.
Transport
This is the time spent moving material or finished goods between locations, whether inbound, in-plant, or outbound to the customer.
So what? Transport delay changes reorder timing and network design because every extra day expands the buffer you must plan.
Why lead time matters
The right lead time is not simply “the shortest possible.” Good planning balances responsiveness, stability, and cost.
Too long
Long lead time locks you into earlier decisions, higher safety stock, and slower reaction to demand or supply shocks.
So what? Inventory cost rises and service risk increases when forecasts miss or suppliers slip.
Right fit
A lead time that matches the business need gives planners enough time to execute without forcing excess buffer into the system.
So what? You get a more balanced flow, cleaner reorder logic, and less firefighting.
Too short
An unrealistically short target can create chronic expediting, unstable schedules, and supplier pressure that the process cannot sustain.
So what? A bad promise is worse than an honest one because planning starts from the wrong assumption.
Formulas
Use the simple formula when you are mapping one lead time path. Use the advanced formulas when you need planning assumptions that reflect actual performance over time.
Basic lead time
Lead Time = Processing + Waiting + Transport
Use this when you want a quick, practical total for one flow or one order path.
Average lead time
Average Lead Time = Sum of observed lead times / Number of observations
Use this when you have historical receipts or production orders and want a realistic baseline instead of one anecdotal example.
Lead time variability
Lead Time Variability = sqrt(Σ(LTᵢ - Average LT)² / (n - 1))
Use this when you are setting safety stock, comparing suppliers, or checking whether a lead time is stable enough to trust in planning.
Interpret the result
The number itself matters less than what it forces you to do. Good interpretation turns a timing metric into a planning action.
Short lead time
A shorter lead time usually means better agility, smaller reorder coverage windows, and less capital tied up in stock.
So what? If the lead time is also stable, you can often run leaner buffers with less service risk.
Long lead time
A longer lead time pushes decisions earlier and widens the period demand must be covered before replenishment arrives.
So what? Expect higher safety stock, earlier reorder points, and more exposure to forecast error.
High variability
Variability is often the biggest risk because the planner cannot rely on the average arrival or completion date.
So what? Even a moderate average lead time can drive high buffer stock when the actual result swings too much.
Real-world examples
These examples show how the calculator should drive a business decision, not just produce a number.
Manufacturing case
Inputs: Queue 4 days, setup 1 day, processing 3 days, move 1 day, wait 2 days.
Result: 11 days manufacturing lead time.
Business decision: The plant keeps the route but attacks queue time first because it is the largest contributor and delays customer promise dates more than run time does.
Supplier case
Inputs: Supplier processing 8 days, transport 12 days, inspection 2 days.
Result: 22 days procurement lead time.
Business decision: The buying team raises the reorder point and evaluates a regional supplier because transport is driving too much buffer stock.
Logistics case
Inputs: Order processing 1 day, picking and packing 2 days, shipping 6 days.
Result: 9 days fulfillment lead time.
Business decision: The operations team keeps warehouse labor unchanged and instead redesigns the carrier mix because outbound transit is the real bottleneck.
Common mistakes
- Using averages only and ignoring whether actual lead time swings widely around the mean.
- Ignoring variability when setting safety stock, reorder points, or supplier expectations.
- Not updating lead time assumptions after network, supplier, capacity, or process changes.
- Treating all suppliers and SKUs equally even though the business impact of delay is very different by item.
Best practices
- Track actual versus expected lead time so planning parameters reflect reality rather than promises.
- Reduce variability first because unstable lead time creates more planning pain than a stable but longer cycle.
- Work with suppliers, carriers, and internal teams on the largest delay component before trying to optimize everything at once.
- Combine lead time analysis with safety stock and reorder point logic so the number changes policy, not just reporting.
Frequently asked questions
A good lead time is one that supports your service target without forcing unnecessary inventory into the system. The right threshold depends on demand volatility, item criticality, and how expensive a late replenishment would be.
Reduce the biggest delay first. That might mean shorter supplier processing, less queue time, faster approval flow, better transport mode choice, or fewer receiving bottlenecks.
Cycle time usually measures active work on one operation, while lead time measures total elapsed time from request to usable output, including waiting and movement between steps.
Yes. High variability is often the biggest risk because average lead time becomes less trustworthy, which drives higher safety stock and more conservative reorder points.
Review them regularly, typically monthly or quarterly, and immediately after supplier changes, logistics disruptions, capacity shifts, or policy changes that alter actual elapsed time.
Turn lead time into a stronger inventory policy
Use the lead time result as the starting point, then connect it to safety stock, reorder point, supplier performance, and sourcing economics so your planning decisions hold up in the real world.