What Is the Critical Path in a Bag Production Calendar?

Most schedules treat every stage as equally important, which is why most schedules cannot be argued with. A critical-path view is different: it says one thread sets the date, the others have slack, and pressure applied anywhere except the critical thread is wasted. This piece is how to find that thread on a real order and how to know when it has moved.

What Is the Critical Path on a Bag Order?

The longest chain of dependent steps from the trigger to the end point. Dependencies matter more than durations: a two-week stage that runs in parallel with a three-week one is not on the critical path, and a four-day stage that nothing can start without is. On a 500-piece programme the chains are short and the answer is usually obvious once it is written down.

The table makes the practical point: the critical thread is a property of the specification, not of the factory. A buyer who removes the dyed fabric moves the critical path to hardware or to the line. A buyer who removes the tooling moves it back to fabric. That is why the specification conversation and the date conversation are the same conversation.

How Do You Find Which Thread Is Yours?

Ask one question of each thread: if this slipped by a week, would the ETD move? A thread with float answers no. The one that answers yes is critical, and there is usually exactly one. Where two answer yes, the schedule has two critical threads, which usually means a dependency was modelled as parallel when it is not.

The question sounds simple and it is rarely asked, because it requires the vendor to admit which thread is weakest. The answer is more useful than any assurance: it tells the buyer where to apply pressure, where to spend money and where to leave things alone. Pressure on a non-critical thread is not merely wasted, it is counterproductive, because it displaces attention from the one that matters.

What Is Float and How Is It Used?

Float is the number of days a non-critical thread can slip before it becomes critical, and on a 500-piece programme there are typically ten to sixteen days of it spread across four or five rows. It is real and it is finite, and the honest way to use it is to spend it deliberately rather than to discover it was spent.

A worked case: hardware procurement has four days of float against a fabric thread of twelve. If the hardware vendor slips by three days, nothing moves and the buyer should say so rather than treat it as a crisis. If it slips by five, the critical path has moved to hardware and the recovery conversation changes completely. Knowing which side of four you are on is the whole value of the exercise.

When Does the Critical Path Move During a Run?

1. At the start, fabric is critical on a dyed programme and hardware on a tooled one.
2. Once material is in the store, the critical path moves to the line slot, because the material threads are finished.
3. At the mid-run gate, it can move back to a component, if the tally finds a systematic problem that needs a replacement.
4. At packing, it moves to inspection, if the first submission fails and the re-check branch opens.
5. In the last week, it moves to booking, because the container yard cut-off is a fixed time.

Five moves in eight weeks, which is why a critical-path analysis done once at the start is worth less than one redone at each milestone. The redoing takes five minutes and it is the difference between applying pressure where it works and applying it where it only costs goodwill.

Why Does the Line Slot Become Critical Late in the Run?

Because it is the longest remaining thread once material has landed. Sewing on a 500-piece run is twelve to fourteen days at a planned rate, and once it starts there is no parallel chain left to absorb a slip. This is also why overtime is the most commonly offered recovery instrument: it is the only lever available on the thread that is critical at that moment.

It is worth knowing what overtime costs, because it is offered casually. A second shift raises output and raises the defect rate at the tail of a long shift, and the defects show up at inspection, which is the next thread. A recovery that shortens the critical path by four days and lengthens the inspection branch by three has recovered one day and added a risk.

How Does Tooling Change the Shape of the Path?

It front-loads it. A tool has to be cut, a first article shot and measured, the first article frequently corrected, and only then can bulk components be ordered. That is four dependent steps before the assembly thread can start, which makes hardware the critical path on any first run with a branded or moulded component — and makes it vanish entirely on the second.

This is the single clearest case for treating the first order and the reorder as different programmes. The first carries a tooling thread that can be two weeks long; the second does not. A buyer who expects the second run to be quoted on the same schedule as the first is asking the vendor to re-charge for a thread that no longer exists.

What Happens When Two Threads Tie?

Then the schedule has a convergence point and the risk at it is doubled, because a slip in either thread moves the date. The common convergence is cutting: fabric must be in the store and hardware must be received before a single panel can be cut, so both threads have to finish. Where two threads tie, both need an artefact and both need the buyer attention.

The remedy for a tie is to break it. Either accept a stock item on one side, which removes the thread, or release material before the sample is formally approved, which removes the dependency and adds a risk. Both are legitimate and both should be decided in week one rather than discovered in week four.

How Is the Critical Path Written Into a Schedule?

Threads

Fabric, hardware, line slot, inspection branch, booking

Duration of each

In days, with the dependencies named

Critical thread

Named at the start of the run

Float

Days of slack on each non-critical thread

Convergence points

Where two threads have to finish before a third can start

Re-check

At every milestone, because the critical thread moves

Recovery instrument

The lever available on the thread that is critical at that moment

Seven fields and the schedule stops being a list and becomes a model. We do not promise the fastest 20 days. We promise a delivery date you can calculate. A critical-path schedule is the calculation, and the re-check at each milestone is what keeps it current.

What Does Critical Path Thinking Change About the Order?

Three practical things. It changes what the buyer asks for: not a faster line but a shorter fabric thread. It changes where the buyer spends money: on the instrument that works on the critical thread rather than the one that is easiest to offer. And it changes what the buyer leaves alone, which is the hardest of the three and often the most valuable.

It also changes the conversation about specification. Once the critical thread is named, every design decision can be read for its effect on it — a branded pull adds a tooling chain, a dyed shade adds a dye-house queue, a second colourway adds a set-up. Those are the decisions that set the date, and they are all made before the order is placed.

How Much Float Does Each Thread Carry?

Read the first row and the shape of the problem becomes visible. On a dyed-to-order programme the fabric thread carries no float at all, because the dye-house queue is the longest chain in the run and nothing downstream can start without it. Every other row has some. That asymmetry is why the practical advice for a buyer who needs a shorter window is a specification change rather than a scheduling one: accepting a stock shade does not shorten a stage, it creates four to six days of float where there were none.

The float column is also the answer to the question buyers ask most often after a slip, which is how bad it is. A hardware slip of three days against a row carrying five costs nothing, costs nothing later, and should be answered with a note rather than an escalation. The same slip against a row carrying two has moved the critical path to hardware, and from that moment the recovery conversation is about the tool vendor rather than about the line. Knowing which side of the number you are on is worth several days of correspondence.

Float is also spent silently, which is what catches programmes out. A non-critical row that slips two days a week for three weeks has consumed six days without anybody deciding anything, and the slip that finally moves the date looks sudden when it was not. Recording the remaining float at each review catches that drift while it is still a note, and a buyer who can see the drift can ask about it before it becomes the date.

What Does a Critical-Path Review Cover at Each Milestone?

It is five minutes at each of the five milestones and it asks the same two questions every time. Which thread would move the ETD if it slipped by a week? And what has happened since the last review that changes the answer to the first question? The first names the critical thread; the second catches the moves, which are exactly what a schedule written once at the start of the run always misses. Two questions, five minutes, and the model behind the schedule stays current rather than becoming a document that was true in week one and decorative by week five.

The output is one line in a log: the date, the critical thread, the float remaining on each of the others, and any action taken. That log then becomes the artefact the delay conversation refers to, and it does the same job here that a delay record does once a slip has happened, which is turning a recollection into a document. It costs almost nothing to maintain, because the answers are already on the schedule and the review only has to write them down in one place.

The review has one further use that buyers rarely exploit, which is that it is the natural moment to ask for the artefact belonging to the critical row. Where the critical thread is fabric, that artefact is the mill confirmation with its inbound date. Where it is hardware, it is the first article with its measurements. Asking for the document that belongs to the critical row is more useful than asking for a percentage, and it is the same discipline the milestone calendar is built on: one row, one document, one date.

Frequently Asked Questions

People Also Ask