What should a WIP report include?

At minimum: the PO number and style-color, the order quantity, the current milestone, quantities completed at that milestone, the planned date from the T&A calendar, the actual or projected date, and a remark explaining any variance. Reports that carry status flags without quantities, or dates without the planned date beside them, force the brand to reconstruct the picture from other documents — which is the work the report exists to remove.

How often should factories send WIP updates?

Weekly is the common baseline, with many brand-factory pairs moving to twice weekly during peak production months or in the final weeks before ex-factory. More important than frequency is that the cadence is agreed in advance and treated as a floor rather than a ceiling: a known delay should be reported when it becomes known, not held for the next scheduled report.

What is the difference between a WIP report and a T&A calendar?

The T&A (time and action) calendar is the plan: the sequence of dates each production milestone is supposed to hit, working back from the delivery date. The WIP report is the actuals against that plan: which milestones have been reached, in what quantities, and how the projected dates now compare to the planned ones. A WIP report without a T&A behind it can describe progress but cannot describe lateness.

Why do brands ask for size-level WIP detail?

Because a style total can look healthy while the size run underneath it is broken. If a PO is 90 percent sewn but the missing 10 percent is concentrated in two sizes, the brand may face a partial shipment that cannot support a full size curve on the floor. Size-level detail matters most at cutting and at packing — the two points where a shortfall stops being recoverable within the original window.

When should a factory report a production delay?

As soon as the delay is known with reasonable confidence — not at the next scheduled report, and not when the milestone date arrives. An early report of a two-week slip leaves the brand options: split the shipment, adjust the launch, rebook the freight. The same slip reported at ex-factory leaves none. Factories sometimes hold bad news hoping to recover the time; the recovery occasionally happens, but the brand's planning options expire while everyone waits.

WIP Reporting Between Factories and Brands: What Good Looks Like

What a WIP report is for, the standard production milestones worth tracking, why reporting breaks down between factories and brands, and how both sides fix it.

What is a WIP report?

A WIP report (work-in-progress report) is the recurring status document a factory or vendor sends a brand showing where each purchase order stands in production: which milestones have been reached, in what quantities, on what dates, and how those dates compare to the plan. It is the factual counterpart to the T&A calendar — the T&A says when each step should happen; the WIP report says what has happened and what the revised projection is. For the brand, it is the earliest reliable signal of whether goods will arrive on time, complete, and in the intended size mix. For the factory, it is the channel through which delays get explained before they become disputes.

This guide is about the practice, not any particular tool: what the report should contain, why the exchange breaks down so often between factories and brands, and what a working version looks like from each side of the relationship.

The milestones worth tracking

Most woven and knit apparel production can be tracked against six standard milestones. Some brands add more (trim in-house, embroidery or wash out, packing), but adding milestones has a cost — every extra field is another thing the factory must maintain — so the useful question is what each milestone lets the brand decide, not how much detail is theoretically available.

Milestone	What it confirms	What the brand does with it
Fabric booked	Greige or fabric committed at the mill, with an in-house date	The earliest slip signal; fabric delay is the classic root cause of a late ex-factory
Cut	Fabric cut against the marker, by quantity	Quantity is now largely locked; shortfalls after cut are hard to recover in the same window
Sew	Units through the sewing line	The throughput signal — daily output against remaining days tells both sides if the date holds
Finishing	Wash, press, trim, and detail work complete	Last stage where quality rework can happen without moving the shipment date
Final QC	Inspection passed (or failed, with defect rate and disposition)	A failed inspection this late nearly always moves the date — the brand needs it same-day
Ex-factory	Goods handed to the forwarder	Hand-off to logistics; in-transit and in-DC tracking continue on the brand side

Two refinements make this list considerably more useful. First, each milestone needs a quantity, not just a status flag — "sewing" tells the brand little; "6,200 of 9,000 sewn as of Tuesday" supports arithmetic. Second, milestones need an agreed definition of complete. Does "cut" mean the full PO quantity is cut, or the first lay? Ambiguity here is where factory and brand reports quietly diverge while both believe they are telling the truth.

Why WIP reporting breaks down

The failure modes are consistent enough across the industry to name. Most WIP breakdowns are not caused by anyone hiding anything — they are caused by the mechanics of the exchange.

Format proliferation. A factory shipping to eight brands maintains eight report formats, because each brand's production team built its own spreadsheet. Every format has its own milestone names, its own definition of complete, its own tab structure. The factory's merchandiser spends hours re-keying the same facts into different shapes, and re-keying is where errors enter. From the factory's side this is pure overhead; from each brand's side, its own format looks perfectly reasonable.

Email lag. The report is a spreadsheet attached to an email, which means the brand is reading a snapshot that was already a day old when it was exported. Questions go back by email, answers return a day later, and by the time a discrepancy is resolved the next weekly report has superseded the one under discussion. The conversation is perpetually about stale data.

Size-level detail lost at aggregation. Factories track production by cut ticket and lot; brands think in PO, style-color, and size curve. Somewhere in between, size detail gets summed away. A report that says a style is 90 percent complete can conceal that the missing units are concentrated in two sizes — which means the "90 percent complete" PO may not be shippable as a floor-ready size run at all.

Amendments not reflected. The brand moves a delivery date, revises a quantity, or drops a color — by email, in a phone call, or in a portal the factory checks weekly. The WIP report keeps tracking against the original PO. Now the two sides are reporting variance against different plans, and the argument that follows is not about production at all; it is about which version of the order is real.

What good looks like — from each side

The interesting thing about WIP reporting is that the factory and the brand both want it to work, and their definitions of working still conflict.

The factory's version of good: one format that stays stable season to season, so the report becomes routine rather than a weekly translation project. Milestone definitions agreed once, not re-litigated per style. Questions asked once, by one person, rather than the same question from the brand's production, merchandising, and logistics contacts separately. And — the sensitive one — a counterpart that treats an early delay report as professionalism rather than as an admission to be punished.

The brand's version of good: reports that are comparable across vendors, so twenty factories' updates roll up into one view of the season. Size-level quantities at the milestones where size runs break. Data current enough to act on. Exceptions surfaced at the top of the report rather than buried in row 214. And every report tracking against the amended PO, not the PO as issued.

Where they conflict: granularity is the obvious one — the size-level, per-milestone detail the brand wants is real work for the factory to maintain, and a brand that demands maximum detail on every PO tends to get slower, more mechanical reporting on all of them. The subtler conflict is around candor. If early warnings trigger penalty conversations, factories learn to report optimistically and hold bad news until it is undeniable — which is precisely when it is least actionable. A brand's escalation posture, more than its template design, determines the quality of the WIP data it receives.

A practical approach to standardizing milestones

Standardization does not require industry consensus — it requires one brand and its vendors agreeing on a small set of rules and holding them for a few seasons.

Fix the milestone list and define complete for each. Six milestones, each with a written one-line definition ("cut = full PO quantity cut and bundled"). Circulate it once; reference it thereafter.
Anchor every line to the PO and style-color. The factory may track by cut ticket internally; the report translates to the brand's unit of planning. Whoever owns the translation owns it explicitly.
Carry three dates per milestone: planned, projected, actual. Planned comes from the T&A and does not move without an amendment; projected is the factory's current estimate; actual is filled when the milestone completes. Lateness is visible as the gap between the first and the other two.
Report quantities at each milestone, size-level at cut and packing. Those are the points where a broken size run is hardest to recover within the original window, so that is where the detail earns its cost.
Route amendments through the same channel as the report. A date or quantity change that does not update the plan the WIP is measured against has not really been communicated.
Agree the cadence and the owner on each side. One sender, one receiver, one schedule — weekly as a baseline, tighter near ex-factory if both sides agree.

If the T&A calendar itself is the weak link — missing, stale, or built ad hoc per season — fix that first; the WIP report can measure progress against a plan but cannot substitute for one. Building the calendar is its own discipline, covered in how to build a T&A calendar on retail-plan.com, with a free T&A calendar template alongside it.

Escalation discipline: report the slip when it is known

The escalation habit that matters most costs nothing to adopt: report the slip when it becomes known, not when the milestone falls due. The weekly cadence is a floor for routine status, not a holding period for bad news.

A useful escalation is specific in three ways. It names the revised date, not just the fact of a delay. It names the affected portion — full PO, certain colors, certain sizes — because a partial problem often has a partial remedy, like splitting the shipment so the core sizes make the launch. And it names the cause and the recovery plan, because "fabric arrived short, re-order confirmed for the 14th, sewing resequenced to other colors meanwhile" is a report a brand can plan around, while "slight delay, will update" is not.

The brand's half of the discipline is to make early escalation rational. Acknowledge the report, work the options, and keep the penalty conversation — if one is warranted — separate from the reporting channel. Factories calibrate quickly: counterparts who treat early warnings as useful data get more of them, and counterparts who treat every escalation as an opening for a claim get sandbagged dates and late surprises instead.

When to move WIP off spreadsheets

Spreadsheet WIP reporting works at small scale, and pretending otherwise would be dishonest. The question is when it stops working, and the signals are fairly concrete. Treat these as evaluation criteria rather than a verdict:

Vendor count. With a handful of factories, one production merchandiser can consolidate reports by hand. Past that, consolidation itself becomes a weekly job, and the roll-up is stale by the time it is finished.
More than one internal consumer. When production, merchandising, planning, and logistics each need the same status — and currently get it by forwarding emails — the single-copy spreadsheet has become a bottleneck rather than a record.
Amendment frequency. If in-season date and quantity changes are routine, version control across emailed files fails in predictable ways, and the two-plans problem described above becomes chronic.
Size-level requirements. Spreadsheets can hold size-level WIP, but maintaining it across dozens of POs is where factory compliance quietly collapses.
The need for history. On-time delivery rate, slip causes, and milestone variance by vendor are the raw material of vendor scorecards and next season's allocation decisions. Emailed snapshots do not accumulate into that history; a system of record does. A free vendor scorecard template shows what brands typically build from this data, and a lead-time and on-time-delivery calculator covers the headline metric.

Whatever tool replaces the spreadsheet, hold it to the standards this guide describes: low-friction status entry for factories that do not run their own ERP, milestone definitions both sides agreed to, planned-versus-actual tracking against the T&A, and exception views that surface the late POs rather than listing all of them.

RetailNorthstar tracks WIP by style and milestone, with factories updating production status directly — no email chains or spreadsheet attachments. See it in a live demo.

Book a Demo →

Related resources

Free production WIP tracker template — a spreadsheet starting point structured around the milestones in this guide
Production tracking for apparel — the wider production-tracking picture on retail-plan.com
Lead time — the glossary entry behind every planned date in the T&A
PO coverage and fill rate — the formulas WIP data feeds on the brand side