RMG

TNA calendars that actually keep garment orders on time

Why most time and action plans are out of date by week three, and the few habits that keep them honest.

TechBeez RMG solutions team 6 min read
A worker sewing fabric on an industrial sewing machine
Photo: Luba Glazunova / Unsplash

Every garment exporter has a time and action calendar. Very few have one that is still true three weeks after the order is confirmed.

A TNA plan is meant to answer one question at any moment: will this order ship on time, and if not, which step is holding it up? In most factories we visit, nobody can answer that without phoning three departments.

Why TNA plans drift

The plan itself is rarely the problem. Merchandisers know the critical path well: lab dips, fabric booking, trims, fit and PP samples, bulk fabric in-house, cutting, sewing, finishing, final inspection and ex-factory. The trouble is what happens after the plan is made:

  • Actual dates live somewhere else. Fabric receipt is in the store's register, sample approval is in an email, and the TNA sheet is updated "when there is time".
  • One delay is not pushed forward. A lab dip approved five days late should move every later milestone. On a static sheet, it moves nothing.
  • Everything is red. When half the cells are overdue, the colour stops meaning anything and people stop looking.

Five habits that keep a TNA honest

  1. Plan backwards from the ex-factory date. Start from the shipment date and the buyer's lead times, not from today. The slack, or the lack of it, becomes visible on day one.
  2. Record actual dates where the work happens. The store records fabric receipt, the sample room records approvals. The TNA reads those dates instead of waiting for someone to copy them in.
  3. Separate critical from routine. Mark the eight to ten milestones that really decide the ship date. Track the rest, but alert only on those.
  4. Re-forecast automatically. When a critical step slips, push the dependent steps and show the new expected ship date straight away.
  5. Review exceptions, not the whole calendar. The weekly order review should start with the orders whose forecast ship date has moved, not with every order on the books.
A useful rule of thumbIf an order's forecast ship date cannot be seen in under ten seconds, the TNA is a record, not a plan.

Templates by buyer and product

Lead times differ between a basic knit T-shirt and a lined woven jacket, and between buyers. Keep a small set of TNA templates by buyer and product type, with standard durations, and let merchandisers adjust only what is different for each order. It saves hours per order and makes plans comparable across the team.

What software should and should not do

A good system connects the TNA to the records that already exist: sample approvals, purchase orders, fabric receipts and production output. It should not ask merchandisers to type the same date twice. Whether you use an ERP or a well-built shared workbook, the test is the same: does the plan update itself when reality changes?

Key takeaways

  • Plan backwards from the ex-factory date using buyer and product templates.
  • Capture actual dates where the work is done, not in the TNA sheet.
  • Alert only on the critical milestones and re-forecast when they slip.
  • Run order reviews on exceptions: orders whose ship date has moved.

Have a project in mind?

Tell us what you want to build, improve or automate. We reply within one working day.

Start a Project
↑