Revision Control

A PCB engineering change order (ECO) is the formal authorization to change a released board or assembly and to control when that change becomes effective. A usable ECO identifies every affected item and file, records approval, defines what happens to existing material and work in process, and gives the PCB or PCBA supplier an unambiguous release point.

The first action is not editing a Gerber or BOM. It is stopping the wrong revision from moving forward while the team establishes the current production status. One uncontrolled attachment, verbal approval or missing effectivity date can create mixed board revisions, unusable components, repeated setup cost and field traceability gaps.

What a PCB Engineering Change Order Must Control After Design Release

An ECO controls more than the technical difference between revision A and revision B. It connects six decisions: what changes, why it changes, which item numbers and files are affected, who approves it, when it takes effect, and how existing material is handled. Without that chain, a technically correct edit can still become a manufacturing failure.

For PCB work, the controlled object may include the bare board, assembled PCBA, programmed device, test fixture, enclosure interface or purchasing specification. The ECO should therefore identify the product level and every downstream document that inherits the change. A schematic update alone does not release a new manufacturing build.

Stop the Wrong Build First: Classify the Change by Production Status

Before revising files, establish where the current revision exists. Ask the supplier to confirm whether the job is unquoted, quoted, in engineering review, released to fabrication, in assembly, waiting for test or already shipped. The correct disposition and cost depend on this status.

ECR, ECN and ECO: Which Record Does What?

Organizations use the terms differently, so define them in the project procedure. A common model is: an engineering change request (ECR) proposes and investigates a change; an engineering change notice (ECN) communicates an approved change; and an engineering change order (ECO) authorizes implementation. Some companies use ECN and ECO interchangeably.

The name matters less than the gate. The supplier needs one controlled record that links the approved change to the released data, affected inventory, implementation date or lot, and verification evidence. If your PLM or CAD tool generates an ECO comparison, treat it as input to manufacturing release—not as proof that the supplier received a complete production package.

Required Fields for a PCB ECO That a Supplier Can Execute

The following fields turn a change description into an executable release. They also satisfy the need for a practical PCB engineering change order template without forcing every organization into the same document layout.

Release the Complete Manufacturing Data Package, Not One Edited File

Release a new, internally consistent data set. Do not ask the supplier to combine “the old Gerber except this layer” with an edited drawing from another email. Regenerate or deliberately reapprove the manufacturing package, assign the correct revision, and include a concise change summary.

• Gerber/ODB++ or IPC-2581 data, NC drill files and netlist as applicable;
• fabrication drawing, controlled stackup, material, copper, finish and impedance notes;
• panel, profile, mechanical, keep-out and special-process instructions;
• BOM with manufacturer part numbers, approved alternates and do-not-substitute items;
• CPL/pick-and-place, assembly drawing, polarity/orientation notes and stencil requirements;
• firmware/program files, test procedure, acceptance limits and inspection/report needs;
• a file index or checksum when the release system supports it.

The PCB CAM front-end guide explains why edits must have visible authority. For broader handoff ownership, use the PCB design outsourcing handoff checklist.

Decide What Happens to Bare Boards, Components, WIP and Finished PCBAs

An ECO is incomplete until affected inventory has a decision. First identify physical quantity, lot/date code, location, ownership, production stage and traceability. Then compare rework feasibility, reliability effect, verification cost, schedule impact and the consequence of mixing configurations.

• Use as is: requires documented acceptance that the old configuration still meets the intended requirement.
• Rework: needs an approved instruction, skilled process, inspection criteria and a record linking reworked units to the ECO.
• Scrap or return: should identify responsibility, evidence and commercial treatment.
• Exhaust stock: needs a firm effectivity boundary so old and new revisions cannot be mixed.
• Segregate pending evaluation: protects the build while engineering or quality decides.

Do not assume a copper, drill, component or pad change can be reworked safely. Feasibility must be reviewed against the actual board construction and assembly state.

Require Supplier Acknowledgement Before Production Restarts

A sent email is not supplier acknowledgement. Require the PCB or PCBA supplier to confirm receipt of the ECO, identify the data revision loaded into its system, state the affected order/lot, report current WIP and inventory, and confirm that superseded files are blocked from use.

The acknowledgement should also state feasibility questions, new tooling or NRE, price change, lead-time impact, material availability, required deviation and the planned first build under the new revision. If an external process or component supplier is affected, confirm how that party receives and controls the change.

Validate the Changed Revision Before Full Release

Verification should match the change. A geometry or stackup change may need refreshed DFM, impedance review, coupon/microsection or dimensional checks. A component, footprint or assembly change may need first-article inspection, AOI/X-ray criteria, programming confirmation and functional test. A material or process change may require comparison against the agreed performance or qualification requirement.

Define the sample, method, acceptance limit, record and approval owner before the build. The PCB DFM checklist helps structure manufacturability review, while the PCB testing guide helps separate bare-board and PCBA verification choices.

Common PCB ECO Failures and the Controls That Prevent Them

What to Send EBest Circuit for an ECO Manufacturing Review

For a bare PCB change, send the ECO or change summary, old/new part and revision, complete Gerber/ODB++ set, drill data, fabrication drawing, stackup, material/finish requirements, quantity, affected PO or inventory and target release date. State whether fabrication has started.

For PCBA, add the BOM, CPL, assembly drawing, approved alternates, programming files, test method and current status of components, bare boards, WIP and finished units. Identify any safety, regulatory, form/fit/function or customer-approval effect. EBest Circuit will confirm project-specific questions, feasibility and quotation from the released package; no universal rework or timing promise should be assumed before review.

FAQ About PCB Engineering Change Orders

What is a PCB engineering change order?

It is the controlled authorization to implement a change to a released PCB or PCBA design, including affected data, approvals, effectivity, inventory disposition and verification.

What is the difference between an ECR, ECN and ECO?

An ECR commonly proposes a change, an ECN communicates it and an ECO authorizes implementation. Company definitions vary, so document the gate and authority.

When should an ECO become effective?

Use an unambiguous boundary such as a purchase order, lot, serial number, approved date or first controlled build—not “as soon as possible.”

Does a new Gerber file count as an ECO?

No. The new file is one affected artifact. The ECO also controls related drawings, drill data, BOM/CPL, inventory, approvals and validation.

Can old PCB inventory be used after a change?

Only after authorized review confirms it still meets requirements and defines traceable use-as-is or exhaust-stock effectivity.

What should a PCB supplier acknowledge?

Receipt, loaded revision, affected order and inventory, feasibility, cost/lead-time impact, obsolete-file control, effectivity and first-build verification.

How should an ECO be closed?

Close it after the new release is implemented, affected material is dispositioned, required verification passes, records are linked and responsible approvers accept the result.