Cover: AI-generated conceptual illustration for WEFTSIGNAL, not documentary photography.
Where a revised order goes wrong
A production order is revised constantly: a colour adjusted, a trim substituted, a measurement corrected, a delivery split changed. Most revisions are agreed in good faith and most are applied. The ones that fail usually fail at the handover, not in the decision: the change is agreed between two people and then has to reach a pattern room, a cutting floor, a subcontractor and a logistics booking, each working from a document nobody updated.
What a revision actually changes
A revision is rarely a single edit. Changing a trim changes the bill of materials, the cost, possibly the test requirement, and the packing list; changing a fabric changes the colour approval basis, the care label and often the fit. Every revision has a blast radius; the handover is where it is traced or lost.
Version control across two organisations
Version control works inside one company because there is one place the current document lives. Across two companies, that place has to be agreed rather than assumed, and it has to be a single location rather than whichever mailbox holds the latest message. The arrangement is the same one the wider sequence relies on, as set out in our garment production workflow overview.
What the handover record contains
A revised order handed over in a structured record can be reconstructed by someone who was not in the conversation.
- Revision identifier: a number quotable in conversation, so a disputed instruction has a name.
- Documents changed: every specification element the revision touches, not only the one that prompted it.
- Author and approver: who asked for the change and who signed it off, recorded by role as well as name.
- Effective point: the stage after which the revision applies, since a change agreed mid-production may apply only to the next lot.
- Approvals voided: which earlier approvals the revision invalidates and must be repeated.
- Superseded documents: what is withdrawn and where, so the old version cannot be worked from by mistake.
Subcontracting: the handoff that leaves the building
Where part of the order goes to another unit, the revision must cross a boundary the buyer does not control. Revisions lost here are the hardest to recover, because the subcontractor may never have held the original document and cannot tell which version it was given. Version discipline at that boundary is a matter of controls rather than documents, as our subcontracting controls material describes.
An illustrative example: a trim substitution agreed late
Consider, illustratively, a buyer who agrees a substitute drawcord in a call some weeks after the order was placed. The supplier updates the bill of materials and confirms by message. The cutting floor works from an older packing instruction, and the subcontractor sewing the hood has the first version. Nothing in that chain is negligent; the revision existed as a decision with no handover attached, so each party applied the version it held.
Approvals given before the revision
Earlier approvals are the quiet casualty of a revision. A colour approved on a fabric since substituted, a pre-production sample signed against a chart since corrected, a packing specification agreed before a trim changed: each remains approved on paper while the basis it approved no longer exists. The handover record should say which approvals the revision voids. An approval should survive only while the specification it was given against is unchanged.
Working copies, languages and superseded documents
Superseded documents have to be withdrawn, not merely replaced. A document left in a folder or pinned to a line is a live instruction to anyone who finds it, and the more languages a factory works in, the less reliable a document becomes as a record of what was understood. A translated working copy should be traceable to the version it was translated from. A revision issued in one language and applied in another fails quietly.
Closing the handoff
A handover is complete when the receiving party can state, without checking, which version it is working from. That is worth confirming rather than assuming, and it is the difference between a revision that propagates and one that merely travels. The records that prove the revision reached production belong with the lot records that travel with the goods, and the framing of a handover as an event with defined data attached is the one GS1 uses for critical tracking events and key data elements on its traceability page.
Source and further reading
Sources consulted 16 October 2026: GS1 — Traceability; CBI — 10 tips for organising your apparel exports to Europe (last updated 23 May 2023), for the buyer’s packing and customs documentation requirements. The revision register and the illustrative substitution here are WEFTSIGNAL editorial frameworks, not requirements issued by those organisations.
Continue exploring apparel manufacturing coverage and our editorial standards.
