File Naming and Piece Numbering Conventions for Pattern Sets

A useful file name carries the essential identity of the file without needing to be opened: the style or product code, a version, and the format or purpose. From the name alone you should know what garment it is, which iteration it represents, and whether it is a production file or a proof.

Resist the urge to encode everything into the name until it becomes unreadable. The name carries identity and version; deeper metadata such as measurements and dates lives inside the file or a companion record. The name is an index entry, not the whole catalog card.

• Use lowercase with hyphens or underscores, never spaces, which break scripts and some systems.
• Avoid punctuation and accented characters that behave badly across operating systems.
• Put dates in ISO form, yyyy-mm-dd, so files sort chronologically by name.
• Use zero-padded numbers, style-007 not style-7, so they sort correctly.
• Keep a fixed field order so every name reads the same way.

A clear version field is worth more than any folder of backups. Increment a version number every time a pattern changes meaningfully, and keep the old version rather than overwriting it, so you can always trace what changed and revert if a correction turns out to be wrong.

Distinguish a working revision from a released one. Many operations mark released production versions distinctly from in-progress edits, so no one accidentally cuts from a draft. Whatever scheme you choose, the current released file must be unambiguous.

Within a pattern, each piece needs a stable number and name: front, back, sleeve, collar, and so on, ideally numbered in a consistent order. These identifiers travel in the file as piece names and print on the pieces themselves, so the cutting room and sewing room refer to the same numbers you do.

Include the cut quantity with each piece, cut 2 or cut 1 on fold, and keep the numbering stable across versions. Renumbering pieces between versions is a reliable way to create confusion when someone compares an old plot to a new file.

The same pattern often exists in several formats, DXF AAMA for editing and production, PLT for plotting, PDF for proofing and home printing. Decide whether formats live in one folder per style or in format-specific folders, and apply the choice consistently so the DXF and its matching PDF are never separated.

A common structure is one folder per style containing the current files, with an archive subfolder for superseded versions. The point is not the exact tree but that anyone can predict where a file lives from the style code alone.

A convention only works if it is written down and applied without exceptions, because a single ad hoc file name breaks the sortability of the whole folder. Document the scheme on one page, and rename incoming files that do not follow it rather than letting foreign conventions accumulate.

When patterns arrive from a supplier, consistent delivery makes this far easier. Minerva Patterns supplies made-to-measure patterns in DXF AAMA, PLT and PDF with clear piece names and cut quantities, so the files slot into a naming system rather than needing to be deciphered first.