Why Does One Spec File Control Every Later Reorder?

Most reorder problems trace back to one missing document. The style was developed with a tech pack, the pack was approved, and the reorder was booked against it. But a tech pack answers what the product is, not what the approved unit measured or which inputs were used to make it, and those are exactly the questions a reorder asks.

The spec file is the document that answers them. It sits on top of the tech pack and adds the history layer: the retained reference, the measured values from the approved run, the component register, the tolerance table, the revision log and the comparison sheet from the previous run. Built once, it is reused on every booking.

What Is a Spec File and How Does It Differ From a Tech Pack?

A tech pack is a build instruction. It carries the drawing, the material call-outs, the construction notes, the artwork file and the packing instruction. It is written to make one sample. It is not written to make the same sample twice, which is why it does not record what that sample measured once it existed.

A spec file is a control record. It carries the same build instruction plus the numbers taken off the approved sample, the identity of every component actually used, the bands each measured property must stay inside, and the log of every change since approval. Where the two documents disagree, the spec file wins, because it is the later and more specific record.

Which Field Groups Does Every Spec File Need?

Six field groups cover a bag programme: identity, construction, components, measurements and tolerances, evidence, and change control. Identity fixes the style, colourway, revision and the date of the approved run. Construction carries the seam map, the stitch specification and the assembly sequence.

Components is the register of every bought-in item. Measurements and tolerances is the table of properties and bands. Evidence is where the retained reference, the test reports and the comparison sheets are listed. Change control is the rule that says who may change a field and what happens when they do.

Identity

Style code, colourway, revision number, approval date, retained-sample location

Construction

Seam map, stitch specification, assembly sequence, reinforced points

Components

Body, lining, foam, webbing, thread, zipper, hardware, print - by brand and code

Measurements

Dimensions at named points, mass, foam thickness, stitch density

Tolerances

Band per measured property, with the method used to take it

Evidence

Retained reference, test reports, comparison sheets, revision log

Change control

Who may authorise a change, what notice, and what evidence

How Are Dimensions Written So They Can Be Checked?

A dimension is only checkable when three things are stated: the point, the state and the method. The point is where the tape sits. The state is whether the bag is empty, stuffed or laid flat. The method is the tension on the tape and the tool used. Without all three, two people measure the same bag and disagree by more than the tolerance.

Write dimensions as a list of named points rather than as one overall figure. Length at the base seam, width at the mid panel, depth at the gusset centre, handle drop measured from the top edge to the apex of the loop. Four or five named points catch the drift that an overall figure hides, because panels rarely move by the same amount.

How Are Materials Named So They Cannot Be Swapped?

Generic call-outs invite substitution because they are satisfied by many products. Black webbing is satisfied by a dozen weaves. Number five zipper is satisfied by several brands with different pull weights and plating. A register line that names the brand, the material, the finish and the code is satisfied by one product, and a swap becomes visible on paper.

The register should also carry the reference sample. A physical swatch of the webbing, a retained slider, a foam offcut and a printed label, attached to the file, let a comparison be made by eye and by hand at the station rather than by reading a code and hoping the code means the same thing to both parties.

Where a component is genuinely single-sourced, say so on the register line and record the lead time. That single note converts a future shortage from a surprise into a planning item, and it is the difference between a substitution proposed in writing before the run and one discovered at goods-in after it.

Where Do Tolerances Live Inside the File?

Tolerances belong next to the measurement, not in a separate annexe, because the person using the file should read the value and the band in one place. Each line should carry the property, the nominal value from the approved run, the band, the method and the named position. Five columns, one row per property.

The band should be achievable before it is written. A band that the process cannot hold becomes a permanent argument rather than a control. The practical way to set the first bands is to measure ten units from the approved run, take the spread, and set the band just outside it; tighten later, once two consecutive runs sit comfortably inside.

It is also worth stating, on the same line, what happens when a property sits just outside its band. Sorting, rework, acceptance on one run with a written exception, or rejection of the lot are four different outcomes, and deciding which applies after the cartons have landed is how a small measurement difference becomes a large commercial one. One extra column on the table prevents it.

How Is a Revision Number Used?

A revision number is the mechanism that makes a change visible. The file carries a revision for the document and, where useful, a revision per field group: identity at revision three, components at revision two. When a reorder is booked, the purchase order cites the revision, and the comparison is made against that revision rather than against whatever the file says today.

Without a revision number, a change is silent. The file is edited, the edit is correct at the time, and six months later nobody can say whether the run was made to the old field or the new one. Citing the revision on the purchase order is a one-line change that removes that ambiguity for the life of the style.

Who Owns the File and Who Can Change It?

One owner per style, named on the file, on both sides. The owner is not the person who wrote it but the person who must agree before a field changes. Where a change affects a tested property, a regulated claim or a dimension that governs fit, the owner's approval is the gate; where it affects a cosmetic field, the owner is informed rather than asked.

The change rule should also say what happens to units already made. A change that applies from a date forward leaves the earlier run inside the old revision, which is exactly why the revision number exists. Without that, a mid-run change is either applied retrospectively to units that never had it, or hidden.

How Does the Spec File Reach the Cutting Room?

A file that lives in an email thread does not reach the cutting room. The working copy has to be issued with the order: printed, dated, revision-stamped, and acknowledged by the line supervisor before cutting starts. The acknowledgement is the point at which the file stops being a document and becomes an instruction.

Where a programme runs across several seasons, reissue the file at each booking even when nothing has changed. The reissue costs one email and it re-establishes which revision the run is being made to, which is precisely the fact that gets lost when a style is assumed to be settled.

What Proves the File Was Followed on the Run?

Three records prove it: the first-piece sheet, the in-process check and the final comparison sheet. The first-piece sheet proves the line was set to the file. The in-process check proves the setting held through the run. The comparison sheet proves the finished lot sits inside the bands.

Those three records are also the whole of what a buyer needs at goods-in. A shipment that arrives with its measurements, its sampling plan and its pass lines can be released on paper in minutes. A shipment that arrives with only a style code has to be re-measured at the destination, which is the slowest and least reliable place to do it.

What Happens When the Spec File and the PO Disagree?

It happens when a buyer revises a field in an email and the revision never reaches the file, or when a sales team quotes a change that the file does not carry. The rule that resolves it should be written in advance: the file governs construction and measured properties, the purchase order governs quantity, price, incoterm and delivery, and any conflict is resolved in writing before cutting.

Resolving it before cutting matters because almost every conflict of this type costs little to fix on paper and a great deal to fix in units. A day spent reconciling two documents is a fraction of the cost of a run made to the wrong revision, and it is the reason the revision number belongs on both documents rather than on one of them.

The same rule applies to artwork and to packing. Where a colourway is added, where a label changes, or where the carton marking is revised, the change should move through the file and onto the order in the same step. Splitting those two across two conversations is the most common way a correct decision produces an incorrect run.

Frequently Asked Questions

People Also Ask