Why time and action plans fail, and what a TNA engine changes

Every apparel factory has a time and action plan. Most of them are dead documents: built once at order confirmation, printed, and then quietly abandoned as reality diverges. By week three, the TNA says one thing, the floor says another, and the merchandiser finds out which one was right when the buyer asks why the inspection slipped.

The plan did not fail because anyone was careless. It failed because a static document cannot do the one thing a TNA exists to do: tell you about a problem while there is still time to act on it.

Why static TNAs die

A TNA is a chain of dependencies. Fabric in-house feeds cutting; cutting feeds sewing input; PP approval gates bulk production. When one milestone moves, every downstream date moves with it, and the arithmetic is tedious enough that nobody redoes it daily by hand.

So the document freezes. And a frozen plan has a specific failure mode: it keeps reporting the original dates as if they were still true. The worst plans are not the ones that are wrong; they are the ones that are wrong while looking authoritative.

What an engine changes

A TNA engine treats the plan as a living model rather than a table:

• Milestones carry evidence. "Fabric in-house" is not a checkbox; it is a claim backed by store receipts, line by line. A milestone that says done without the goods behind it is the lie that sinks the shipment, so the engine refuses it.
• Dependencies recompute. When the dyeing batch slips two days, every downstream date updates itself, and the people owning those dates are told once, clearly, rather than discovering it in a meeting.
• The critical path is visible. Of forty milestones, perhaps six decide the ship date this week. The engine names them, so attention goes where the calendar is actually at risk.
• History teaches. When the same milestone type slips on every order from the same supplier, that is not bad luck. It is a pattern, and patterns are where negotiations start.

The merchandiser's day, before and after

Before: chase five departments for status, reconcile three versions of the truth, and compose a careful email to the buyer that is accurate as of yesterday.

After: open the order, read the milestone board, see which claims carry evidence and which are promises, and answer the buyer from the same screen the factory works from. The chase does not disappear entirely. It becomes an exception rather than the job.

The honest limitation

An engine is only as truthful as its inputs. A factory that records receipts late will have a TNA that is late in the same measure. The discipline the engine enforces, milestones that demand their evidence, is exactly the discipline that makes the numbers worth reading. That trade is the point: a little rigor at capture buys a plan you can act on.

A time and action plan should be the most-read document in the factory, not the least. It earns that place the day it starts telling the truth on its own.

Further reading: Delay Letters and the Price of Surprise and Backward Scheduling from the Ship Date.