An engineering change order can be technically correct and still leave production uncertain. The design team may have released a new connector while purchasing holds the old part, work in process carries the previous revision, and the test fixture still supports the original configuration.
Managing PCB revisions requires a decision about where that change takes effect. The change record should connect engineering intent with materials, assembly instructions, test requirements, and the identity of the finished product. Otherwise, a revised drawing may coexist with an undefined mix of old and new assemblies.
Versa’s engineering change order overview introduces the change process. This article focuses on the manufacturing cut-in: how the OEM and its partner decide which configuration will be built, accepted, and shipped.
Make the engineering change order scope explicit
Describe the reason for the change and identify every affected item. A component substitution may affect the bill of materials alone, or it may also change footprints, mechanical clearance, firmware behavior, and testing. The impact review should determine that scope instead of assuming it from the size of the edit.
List the old and new revision identifiers and the files that control the revised build. Include related assemblies when the board is part of a box build. A cable change can affect the connector on the board and the routing inside the enclosure even when the circuit remains unchanged.
Name the person authorized to approve the engineering decision. Separate that authority from the purchasing decision to commit material or the operations decision to start the next build. Those actions may be related, but their responsibilities are different.
Locate the product across manufacturing stages
Ask the manufacturer for a status view before selecting a cut-in. Include uncommitted requirements, open purchase orders, received inventory, work in process, finished assemblies, and any product awaiting disposition. A count of finished boards alone can miss much of the change’s practical impact.
Identify which items can use the new configuration without further work. Others may need evaluation, rework, a separate release decision, or continued use under the previous revision. The OEM should provide the disposition rather than asking the manufacturer to infer design acceptability.
Materials that are already committed deserve an explicit purchasing discussion. A change request does not automatically cancel an order or make an older component returnable. Agree on the handling of those commitments and record any cost implications before assuming the revised build can proceed.
Choose a cut-in rule that operators can follow
A cut-in rule might use a defined build order, lot, serial range, or other traceable boundary. Select one that fits the product’s identification and production controls. An instruction such as “use the new version when possible” leaves too much to local interpretation.
Check that the rule can be applied at every relevant stage. The materials team needs to select the correct parts. Assembly needs the matching instructions. Test needs the matching program and limits. Shipping needs to recognize the configuration that the customer has authorized.
If the OEM permits overlapping revisions, describe their allowable destinations and identification. Do not assume interchangeability because two units look alike. Product requirements may distinguish configurations that are difficult to recognize visually.
Reconcile the revised documentation
Update the files affected by the accepted change and confirm that they agree. Versa’s PCB assembly documentation guide is a useful reference for the underlying package. The change review adds a further question: does every document needed for this build point to the intended revision?
Use an authoritative release location and retain the superseded configuration in a controlled record. The aim is to prevent older information from remaining active while preserving the history needed to understand prior builds.
Engineering data exchange can reduce ambiguity when structured information is used consistently. The IPC-2581 Consortium describes a standardized format for exchanging PCB design and manufacturing data. Whatever format the project uses, the manufacturer still needs to know which release controls the work.
Review instructions that exist outside the core design files, including operator notes, programming references, labels, packaging information, and customer-specific acceptance requirements. These are easy places for an old configuration to survive.
Versa’s HD cable project case study describes moving from a diagnosed harness connectivity problem to a prototype and a pre-production design finalized with the customer’s engineers. It is relevant experience of coordinating an interface change, although the account does not describe a particular ECO system or serial-number cut-in. For your change order, make that missing boundary explicit: which approved design replaces which configuration, and which build may first use it?
Review fixtures, programs, and acceptance criteria
Ask whether the changed board fits the existing fixture and whether the electrical connections remain valid. A mechanically small change can affect test access. A component change can require a review of the measurement or functional limits.
Where firmware is involved, specify the configuration relationship between hardware and software. Record whether older firmware remains acceptable and how the production process will confirm the approved combination. Avoid relying on a filename that does not clearly identify a controlled release.
Decide what evidence is required from the first changed build. It may need a focused inspection, a fit check, or a reviewed test result, depending on the change. Define that requirement in advance so the initial revised assemblies do not arrive without the information needed for disposition.
Give older inventory a recorded disposition
Separate use-as-is, rework, return, and other authorized decisions. State which items the decision covers and who approved it. A direction applying to loose components should not be treated as permission to ship completed units.
For rework, provide controlled instructions and acceptance requirements. Identify any checks that must be repeated and how the revised identity will be recorded. If a reworked unit differs from one built directly to the new revision, determine whether that distinction needs to remain visible in the records.
Discuss service and replacement needs where relevant. Versa’s product lifecycle support services describe the wider relationship after initial production. A change should consider which configurations remain in use and what information future support will need.
Confirm closure at the manufacturing boundary
Before the next build starts, have the responsible teams acknowledge the same cut-in rule and release package. Confirm that open items have dispositions and that required tooling or test updates are available. This is a readiness check, not simply evidence that a change email was sent.
Retain the resulting build identifiers and the evidence reviewed for the first changed units. That record gives future purchasing and engineering teams a way to understand what happened when the design moved into production.
When a revision changes tooling, materials, or recurring work, request a quote adjustment tied to that scope. Versa’s ebook, The Threat To OEM Success: Price and Lead Time, provides a related resource for discussing the purchasing consequences of manufacturing decisions.
