A usable fabric sample approval record links handfeel, color, construction, test scope and the physical golden sample to one controlled version. It also states the limits of the approval so that visual acceptance is not mistaken for bulk or performance approval.
Build the record around sample identity and approval scope
A fabric sample approval record should show exactly which material was reviewed and which decisions were made. A signature or an email saying "approved" can be difficult to apply later if the sample version, color lot, finish route or test scope is unclear.
The record should travel with the technical specification, purchase order and relevant test requirements. When information conflicts, the parties should document which reference has priority before bulk production.
- Identify the sample type, such as lab dip, handloom, strike-off, development sample, pre-production sample or shipment reference.
- Record the supplier, buyer, article or style number, fabric description, composition, construction, nominal GSM, usable width, color name and color code.
- Assign a sample version, submission date, approval date and approval status. Use clear terms such as approved, approved with comments, rejected or resubmission required.
- State what the approval covers and what remains pending. Visual, handfeel or construction approval should not be recorded as test approval unless the required results have also been reviewed.
Compare handfeel under repeatable conditions
Handfeel is subjective, but the review process can still be controlled. The buyer and supplier should compare samples in similar lighting and handling conditions, against the same reference, and at the same processing stage.
The approval note should identify the intended end state. A greige, dyed and washed fabric may each have a different touch, so approval at one stage should not automatically be treated as approval at another.
- Compare softness, smoothness, dryness, crispness, fullness, drape, surface friction and perceived weight with the agreed reference.
- Assess both face and back, and check whether the fabric feels consistent across the sample rather than only in one area.
- Condition samples in the agreed environment before comparison when moisture or temperature may affect the result.
- Record whether the handfeel is approved as submitted or only after an expected process such as washing, compacting, brushing, calendaring or garment finishing.
- Describe differences in observable terms. Comments such as "slightly drier than approved reference" or "less full after wash" are more useful than "handfeel not good."
Separate color identity from color performance
Color approval should identify the standard, viewing conditions and sample version. A color name alone is not a sufficient control because the same name may be used for different shades or finishes.
Visual shade acceptance and colorfastness performance are separate decisions. The approval record should avoid implying that an acceptable shade has also passed washing, rubbing, light, perspiration or other applicable testing.
- Confirm whether the submission is a lab dip, strike-off, yarn-dyed pattern, printed sample or bulk lot cutting.
- Record the color standard used, including the physical swatch, color code or approved digital reference where applicable.
- State the light source or light sources used for visual assessment and note any observed metamerism.
- Compare face-to-back variation, side-to-center variation and color consistency across different parts of the sample.
- Document whether color is approved only for shade or also for appearance after washing, heat treatment, coating, lamination or other finishing.
Confirm construction before judging appearance alone
Two fabrics can appear similar while differing in construction, weight or finishing. The sample approval record should therefore connect visual acceptance to measurable fabric parameters.
Nominal values and tolerances should come from the agreed specification rather than being added after review. If the development sample is outside specification but accepted for design direction, the record should say that bulk must still meet the specified construction and GSM.
- Verify fiber composition and yarn type against the specification.
- Compare weave or knit structure, yarn count or linear density, thread density or stitch density, and any relevant pattern repeat.
- Measure GSM and usable width using the agreed method, sample conditioning and tolerances.
- Check surface features such as slubs, ribs, brushing, raising, loops, coatings, prints, embossing or mechanical finishes.
- Record defects or irregularities visible in the submitted sample, including bowing, skewing, barre, streaks, needle lines, missing yarns, print misalignment or finish variation where relevant to the fabric type.
Define the test scope without turning the sample into a blanket approval
The required test scope depends on fiber content, fabric construction, finish, product use and destination requirements. It should be agreed rather than assumed.
The record should distinguish tests completed, tests pending, tests not applicable and tests required later on bulk material. Reports should be linked by report number, sample identity and date, without treating one tested specimen as evidence for unrelated colors, finishes or production lots unless that coverage has been agreed.
- List each required test, the applicable method or buyer protocol, the required stage and the acceptance criteria.
- Clarify whether testing applies to the submitted sample, a pre-production lot, bulk production, finished garments or more than one stage.
- Include relevant performance areas such as dimensional stability, spirality, seam performance, pilling, abrasion, tensile or tear strength, stretch and recovery, colorfastness, appearance after laundering and restricted-