
Buyer resource
Sample Feedback and Correction Log
Make sample feedback actionable with revision references, evidence, responsible contacts, deadlines and recheck decisions.
01
Create one record for each correction
Begin with the style code, sample revision, size, date received and specification version. Assign a comment ID to each issue. Separate fit, construction, material, artwork and packing comments; they may involve different people and different samples. Keep positive approvals too, but do not let approved packaging hide an unresolved garment change.
02
Write a reproducible observation
State where the issue is, what was observed and which reference applies. For a measurement issue, identify the measurement point, method, unit, target, tolerance and actual result. For artwork, use a dimension or annotated photo rather than move it a little. Label subjective observations as wearer or buyer feedback so they are not mistaken for measured failures.
03
Agree the correction and its consequences
Use separate columns for requested action and agreed action. The development team may propose a different solution after reviewing feasibility. Record who must decide, a requested review date, and whether the change affects other sizes, materials or the quote. Dates are coordination targets, not guaranteed DALI lead times. Update the specification when a change is accepted.
04
Recheck before closing the issue
Use statuses such as open, action agreed, revised sample received and closed. A message saying corrected is not the same as a buyer recheck. Link the next sample, photograph or measurement to the original comment, then record the approver and date. If a correction is rejected, preserve the record and explain the next action instead of deleting its history.
Common mistakes to avoid
- Mixing requested changes with already agreed changes.
- Closing a comment without identifying the revised sample.
- Sending corrections without updating the controlled specification.
Working example
Illustrative sample correction log
| Comment ID / sample | Location / method | Observation | Requested action | Agreed action | Decision owner | Review date | Recheck evidence / status |
|---|---|---|---|---|---|---|---|
| C01 / UW01 R01 | POM01, waist flat width; size M; relaxed; drawing 01 | Target 34.0 cm +/- 0.5 cm; actual 34.7 cm | Investigate and correct | Pending technical review | Technical contact | Illustrative: 2026-10-08 | No revised sample / open |
| C02 / UW01 R01 | Waistband / photo 03 | Logo position differs from artwork R02 | Match approved artwork position | Revise placement on sample R02 | Artwork contact | Illustrative: 2026-10-12 | R02 / photo 07 matches artwork R02; reviewer accepted / closed |
| C03 / PJ01 R02 | Pack / photo 08 | Contents match brief | Confirm pack contents | No change | Packing reviewer | Illustrative: 2026-10-12 | R02 checked against PACK_R02 / closed |
Project worksheet
Start with the Project brief, then complete the relevant product details. Email the workbook and available references to [email protected]. You can leave undecided items blank.
Use the completed worksheet alongside the product drawings, approved specification and agreed order requirements.
Useful information
Your working checklist
- 01Style and sample version
- 02Issue and location
- 03Requested change
- 04Responsible contact
- 05Due date and approval status
Frequently asked
Buyer questions
01Can an email thread be used?
Yes, but consolidate the agreed decisions in a versioned log. Link the email or attachment that supports each action.
02What if the buyer changes the specification rather than fixing a defect?
Mark it as a specification change. Record the commercial or development implications separately from the original sample observation.
From preparation to development
Discuss the questions that remain open.
Use the guide to organize the information you have, then discuss your product and estimated bulk requirement with DALI. A complete worksheet or technical pack is not required for the first conversation.
