Design. Develop. Source. Manufacture.

Apparel Development & Production Process

Keep the product, people and revisions connected from first brief to reorder. Agree the required records before work moves to the next stage.

Planning guide · Actual services, supply, fees and commitments require project-specific confirmation.

Six connected approval gates

This is a proposed planning sequence, not a live project tracker. Agree actual deliverables, owners and conditions.

  1. Brief & route

    Identify intended product and use, design readiness, authorised references, market, quantity unit and open decisions. Select OEM, ODM or Private Label by the actual work needed.

    Responsibilities to agree: Buyer provides the inputs; the proposed development/supply scope and named contacts need review.

    Decision record: A dated brief, route decision and gap list. No quote or project acceptance is created by preparing a brief.

  2. Scope & quote

    Separate development and production deliverables, quantity/minimum basis, assumptions, costs, currency, evidence requirements and timing dependencies.

    Responsibilities to agree: Agree the review owner and which party supplies, checks or approves each input before commissioning work.

    Decision record: Written scope and commercial confirmation, identifying exclusions, price validity and unresolved conditions.

  3. Materials & technical baseline

    Review the actual material/trim direction alongside drawings, measurements, construction and artwork. Treat a guide or visual reference as an input, not an approved material record.

    Responsibilities to agree: The agreed sourcing/development contact records candidates; the named approver decides the proposed baseline and any evidence needs.

    Decision record: Versioned BOM/material references, drawings and chart, with substitutions and open tests explicitly identified.

  4. Sample & corrections

    Plan the required development, fit, decoration or pre-production samples. Link comments to sample ID, revision and feature; classify corrections separately from new requirements.

    Responsibilities to agree: Agree the sample reviewer, fit reference and final approval owner. Specify which changes require another sample or extra scope.

    Decision record: Dated sample decision and correction log, identifying exactly which size, material, artwork and construction were reviewed.

  5. Production release & quality

    Identify final technical files, approved samples/materials, size/colour allocation, packing and inspection criteria. Resolve or explicitly handle outstanding items before release.

    Responsibilities to agree: The named owner authorises production only under the agreed commercial/booking conditions; inspection and deviation decisions need assigned owners.

    Decision record: Written production baseline and release; inspection/disposition records for the actual bulk. Sample approval alone does not verify bulk quality.

  6. Dispatch & reorder

    Confirm release disposition, quantities, packing, shipping documents and delivery arrangements. Reorders refer to the approved baseline but need current sourcing and commercial confirmation.

    Responsibilities to agree: Agree dispatch authorisation and follow-up contacts. Review any licensed-design or agent attribution requirements only where they actually apply.

    Decision record: Dispatch/reorder reference and outstanding-issue log. Past orders do not establish unchanged availability, pricing or timing.

Use one decision record format

Suggested fields for your project documents. This page does not create, upload or store approval records.

Reference & revision
Project/style ID, stage, document/sample IDs, issue date and superseded revision.
Scope reviewed
Exact materials, construction, size/colour scope, artwork or evidence included in the review.
Decision & reviewer
Named approver, date, approved/revise/on-hold decision and conditions or unresolved items.
Change & impact
Requested correction or new requirement, affected files, sample needs, fees and timing consequences.
Next release condition
Required action, responsible contact and what must be confirmed before the affected work continues.

Name the current baseline and remove ambiguity about obsolete files. An acknowledgement is not automatically an approval, and approval of one scope does not approve unrelated changes.

Handle open items and changes explicitly

Do not silently replace the baseline or assume a requested change has been accepted.

Missing input
List the gap, owner and next review. Mark estimates and unconfirmed materials separately from approved specifications.
New requirement
Assess effects on completed development, materials, sample scope, cost, timing and evidence. Confirm revised scope before affected work.
Sample or bulk deviation
Identify the specimen/batch, agreed criterion and observed issue. Record the proposed response and disposition owner; do not imply every issue can be waived.
Release hold
Record what is held and why. Identify the needed confirmation and who can authorise the next step under the agreed project terms.
Repeat order
Reconfirm the baseline and current supply/price/quantity rules. Review applicable design permission, royalty and agent attribution before commercial confirmation.

Connect the records to the right guide

Keep approvals linked to the exact product and purpose, not only to a general platform description.

Questions about approvals

The project documents define the actual responsibilities and release conditions.

Can a target launch date replace the approval sequence?

No automatic release is implied. Identify timing dependencies and required decisions, then agree a realistic project plan without treating a requested date as a commitment.

Does sample approval prove bulk quality or performance?

No. Record the sample scope, then separately agree bulk inspections and any product-specific performance evidence.

Can one approval cover later substitutions?

Only the agreed scope is described here. Record substitutions, review their impact and obtain the required change decision before affected work continues.

Are these records stored in a website account?

No. This page is a planning guide, not an account, order-management or approval-storage service. Use your agreed project documents and manual follow-up.

Prepare a reviewable project.

The project page prepares a downloadable brief for manual email follow-up. It does not upload attachments, accept an order or confirm a quote.

Prepare a project brief