Knitted Bag Prototype Revision Cycles: A Three-Question Decision Tree and What Each Branch Costs

The Revision Decision Tree: Three Questions Before Any Change Is Requested

Three questions, asked in order, classify any prototype revision: what kind of change it is, what it physically touches, and whether it belongs in this cycle or the next — and asking them out of order is why programmes spend both rounds on one problem.

The first question is a classification and the second is a routing. A change is either a programme correction, where the work did not deliver the brief, or a specification change, where the brief moved. It then touches one of three things: the knitting programme, the yarn, or the trim. Those two answers together determine the cost, and they determine it before anyone argues about it. The third question is the one most buyers forget — is this worth a round at all, or does it cost less to accept the piece and fix it in the next cycle — and it is the question that preserves rounds for the changes that matter.

The order matters for a specific reason. A buyer who starts from the third question, asking whether a change is economically viable, has no basis on which to answer it, because the cost depends on the branch. A buyer who starts from the first two knows the cost and can then decide rationally whether to spend it. Two rounds is not many, and the discipline of classification is what makes them stretch.

Question One: Did the Programme Miss the Brief, or Did the Brief Change?

A programme correction is one where the knitting did not deliver what the tech pack specified; a specification change is one where the brief moved after the piece was seen — and only the first is inside the quoted sampling scope.

The examples are concrete and the distinction is usually obvious once it is stated. A body that came out 6 mm narrow against a stated dimension is a programme correction. A handle drop that does not match the drawing is a programme correction. A base transition that creases is a programme correction. A decision, after holding the piece, that the bag should be 20 g/m² heavier is a specification change. A decision that the handle should drop 3 cm lower is a specification change. Both categories are legitimate requests; they are simply accounted differently.

Naming the category at the moment the request is made is the single highest-value habit in a revision cycle. It converts a negotiation into a classification, it keeps the calendar honest, and it prevents the most corrosive outcome in sampling: a buyer who feels charged for a fault and a programme that feels it is being asked to absorb a change of mind. Both are usually right, and the classification is what lets them agree without either conceding.

• Programme correction: the body is 6 mm narrow, the handle drop is wrong, the base creases, the band sits too low.
• Specification change: a different GSM, a different handle drop, a different yarn, a different closure.
• Programme corrections are inside the quoted window; specification changes consume a round and may consume a booking.
• Ambiguous cases: state the reference document, usually the tech pack, and the answer follows from it.
• Where the pack is silent: treat the request as a specification change, since there was no stated number to miss.

Question Two: Does the Change Touch the Programme, the Yarn or the Trim?

The three branches of the second question cost about 1 day, 10 days and 10 to 15 days respectively, and the reason for the gap is that a programme is written, yarn is booked and trim is bought.

A programme revision is a change to a file. It costs engineering time and a bed run, about 1 to 1.5 days, and it is the least costly branch by an order of magnitude. A yarn revision is a change to a purchase that has usually already been made: the count or the shade has to be rebooked, and on a custom or dope-dyed shade that is about 10 days or more, plus the waste of whatever was booked. A trim revision is a change to a purchase from a supplier with its own lead time, typically 10 to 15 days, and it is the slowest branch because it is the furthest from the programme's control.

Programme revision

About 1 to 1.5 days; a file change and one bed run

Yarn revision, stock shade

About 5 days; a re-pick from available stock

Yarn revision, custom or dope-dyed shade

About 10 days or more, plus the booked lot

Trim revision, stock item

About 10 days against a supplier lead time

Trim revision, custom finish

About 15 days, and sometimes longer on a plated coating

Correction rounds included

Two, inside the 7-working-day sampling window

Additional round

About 1 day of programme time plus the branch cost

Question Three: Is It Worth a Round, or Is It Worth a Re-Sample?

With two rounds available, the third question is triage: spend a round now, accept the piece and fix it in the next programme, or accept it permanently — and the answer depends on whether the issue is visible at the shelf.

Not every imperfection deserves a round. A handle drop that is 3 mm out of tolerance will not be noticed by a shopper and will not be noticed by an inspector either, and spending a round on it leaves one round for the base transition that is visibly wrong. A shade that reads slightly warm under a showroom light, against a reference that reads neutral, will be noticed at the shelf and deserves the round. The test is visibility at the point of sale rather than visibility on the sample table, because the sample table is where everything looks wrong and the shelf is where none of it does.

There is a third option that is underused: accepting the piece for this season and booking the change into the next programme. It costs nothing now, it does not consume a round, and it is the right answer for anything that is a refinement rather than a fault. A programme that accepts two refinements per season and fixes them at the next re-book will improve steadily without ever spending a sampling round on something that was not broken.

What Two Rounds Actually Buy

Two rounds buy two programme corrections, or one programme correction and one trim rebooking, or one yarn change with the calendar extended — and the first of those three is what most well-briefed programmes actually use.

The shape of that sentence is the argument for a good brief. A programme that starts from a complete tech pack with gauge, GSM, yarn count and a trim list will usually need one programme round and one refinement round, and will finish inside the 7 working days. A programme that starts from imagery and four defaults will need more, and the additional rounds are the cost of the brief rather than the cost of the sampling. Two rounds is generous for the first case and tight for the second, which is why the brief is where a buyer has the most leverage over the revision count.

Programme Revisions: What They Cost and What They Fix

A programme revision costs about 1 to 1.5 days and fixes anything that is a property of the file: dimensions, shaping, loop density, reinforcement placement and the position of a knitted-in mark.

This is the branch buyers should prefer, and it is worth understanding why it is so much less costly than the other two. A knitting programme is a file; changing it costs engineering time and one bed run, and it consumes no material beyond the pieces knitted. Compare that with a yarn change, where the material has already been bought, or a trim change, where the material has to be bought from someone else. The practical consequence is that a buyer who can express a correction in programme terms rather than in material terms will get it faster and at no material cost. Three millimetres lower on the handle drop is a programme change; a softer hand is usually a yarn change.

Yarn Revisions: The Expensive Branch

A yarn revision costs about 10 days on a custom or dope-dyed shade and about 5 days on a stock shade, and it is expensive not because of the yarn price but because of the booking that has already been made.

Yarn is the longest-lead item in a knit programme and is committed early, which is what makes a late change to it costly. On a stock shade, the change is a re-pick and costs about 5 days. On a custom shade, the dye lot has to be run, which is 10 days or more, and the lot already booked becomes waste. The waste is the part that surprises people: a booked lot of 300 kg does not get returned because the buyer decided on a different shade. The practical rule is therefore simple and worth stating plainly — confirm the count and the shade before day one of sampling, and treat any subsequent yarn request as a new programme rather than as a revision.

Trim Revisions: The Slow Branch

A trim revision costs about 10 days on a stock item and about 15 on a custom finish, and it is slow because trim is bought from a supplier with its own lead time rather than programmed on the bed.

The difference between a programme change and a trim change is the difference between writing and buying. A zip gauge, a webbing width, a hardware finish and a label type are all purchased items; changing any of them starts a purchase order against someone else's schedule. A plated finish is the slowest of all, because it may also trigger a fresh substance screen on the component, which is a further fixed cost. The rule that follows is the one most programmes learn the hard way: freeze the trim list at the finished sample stage, and resolve every trim question before rather than after the trimmed piece is made.

Records: How a Revision Is Tracked Through the Cycle

A revision is tracked as a numbered line with three fields — the request, the classification and the date it was made — and the record exists so that the same change is never requested twice and the round count is never disputed.

Round-count disputes are entirely avoidable and surprisingly common, because without a record both sides remember the sequence differently. A buyer remembers one conversation about the handle and one about the base; the programme remembers three correction runs. A numbered record with dates settles it in a minute and prevents the argument from consuming the goodwill that the rest of the programme runs on. The record also prevents a specific and wasteful error: requesting a change that was already made in an earlier round because the sample on the table is an older piece.

Reducing the Number of Rounds a Programme Needs

Three actions reduce the revision count more than anything else: a complete tech pack with all fourteen fields, a yarn decision taken before day one, and one named approver who answers within a day.

All three are inexpensive in the sense that they cost no money — though the first two do cost preparation time, and the third costs an internal conversation. A complete pack removes the four defaults that generate most first-round corrections: gauge defaulting to E12, structure to plain jersey, GSM to whatever the yarn produces, and the handle junction to no reinforcement. An early yarn decision removes the most expensive branch entirely. A single approver removes decision latency, which is not a revision but feels like one because it consumes the same calendar.

Where the Rounds Sit in the Wider Programme

The two rounds sit inside the 7 working days of sampling, before the 30 days of bulk production, and the boundary between them is the handover — after which a change is not a revision at all but a re-run.

That boundary is worth marking clearly. Inside sampling, a change is a correction and costs a branch. After handover, yarn has been booked, the programme has been released and the bed is scheduled, so the same change costs a re-run: another 30 days and the material already committed. The reason to spend rounds during sampling, even on changes that feel optional, is that the same change later costs an order of magnitude more. MOQ is 100 pcs per style and per colourway, FOB Xiamen is the standard term with CIF and DDP available, and the reference unit cost for a standard E12 tote at 320 g/m² in 300D is USD 4.80. Behind the programme sit 7 production lines running about 200,000 pcs per month.

Running the Decision Tree on Your Next Revision

Running the tree takes about a minute: name the category, name the branch, then decide whether the change is worth a round — and a programme that does this on every request will almost never need more than the two rounds it was given.

The value is not in the arithmetic; it is in the shared vocabulary. A buyer and a programme that both use the words programme correction and specification change, and both know that trim is a 10 to 15 day branch, will resolve a revision request in one exchange rather than in four. That is worth more than the days it saves, because the days are recoverable and the goodwill is not.

Frequently Asked Questions

People Also Ask

Two Rounds Are Enough If the Branch Is Named

Two correction rounds is a workable allowance for any well-briefed programme and a tight one for any poorly briefed one. The difference is not luck; it is whether the buyer and the programme share a vocabulary for what kind of change is being requested and what it physically touches. Naming the branch is what makes two rounds stretch.

For the workflow the rounds sit inside, see knitted bag sampling workflow. For the shade decisions that most often trigger the yarn branch, see custom knitted bag colour matching, and for the programme windows behind the quotation, see custom knit bags.