Why this matters
Track T1 sample issues by defect, likely cause, mold action, owner, due date, retest result and buyer approval status. A T1 correction log turns sample comments into traceable mold actions so buyers can see what changed, who owns it and whether the next trial actually closed the issue.
Buyer checks
Give every T1 issue an ID, photo and affected part areaSeparate dimensional, cosmetic, assembly, material and process issuesRecord likely cause and whether the action is mold correction, process tuning or design changeAssign owner, due date and next-trial evidence neededClose each issue only after retest samples or inspection records support approval
Quote variables
| Quote variable | Why it changes the mold route |
|---|---|
| Issue severity | Critical fit or safety issues should block release until retested. |
| Correction type | Mold welding, machining, polishing, gate changes or process tuning carry different cost and timing. |
| Evidence needed | Photos, measurement reports, videos or assembly tests make closure auditable. |
| Approval status | Open, corrected, retest required and accepted statuses prevent vague release decisions. |
Common mistakes
Letting supplier comments stay in chat without an issue ownerTreating all sample defects as mold problems before checking process and design causesApproving the next trial without comparing against the previous defect list
How to apply it
Build the correction log before the second trial: issue ID, photo, defect type, likely cause, action, owner, due date, retest method and buyer approval status. If the project is already in T1, the guide can turn scattered sample feedback into a traceable correction and retest workflow.