What Is Estimated Lead Time on a Quote? EDGEBIC Definition
User Solutions TeamEstimated lead time on a quote is the number of calendar days between the simulated start date and the simulated end date of the job being quoted. It is derived from those two dates rather than stored as a figure of its own, and both dates come from running the real scheduling engine in memory against the shop's current load. That makes it a promise-shaped number: it already contains nights, weekends, holidays and every hour the job spends waiting behind work already committed.
This entry is part of the EDGEBIC by User Solutions glossary series introduced on the platform overview; the wider vocabulary index sits in the manufacturing glossary. For the general concept independent of any quote, see lead time in manufacturing.
How Estimated Lead Time Works
The pizza shop's "45 minutes from order to door" is a lead time, and it is instructive because nobody imagines the pizza is being worked on for 45 minutes. Perhaps six of those minutes are hands on dough. The rest is the oven queue, the boxing, and the drive. A customer does not care about the six; they plan around the 45.
A quote works the same way, and the split between the two figures is explicit.
Estimated total hours is the sum of the work hours assigned to the job across every operation. It is effort, and it is what the cost rollup is priced from.
Estimated lead time is the calendar gap between the simulated start and the simulated end. It is duration, and it is what a delivery promise is made from.
The gap between them is where the honesty lives. It is filled by shift boundaries, by weekends, and above all by queueing: the job waits because the machine it needs is committed to other work. That is only visible because the quote runs against finite capacity. A quote built by adding routing hours to today's date would return a comfortable number that stays comfortable no matter how loaded the shop is, and would be wrong precisely when it mattered.
Two consequences follow. First, the number is a snapshot. Re-running the same quote next week can return a different span, because the shop it was simulated against has changed. Second, the number ages. After a routing change, re-running the simulation is what keeps the quote honest, because the stored dates reflect the routing and the load at the moment the simulation ran.
None of this touches the live plan. The simulation borrows the scheduling engine, produces its answer in memory, and writes no schedule rows, so a sales engineer can run twenty variations without disturbing the floor.
A Concrete Example
Quote for 200 units of Widget A, a two step routing: 8 hours per unit on Mill-1, then 2 hours per unit on Assembly-1. The quote is raised on June 13 as a forward simulation with a target start of that date.
The simulation returns:
| Field | Value |
|---|---|
| Estimated start date | 2026-06-16 |
| Estimated end date | 2026-08-22 |
| Estimated lead time | 67 days |
| Estimated total hours | 2,000 |
Two thousand work hours: 1,600 on the mill and 400 on assembly. Sixty-seven calendar days from June 16 to August 22. The two numbers are describing the same job.
Nothing is wrong. The mill has finite instances and a shift pattern, so 1,600 hours of milling cannot be compressed below what the machine can deliver per day, and the schedule threads around every night and weekend in between. If the customer wanted delivery by September 15, the August 22 finish clears it with room to spare, and the planner can say so with a plan behind the sentence rather than an instinct.
Had the customer instead asked for August 1, the useful move is not to argue with the 67 days but to re-run the quote backward against that date. The simulation then right-aligns the work to end on or before it, and either produces a plan with a viable start or falls back to the earliest achievable plan, which is the answer to the question.
How EDGEBIC Uses Estimated Lead Time
The figure appears on the quote alongside the estimated start and end dates, the estimated total hours, and the cost breakdown, all stamped onto the quote when the simulation is applied. From there:
- It carries forward on conversion. When an approved quote becomes a manufacturing order, the dates and costs travel with it, so the commitment the customer accepted is the commitment the shop schedules against.
- It is a calendar span, not a working-day count. Weekends and holidays are inside the number, which is what makes it directly comparable to a customer's date.
- It is not the product's lead time. A product's end-item lead time is the delivery, cure or ship tail in calendar days after the last operation, a fixed property of the item. Estimated lead time is a simulation result for one quantity at one moment. Both exist, and confusing them produces promises that are wrong by exactly the length of the tail.
How the simulation itself is assembled, including why work hours and wall-clock span must never be substituted for one another, is covered in the EDGEBIC quote simulation explained. The lifecycle the quote then moves through has its own entry, the quote status.
Estimated lead time is the number of calendar days between the simulated start date and the simulated end date of a quote, calculated from the two dates rather than stored separately. It comes from running the real scheduling engine in memory against current shop capacity, so it already includes nights, weekends, holidays and time spent queueing behind work the shop has already committed to.
Because they measure different things. Estimated total hours is the sum of work hours assigned to the job across every operation, so it is pure effort. Estimated lead time is the calendar span from first start to last finish, which includes every hour the job is not being worked on: nights, weekends, and waiting for a machine that is busy with something else. A job of 2,000 work hours can easily span 67 calendar days, and the gap between the two figures is queueing.
No, and the shared word causes confusion. A product's lead time is the delivery, cure or ship tail in calendar days that follows the last operation, and it applies to every job for that product. Estimated lead time on a quote is the whole simulated span from start to finish for one specific quantity at one moment in the shop's loading. One is a fixed property of the item, the other is a result of a simulation.
Expert Q&A: Deep Dive
Q: I re-ran the same quote a week later and the lead time changed. Is the simulation unreliable?
A: It is working exactly as intended. The simulation schedules against current capacity, so the answer depends on what the shop is already committed to. A quote run when the mill is free returns a shorter span than the same quote run after two large orders have been accepted onto that mill. That sensitivity is the whole value of a finite-capacity quote: an infinite-capacity estimate would return the same comfortable number every time and be wrong whenever the shop was busy.
Q: The customer wants delivery by a fixed date. Should I read the lead time or run it differently?
A: Run it differently. A forward quote treats the requested date as the target start and answers 'if we begin here, when do we finish?', which leaves you comparing the simulated end against the customer's date by eye. A backward quote treats the requested date as the finish-by date and right-aligns the plan to end on or before it, so the direct question gets a direct answer. If the backward plan cannot fit, the result falls back to the earliest achievable plan, which is itself the answer to whether the date is possible.
Frequently Asked Questions
Ready to Transform Your Production Scheduling?
User Solutions has been helping manufacturers optimize their production schedules for over 35 years. One-time license, 5-day implementation.
User Solutions Team
Manufacturing Software Experts
User Solutions has been developing production planning and scheduling software for manufacturers since 1991. Our team combines 35+ years of manufacturing software expertise with deep industry knowledge to help factories optimize their operations.
Share this article
Related Articles
The EDGEBIC Scheduling Glossary Index
A themed index to the EDGEBIC glossary: scheduling engine, capacity and calendars, materials and planning, shop floor, reporting, quoting, and data import terms, defined in plain language.
What Is the Critical Chain in Manufacturing Scheduling?
The critical chain is the longest dependent path through a plan once shared machine contention is counted, not just step precedence. Here is how it differs from the critical path.
What Does Finite Capacity Mean in EDGEBIC?
Finite capacity means the scheduler refuses to book more hours on a machine than that machine actually has. See exactly how EDGEBIC enforces it, day by day and shift by shift.