Size-set and revision files for shoe-upper dies

For a shoe-upper die, a note saying “sizes 36–40” does not on its own define a size set. Without clear information on which components exist in each size, how the left-right pair is handled and which file is current, an old revision can easily enter production. This guide prepares the customer-approved range and revision file for die assessment; it does not create new models, measurements or grading.

Define the model file and size set separately

One master model drawing does not mean that every size has been approved for production. The file set should show the model code, the covered sizes and the component drawings for each size. When the size changes, the outer profile is not the only thing that can change: a notch, hole, stitch reference or paired-component position can change too.

Rather than assuming the full range from one sample size, list the sizes in use explicitly. If a size is missing, record that condition and return to the approval source. The die set is then tied to a controllable file scope rather than an ambiguous range.

• Put the model code and covered sizes under the same heading.
• Keep the component drawings for every size separate and readable.
• Do not complete a missing or unapproved size by assumption.

Read the revision code, date and change note together

A file named “latest” is not reliable revision information by itself. Every issue should carry a revision code, release date and brief note describing which component changed and how. If only the vamp perimeter, one notch or a left-right mark changed, the affected component row should say so.

Old and new files can remain in the same folder; what matters is clearly selecting the document released to production. The revision note also helps identify which marks need updating on the die. That reduces the risk of reusing an older profile or label.

• Give every file a revision code and release date.
• Name the affected component in the change note.
• Separate the production-released revision from older files.

Preserve component identity and pair relationships in every size

Size-set control is not simply a list of measurements. In every size, the vamp, inner quarter, outer quarter, tongue and other components need to retain the same identity system. Left-right pairing, inside-outside distinction, direction arrows and critical notches should remain visible in the component row even where the size changes.

Some ranges may need one die in certain sizes and separate pairs in others; the approved file should state such an arrangement clearly. Die production does not derive a pairing rule that is absent from the drawing. The approved drawing, component list and, where useful, physical sample should point to the same result.

• Keep component codes consistent through the size range.
• Show left-right, inside-outside and direction information on every relevant row.
• State the pair arrangement explicitly in the approved file.

Build one production package before sending

Before sharing, collect the current revision, size list, component drawings, change note and, if available, a reference photo or physical part in one package. A photo can be a silhouette reference, but it does not replace approved 1:1 production geometry. Writing the critical notes into the file helps the same information remain readable on different screens and printouts.

The final question is straightforward: can the person opening this package understand which model sizes are valid and which component changed without guessing? If the answer is no, clarify it with the file owner before sending it into production.

• Keep the current revision and change note in one package.
• Do not use a photo as a substitute for an approved 1:1 drawing.
• The file scope should be readable without guesswork.