Garment Sample Requests: Give the Sample Room a Complete Brief

A sample room can make a neat garment and still leave the buyer's question unanswered. The collar may look right, but the wrong fabric makes its shape hard to judge. A sample sent for fit may arrive after washing, although the reviewer expected to see it in its original state.

A garment sample request form should make the intended decision clear before work starts. It tells the sample room what to make, which inputs to use, what may change and what evidence to return. It also lets the team flag a missing input while there is still time to act.

The form does not need to be long. It needs to be complete enough for someone who missed the latest phone call to follow it. The method below uses a fictional overshirt request to show how to write that brief and check its quantities.

Begin with the question the sample must answer

“Make a fit sample” gives a stage name, but leaves much of the task open. Which size needs review? What changed since the last round? Does the team need to assess movement, collar shape, pocket position or all three?

Write the decision in plain terms. For an adult woven overshirt, it might be: “Check arm movement in sizes M and L after the sleeve change. Confirm the pocket position in stone. Record the results before any home-laundering study.”

That statement helps the sample maker set priorities. It also gives the reviewer a reason to ask for more evidence. If the new sleeve works in M but has not been tried in L, the second size remains open.

List the decisions that this request will not settle. A development sample made with temporary buttons cannot prove the final button's appearance or durability. A review of two sizes does not approve every size in the range. These limits belong beside the purpose so that later readers see them.

Buyer requirements must be confirmed for the actual account. For example, URBN's sample requirements place the requirements with the buyer and direct vendors to ask about quantities, sizes and due dates. They also point to separate brand guides. One customer's sample plan should therefore not become a rule for every order.

Build the request around a usable brief

The request is the entry point to a set of product records. It should identify those records without repeating every measurement and construction detail. Copying the same specification into several forms creates more places where an old value can survive.

Use a request number and a revision, such as SR-042, revision 2. Keep the style reference separate. A single style may have several sample requests for different purposes, and the team must know which request each physical garment belongs to.

This example shows the core of a brief. The codes, dates and decisions are invented for illustration.

The open question must be resolved before the affected work proceeds. It is not enough to put it in a notes box and then treat the whole request as ready.

Attach a small file list with each file's name, revision and role. Check that the pattern and measurement sheet describe the same change. A new date on a PDF does not prove that its contents include the latest sleeve correction.

The SEIP apparel merchandising student guide links technical and measurement records, sample comments, shade approvals and trim records within merchandising work. The practical point is to keep those records connected to the request. A loose photograph of a trim cannot show which sample round used it.

Where a product lifecycle management system holds these files, link to the released version and check the sample room's access. ApparelDiary's guide to PLM for fashion product development explains the broader role of shared product records. For this brief, the immediate test is simple: can the maker open the exact inputs named on the request?

Count physical copies by their intended use

Start with the people and activities that need a garment. Then assign sizes and colours to each use. This is more reliable than ordering an unexplained “two of each” and sorting out the purposes later.

In the example, the team plans eight garments. Three go to the buyer, three stay with the factory and two are reserved for a separate wash study. These are planning quantities for this fictional case. The test laboratory must confirm that its intake and method needs are met.

The size totals are six M and two L. The colour totals are six navy and two stone. Both checks must return eight. A spreadsheet can compare these totals, but the allocation still needs a person to check whether each copy serves a real purpose.

Give each garment its own identity before dispatch or testing. Record the request number, copy number, size, colour and intended use on its tag and in the return record. Use the same identity on measurement sheets and photographs.

Two copies may share a purpose only when their handling allows it. A garment can be photographed before washing if the sequence is planned and the photograph meets the review need. It cannot serve as an untouched retained copy after it has been washed or cut for testing.

Discuss that sequence before reducing quantities. If both a reviewer and a laboratory need the same garment at the same time, the plan has a conflict even though the arithmetic adds up. Confirm extra test pieces with the laboratory instead of assuming that spare garments will cover every method.

These development quantities are not a statistical acceptance sample from bulk production. They answer specified product questions. They do not establish an inspection plan for a shipment.

State exactly which materials may be substituted

“Use available trims” is too broad. It leaves the maker to decide which differences matter, while the reviewer may assume that the sample uses the final components.

Name the required component first, then record any temporary replacement. Explain what can still be assessed and what remains open. If no replacement is allowed, say so before the room commits time to the sample.

For example, a temporary button may let the team assess the general layout. A different diameter, thickness or shape could affect the buttonhole and fastening action, however. It would be unsafe to treat a successful fastening trial as evidence for a final button with different dimensions.

The same reasoning applies to fabric. Similar colour does not establish equal weight, stretch, surface or drape. When those properties could affect the question being asked, the technical reviewer should decide whether the trial remains useful.

Record the material source and lot where known. If there is no lot reference, describe the limitation honestly. Do not label leftover development fabric as bulk fabric just because both use the same article number.

For OS-218, the request allows TB2 buttons to hold the front in its intended position during the movement review. It leaves final button appearance and buttonhole performance open. The maker must tag that substitution and include it in the return notes, so a photograph cannot later be mistaken for final trim approval.

If the substitute prevents a meaningful fit assessment, stop the affected work and ask for a decision. The purpose of the exception record is to preserve useful learning, not to make every available material acceptable.

Work out a small material issue without hiding the assumptions

A sample room needs enough usable material to complete the agreed work. The request should show how that quantity was reached, especially when two colours or several sizes are involved.

Assume the room has prepared layout estimates for this exact overshirt pattern and fabric width. Each M garment needs 1.62 m of shell fabric, and each L needs 1.78 m. These fictional lengths already include the pattern's required allowances and the planned layout gaps. They are not general consumption rates for overshirts.

The garment requirement is:

M garments: 6 × 1.62 m = 9.72 m.

L garments: 2 × 1.78 m = 3.56 m.

Total shell length for garments: 9.72 + 3.56 = 13.28 m.

The colour split matters because a surplus of stone cannot replace missing navy. Four navy M garments use 6.48 m, and two navy L garments use 3.56 m. Navy therefore needs 10.04 m for garments. The two stone M garments need 3.24 m.

The sample room also plans small construction trial panels and measured short-end allowances. They are separate additions, with their own reasons.

Suppose the store issues this fabric in quarter-metre increments. Round each colour up separately. Navy becomes 11.00 m and stone becomes 3.75 m, giving an issue of 14.75 m. The rounding adds 0.27 m above the 14.48 m plan.

That 0.27 m is a rounding surplus, not another stated waste allowance. Do not add the trial panels or short ends again under a general percentage. Check that the available lengths have the width and condition used in the layout estimate. A narrow end piece may not fit the pattern even when its length appears sufficient.

Keep lining, interlining, thread and trims on separate lines with their own units. Metres of shell fabric cannot be added to pieces of buttons. Record unused returns and trial offcuts so that the next request can use the learning without treating a small development layout as a bulk consumption standard.

Write the test instruction before using the test copies

A label such as “wash sample” is incomplete. It does not say what the team wants to learn, how the garment will be treated or which condition the reviewer will see.

For dimensional change, the public scope of AATCC TM150 addresses garment length and width changes after home laundering. It includes choices for washing and drying and notes limits for certain stretch fabrics. The brief should identify the agreed method and option, rather than allow each team to choose its own treatment.

ISO 6330 covers domestic washing and drying procedures for textile testing. Its public abstract explains that a complete test includes both washing and drying, and that changes in equipment or other parameters can affect results. Naming only the wash temperature leaves part of the treatment undefined.

These references explain why precise instructions matter. They do not make the two documents interchangeable or require that they be combined. The buyer and laboratory must agree which current procedure applies, the required copies, the reported properties and any pass limits.

Keep an internal exploratory wash distinct from a formal test report. If the factory runs a trial to see whether a pocket changes shape, record the actual treatment and purpose. Do not present that observation as a result from a standard that was not followed.

For the overshirt, allocate the two study copies only after the laboratory confirms its needs. Identify the measurement points and record their initial state. Schedule the report separately from the first fit review, since the buyer's three unwashed review copies do not need to wait for an unrelated laboratory result unless the buyer says otherwise.

Set dates for events people can actually confirm

One date headed “sample due” can mean ready in the sample room, handed to a courier, received by the buyer or reviewed. Those are separate events with different owners.

Start with the required review date and ask when the reviewer needs the garments. Then work back through transport, the factory check, sample making and input readiness. Show working calendars and any booking cutoffs that affect the plan.

For a simple illustration, assume all materials and decisions are ready at the end of working day 3. Making takes days 4 and 5. Checking, measuring and packing use day 6. Transport is planned for days 7 and 8, with receipt at the end of day 8.

This is an assumed sequence for the three buyer copies, not a transport promise. A day-6 receipt request would not fit it. The team must change a dependency, obtain an agreed shorter duration or revise the required date. Writing “urgent” beside day 6 does not remove the missing time.

Confirm sample-room capacity as well as elapsed time. A two-day task may still wait in a queue. Review slots, equipment, external decoration and material release can also delay the start. Record the point at which each needed input becomes usable, as explained in ApparelDiary's guide to measuring supplier lead time.

After the room accepts the request, report changes against the affected event. “Navy fabric now available on day 5” gives the planner something concrete to assess. “Sample delayed” does not identify which part of the plan needs a decision.

Make the required condition easy to reproduce

The request should point to the measurement instructions as well as the target values. A sleeve length needs a start point, an end point and a stated path. A garment width measured with a fold or with tension may not be comparable with the same point measured flat and relaxed.

Do not leave the maker to infer those details from a number. Refer to the relevant point-of-measure diagram and identify any point that changed in this round. When a sketch is unclear, resolve it with the technical team before using the result to judge the sample.

State when the measurements are required. Measurements before pressing, after pressing and after laundering can describe different garment states. The room should record the requested state and any agreed preparation, then identify departures from it. A value without that context may send the next pattern adjustment in the wrong direction.

Also explain which finishing details are needed for the review. The overshirt's collar may need its intended pressing treatment before its appearance can be assessed. A temporary pin that holds a pocket in place should be visible in the notes, because it differs from the sewn construction the reviewer may expect.

Keep the request proportionate to its purpose. If the buyer asks to assess a revised sleeve, direct attention to sleeve movement and the connected areas. The team must still follow the agreed specification, but it should not bury the new question in a long list of unchanged features.

For photographs, identify the copy and view rather than sending unnamed files. A front view, a close detail and a marked measurement can each answer a different question. Record which view supports which comment. Do not use an ordinary screen image as proof of an exact physical colour match; arrange the required physical or controlled colour assessment when colour approval is part of the brief.

Let the sample room answer the brief before it starts

The maker should acknowledge the request with a short readiness check. Confirm the files received, materials available, quantity allocation and expected completion. List any conflict that prevents a useful result.

This response is a technical check, not simply an email receipt. A pattern cutter may find that a pocket placement note conflicts with the drawing. A sample machinist may need a clear seam detail to reproduce the intended finish. Resolve those questions before treating the request as accepted.

If the team proposes a construction change, describe its effect on the review purpose. Show the proposal to the person who can approve it. A quicker operation may be helpful, but the sample maker should not silently change a visible feature to meet a date.

Ask for evidence proportional to the issue. A marked detail view may explain a pocket problem better than a long message. A measurement discrepancy needs the point, target, actual value and method, not merely the words “out of spec.”

Agree which work can continue while a question is open. The room may be able to prepare unaffected pattern pieces, but cutting disputed parts can create avoidable waste. Record that limited permission clearly so it does not become an assumed release for the whole sample.

Return the garment with evidence of what was made

The return record should answer three questions: what was requested, what was actually made and what the reviewer can now decide. Attach it to the copy identities established in the quantity plan.

Record actual material use and any departures from the brief. Include measurements taken in the required condition, views of the changed features and the maker's unresolved concerns. State whether the garment has been pressed, washed, altered or used in a fitting where that history affects the review.

Check completeness before dispatch. In an eight-piece request, making all eight does not prove that eight useful copies exist. If two retained copies were accidentally washed, only six still meet their assigned purposes. The team needs a decision about those two gaps, even though the physical count is correct.

Separate this check from product approval. The factory can confirm that a sample follows the brief while the buyer still decides that the design needs work. ApparelDiary's explanation of quality assurance and quality control provides wider context for controlling a process and checking its outputs.

When comments return, keep the sample identity attached to them. “Raise pocket” is hard to apply if the team cannot tell which colour, size or revision the reviewer saw. A signed comment on the wrong copy may create more confusion than an unanswered request.

Give digital samples an equally clear brief

A digital sample also needs a defined question and known inputs. State the pattern version, avatar, material model, required views and output format. Explain whether the review concerns appearance, placement or a particular aspect of fit.

CottonWorks' digital product creation guidance discusses common standards for digital fabrics, avatars, sewing details and visual presentation. It also covers alignment between physical and digital fit references. Those choices belong in the request when they affect how two reviewers interpret the same model.

A screen image alone cannot demonstrate physical test results. If a digital material is a stand-in, identify it and keep the affected conclusions open. The reasoning is the same as for a physical substitute: a model can answer a useful question only within the limits of its inputs.

Close the request when the required evidence has reached the named reviewer and the remaining actions are assigned. Keep the final brief with its response and sample identities. The next round can then begin from a clear record of what was learned and what still needs to be resolved.

References

• URBN: Sample requirements and buyer-specific questions.

• SEIP: Competency-based learning material for apparel merchandising.

• AATCC TM150: Public scope for garment dimensional change after home laundering.

• ISO 6330:2021: Public scope for domestic washing and drying procedures.

• CottonWorks: Digital product creation best practices.