Engineering Change Control for PCB Designs

An engineering change is any modification to a released design, and the way it is controlled decides whether it corrects a problem or creates one. The discipline costs a few minutes per change and prevents the situation in which two versions of the same board are in circulation without anyone knowing which is which.

What Counts as a Change

Anything that alters the fabrication data or the bill of materials is a change: a move of a component, a change of a value, a revised silkscreen, an added test point, a change of laminate. Cosmetic changes to the drawing that do not affect the data are usually excluded, although they should still be recorded so that the drawing history is complete.

The distinction matters because the change control process is what triggers the re-verification. A change that is treated as cosmetic and left uncontrolled is the one that later turns out to have moved a net. Our design release checklist lists the items that a change review should cover.

Why Changes Are Expensive Later

The cost of a change rises by roughly an order of magnitude at each stage of the program. A change on the drawing costs the engineering time. The same change after the fabrication data is released costs the data preparation. After the panels are made, it costs the panels and the schedule. After the product has shipped it may also cost a recall.

That progression is the reason for reviewing the design thoroughly before release rather than relying on the prototyping cycle to find problems. The prototype is an expensive place to discover a change that a review would have caught.

The Change Request and Its Content

A change request should state what is being changed, why, which documents are affected, and what the effect is on cost and schedule. The reason is the most important field, because it is what allows a future reader to understand why a design looks the way it does.

The documents affected are not always obvious. A change to a component may also affect the assembly drawing, the test programme, the conformity documentation and the packaging. Listing them at the time of the change is easier than discovering them later.

Impact Analysis

Impact analysis asks what else the change touches. Moving a component changes the routing, which changes the impedance of the traces that were rerouted, which may change a signal integrity result. Changing a material changes the dielectric constant, which changes the impedance of every controlled trace on the board.

The analysis should therefore be driven by the interfaces rather than by the change itself. A short list of questions, applied consistently, catches most of the second-order effects. Our release checklist is structured to support that.

<img src="https://www.gopcba.com/wp-content/uploads/2026/06/DWDM波分复用设备-PCBA.jpg" alt="Revision marking on a PCB fabrication data set” />

Version Control for Board Data

Fabrication data should be stored in a version control system rather than in a folder of dated archives, because the version history is what allows a change to be traced. Naming a file with a date is not version control, since the date says nothing about what changed or whether the files are consistent with each other.

Every archive should contain one consistent set: the artwork, the drill data, the stack drawing and the notes. Mixing a drawing from one revision with artwork from another is the failure that version control is intended to prevent.

The Change Order and the Shop

A change that affects fabrication has to reach the shop as a new revision, with the superseded revision explicitly withdrawn. Sending a new file without withdrawing the old one leaves the shop to decide which is current, and the decision may be made by whoever opens the email first.

The same applies to the assembly documentation. A board that is built to one revision and assembled to another is difficult to detect and expensive to correct.

Configuration and Effectivity

Where a change is made part-way through a production run, the point at which it takes effect has to be defined. A change that is effective from a serial number onward allows the earlier units to remain as they are, while a change that is effective immediately requires the earlier units to be reworked.

The effectivity decision is a commercial one as much as an engineering one, and it should be made explicitly rather than left to the shop’s interpretation of the revision note.

Records and Traceability

The record of a change should link the reason, the analysis, the approval and the resulting data, so that a board produced two years ago can be explained. Without that link, an investigation into a field failure has to reconstruct the design history from memory.

The record also supports the next change. A designer who can see why a value was chosen is less likely to change it back, and the loop of undoing and redoing is one of the quiet costs of poor documentation.

Process Control and Verification

Reviewing the design before the data is released is far cheaper than correcting it after the panel is in the tank, because every step downstream inherits the decision made at the front end. Where a value sits close to a process limit, the drawing should say so, since the shop can then open the process window rather than working to a nominal figure that carries no tolerance.

The measurements that matter are the repeatable ones: conductor width and spacing, annular ring, finished hole size, plating thickness and surface finish are all verifiable on a coupon that travels with the panel. Documenting the assumption is part of the design work, and a short note on the drawing prevents a question that would otherwise arrive a day later and cost a day of schedule.

Where a value sits close to a process limit, the drawing should say so, since the shop can then open the process window rather than working to a nominal figure that carries no tolerance. Running a first article through the same checks as the production panel confirms that the two agree, and that comparison is the cheapest form of process control available at prototype stage.

Documenting the assumption is part of the design work, and a short note on the drawing prevents a question that would otherwise arrive a day later and cost a day of schedule. A stack-up that is drawn rather than described removes most of the ambiguity from a quotation, and it lets the fabricator price the board against the dielectric and copper weights that will actually be used.

Related reading: our fabrication notes, board quality and design release notes cover the same ground.

FAQ

Who should approve a change? Someone who owns the product rather than the change itself, which in practice usually means the design authority together with whoever is accountable for cost and schedule. Approval by the person who requested the change is not approval.

Can a change be made without a new revision? It can be made in the working files, but it should not be released without a new revision. A revision number is the only mechanism by which the shop, the assembler and the test house can agree on which version they are working from.

How does gopcb handle a change after release? We treat any change to the fabrication data as a new revision, quote the effect on cost and schedule before proceeding, and confirm that the superseded data has been withdrawn. We also report any change that affects a parameter we have already verified, such as an impedance target.