The pocket that was meant to be gone
The production samples arrive for the new utility jacket. The chest pockets you removed after the second fit session are back. The sleeve length is the old one. You check your email and find the revised tech pack you sent, version 4, three weeks ago. The factory replies with a photo of the version 3 PDF pinned to their cutting table. Somewhere between your designer's email, the agent's WhatsApp and the factory's printer, version 4 got lost.
Now you are choosing between accepting a jacket you did not design or delaying the whole drop while it is re-sampled.
How versions get crossed
- Tech packs are PDFs or spreadsheets sent as attachments, so every reply creates another copy.
- Fit comments are sent separately as photos with arrows, not in the tech pack itself.
- The agent or sourcing office forwards some changes and not others.
- Files are named 'final', 'final v2' and 'FINAL use this one'.
- Nobody records that the factory has received and accepted a version.
Everyone involved is trying to get it right. The problem is that there is no single place that says 'this is the current version, and the factory has confirmed it'.
What a wrong version costs
| Where it shows up | What it costs |
|---|---|
| Production samples | Another sample round, more weeks lost |
| Bulk production | A run made to the wrong spec |
| Fit | Returns for faults you had already fixed |
| Relationship | Arguments with the factory over who sent what |
| Time | Designers hunting through email to prove a change |
How we keep one current tech pack
- Each style has one record holding its tech pack: measurements, construction details, trims, artwork and bill of materials. Old versions are kept but clearly marked as superseded.
- Every change creates a new numbered version with a short note saying what changed and why, for example 'v4: chest pockets removed, sleeve shortened, see fit session 2'.
- Fit comments and photos are attached to the version they belong to, not sent as separate messages.
- The factory and agent get a link, not an attachment, so they always open the current version. They can still download a PDF, stamped with the version number and date.
- When a new version is issued, the factory is asked to acknowledge it. Until they do, the style shows as 'waiting for factory confirmation'.
- A dashboard lists every style in development, its current version and whether the factory has confirmed it.
If you already use a product lifecycle system for this, we connect to it rather than replacing it. Many smaller brands do not, and the tech packs live in folders, which is where this helps most.
The next fit session
After the fit session, your designer updates the jacket to version 5, adds the fit photos and notes, and issues it. The factory contact gets an email with the link and confirms it the next morning. When the production sample arrives, anyone can open the record and see version 5 was confirmed on that date. If something is wrong, the conversation is about fixing it, not about which PDF was on the cutting table.
Working with agents and more than one factory
Many brands work through an agent who manages several factories. The agent can have access to all their styles, and each factory only sees its own. Comments from the factory, such as 'we cannot source this zip', are logged against the version so decisions are recorded. Where factories prefer WhatsApp, a message with the link and version number is still better than a forwarded PDF.
Signs your tech packs are drifting
- Samples arrive with changes you had already removed.
- Tech packs are emailed as attachments with 'final' in the file name.
- Fit comments are sent separately from the spec.
- You cannot prove which version the factory worked from.
- Designers spend time searching emails to settle arguments.