How to validate PCB engineering change orders

Write the change contract

Identify the parts, nets and mechanical areas that may change. State constraints that must remain fixed, such as connector pinouts or the board outline. Define whether rerouting nearby signals or replacing equivalent components is permitted.

Compare before and after structurally

Inspect netlist changes, part values, footprint assignments and project rules. Separate expected changes from collateral edits. A file-level text diff is useful evidence but can be noisy when an EDA tool rewrites formatting or object order.

Rerun the affected release gates

Check schematic-board parity, ERC, DRC and any functional tests touched by the edit. Regenerate manufacturing outputs if the released design changes. Keep the original and revised artifacts together so the reviewer can reproduce the intended difference.

Practical checklist

1. Define allowed edits.
2. Save the baseline project and reports.
3. Compare connectivity and part identity.
4. Reject unexplained rule changes.
5. Rerun functional and release checks.

A concrete example

Replace a regulator whose footprint differs from the old device.

Evidence to accept

The new device meets the requirements, its mapping is updated and unrelated interfaces are preserved.

Evidence that is insufficient

The schematic value changes while the PCB retains the old footprint mapping.

Common questions

Primary references and further reading

Use the matching device documentation and project configuration when applying this checklist. These references explain the underlying tools and evaluation approaches.

• KiCad PCB editor documentation
• KiCad schematic editor documentation