The Lead-Time Tail: the EDGEBIC Gantt Bar You Cannot Drag

The lead-time tail on the EDGEBIC Gantt is a display-only bar between a job's last operation and its final availability date: it shows the end-item lead time built into the product, consumes no capacity, and cannot be dragged, resized, or edited. EDGEBIC by User Solutions draws it so that a schedule never lies about when a product is actually deliverable. This short guide explains what the tail is, why it is immovable, and how to read it into an honest promise date.

The visual scheduling pillar guide covers the working bars; the tail is the one bar that is not work at all.

What the Tail Represents

Many products are not deliverable the instant the last machine finishes. A casting has to cool, a coating has to cure, an adhesive has to set, or the finished item has to travel to a shipping point. That gap between "production done" and "product available" is the end-item lead time, and it is a real part of the delivery promise.

The lead-time tail draws that gap. After a job's last operation, EDGEBIC appends a slate-colored bar labeled with the lead-time duration, spanning from the last work center's finish to the job's final availability date. It is the visible bridge between the shop clock and the customer's clock.

Why It Cannot Be Dragged

The tail looks like a bar, but it is not an operation, and that difference is the whole reason it is locked. There is no work to reschedule inside it, no machine it occupies, no capacity it consumes. It is a reflection of a product setting, drawn onto the chart for context.

So EDGEBIC treats it as information, not work:

• It cannot be dragged to a new position.
• It cannot be resized.
• It cannot be edited through the edit form.
• It does not appear in the right-click operation menu.

If dragging the tail were allowed, you could accidentally promise a date the product cannot meet, which is exactly the error the tail exists to prevent. Making it immovable keeps the availability date honest. It sits in the same protected category as completed work, which a reschedule never moves: both are facts the chart displays rather than plans you edit.

It Consumes No Capacity

Because the tail is not work, it books no machine time. A cure window does not tie up an oven lane on the Gantt, and shipping time does not consume a work center. This matters for reading the schedule correctly: the tail extends a job's total span on the chart without adding to any machine's load. When you check the resource load view for overloads, the tail is not part of the picture, because it never asked for capacity in the first place.

Reading the Tail Into a Promise Date

The practical skill is simple: the end of the tail is your deliverable date, not the end of the last operation. Suppose a job's last operation finishes Tuesday and the tail runs to Friday. The shop is done Tuesday, but the product is not available until Friday because of a built-in cure or transit window. Promise Friday.

The classic mistake is to read the finish of the last work center as the delivery date, promise it, and then miss because the product still had two days of cure ahead of it. The tail puts that gap on the same chart as the work so the honest date is right in front of you. This is the visual expression of how backward scheduling reserves lead time when it fits a job to a due date: the engine already accounts for the tail when it plans to a deadline, and the tail shows you the reservation.

Changing the Tail's Length

Since the tail is display-only, you do not change it on the chart. Its length comes from the product's end-item lead time, so you edit that on the product master. Shorten the product's lead time and the tail redraws shorter on the next load; lengthen it and the tail grows. The chart always reflects the setting, so the way to move the availability date is to change the underlying product data, not to fight the bar.

That separation, the setting lives on the product and the chart reflects it, is deliberate. It keeps every job of that product consistent: change the lead time once and every schedule that uses the product shows the new tail, rather than each planner nudging a bar by hand and drifting out of agreement.

Why a Small Bar Earns Its Place

It would be easy to leave the tail off and let planners remember to add lead time in their heads. EDGEBIC draws it instead, because a promise date you carry in your head is a promise date you eventually get wrong. The tail makes the availability date a visible, consistent, immovable part of the schedule, tied to a product setting rather than a planner's memory. It is a small bar, but it is the difference between promising when the shop finishes and promising when the customer can actually have the product, and on a factory floor that difference is the whole business of an on-time delivery.

See the full EDGEBIC platform, read the visual scheduling pillar guide, or bring a product with a cure or transit window to a demo and watch its lead-time tail draw the honest availability date with US.