Engineering resource
PCBA DFM feedback: deciding which changes need approval
PCBA DFM feedback is most useful when it becomes a clear engineering decision. A supplier may identify an ambiguous drawing, propose a manufacturing adjustment or request a design change that affects the finished assembly. Those situations should not all receive the same reply. The release team needs to know what will change, which requirement is involved and who is authorized to approve the result.
A response such as “please proceed” can be dangerously incomplete when several options or file revisions are under discussion. A better response identifies the specific issue, accepted solution, applicable revision and any verification required. This article describes a practical way to make that approval record useful to design, purchasing and manufacturing without turning every routine clarification into an unnecessary redesign.
Separate clarification from permission to change the design
A clarification explains the intended meaning of existing data. For example, a drawing may omit a unit label even though the underlying dimensions are otherwise consistent. The response should resolve the ambiguity and identify any document correction needed. It should not give the supplier open-ended permission to reinterpret other dimensions.
A proposed change is different. Moving a hole, changing a material or altering a pad can modify the product that will be manufactured. The reviewer needs a before-and-after description and the reason for the proposal. Even when the change appears small, its significance depends on the feature’s function and the approved project requirements.
There can also be agreed process adjustments within an established manufacturing envelope. Define that envelope in the project documentation instead of expecting every engineer to infer it. When a proposal falls outside the agreed scope or its effect is unclear, escalate it to the responsible design authority before releasing the affected work.
Turn each feedback item into a traceable question
Give each issue an identifier and tie it to a board revision, file set and physical location. Include a reference designator, layer or drawing coordinate as appropriate. A marked image can help, but it should accompany a description precise enough to identify the same feature in the controlled data.
The question should explain the conflict or manufacturing concern and the available options. Ask the supplier to identify which option it recommends and why. If the proposal changes a dimension, show the original and proposed values with units. If it changes a material, state both complete specifications rather than using a broad phrase such as “equivalent laminate.”
Eurocircuits’ data-feedback guide illustrates a structured approach with separate topics and solution choices. It distinguishes recommended, implemented and accepted solutions and notes that an implemented proposal still requires acceptance in that workflow. The transferable lesson is to preserve the decision for each issue, rather than treating a general acknowledgment as approval of every item.
Assign approval according to the affected requirement
Identify the person or role responsible for the function touched by the proposal. A mechanical change may require review by the enclosure designer, while a stackup change may involve signal-integrity and fabrication engineering. A component alternate may require circuit, firmware and procurement input. The project should define how these reviews combine into one release decision.
Purchasing can coordinate the response and obtain price or schedule consequences, but commercial urgency does not answer a technical question. Likewise, a design engineer’s technical acceptance may not authorize an unexpected cost commitment. Keep the required decisions linked while preserving their separate owners.
Use an approval matrix proportionate to the project. The goal is not a long list of signatures for every typographical correction. It is a clear route for changes with electrical, mechanical, reliability, test or commercial implications. If responsibility is unclear, resolve that ambiguity before asking the factory to act.
Evaluate a legend change differently from a hole change
Consider a hypothetical proposal to move a reference-designator label away from a solderable pad. The review might confirm that the new location remains readable and does not confuse polarity identification or service instructions. If the change stays within the agreed legend-adjustment scope, the project can handle it through the defined process and retain the resulting artwork.
Now consider increasing a mounting-hole diameter to suit a manufacturing preference. That change may affect fit, fastening, insulation or the available copper clearance. The reviewer should compare the proposal with the mechanical and electrical requirements. It cannot be classified as harmless merely because the numerical difference looks small.
These examples are illustrative, not universal approval rules. A label can be functionally important, and a particular hole adjustment may already be covered by an approved tolerance. The responsible reviewer should connect the proposed change to the actual requirement rather than assigning significance solely from the feature’s name.
Review manufacturing data before it becomes the released product
Eurocircuits’ pre-production approval explanation describes examining prepared production data before manufacture and obtaining approval where a change may affect functionality. This is a supplier-specific workflow, but it demonstrates why reviewing the files that will actually be used can reveal issues not obvious in an earlier design screenshot.
Ask which dataset incorporates the accepted responses and how it is identified. Compare the affected areas with the approved decisions. If a supplier supplies a marked preview, retain its relationship to the actual production files. A review image without a revision or dataset reference can become detached from the material eventually manufactured.
When new customer data are submitted, identify which earlier files they replace. Do not send a complete archive and a loose corrected file with no precedence instruction. The manufacturing team should receive one unambiguous release package or an explicitly controlled amendment that it has confirmed it can apply.
Keep design sources and manufacturing outputs consistent
An accepted change should not exist only in a factory email if the controlled design source also needs correction. Update the relevant schematic, PCB, BOM or drawing through the project’s change process. Otherwise the next export may restore the original problem, and a different supplier may never see the earlier exception.
Altium’s schematic-to-PCB synchronization documentation describes reviewing and validating proposed engineering changes before execution. Such a tool helps manage consistency between design documents. Its validation should not be confused with approval of the product’s performance or the completeness of the manufacturing release.
After applying the change, regenerate the affected outputs and check them. A successful edit in the design tool does not prove that the exported drill file, placement file or assembly drawing came from the revised source. Record the new package identity and retire superseded files from the active release through normal document control.
State whether approval is permanent or limited to one build
Some decisions are temporary deviations for a defined quantity or pilot run. State the applicable board revision, lot or serial range and the expiration or closure condition. A limited approval should be visible in the work instructions and purchasing record, not buried in a conversation that production cannot retrieve.
For example, an engineering team might approve a specific alternate for an evaluation build while verification continues. That does not authorize its use for all future production. The response should identify the exact alternate, scope of use and evidence required before broader approval. Remaining stock needs a disposition consistent with that restriction.
For a permanent change, identify the revision at which it becomes effective and how existing material will be handled. The team may need to separate old and new stock, revise a fixture or update test instructions. Approval is incomplete if the changed files are clear but the factory does not know which configuration to build.
Close feedback with evidence rather than a status label
A useful closure record contains the accepted option, approving role, date, affected revision and verification evidence. The evidence depends on the issue: it might be a corrected drawing comparison, a first-article measurement or a test result. Avoid marking every issue closed solely because the supplier has acknowledged the message.
Keep rejected options and unresolved assumptions identifiable where they explain the decision. If the factory proposed two different solutions, the record should make clear which one was accepted. A reply that says “option two” is fragile if the options are later reordered; include the option’s identifier and description.
Review the complete issue list before release. Several individually reasonable changes can interact, such as moving a component while also changing a nearby test point. The final dataset and process instructions need a coherent review of the resulting configuration, not only isolated approvals collected at different times.
Connect approval timing to the production plan
Ask which operations are waiting for the response and which can proceed independently. Do not assume the entire order is either moving or stopped. A fabrication decision may block one stage while procurement continues, and an unresolved component choice may prevent a reliable assembly start date.
Use the open issue list when you plan the production timeline. Assign response owners and realistic due dates, and update the schedule when an engineering decision changes the scope. A target ship date should not be maintained by pretending a technical hold has already been resolved.
For low volume assembly, the review effort can be especially visible relative to the production quantity. Clear feedback still matters: a small run is often the source of learning for a larger release. Preserve the decisions so the next build benefits from the work rather than repeating it.
Define the handoff before requesting a turnkey build
In a full turnkey supply arrangement, identify the technical contact, commercial contact and release authority before the supplier begins its review. Agree how questions, revised files and approvals will be exchanged. The supplier needs a reliable path to a decision, and the customer needs a record of what will actually be built.
Send the current file package, known open issues and any limits on permitted changes. Ask for a final issue disposition and dataset reference before the affected production stage is released. This makes DFM feedback a controlled part of design transfer: a specific concern leads to a specific decision, implemented in a specific revision and checked with evidence appropriate to the change.