ProApparel Costing & Merchandising

Time & Action Calendar

A calendar built forward from today always fits, because every duration in it is the optimistic one. Built backward from the ship date, the same numbers show which milestones are already late.

Ship Window

Working days between today and the vessel, counted honestly

Rostered working days between today and the vessel, BEFORE deducting the shutdowns below

Festival closures, national holidays, annual maintenance. Days the plan assumes it owns and does not

Used only to translate the answer back into the weeks buyers negotiate in

Planning Policy

The reserve you hold, and the optimism you correct for

Reserve held behind the last milestone. Consuming it is the first failure, missing the ship date is the second

How much longer these activities actually take than the plan books them for. Take it from closed orders, not from the target

Buyer approval round-trips overrun harder than in-house work does, so the second setting is usually the truer one

Milestone Chain

In sequence, earliest first. Each milestone starts only when the one above it has finished and its waiting time has elapsed. The last row has no successor, so any wait entered against it is ignored - put pre-vessel wait into the buffer instead.

ActivityDuration daysWait After daysOwnerLatest Start days before shipLatest Finish days before shipMust Start Within daysRow actions
———
———
———
———
———
———
———
———
———
———
———
———
———
———
———
———

Add line opens a form. Cells in the sheet stay directly editable.

How to read this sheet

Because the chain is a strict sequence, every milestone carries the same total float, and that float is the headline slack figure. The per-milestone column is therefore a countdown to each start deadline rather than a float figure: a positive number is the working days left before that activity must begin, not spare time it owns. Chase the smallest number, not the most negative result elsewhere on the sheet. The chain is a strict sequence and nothing else: each milestone waits for the one above it, and there is no dependency graph, no parallel branch and no resource contention. Real programmes run trims alongside fabric and sampling alongside the mill, so entering every activity here will overstate the path. Enter only the branch that actually binds - usually fabric through sewing - and fold parallel work into the milestone it eventually waits behind. There are no dates. The tool works in working days from today and working days before shipment, which is what makes it reproducible, and it cannot tell you a Tuesday; shutdowns are one lump figure rather than a real holiday calendar, so a window that straddles two closures in different countries needs both counted by hand. The overrun percentage is uniform, which is the crudest possible model of variance: in practice overrun is concentrated in buyer approvals and in the mill, and a flat 20 percent will understate a programme waiting on a slow approver while overstating one with a reliable one. Waiting time is treated as fixed, and buyer approval round-trips are the least fixed quantity in the chain - type what the last three orders actually took, not the service level in the contract. Nothing here models compression: it will tell you how many days you need to recover but not whether overtime, a second line, split shipments or air freight can buy them, and those are commercial decisions with costs this tool does not carry. Finally, the buffer is a flat reserve rather than a statistical one, so it protects against a small overrun anywhere, not against the one large failure that actually sinks orders.

Textile SchoolTime & Action Calendarwww.textileschool.com

Time & Action Calendar — free while in preview, with every line item and the download, at Textile School.