A technical query is not closed merely because someone replied to an email. The answer must resolve a defined question and become part of the instructions used by production. Otherwise an old drawing, a portal selection, and an informal comment may continue to disagree.
The Eurocircuits data feedback guide separates saving responses from submitting the completed response set. That interface-specific distinction illustrates a broader problem: a drafted answer and an accepted manufacturing instruction are different states.
Give every question an identity
Capture the supplier job, design revision, query number, and affected feature or document field. Preserve the original question and any marked drawing. When several issues arrive in one message, separate their dispositions so that an answer about mask clearance cannot be mistaken for approval of a hole change.
Assign the decision to someone who understands the requirement involved. Purchasing can coordinate a response, but an electrical, mechanical, or process tradeoff may need its relevant owner. Identify the decision owner in the record without creating a long approval chain for routine factual clarification.
Write an executable answer
| Weak response | Information needed for closure |
|---|---|
| Use your standard | The accepted characteristic or specifically bounded option |
| See the drawing | Document identity, revision, and relevant location |
| That is fine | The exact proposed solution being accepted |
| New files attached | Which previous files the new release supersedes |
If the correct answer is to regenerate design data, keep the query open until the replacement set has been received and interpreted correctly. An intended future edit is not a production-ready instruction. Avoid issuing a partial patch without defining its relationship to the remaining files.
Check the final instruction set
- Confirm every query has an explicit disposition.
- Identify which answers changed files or order settings.
- Remove or supersede contradictory instructions.
- Verify supplier acknowledgement of the resulting release.
- Archive the closed query set with the build record.
Read the final package as though the reviewer had never seen the conversation. If the intended result still depends on remembering a call, add a concise written instruction or revised document. This is particularly useful when a job moves between engineering review and production planning teams.
Keep unresolved questions visible as unresolved. A general release message should not erase a specific hold condition. Conversely, once a question is conclusively closed, reference its final disposition instead of circulating several competing explanations. This creates a usable engineering history for repeat orders and for investigating any later discrepancy.
Move from reading to a build-ready project
Use the fabrication and assembly checklists to prepare drawings, production files and test requirements.
Open the DFM checklist