What is a tech pack in apparel? A practical guide.

What a tech pack actually is

A tech pack - short for technical specification pack, sometimes tech spec or spec pack - is the complete manufacturing brief for a garment. It contains everything a factory needs to make the style correctly on first attempt: what the garment looks like, what it’s made of, how it’s constructed, how it’s measured, how the artwork sits, how it’s labelled and how it’s packed.

In apparel, the tech pack is what turns a design into a producible product. A designer’s sketch or CAD drawing shows what the garment should look like; the tech pack tells the factory how to make it. The moment either is missing detail, the sample process becomes guesswork - which is expensive at proto stage, catastrophic at bulk.

The word “pack” is historical - tech packs used to be physical folders of drawings, spec sheets and swatch cards mailed to overseas factories. The physical form is largely gone; the content and its role in the product cycle are unchanged.

The core components of a tech pack

A complete apparel tech pack has eight sections. Missing any of them causes a specific type of rework or delay.

Some styles need extra sections - performance testing specs for technical activewear, water-resistance ratings for outerwear, safety compliance for children’s wear. These are extensions of the standard set, not replacements.

Who reads the tech pack and why

The tech pack isn’t just for the factory. Multiple teams use different sections at different stages:

• Sourcing team uses the tech pack to quote suppliers. Missing BOM detail means quotes are guesses, and the cheapest quote often wins on assumptions that don’t hold in production.
• Factory uses the tech pack to make the sample and then bulk. Construction and measurement spec are what determine whether the sample matches the design intent.
• Fit team uses the measurement spec to evaluate sample rounds and drive fit corrections between rounds.
• QC team uses the tech pack to audit inline production and final shipment. Without a definitive spec, “pass” and “fail” are subjective.
• Merchandising uses the tech pack when adopting styles to build the line sheet - target FOB, category, colour options, size range.
• Finance uses BOM cost data when reconciling landed cost. A BOM that doesn’t match the final construction produces reconciliation exceptions every season.

The useful test: for each of these teams, can they answer their key question from the tech pack alone? If any of them regularly needs to email the designer or technical designer to clarify, the tech pack is incomplete. Fixing the pack once is cheaper than answering the same clarification for every style.

Spec sheet vs. tech pack

The terms “spec sheet” and “tech pack” are often used interchangeably, which causes confusion when a factory asks for one and the designer sends the other.

Strictly: a spec sheet is the measurement specification - points of measure, tolerances and grading rules for one style. It’s one section of a full tech pack. Some brands call it a measurement chart or graded spec.

A tech pack is the complete document - construction, BOM, measurement spec, artwork, labelling and packing all together. Sending “the spec” when a factory needs the tech pack means they’re missing seven of the eight sections above.

In casual use, most people say “spec” when they mean tech pack. In vendor communications and factory briefings it’s worth being explicit: say “tech pack” when you mean the whole document and “spec sheet” only when you mean the measurement section specifically.

How tech packs typically fail

Every experienced apparel operator has stories about tech packs that caused problems. The failure modes cluster into six patterns.

1. Version drift. Multiple PDF tech packs circulating between design, sourcing, factory and QC - none of them clearly marked as current. The proto is made from version 2, the fit sample from version 3, the bulk from version 2 because someone re-sent the older one. Fixed by strict revision control and a single source of truth (which is what PLM is supposed to provide, but only if the team actually uses it).
2. Ambiguous construction callouts. “Contrast topstitch” without a stitch density spec, thread weight or colour code. The factory picks a default; the sample looks different from the design intent; the round is wasted.
3. Missing components in BOM. Thread, interlining, hangtag string and polybag are the most-forgotten items. Missing components mean unquoted costs at costing stage and unbudgeted charges at invoicing.
4. Grade rules that don’t reflect the fit. Standard grade rules on a style with a non-standard silhouette produce sizes that don’t hang right at the extremes. Solved by validating grade against actual fit models at multiple sizes, not just the base size.
5. Artwork placement described in words instead of dimensions. “Chest logo centred” without a placement measurement means every factory places it slightly differently. Precise dimensions from HPS and CB are what factories can execute reliably.
6. Care content that doesn’t match the fabric. The main body fabric changes during development from 100% cotton to 60/40 cotton-poly. The care label wasn’t updated. Result: the retail label is legally non-compliant. In the US this is a Federal Trade Commission issue; in the EU it’s a national market surveillance issue.

None of these are exotic problems. They’re what routine tech pack discipline exists to prevent, and what breaks when discipline slips under seasonal pressure.

PDF tech packs vs. PLM-generated

Tech packs have historically been produced in Excel, Adobe Illustrator or InDesign and shared as PDFs. That model still dominates and works, especially at smaller scale. It also has one persistent flaw: a PDF is a snapshot. The moment it’s exported and emailed, it stops matching the underlying data. Every subsequent change requires a re-export and re-send, and every re-send introduces version drift risk.

A tech pack generated from live PLM data solves this by never being a snapshot. Construction, BOM, measurement spec, artwork and labelling all draw from the current style record. If a component changes or a POM is updated, the tech pack view reflects it immediately - factories always see the current version. Export to PDF is still available when a factory workflow needs one; the PDF is generated from live data at the point of export, so it’s at least current at the moment it left the system.

The practical model most brands settle on:

• Style master, BOM, measurement spec and revisions all live in PLM as structured data
• Tech pack view is generated from that data - visible to internal teams and to controlled supplier accounts
• PDF export is available when needed, but the PLM view is the source of truth
• Revisions and change history are tracked automatically as PLM records

Making this switch is less about technology than about workflow discipline. It only works if the teams that used to email PDFs stop doing that - the failure mode is a PLM system that’s technically deployed while the team still trades PDFs on the side.

How brands build tech packs in practice

The reality of tech pack production varies dramatically by brand scale:

Small brands (fewer than 50 styles/year)

Usually one person - the founder or a technical designer - builds tech packs in Illustrator or a spreadsheet template. Sample rounds are few, factories often are direct relationships, and tech pack discipline is a function of the person doing it. Works fine at this scale; breaks when the brand grows past two collections.

Mid-market brands (50-500 styles/year)

Usually a technical design team of 2-6 people, working from templates in Illustrator plus BOM/spec data in Excel. Common failure point: the templates diverge between designers, BOM sits in someone’s local spreadsheet, and version control breaks by mid-season. PLM is usually adopted at this stage, sometimes reluctantly.

Larger brands (500+ styles/year)

Technical design becomes a real team, tech pack production is centralised through PLM as a matter of necessity - no Excel workflow scales past this. Focus shifts from producing individual tech packs to managing reusable components (fabrics, trims, POMs, grade rules) that make each new tech pack faster to build.

Time per tech pack at each stage: 20-40 hours for a truly new style; 4-8 hours for a carry-over or re-colour built on an existing block; under an hour for a straight colour change. PLM shifts these numbers meaningfully - not by making any single tech pack faster to build initially, but by making the reusable components mean each subsequent style takes less time than the last.

A tech pack review checklist

The questions to ask before sending a tech pack to a factory for a proto quote or sample:

• Cover sheet - style ID, season, revision number and date all present?
• Construction sketches - front, back, and detail views? Every seam and construction element called out?
• BOM - every component listed with placement, consumption, supplier and cost? Thread, interlining and packaging included?
• Measurement spec - POMs defined? Graded across the full size range? Tolerances specified?
• Artwork - placement dimensions from HPS/CB or fixed reference point? Colour breakdowns? Print method specified?
• Labelling - main, care, size and brand labels defined? Care content matches actual BOM composition? Compliant with destination market law?
• Packing - poly bag, folding, hangtag placement, carton spec all included?
• Colourways - for multi-colourway styles, colourway-specific components clearly indicated?

If any of these gets a “we’ll fix that later,” the tech pack isn’t ready. Sending it anyway is choosing a rework loop over an extra hour of preparation.

Frequently asked questions