Preproduction Handover: Release a Garment Order With Clear Approvals

A confirmed order still needs a controlled release

The buyer has approved an overshirt. Fabric is in the store, and the sewing line is ready. During the preproduction meeting, the team finds a conflict. The trim card shows one button, while the bill of materials names another. The sample carries the new button, but the store has both types.

This is a handover problem. The buyer may have confirmed the order. The product may be workable. Yet the factory still lacks one clear instruction about what to make.

A garment preproduction handover gives the factory controlled instructions for an accepted order. It connects approved samples, written requirements, materials and process checks. It also states who may release which work, with what limits.

The handover happens after the earlier decision that the order is feasible. Its question is now specific: can this team start this part of the order using these materials and current instructions? A purchase order, a meeting signature or a sample marked “approved” cannot answer that question on its own.

Identify the exact work being handed over

Begin with the order number, style, product revision, quantity and delivery split. Name the factory and any approved outside process. List the colours and sizes covered by the proposed release.

Then identify the receiving teams. Cutting and sewing may need different details from washing or packing. Each team, including quality and finishing, must follow the same product decision. Include the store and planning team when their actions control what can start.

Do not assume that all work is being released at once. The team may be discussing a construction trial, one colour or the full order. State the scope in the meeting invitation and on the release record.

A useful opening statement might be: “Review style OS28 for a limited navy trial using fabric lot N17 and button lot B91.” That is more precise than “PP meeting for overshirts.” It lets attendees bring the correct material records and physical references.

Avoid rebuilding the entire commercial negotiation in this meeting. Raise any unresolved term that blocks production, but keep the focus on instructions and permission to act. Someone must own the decision if an open price, payment or delivery issue prevents release.

Make a compact index of the release package

The handover package should be easy to navigate. Hundreds of emails can preserve the history. They may still leave the factory unsure which instruction to use today.

Create an index that links each required record to its current revision and owner. The exact records depend on the product and buyer. A practical starting set is:

Keep old records available for traceability, but separate them from active instructions. Mark an outdated paper copy at the point of use or remove it through the factory's controlled process. Do not rely on a worker noticing that an email attachment is newer.

The index is a guide to evidence, not a substitute for it. Each link should open the relevant file or identify the physical sample's location. Check access from the receiving team's device before the meeting ends.

Reconcile the files against the physical product

Different documents do not need identical revision numbers. A specification at revision 7 can correctly match a BOM at revision 5. What matters is whether both describe the same approved product and include the relevant changes.

In the overshirt example, the sample uses button T24. The BOM still lists T20, while a later approval email accepts T24. Check what the approval covers. Then update the affected record and issue a clear current trim reference.

Do not resolve the conflict by declaring that the latest email always wins. It may cover appearance only or apply to one colour. Its sender may lack authority for that change. Establish the decision before updating instructions.

URBN's technical manual gives a buyer-specific example of approval control. It requires Technical Designer approval for deviations from its standards before bulk production. It also calls for approved-quality fabrics, trims and wash treatments in fit samples. Other buyers may use different roles and processes.

For the actual order, list each change since the last sample. Confirm where it appears in the pattern, BOM, specification and process instructions. A comment marked “done” is weak evidence if the corresponding file still shows the old detail.

The ApparelDiary PLM guide explains how linked product records can support this work. The handover still needs people to resolve the meaning of conflicting information.

State what each approval permits

An approval should identify its subject. A colour approval may confirm a shade submission without approving bulk fabric quality. A fit approval may leave a label or packing question open. A passing test report may cover one material state and no others.

Read the comments with the sample. Record its ID, size, colour, materials and purpose. If it uses a substitute trim, make that exception visible. Do not leave the production team to discover the substitution after copying it.

Ask a direct question for every open comment: does this prevent the proposed work from starting? Some matters may affect a later operation only. Others make cutting or assembly unsafe to begin because the product could change.

The decision belongs to the authorised owner under the buyer's and factory's agreed process. The merchandiser gathers the answer and records it. Attendance at a meeting does not automatically grant approval authority.

Use clear status labels. These might be approved for the stated scope, pending review, failed or replaced. If the buyer uses a different vocabulary, explain its meaning in the handover. A green cell is useful only when everyone knows what it permits.

Protect the physical reference during use. Identify where the approved sample is held and which working copies have been checked against it. A replacement sample needs a clear link to the original approval. Do not assume that two samples made at different times are identical. If the reference is damaged or lost, arrange a controlled replacement through the responsible owner. An unclear photograph may help locate a detail. It cannot answer every question about colour, feel or construction.

Check material identity, quantity and status separately

Material can be present without being ready to use. The item may be wrong or its lot may be on hold. Some of the stock may already belong to another order. Check all three points.

For fabric, connect the approved quality and colour to the actual roll or lot records. Follow the applicable receiving and shade controls. ApparelDiary's fabric roll acceptance checklist provides a separate guide to those receiving decisions.

For trims, compare the actual item with the released reference. Check the supplier's item code, size, colour or finish and any required performance evidence. Two components with the same informal description may still differ in function.

The GS1 Global Traceability Standard describes several levels of identity. A product type differs from a particular batch, lot or individual item. Its manufacturing example records the connection between inputs and outputs. Apply that distinction during the handover. Which approved material lot will enter the released work? Can the team identify it?

A barcode can carry an identifier, but it does not prove approval. The linked status and records must be correct. A handwritten lot record can be useful too. It needs a unique ID within the defined system, clear writing and reliable upkeep.

Work through a release case with actual boundaries

Consider an invented order for 3,600 adult button-front overshirts. Navy accounts for 1,800 pieces, olive for 1,200 and ecru for 600. Each colour uses four sizes in a 1:2:2:1 ratio.

The ratio has six parts. For navy, 1,800 ÷ 6 = 300 pieces per part. The two middle sizes each receive 600. This checks the order split; it does not set a cutting allowance or permit extra shipment.

The team finds three different release positions:

Navy represents 1,800 ÷ 3,600 × 100 = 50% of the order. That does not make the whole order “50% approved.” Approval has a defined scope. The remaining colours retain their own holds.

All other necessary requirements for the navy work are assumed to be satisfied in this example. In practice, the owner must establish that fact. The presence of approved fabric and buttons alone is not enough to release a garment.

Check quantities without disguising a shortage

The invented overshirt uses six front buttons, two cuff buttons and one spare button. Its approved net requirement is nine buttons per garment.

For the navy quantity:

1,800 garments × 9 buttons = 16,200 buttons.

Suppose 16,700 approved buttons from lot B91 are available and assigned to this work. The difference is 500 buttons. That balance is not an automatic waste allowance or permission to make extra garments. Its use must follow the approved material plan.

The full order's net need is 3,600 × 9 = 32,400 buttons. The navy stock does not establish that the other colours are ready. Nor can the team silently use the wrong olive button to cover a shortfall.

Keep net use, approved allowances, reserve stock and actual issue as separate fields. A single “required” total can hide which assumption changed. If material is taken for trials or damaged during handling, record that use so the remaining balance is credible.

This is a quantity check for handover. It does not replace the detailed BOM or the store's issue and return records. Its purpose is to expose a mismatch before production receives an unsupported instruction.

Use a limited trial when the remaining question is specific

A controlled trial can answer a setup question before the factory commits a large quantity. It is useful only when the team knows what it must prove and has permission to use the materials.

For the navy overshirt, imagine a trial of 24 garments. The written permission names the pattern and files, fabric N17 and button B91. It states which operations may proceed and who supervises them. It also names the checks and who will decide the next step.

The trial is not a small, unofficial bulk run. Set a quantity limit and a stop point. Keep its output identifiable and prevent it from blending with released goods while the result is pending.

If the 24 garments may count toward the 1,800-piece navy order, record that condition. They must meet all applicable acceptance requirements. If accepted into the order, the remaining quantity is 1,800 − 24 = 1,776 pieces. Destructive tests or unsuitable samples may require replacement under a separate approved instruction.

Do not invent a standard trial size of 24 for every garment. The number here is illustrative. The real plan depends on the question, product differences, method and required evidence.

Transfer the method as well as the sample

A sample shows an outcome. It may not show how the factory achieved that outcome. The handover should preserve the method where it affects repeatability.

Include relevant attachments, guides, seam details and settings from the approved trial. State the machine or process conditions to which they apply. Avoid copying a setting from another material without checking the result.

Seam Seal International's preproduction guidance provides a specialist example. It calls for checks on how the tape bonds to the production fabric's coating. It also stresses recording the machine settings. That guidance concerns seam taping. It does not set a process for all ordinary sewn shirts.

The broader handover lesson is to capture the conditions behind a successful result. For the overshirt, record the approved button attachment method. Include the press setup used to achieve the required appearance. The qualified process owner should define the actual controls.

Explain any difference between the sample room and the bulk line. An outcome achieved by one specialist using a special tool needs a route for transfer. A photograph of the sample is not a training plan.

Bring label and packing decisions forward

Packing occurs late in the route, but its instructions can affect earlier work. Decide where labels and hanger loops belong before sewing starts. Spare trims and retail identifiers may need early decisions too.

Review the approved artwork and the variant mapping. A correct size label attached to the wrong size creates a different problem from a printing fault. Check both the label content and the instruction for where it belongs.

Care information needs the relevant evidence. The FTC care-labelling guidance applies to covered US products. It requires reliable evidence for care instructions. That evidence must support the garment as a whole. This is a US example; the responsible team must establish the rules for the actual market.

Check the packing method against the order. URBN's carton-packing instructions distinguish mixed cartons from specified prepacks. They also include conditions for particular orders. They show why a general phrase such as “standard export packing” is not enough.

Use the buyer's current instructions. Do not apply another customer's carton limits or assortment rules to the overshirt case. If packing remains unresolved, check its effect on earlier operations. State clearly which work may proceed.

Make open issues actionable

An open-issue list should be short enough to manage and specific enough to close. Give each item an owner, evidence required, due date and affected work. Avoid entries such as “quality to confirm” with no defined question.

The olive button mismatch needs a decision. The owner may obtain the approved T24 item or seek valid approval for a change. The record should identify whether sampling, testing, price or timing must also be reviewed. It remains open until the required decision is recorded.

For the ecru fabric, name the review still pending and the authority that can release the lot. Do not turn a promised report date into an approval date. The result may need assessment or may fail.

Where a hold applies, show how it is enforced. That may involve the material location, issue permission and production instruction. A hold entered only in meeting minutes may not reach the person handing fabric to cutting.

Make escalation factual. State the effect on the next operation and the latest decision time. A warning about delivery risk should help someone decide, not pressure them to sign an unsupported pass.

Extend the handover to outside processing

Garments may go out for embroidery, washing or another approved process. The outside team needs its own clear instruction. Name the style and revision, quantity, lot identities, permitted process and return requirements. Confirm that the receiving contact can access the relevant reference.

Do not send several old sample comments and ask the processor to decide which still apply. Provide the current decision with any limits. Where the processor proposes a change, route it back to the authorised owner before work proceeds.

Record the goods sent, returned and held. Keep trial pieces and rejected goods visible rather than treating every returned item as usable production. The garment factory must still complete the required receiving and quality decisions.

A partial release also needs boundaries at the outside site. If only navy goods are authorised, the instruction should not imply permission for the whole style. Agree how the processor will separate other colours and held lots. Define how it must report a problem before adding more work to the affected batch.

Check the controls behind the screen status

A software status can support the handover, but its meaning depends on setup. Do not assume that marking a checklist complete prevents every unauthorised transaction.

Microsoft's product-readiness documentation illustrates this distinction. It assigns checks to people or teams and supports manual or system checks. It also describes a limit for standard products. They can still be used in transactions with checks incomplete. A suitable lifecycle state is needed to block that use.

That is a software-specific example, not a requirement to buy a particular system. The factory should test the control it actually uses. Can held stock still be issued? Can an old BOM be selected? Who can change a release status, and is the action recorded?

Use a proportionate control for the risk. A small operation may use a signed issue instruction with a clear material hold. A larger one may need linked system permissions. In either case, the receiving team must understand what it may do.

Finish the meeting with a decision and a demonstration

Before closing, ask each receiving owner to show the current instruction they will use. Cutting should identify the released pattern and material scope. Sewing should locate the approved construction reference. Quality should state the first checks and hold points.

This brief check may reveal an access failure or old attachment. A general signature could miss either problem. Resolve it while the relevant people are present.

Record a clear outcome: full release for the stated scope, a limited trial, a partial release or a hold. Include the effective time, authorised owner and any expiry or next review point. Keep the unresolved colours visible beside a partial release.

A signature should confirm a defined responsibility. It may acknowledge receipt, completion of a technical check or authority to release work. Do not use one signature box to imply all three without explanation.

Send the decision to every affected team through the agreed route. Give outside processors the current instructions they need. Limit the information to what their work requires.

Keep the handover valid after work starts

A later change can invalidate part of the release. If the approved button becomes unavailable, the store cannot treat a similar item as an automatic replacement. The affected work needs a defined review.

Identify what has already been issued, cut, sewn or packed. Record the affected lots and quantities before deciding how to proceed. Separate untouched stock from work that may need inspection or correction.

Update the linked instructions together. A revised BOM with an unchanged trim card recreates the original overshirt problem. Notify everyone who holds a paper copy or local file. Telling the person who maintains the main folder is not enough.

The first production checks should also confirm that the handover worked. Compare early output with the released requirements and record any difference. If a new problem appears, use the defined stop and escalation route. Do not let more affected work build up.

Close the handover record once the required actions are complete. Keep it linked to the production history. Its value is the clear link between a decision, the evidence behind it and the work that was allowed to begin.

References

• URBN: technical manual, approval scope and sample requirements.

• GS1: Global Traceability Standard, identification and production records.

• Seam Seal International: preproduction compatibility and setting checks.

• FTC: evidence for garment care instructions.

• URBN: carton and prepack requirements.

• Microsoft: product-readiness checks and transaction controls.