Garment construction notes that are vague, inconsistent, or written for a designer's eyes rather than a machinist's hands are one of the most common causes of sampling rework. When a sewing room has to guess whether "finish seam" means a serged edge, a Hong Kong binding, or a flat-felled seam, they will guess—and they will guess wrong. This tutorial walks you through writing stitch-type callouts, seam allowances, and assembly sequence notes that are specific enough to follow without a single clarifying email.
Key takeaways
- Every stitch callout should reference an internationally recognised stitch class number (ISO 4915 or ASTM D6193) alongside a plain-language description so any factory can identify it.
- Seam allowance values must be stated per seam, not as a single global default, because different construction zones carry different tolerances.
- Assembly sequence notes should be written in the order operations happen on the floor, not the order they appear on a flat sketch.
- Ambiguous language—"neat finish", "secure well", "as needed"—belongs nowhere in a construction note.
- Keeping your notes inside a structured tech pack tool reduces version-control errors and gives the factory a single source of truth.
What you need before you start
- A completed flat sketch or tech pack shell for the style (front, back, details)
- Your brand's standard seam allowance chart, or the factory's preferred defaults if you are working to their tolerances
- Access to a stitch reference—the ASTM D6193 Standard Practice for Stitches and Seams classifies stitch types with drawings and seam assembly recommendations, and the American & Efird Stitch Type Matrix maps ISO 4915 numbers to common applications and SPI requirements
- A tech pack editor or PLM system where notes attach directly to the relevant view (more on tool options at the end)
- The factory's language: if your production partner uses ISO numbers internally, use ISO numbers; if they use ASTM, use ASTM; if they use both, state both
Step 1 — Audit your current language for ambiguity
Before you write a single new note, read every construction instruction you already have and flag any phrase that could mean more than one thing. Common offenders: "clean finish", "topstitch as shown", "reinforce", "match notches carefully", "standard seam".
For each flagged phrase, ask: Could two different machinists interpret this differently? If yes, it needs to be replaced with a specific instruction. Write the flagged phrases in a column; you will replace each one in Step 3.
Expected result: A marked-up list of every instruction that is currently open to interpretation. This is your rewrite list.
Step 2 — Build a stitch reference legend for the tech pack
Add a one-page stitch legend to your tech pack before the construction notes begin. This legend is a simple table: stitch class number, common name, machine type, and the SPI (stitches per inch) range your brand specifies. Every callout in the notes will reference a row in this legend.
A practical starting set for woven sportswear or casual wear:
| Class | Common name | Typical machine | SPI range |
|---|---|---|---|
| 301 | Lockstitch | Single-needle lockstitch | 10–12 |
| 401 | Double chainstitch | Double-needle chainstitch | 8–10 |
| 504 | 3-thread overlock | Serger / overlocker | 12–14 |
| 512 | 4-thread safety stitch | Safety-stitch machine | 12–14 |
| 605 | Coverstitch (3-needle) | Coverstitch machine | 8–10 |
| 101 | Single chainstitch | Chainstitch machine | Specify per use |
Adjust this for your fabric and end-use. Knitwear will lean on 401, 504, and 605 far more than wovens. Tailored clothing may need 101 for basting and 301 for most structural seams.
Expected result: A legend that every note in the document can point back to. The factory's quality team can check any seam against a single reference without hunting through prose.
Note: SPI requirements vary by fabric weight and yarn count. Always confirm your SPI range with the factory before locking the spec—what works on a 200 gsm twill may cause skipped stitches on a lightweight chiffon.
Step 3 — Write stitch callouts in a fixed format
Every stitch callout should follow the same sentence structure so the factory can parse it at a glance. A reliable format:
Location — Stitch class + name — [SPI] — [Thread] — Topstitch distance if applicable
Examples:
- Side seams — 512 (4-thread safety stitch) — 12 SPI — match body thread — 1.0 cm SA
- Waistband attachment — 401 (double chainstitch) — 9 SPI — contrast thread per colourway spec — stitch in ditch
- Hem — 605 (3-needle coverstitch) — 9 SPI — match body thread — 2.5 cm hem allowance folded twice
- Pocket bag — 301 (lockstitch) — 11 SPI — match lining thread — 1.2 cm SA, press open
Never write "topstitch as shown". Write the distance from the edge: "topstitch 0.6 cm from edge" or "twin-needle topstitch 0.6 cm and 1.2 cm from edge".
Expected result: Every seam in the garment has a callout the machinist can read in under five seconds and act on without asking a supervisor.
Step 4 — State seam allowances per seam, not as a global default
A single global seam allowance—"all seams 1.0 cm unless noted"—sounds efficient but creates problems. Shoulder seams on a woven jacket need more allowance than a side seam on a knit tee. Curved seams at the crotch or armhole need to be clipped or notched, which affects the usable allowance. Seams that will be flat-felled or French-seamed need extra allowance to turn correctly.
Instead, annotate each seam directly on the technical flat or in a seam allowance table keyed to the flat:
| Seam location | SA | Finish | Notes |
|---|---|---|---|
| Centre back (zip) | 1.5 cm | 504 overlock each edge | Press open |
| Side seams | 1.0 cm | 512 safety stitch together | Press toward back |
| Shoulder seams | 1.5 cm | 504 overlock together | Press toward back |
| Armhole | 1.0 cm | 504 overlock together | Clip at notch points |
| Hem | 2.5 cm | 605 coverstitch | Fold twice, press before stitching |
| Pocket opening | 0.6 cm | 301 lockstitch, bar-tack ends | Reinforce: 4 × bar-tack at top corners |
Note that "reinforce" in the last row is still vague on its own—that is why the note specifies how to reinforce (bar-tack, 4 ×, at top corners).
Expected result: The factory's cutting room and sewing room both have the same SA information, keyed to the same flat. There is no room for a cutter to apply a different allowance than the machinist expects.
Warning: If you are working with a factory that cuts its own patterns from your tech pack rather than from your graded files, double-check that your SA values are consistent between the flat annotation, the seam table, and any written notes. A mismatch between two of these three places is a common source of first-sample errors.
Step 5 — Write the assembly sequence in production order
Designers often describe construction in the order they think about a garment—collar, then sleeves, then side seams—because that is how the sketch reads. A sewing room works in a different order, driven by what can be pressed flat before the next operation closes it off.
A practical assembly sequence for a basic woven trouser, written in production order:
- Sew and finish pocket bags; attach to front panels; topstitch pocket openings.
- Sew front rise (fly construction); press and topstitch.
- Sew back rise; press open.
- Join front to back at side seams; press toward back.
- Join front to back at inseams; press toward front.
- Attach waistband; topstitch; bartack belt loops.
- Attach zip; press.
- Hem: fold twice, press, coverstitch.
- Final press and inspection.
Each step should be a single, completable operation. If a step requires a sub-operation (e.g., pressing before the next stitch), include it in the same numbered point rather than as a separate step—this keeps the sequence readable without becoming a flowchart.
Expected result: The sewing room supervisor can use your sequence as a line-balancing guide. Operations that must happen before others are explicit; nothing is left to the floor to figure out.
Step 6 — Add a callout for every reinforcement and bar-tack
Reinforcement points are the most commonly omitted detail in construction notes. Factories will add them where they think they are needed—but "where they think" may not match your quality standard or the stress points your testing has identified.
For every stress point on the garment, write:
- Location ("top of pocket opening, both sides")
- Method ("bar-tack, 0.8 cm width, 6 mm length")
- Thread ("match body thread" or "contrast—see colourway spec")
Common reinforcement points to check: pocket openings, belt loop attachment, fly tack, strap attachment, drawcord exits, and any seam intersection that will carry load in use.
Expected result: Your quality control checklist and the factory's QC checklist will match. Reinforcement points will not be a negotiation after the first sample arrives.
Step 7 — Review with a plain-language read-through
Before you send the tech pack, read every construction note aloud as if you are a machinist who has never seen the garment. If any sentence requires you to look at another page to understand it, it needs a cross-reference or a rewrite. If any sentence uses a word that could mean two things, rewrite it.
Common final-check questions:
- Does every stitch callout reference the legend?
- Does every seam have an SA value in the table?
- Does every reinforcement point have a method, not just a location?
- Is the assembly sequence in the order the floor will actually work?
- Are thread colours specified, or does the factory have to guess?
Expected result: A tech pack that a factory can hand directly to a floor supervisor without a pre-production meeting to decode it.
Where to keep your construction notes
Construction notes buried in a PDF that gets emailed, revised, and re-emailed are a version-control problem waiting to happen. Two tools worth knowing:
Techpacker is a tech pack editor that lets you attach construction notes directly to annotated flats, keeping stitch callouts, seam tables, and assembly notes in one linked document. It suits solo designers and indie brands who need a structured format without a full PLM implementation.
Backbone PLM, now part of Bamboo Rose, is a product lifecycle management platform aimed at retailers managing private-label at scale and brands in growth mode. It handles tech pack creation alongside approvals and supplier collaboration, which means your construction notes, revision history, and factory sign-offs live in the same system.
The right choice depends on your team size and how many styles you are running concurrently. Either way, the goal is the same: one version, one place, no ambiguity about which document is current.
Troubleshooting common problems
The factory is still sending queries after you sent detailed notes. Check whether your notes are reaching the floor supervisor or stopping at the merchandiser. Ask the factory to confirm which document their sewing room is working from. Sometimes a well-written tech pack gets summarised into a floor sheet that loses the detail.
First samples have the right stitch type but wrong SPI. This usually means the factory's machine settings were not updated for your spec. Add a note at the top of the construction page: "SPI values in this spec override factory defaults. Please confirm machine settings before cutting."
Seam allowances are inconsistent across the garment. Go back to Step 4 and check whether your flat annotation, seam table, and any written notes all agree. A single discrepancy is enough for a cutter to default to their own standard.
The assembly sequence is being ignored. Ask whether the sequence conflicts with the factory's standard line setup. Sometimes a sequence that is correct in principle is impractical on a specific line. Be willing to adjust the sequence to match their equipment, then document the agreed version.
Reinforcement points are missing on the sample. Check that reinforcement callouts are on the same page as the relevant detail view, not buried in a general notes section. If a bar-tack callout is on page 7 and the pocket detail is on page 3, it will be missed.
What success looks like
A well-written set of construction notes produces a first sample where the sewing room's questions are about fit—grading, ease, proportion—not about how to build the garment. You will know your notes are working when the factory's pre-production questions shift from "what stitch do you want here?" to "the armhole ease feels tight at size L—can we review the grade?"
That is the conversation you want to be having.
FAQ
What stitch type should I specify for most woven seams? Class 301 lockstitch is the standard for structural seams on wovens. It is secure, reversible, and available on almost every factory floor. Use a safety stitch (512) where seam strength and edge finishing need to happen in one pass.
Do I need to specify SPI for every stitch callout? Yes. SPI affects seam strength, elasticity, and appearance. A lockstitch at 8 SPI looks and performs very differently from one at 12 SPI. Always state your required range and note that it overrides factory defaults.
How do I handle construction notes for stretch fabrics? Switch from lockstitch to chainstitch (401) or safety stitch (512) for seams that need to move with the fabric. State the required stretch percentage if your brand tests for it, and specify whether the seam should be sewn with the fabric under slight tension or relaxed.
Should construction notes go in the tech pack or in a separate document? Keep them in the tech pack, attached to the relevant flat views. A separate document will eventually get out of sync with the spec. The factory should have one document that covers everything.
How detailed should assembly sequence notes be for a simple style? Even for a five-seam garment, write the sequence out. "Simple" styles often have one non-obvious operation order—a hem that must be done before a side seam is closed, for example—and a written sequence prevents that from becoming a first-sample error.
Further reading
- ASTM D6193 Standard Practice for Stitches and Seams
- American & Efird Stitch Type Matrix
- What Is a Tech Pack? — Techpacker