The Item Start date on a manufacturing order is the moment its last work-center operation ends, which is when the manufactured item physically exists. In EDGEBIC by User Solutions it excludes material rows and counts only real operations, and despite its name it marks a beginning rather than an end: production stops there and the end-item lead-time clock starts, so Item Start plus the product's lead time gives the delivery-ready Job End date that lateness is actually measured against.
This entry is part of the EDGEBIC glossary series; for the broader vocabulary of production planning, see the manufacturing glossary.
How Item Start Works
Every scheduled job produces a set of operation-level dates, one pair per routing step. Item Start is a job-level roll-up of those: it is the latest end date among the job's work-center operations.
Two details in that sentence carry weight.
It is the latest end, not the last step in sequence. On a routing with independent parallel branches, or with a sub-assembly feeding a final operation, the step that finishes last is not always the step drawn last. The engine takes the maximum, so a slow parallel branch that overruns the main line correctly pushes Item Start out.
Material rows do not count. A routing may carry material lines that consume no work-center capacity. Those are excluded from the calculation, because a material issue does not make an item exist. Only operations on real work centers move the Item Start date.
What Item Start is not is a delivery date. Between the last machine and the loading dock sits whatever the product needs: a paint cure, a pack-out, an inspection hold, a freight leg. That time is carried on the product record as end-item lead time in calendar days, and it consumes no work-center capacity. Add it to Item Start and you have Job End, the delivery-ready date.
A Worked Example
From the documentation's sample plant: Widget-A carries a Lead Time of 2 days. JOB-2026-0101's last operation, on Assembly-1, finishes Thursday at 14:00.
Item Start is Thursday 14:00. Job End is Saturday 14:00. If the due date is Friday, the job is late, even though the machines finished on Thursday and every operator involved would tell you the job was done ahead of time.
That is the whole lesson of the pair in one example. Production met its date; delivery did not. The two days of packing pushed delivery-readiness past the promise, and a plant reading only the shop-floor number would have found out at the loading dock.
The same sample world shows the opposite case on JOB-2026-0102: Item Start lands Tuesday July 21 at 10:00, the product carries one day of lead time, Job End is Wednesday July 22, and the due date is also Wednesday July 22, so Days Late reads 0. Here the tail fits and nobody has to think about it. Set Lead Time to 0 on any product and Item Start and Job End become identical, which is exactly why plants with no post-production tail can go years without noticing the distinction exists.
How EDGEBIC Uses Item Start
Item Start appears as its own column on the Drive Schedule grid and again in the job-level trio on the Job View grid, sitting beside Lead Time and Job End so the arithmetic is visible rather than implied. It is used deliberately in a few places and deliberately not used in others:
- It is the shop-floor completion date. When a supervisor asks when a job comes off the last machine, Item Start is the answer. It is the moment the part is available to pack, inspect, or move to finished goods.
- It starts the lead-time clock. The end-item lead time is applied forward in calendar days from Item Start, not from a shift boundary, because cure and freight time does not observe your shift pattern.
- It is not what lateness is judged against. Days Late, the dashboard job status buckets, and the Gantt's late coloring all classify against Job End. Every surface agrees on that, which is why a job can show a green Item Start and a red status.
- It responds to the plan, not to product edits. Item Start only changes when the operations themselves move, which means a schedule run. Editing a product's lead time changes Job End immediately and leaves Item Start exactly where it was.
- Backward scheduling reserves the tail up front. A backward-scheduled job is built so the lead-time tail lands inside the promise, which means the engine targets an Item Start early enough for the tail to fit rather than aiming the last operation at the due date. See end-item lead time in scheduling.
The practical habit is to treat Item Start as the internal number and Job End as the external one. Read Item Start when you are talking to the floor and Job End when you are talking to a customer, and the two dates stop being confusing and start being useful. The backward scheduling explainer shows how the tail is placed, and days late on a job covers what happens when the pair does not fit inside the promise.
Item Start is the moment the job's last work-center operation ends, which is when the manufactured item physically exists. Material rows are excluded from the calculation, so a routing that ends with a material line still reports the last real operation as Item Start. It is the point at which production is done and the end-item lead-time clock begins running.
Because it marks the start of something rather than the end. Production finishes at that instant, but the delivery-ready clock starts there: whatever cure, pack, freight, or inspection time the product carries as end-item lead time begins counting from Item Start. The name describes the item's own timeline rather than the shop's, and it is why the grid pairs it with Job End rather than showing one combined date.
Lateness is judged against Job End, not Item Start. Job End is Item Start plus the product's lead time in calendar days, so a product with a two-day tail can come off the last machine before its due date and still be late. When lead time is zero the two dates are identical and the distinction disappears, which is why plants with no post-production tail rarely notice the pair exists.
The habit to break is reading the production date as a delivery date, and the fastest cure is to make the tail visible rather than to hide a column. Item Start is the correct number for the shop floor, because it is genuinely when the last machine finishes and when the part becomes available for packing. Job End is the correct number for anyone talking to a customer, because it includes the cure, pack, and freight days the product actually needs. Both columns sit side by side on the schedule grid for exactly this reason. If your customer-facing people work from an exported grid, drop the Item Start column from their view and keep Job End; if they work in the application, walk them through one job where the two dates differ, because seeing a two-day gap once teaches the distinction better than any policy note.
No machine booking moved. Changing a product's lead time updates the displayed Job End on its jobs immediately, because Job End is derived arithmetic on top of Item Start, but the actual work-center reservations are untouched until the next schedule run. What you are seeing is the delivery-ready date catching up to a truth the plan had not been carrying, and it is why a borderline job can flip from on-time to at-risk on the dashboard the moment somebody edits a product record. If the new Job End dates put promises at risk, the fix is a schedule run, which will let the engine plan with the tail reserved in front of the due date rather than discovered after the fact.
Expert Q&A: Deep Dive
Q: Our supervisor reads Item Start and tells the customer that date, then we ship two days later and look bad. How do we stop that?
A: The habit to break is reading the production date as a delivery date, and the fastest cure is to make the tail visible rather than to hide a column. Item Start is the correct number for the shop floor, because it is genuinely when the last machine finishes and when the part becomes available for packing. Job End is the correct number for anyone talking to a customer, because it includes the cure, pack, and freight days the product actually needs. Both columns sit side by side on the schedule grid for exactly this reason. If your customer-facing people work from an exported grid, drop the Item Start column from their view and keep Job End; if they work in the application, walk them through one job where the two dates differ, because seeing a two-day gap once teaches the distinction better than any policy note.
Q: We changed a product's lead time from 0 to 2 and every job suddenly shows a later date. Did the schedule move?
A: No machine booking moved. Changing a product's lead time updates the displayed Job End on its jobs immediately, because Job End is derived arithmetic on top of Item Start, but the actual work-center reservations are untouched until the next schedule run. What you are seeing is the delivery-ready date catching up to a truth the plan had not been carrying, and it is why a borderline job can flip from on-time to at-risk on the dashboard the moment somebody edits a product record. If the new Job End dates put promises at risk, the fix is a schedule run, which will let the engine plan with the tail reserved in front of the due date rather than discovered after the fact.
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.