Course contents
Practitioner · Course 1: Order to Ship: the Critical Path · Lesson 2 of 5

Working backward from a ship date to set every milestone's own deadline

Level: PractitionerTime: 40 minutesOrder used: A (the T-shirt)Tool: Critical path tracker
For a merchandiser or production planner at a garment factory who must set each checkpoint's own deadline from a fixed ship date, rather than from the order confirmation date forward. Lesson 1 is useful background but not required. Figures are teaching figures.
FactoryDelta Garments
BuyerNorthline Apparel
OrderOrder A, the T-shirt, 15,000 pieces
Business modelMake to Order (MTO), export
Ship dateWeek 10 of a 16-week critical path
ToolCritical path tracker (this course's workbook)
02Opening

This page explains how to count backward from a fixed ship date to set each checkpoint's own deadline, rather than counting forward from the day the order is confirmed

This page is for a merchandiser or production planner at a garment factory who must turn a buyer's fixed ship date into a full set of internal deadlines for every checkpoint on the order's critical path. At work, this person is handed one date that cannot move, the date the goods must leave the factory, and has to work out, stage by stage, the latest date each earlier checkpoint can finish without threatening it. This is chiefly an information-flow skill: converting one fixed end date and a set of known stage lengths into a full internal schedule everyone on the floor can plan against. Without counting backward correctly, a factory can plan each stage forward from confirmation and only discover in week 12 that the stages, added up, do not actually fit before the ship date the buyer already confirmed.

03Before you start

You need: Lesson 1's list of the checkpoints on a typical export order's critical path. Useful, not required.

By the end of this lesson you can:

  • explain why a critical-path deadline is set backward from the ship date, not forward from confirmation;
  • calculate each checkpoint's own deadline from a fixed ship date and each stage's own typical length;
  • state how much buffer sits between two checkpoints, and why a buffer is placed where a delay is most likely;
  • read Order A's own 16-week schedule as a set of backward-counted deadlines, not just a forward list of stages.

Not covered here: naming the checkpoints themselves (Lesson 1, already covered), spotting a slipped checkpoint (Lesson 3), and rebuilding the plan after a slip (Lesson 4).

04Key terms

Words you will meet in this lesson

TermMeaning
Critical pathThe chain of sequential stages that sets the shortest possible total time for the order.
BufferExtra days or weeks added to a timeline on purpose, to absorb a likely delay.
CheckpointA specific moment in an order's life where its progress is checked against the plan.
Confirmed orderAn order both sides have agreed to, in writing, with its payment security in place; not a quotation or a discussion.
Lead timeThe total time from a confirmed order to the goods reaching their destination.
Production trackingComparing a stage's actual finish date against its planned date throughout production, to catch a delay while it can still be fixed.
05Teaching
The rule

A checkpoint's own deadline is set by counting backward from the fixed ship date, subtracting each later stage's own typical length in turn

Once an order's ship date is fixed, every earlier checkpoint's own deadline is set by working backward: starting at the ship date and subtracting, one stage at a time, the typical length of every stage that still has to happen after that checkpoint. This is the opposite direction from how a new planner often starts: counting forward from the confirmation date feels natural, but it answers the wrong question. The ship date is the one date a buyer has actually fixed; every other checkpoint's deadline exists only to protect it. A checkpoint's deadline is not "how much time do we feel this stage deserves"; it is "the latest date this stage can finish and still leave enough time for everything still to come."

Count backward from the fixed end date, not forward from the startWeek 16Arrival (fixed)Week 14− 2 weeksWeek 10− 4 weeksEx-factoryWeek 9− 1 week
Each checkpoint's own deadline is fixed by subtracting a later stage's own typical length from the ship date, working backward.* Counting forward from confirmation instead answers a different question and can silently miss the buyer's own fixed date.
What you meet in real life

The same backward-counting method applies to every order, but how much buffer sits at each point, and where it sits, differs by product, market, and how confident the schedule is

What can differThe shapes you meetWhy it matters
Export order vs. domestic orderAn export order such as Order A counts backward from an overseas ship date, through several weeks of sea freight; a domestic Make to Stock order counts backward from a much nearer local delivery date, with little or no sea-freight stage to subtract.Applying an export order's own long shipping subtraction to a domestic order overstates how early its own fabric booking checkpoint actually needs to finish.
Where the buffer sitsA factory may place most of its buffer around fabric in-house, the stage most likely to run late through a mill delay, rather than spreading it evenly across every stage.A buffer placed on a low-risk stage does nothing for the stage that is actually most likely to slip.
A confirmed order vs. a Make to Stock production runA confirmed export order like Order A works backward from one fixed buyer ship date; a Make to Stock domestic run works backward from its own planned shop-floor date, set by the brand itself rather than a buyer's contract.A domestic brand missing its own internally set date has no buyer claim to answer, but still loses selling weeks in its own shops if the backward count was wrong.
A tight schedule vs. a schedule with spare weeksOrder A's 16-week schedule leaves little spare time once its six stages are added up; a less time-pressured order can carry extra buffer weeks with no named stage attached at all.A tight schedule with no spare weeks has no room to absorb even a small delay without moving the ship date itself.
Socks, terry, and home-textile product familiesA hosiery, terry, or bedding order counts backward from its own ship date using its own stage lengths, such as a shorter finishing stage for socks compared with a bedding set's own cut-and-sew stage.The backward-counting method does not change by product family; only each stage's own typical length changes.
The case we follow

Delta Garments counts backward from Order A's week 10 ex-factory ship date to fix the deadline for fabric in-house and every earlier checkpoint

Order A's ship date, the date the goods must leave Delta Garments' own gate, is fixed at week 10 of the order's confirmed schedule. Mona, the merchandiser, works backward from week 10 rather than forward from week 0. Cutting-and-sewing together typically take 2 weeks, so fabric must be in-house no later than week 8 for sewing to finish by week 10. Fabric itself typically takes 5 weeks to arrive once booked, so approvals and fabric booking must finish no later than week 3 for fabric to be in-house by week 8. Karim, the production manager, checks this backward count against the floor's own known stage lengths before Mona locks the deadlines into the tracker.

The worked number

Counting backward from week 10 sets fabric in-house's deadline at week 8, one week earlier than a simple forward count from confirmation would suggest

Ship date (fixed): week 10
Cutting-and-sewing typical length: 2 weeks
Fabric in-house deadline, counting backward: 10 - 2 = 8
Fabric typical length once booked: 5 weeks
Approvals and fabric booking deadline, counting backward: 8 - 5 = 3

A forward count from confirmation, using the same stage lengths in the same order (approvals 2 weeks, then fabric 5 weeks), would place fabric in-house at week 7 and leave 3 weeks for cutting-and-sewing before week 10, one week more than the 2 weeks the floor typically needs. The backward count instead shows the floor only has until week 8, not week 9, before sewing must be finishing, because it starts from the one date that is actually fixed and works back through what still has to happen, rather than assuming every earlier stage can freely take its full typical length.

The method

A four-step method for turning a fixed ship date into every earlier checkpoint's own deadline

1. Start fromthe fixedship date2. List eachremaining stage'slength, reversed3. Subtract eachlength to set eachcheckpoint deadline4. Place sparebuffer on thehighest-risk stage
Setting every checkpoint's own deadline is a fixed four-step backward count, always starting from the ship date, never from confirmation.* Skipping step 4 leaves a schedule with no protection at its own most likely point of delay.
  1. Start from the fixed ship date, the one date on the order the buyer will not move without a formal amendment.
  2. List every remaining stage's own typical length, in reverse order, working from the last stage back to the first.
  3. Subtract each length in turn to set each checkpoint's own deadline, one stage at a time.
  4. Place any spare buffer against the stage most likely to run late, such as fabric booking through a third-party mill, rather than spreading it evenly.
The trap

A common mistake is planning each stage forward from the confirmation date instead of backward from the ship date

A common mistake, for a planner new to an order, is starting from the confirmation date and adding each stage's own typical length forward, arriving at whatever date the sum happens to reach, rather than starting from the buyer's own fixed ship date and working backward. A forward count can quietly add up to a later date than the ship date actually allows, and the mistake is only discovered once several stages have already used their own full typical length. Working backward from the fixed date instead shows immediately whether the schedule fits at all, and exactly how many spare days or weeks, if any, are left to place as buffer.

06In plain words

Once the date the goods must leave the factory is fixed, every earlier deadline is worked out backward from that date, not forward from the day the order was confirmed. Starting from the fixed end date and subtracting each remaining stage's own typical length, one at a time, shows the latest date each earlier stage can finish. Counting forward instead can add up to a date later than the fixed end date allows, and the problem is often only noticed once it is too late to fix easily. Any spare time left over after counting backward should sit against the stage most likely to run late, rather than being spread evenly across every stage.

07Quick check
  • A checkpoint's own deadline is set backward from the fixed ship date, not forward from the confirmation date.
  • Counting forward from confirmation can silently add up to a date later than the ship date actually allows.
  • Each backward step subtracts one stage's own typical length from the date reached so far.
  • Spare buffer should sit against the stage most likely to run late, not spread evenly.
  • A domestic order's backward count usually has far fewer weeks of shipping to subtract than an export order's.
  • The ship date is the one date on the order that is genuinely fixed; every earlier checkpoint's deadline exists to protect it.
08Workplace scenario

A new planner at Delta Garments proposes a fabric-in-house deadline of week 9 for Order A, using a forward count from confirmation

A new planner joins Delta Garments' merchandising team partway through Order A and is asked to check the fabric-in-house deadline before Mona locks the tracker.

  • Order A's ship date is fixed at week 10.
  • Cutting-and-sewing together typically need 2 weeks once fabric is in-house.
  • The new planner counts forward from confirmation: 2 weeks of approvals, then adds a spare week "to be safe," reaching week 9 for fabric booking and suggesting fabric in-house by week 9.
  • Karim, the production manager, has already confirmed cutting-and-sewing need the full 2 weeks before week 10.

The new planner's proposed deadline, written into a draft note:

Draft planning note, new planner. "Proposing fabric in-house deadline: week 9, based on 2 weeks approvals plus 1 spare week from confirmation."

Does a week 9 fabric-in-house deadline leave enough time for cutting-and-sewing before Order A's week 10 ship date? Decide before you open the decision.

Show decision

No. Cutting-and-sewing together typically need 2 full weeks; a fabric-in-house deadline of week 9 leaves only 1 week before the fixed week 10 ship date.

The two facts that decide this are the ship date fixed at week 10, and cutting-and-sewing's own typical 2-week length, which must be subtracted from week 10, not added forward from confirmation. Counting backward correctly, fabric must be in-house no later than week 8, one week earlier than the new planner's own proposal. Mona corrects the tracker to week 8 before the deadline is locked.

09What it costs

The cost of a one-week backward-planning error against the cost of checking the count before it is locked

Checking a backward count before it is locked into the tracker, as Mona does above, costs a few minutes of arithmetic and a short conversation with Karim. The cost of leaving the new planner's own forward-counted week 9 deadline uncorrected is one full week of missing slack before cutting-and-sewing, on an order whose FOB total is USD 48,000 (15,000 pieces × USD 3.20). If fabric actually arrives on week 9 as planned, cutting-and-sewing then have only 1 week instead of 2, forcing overtime at Order A's own fixed overtime rate of USD 0.15 per piece, USD 2,250 across the whole order, purely to recover a week a correct backward count would never have lost in the first place.

10Working template

Critical path tracker: the columns this lesson fills

This lesson adds each checkpoint's own deadline, calculated backward from the ship date, to the tracker Lesson 1 started. [Download the tracker](templates/T11-C01-critical-path-tracker.xlsx).

MilestoneStageDeadline (backward from week 10)
Approvals and fabric booking completeApprovalsWeek 3
Fabric in-houseFabricWeek 8
Ex-factory ship dateInspection, packing and documentsWeek 10 (fixed)

Download the Critical path tracker (Excel)

11Check yourself

1. Why is a checkpoint's own deadline set backward from the ship date rather than forward from the confirmation date?

2. An order's ship date is fixed at week 20. Its final two stages, each typically taking 3 weeks, still remain. What is the latest deadline for the checkpoint before those two stages begin?

12Glossary
ENARFRTRMeaning
Critical pathالمسار الحرجChemin critiqueKritik yolThe chain of sequential stages that sets the shortest possible total time for the order.
Bufferهامش وقت احتياطيMarge de sécuritéTampon süreExtra days or weeks added to a timeline on purpose, to absorb a likely delay.
Checkpointنقطة فحصPoint de contrôleKontrol noktasıA specific moment in an order's life where its progress is checked against the plan.
Confirmed orderطلبية مؤكدةCommande confirméeOnaylanmış siparişAn order both sides have agreed to, in writing, with its payment security in place; not a quotation or a discussion.
Lead timeالوقت الإجمالي للتنفيذDélai de productionTeslim süresiThe total time from a confirmed order to the goods reaching their destination.
Production trackingتتبع الإنتاجSuivi de productionÜretim takibiComparing a stage's actual finish date against its planned date throughout production, to catch a delay while it can still be fixed.
13Next

Lesson 3: Spotting a slipped milestone before it threatens the ship date

Now that every checkpoint has its own deadline counted backward from the ship date, the next lesson shows how to compare each checkpoint's actual finish date against that deadline, so a slip is caught while it can still be fixed. Back to the course map

14Ladder

RecognizeState that a checkpoint's deadline is counted backward from the ship date, not forward from confirmation.
ConnectSubtract a stage's own typical length from a later date to find an earlier checkpoint's deadline.
CompareContrast a forward count from confirmation against a backward count from the ship date on the same schedule.
DecidePlace any spare buffer against the stage most likely to run late, and lock deadlines only after checking the backward count.