Lead time is the total time between the start of a process and its completion, most commonly the time between placing an order and receiving it. If you order a custom desk on March 1 and it arrives on March 22, the lead time is 21 days.
The concept matters because customers experience lead time directly, and businesses pay for it indirectly through inventory, cash tied up in work in progress, and lost sales when delivery promises stretch too long.
This guide defines lead time precisely, walks through how the term is used in manufacturing, inventory management, shipping, project management, and software development, clears up a common confusion with sales leads, and covers practical ways to shorten it.
Lead Time Definition
The general definition: lead time is the elapsed time from when a request enters a system to when it is fulfilled. The clock starts at the request, not when work begins, and stops at delivery, not when work finishes internally.
That framing matters. Lead time is measured from the perspective of the person waiting. It includes every queue, handoff, approval, and transport step in between, not just the hands-on work. A product that takes two hours to assemble can still have a three-week lead time if orders sit in queues for twenty days.
As a simple formula: lead time = order delivery date minus order request date. Everything else in this article is a specialization of that idea.
Lead Time in Manufacturing
In manufacturing, lead time usually breaks into three components.
Pre-processing time covers order handling, planning, and paperwork before anything physical happens. Processing time is the actual production: machining, assembly, finishing. Post-processing time covers inspection, packing, and delivery to the customer.
Manufacturers also distinguish material lead time, how long suppliers take to deliver raw inputs, from production lead time, and from cumulative lead time, which is the longest chain through the entire bill of materials. If one small component takes 12 weeks to source, the cumulative lead time of the finished product cannot be less than 12 weeks plus assembly, no matter how fast the factory runs.
This is why supply chain teams obsess over their longest-lead-time parts: one slow supplier sets the floor for everything.
Lead Time in Inventory Management
Inventory planners care about lead time because it determines when to reorder. The core concept is lead time demand: how much stock you expect to sell while waiting for a replenishment order to arrive.
A standard reorder point formula, shown here with illustrative numbers: if you sell an average of 20 units per day and your supplier lead time is 10 days, lead time demand is 200 units. Add safety stock, say 60 units to cover variability, and your reorder point is 260. When inventory hits 260, you reorder.
Two things follow directly. Longer lead times force you to hold more inventory, which ties up cash and warehouse space. And variable lead times are worse than long ones, because unpredictability forces larger safety stock than a slow-but-reliable supplier would.
Lead Time in Shipping and Logistics
In logistics, lead time means the door-to-door time from order confirmation to customer delivery, and it is usually quoted as a range rather than a point estimate.
It decomposes into order processing, picking and packing, carrier transit, and any customs or last-mile steps. E-commerce operators track each segment separately, because the fix for slow processing, better warehouse workflow, is completely different from the fix for slow transit, which is a different carrier or a closer fulfillment location.
Quoted lead time also shapes conversion: unrealistic delivery promises generate support tickets and refunds, while honest ranges with reliable delivery build repeat business.
Lead Time in Project Management
Project managers use lead time in a scheduling sense: the amount of time by which a dependent task can be started before its predecessor finishes, or more loosely, how far in advance something must be requested to be ready when needed.
The practical version most teams meet: booking a venue has a lead time of months, printing materials has a lead time of weeks, so the project plan must place those requests early even though the event is far away. Missing a long-lead-time item is one of the classic ways projects slip, because no amount of late effort can compress a supplier queue.
Good project plans therefore start by listing the longest lead time items and scheduling backward from the deadline.
Lead Time vs Cycle Time in Software
Software teams borrowed lead time from lean manufacturing, and the distinction from cycle time is worth getting right.
Lead time runs from the moment a request is made, a ticket created or a feature requested, to the moment it is delivered to the user. Cycle time runs from the moment work actually starts to delivery. The gap between them is queue time: how long the request sat in a backlog before anyone touched it.
An example with invented numbers: a bug is reported on day 0, an engineer picks it up on day 12, and the fix ships on day 15. Cycle time is 3 days; lead time is 15. A team that only measures cycle time will believe it is fast while users wait weeks.
DevOps research popularized a related metric, lead time for changes, measuring how long code takes to go from commit to running in production. Shorter lead times generally indicate healthier delivery pipelines, since work flows without piling up in queues.
Not the Same as a Sales Lead
A disambiguation worth making explicit, because search engines mix these up: lead time has nothing to do with sales leads.
A lead in sales and marketing is a person or company that might become a customer. Lead time is a measurement of elapsed time in a process. The words collide by accident of English, not meaning.
There is a loose analogy people sometimes draw, the time it takes a prospect to move through a pipeline, but the standard term for that is sales cycle length, not lead time. If you are researching pipelines and prospecting, sales cycle is the phrase to search for.
How to Reduce Lead Time
Across every context, lead time reduction follows the same logic: most lead time is waiting, not working, so attack the queues first.
Map the process end to end and time each step, including the gaps between steps. In most processes the hands-on work is a small fraction of the total, which means the biggest wins are in handoffs, approvals, and batching, not in working faster.
Specific levers by context: in manufacturing, source long-lead-time components from closer or secondary suppliers, and keep safety stock of only those items. In inventory, negotiate supplier lead times and order more frequently in smaller quantities. In logistics, position stock closer to customers and automate order processing. In projects, identify long-lead-time items on day one and trigger them immediately. In software, shrink batch sizes, limit work in progress, and automate testing and deployment so finished work does not wait for release windows.
One caution: reducing lead time usually costs something, faster shipping, more suppliers, more frequent orders. The goal is not minimum lead time at any price, but the shortest lead time your margins and customers actually justify.
FAQ
What is the difference between lead time and delivery time?
Delivery time usually refers only to the transit portion, from dispatch to arrival. Lead time covers the whole span from order placement to arrival, including processing before dispatch. A product with 2-day shipping can still have a 3-week lead time if it is made to order.
What is a good lead time?
Entirely context-dependent. Made-to-order furniture measured in weeks can be excellent; an e-commerce staple measured in weeks would be fatal. Compare against alternatives your customers actually have, and against your own trend over time.
Is lead time always measured in days?
No. Use whatever unit fits the process: minutes for a kitchen, hours for a print shop, days for e-commerce, months for construction. Consistency matters more than the unit.
Does lead time include weekends?
Decide once and be consistent. Customer-facing lead times are usually quoted in calendar days because that is how customers experience waiting; internal capacity planning often uses business days.
Conclusion
Lead time is the waiting-room view of your business: the total elapsed time between someone asking and someone receiving. It looks different in a factory, a warehouse, a project plan, and a sprint board, but the mechanics are shared, and so is the main insight.
Measure it from the requester's perspective, break it into stages, and you will almost always find that the delay lives in the queues between steps. Shrink those, and the whole system feels faster without anyone working harder.
