Lead with the intended garment
Name the garment and the part or panel that drives the fabric choice. Explain the appearance you want to preserve and the question a sample should answer. If the reference list is empty, say that article recommendations are welcome. If you have physical references, include their IDs and distinguish them from website development-direction IDs.
Write scale and direction carefully
Describe a fine or broad visual rhythm as a preference unless you have an actual measured repeat. Include millimetres only with the relevant sample identity and measurement evidence. State the direction relationship needed at a pocket, front opening or seam. Keep photographic viewing conditions with the image rather than treating a cropped close-up as a measured specification.
Separate material constraints
State whether the composition is mandatory or open to recommendations. Add target GSM and usable width with units when the project has actual requirements. Unknown values should stay open. If a material claim or test matters, name the evidence needed for the proposed article and intended use. Avoid treating appearance words as proof of fibre content or performance.
List colours, quantities and timing
Keep quantity per colour distinct and retain the original units. Add the colour reference and any acceptable variation to discuss. Select the sample stage needed for the decision and describe target timing as a request. Ask which articles, sample sizes, minimums and next steps are applicable. Do not insert generic prices, stock or production schedules into the template.
Keep questions and versions visible
End the brief with unresolved points and the response you need. Keep your observation or trial record attached where relevant. Review the generated English text before sending, and retain the complete version with your attachments and the team's reply. When a requirement changes, make the revision clear so it does not silently alter an earlier sample decision.
Audit inherited entries before the template becomes the request
A reused worksheet can contain a mixture of current requirements, old candidate values and placeholders that look equally authoritative once printed. Review the origin of each populated material and quantity field before sending. Ask whether the entry came from the current buyer requirement, an identified candidate document, a physical observation or another project's brief. Keep those roles distinguishable. A previous target GSM should not become a new mandatory condition simply because it was already in the cell when the document was copied.
Check the fields that would direct or exclude recommendations first. Composition wording, usable-width needs, colour quantities and the sample task can materially change what the recipient proposes. If the current project has no such requirement, remove the inherited value from the active target or mark it explicitly as background where it genuinely helps. If the buyer did state it, preserve the original wording and unit. Do not make the brief look complete by borrowing a nearby article's specification or a typical value from an earlier example.
Keep an observed value separate from its intended use. A measurement on a retained cutting may explain a previous placement while not defining the requirement for the next article. Likewise, a proposed supplier value may describe a candidate awaiting confirmation rather than the target the buyer originally set. Where both matter, retain both with their roles and sources. Ask for clarification if a single unlabeled number could plausibly mean either. Converting it into a polished specification heading does not resolve that ambiguity.
Imagine copying a former jacket brief to request a larger cutting for a new coat. The old colour total, support reference and pocket trial result may all be irrelevant, even though the broad appearance direction remains useful. Keep the direction with its stated role, rewrite the actual coat question and leave unconfirmed article fields open. The new brief is ready for a recommendation when the recipient can tell which information is current and which answer is being requested. It need not contain a numeric value in every box, and it should not hide inherited assumptions behind a tidy layout.
Check the attachment map as carefully as the written fields
Create a direct connection between each reference named in the brief and the material actually being shared. A physical sample ID, a drawing revision and a photograph file are different references even if their names look alike. State what each contributes: colour direction, actual sample identity, garment shape or evidence of a trial. If one attachment serves more than one purpose, name those purposes and their limits rather than expecting the recipient to infer them from the filename.
Check the available files against that map. Open the intended attachments and confirm the version and relevant content, rather than attaching whichever similarly named file appears first. A correct current brief can still be undermined by an older drawing or a photograph of a rejected sample. If a file has been renamed for sharing, keep its link to the original project reference. If a drawing is proposed rather than approved, retain that status in the accompanying description. The map should explain the evidence, not assign it authority that it never had.
Resolve omissions before they become invented interpretations. When a colour reference is named but unavailable, state what is missing and whether the recipient is being asked to recommend a direction in the meantime. When a required garment outline is absent, decide whether the sample request can still answer its limited question or needs that outline first. Do not replace a missing attachment with another article's convenient image without identifying the substitution. An unavailable file can remain an open dependency rather than a reason to guess its contents.
Review the outgoing message itself. The website's text export and photo index do not automatically supply the local evidence files. Attach or share the authorised files through the actual sending channel, and check that the recipient can locate the view or document referred to in the text. Preserve the complete sent version with its attachment list. A later correction should identify which reference changes and what question that affects. This makes the brief answerable as a received packet, not merely as a document whose author still has the missing context on their own computer.
Keep response information separate from the buyer’s target
After a reply, update the question it actually answers. Keep the original requirement, proposed candidate information and the respondent's confirmation distinguishable. If the team recommends an article with a stated width, that is information about a proposal; it does not automatically change a mandatory usable-width requirement or prove that a particular received cutting has that width. If sample supply is conditional, preserve the condition beside the next action rather than filling a blank with an unconditional available label.
Use an explicit source and status where confusion is likely. A short entry can identify that composition awaits article confirmation, colour remains a direction or a garment trial is requested but not yet made. The exact worksheet arrangement is a project choice. What matters is that a reader can distinguish a value the buyer requires from a value someone proposes and from a physical observation. Do not assign confirmation status because the respondent left another field blank or because a recommendation appears in a formal-looking document.
Check dependencies when a reply changes the next step. A proposed larger cutting may serve the surface question while leaving the collar construction unrepresented. An alternative article may require its own measured repeat before a placement plan is meaningful. List the specific remaining task and its owner instead of carrying a broad unresolved note forward indefinitely. If the reply makes a previous attachment inapplicable, update the active map while retaining its historical relationship. The production-handover guide covers later instructions to actual work; this worksheet should first make the development request internally coherent.
Before sharing the revision, compare it with the version that elicited the reply. Identify any buyer requirement that moved and whether that movement was actually authorised, rather than an accidental consequence of replacing target fields with candidate data. A recipient should be able to answer the current question without guessing what changed in the exchange. This closes answered items while preserving real open conditions. It does not certify the proposed article, create an order or treat the act of completing the worksheet as approval by another party.
Review meaning after shortening or changing the communication language
A concise brief can lose its most important condition when it is shortened for a message, presentation or another language. Compare the outgoing version with the source requirement sentence by sentence where scope matters. Retain mandatory versus preferred wording, negatives, conditions and the object each description applies to. A request to consider a different article only if its composition is confirmed to meet the requirement is materially different from a statement that the alternative is suitable. Clearer language should make that distinction easier to find, not remove it.
Check numeric entries with their surrounding meaning. A quantity per colour is different from a programme total; a number of garments is different from a length of cloth. If units are converted for communication, preserve the original entry and identify the conversion basis rather than replacing it silently. Do not infer a new target from a rounded display or a missing unit. Ask the owner to resolve an unclear quantity before the recipient uses it to propose a sample or commercial next step.
Review reference roles in the rewritten version too. A description of an illustrated direction should not become a confirmed article statement, and a buyer's appearance observation should not become a technical approval. The builder retains typed entries while using English export labels; it does not establish that a rewritten free-text explanation preserved every condition. Keep any communication rewrite connected to the source wording so a later reader can recover what the buyer actually asked. This is especially useful when a short summary travels separately from the complete brief.
Try a practical reader check before sending: can another project participant identify the garment question, the fixed constraints, the actual evidence and the next requested answer from the outgoing packet alone? If they need an explanation, repair the specific ambiguity rather than adding an entire old email thread. For a hypothetical pocket request, retaining the current outline and a sentence identifying the unresolved finished-edge relationship may be more useful than several general texture descriptions. Keep the full source record available as history, while ensuring that the concise current version still contains every condition needed to answer its limited task.
Your decision and record
| Check | Decide | Keep with the reference |
|---|---|---|
| Project | State the garment and decision the sample supports. | End use, part and purpose. |
| Appearance | Separate measured repeat from visual preferences. | Scale, contrast, surface and direction. |
| Requirements | Identify mandatory material and dimension targets. | Composition constraint, GSM and width units. |
| Request | Ask for the applicable sample stage and article information. | Colours, quantities, timing and open questions. |
Questions for this step
Must every field be filled?
No. The brief needs an end use or a description, while unknown article properties and targets remain open. Mark the points you want the team to recommend or confirm.
Can I use the English builder after downloading a local-language worksheet?
Yes. Use the worksheet to organise the project, then enter the information in the builder. The export uses English field labels and retains your typed text in its original language.
What should be kept with the final brief?
Retain its revision, selected IDs, physical sample information, attachments, trial records and the textile team's response. These establish which requirements and questions were actually discussed.
Should a supplier’s proposed value replace the target field?
Keep their roles separate unless the buyer has deliberately revised the requirement. A candidate value describes what is proposed; the target describes what is wanted or mandatory. Retain the source and confirmation status, and ask whether the difference affects qualification or merely an open preference. If the buyer accepts a changed requirement, identify that revision explicitly. Do not make a recommendation appear compliant by overwriting the original target before anyone has decided whether the departure is allowed or assessed the resulting garment question.
Can one attachment answer several rows in the brief?
Yes, when its identity and role are clear for each question. A labelled garment photograph may locate both a pocket concern and a surface change, while not establishing material composition or a measured repeat. Identify the relevant view or area for each use, and keep any unsupported field open. If the two questions require different physical states, ask for those states rather than assigning both to a convenient image. A shared attachment reference saves duplication only when it preserves the separate evidence limits.
How can someone answer the current brief without reading the whole email history?
Send a self-contained current request naming its revision, active evidence, fixed requirements and specific unanswered items. Include the relevant answers already received with their conditions and sources, and mark superseded attachments as background rather than active instructions. Keep a link or reference to complete historical records where needed. The recipient should be able to identify the requested action and the evidence it depends on without reconstructing scattered corrections. Do not achieve brevity by deleting a disputed requirement or turning an unconfirmed proposal into the current specification.