[{"data":1,"prerenderedAt":64},["ShallowReactive",2],{"blog-pcba-engineering-change-order-en":3},{"title":4,"description":5,"date":6,"lastUpdated":6,"category":7,"image":8,"readingTime":9,"wordCount":10,"timeRequired":11,"htmlContent":12,"faq":13,"tags":29,"slug":33,"sourceLocale":34,"availableLocales":35,"jsonld":40},"PCB Assembly Engineering Change Orders: A Release Checklist","Control PCB assembly changes with approved baselines, effectivity, supplier acknowledgement and work-in-process disposition, then verify the new release.","2026-10-28","assembly",null,13,2446,"PT13M","\u003Cp>A PCB assembly engineering change order (ECO) should identify the approved change, the exact production baseline it modifies, and where the change takes effect. Before releasing it to a supplier, resolve the affected files and materials, open orders, inventory, work in process (WIP), verification requirements, and shipment traceability. A revised file alone is not a complete change release.\u003C/p>\n\u003Cp>The practical objective is to make one question answerable for every affected assembly: \u003Cstrong>Was it built to the authorized old baseline or the authorized new baseline, and what evidence supports that answer?\u003C/strong>\u003C/p>\n\u003Cp>This checklist addresses change cut-in after a design or process has been proposed. For preparing manufacturing inputs, see \u003Ca href=\"/en/blog/gerber-data-preparation-pcb-manufacturing-quality/\">Gerber data preparation\u003C/a> and the \u003Ca href=\"/en/blog/pick-and-place-file-checklist/\">pick-and-place file checklist\u003C/a>. Those guides concern file quality; they do not replace the order, inventory, WIP, and authorization decisions required for an ECO.\u003C/p>\n\u003Ch2>Start with the terminology, then define your workflow\u003C/h2>\n\u003Cp>Organizations use change terminology differently. A common arrangement is:\u003C/p>\n\u003Cul>\n\u003Cli>\u003Cstrong>Engineering change request (ECR):\u003C/strong> Proposes a change and starts its technical and business assessment.\u003C/li>\n\u003Cli>\u003Cstrong>Engineering change order (ECO):\u003C/strong> Records the approved change and authorizes implementation under defined conditions.\u003C/li>\n\u003Cli>\u003Cstrong>Engineering change notification or notice (ECN):\u003C/strong> Communicates a change or its status to affected parties.\u003C/li>\n\u003Cli>\u003Cstrong>Product change notification (PCN):\u003C/strong> A notice from a manufacturer about a product or process change that may affect supplied parts.\u003C/li>\n\u003C/ul>\n\u003Cp>Do not assume another company uses these labels in exactly the same way. Define which document authorizes implementation, who can approve it, and what supplier acknowledgement means. An ECN may communicate an approval, but receipt of a notification is not necessarily authorization to change an assembly.\u003C/p>\n\u003Cp>A component manufacturer’s PCN is also not automatic approval of the finished product. Texas Instruments’ \u003Cstrong>Product Change Notification (PCN)\u003C/strong> information describes the change, affected product, reason, potential impact, and implementation timing. The product owner still needs to determine whether the affected component is used, assess the assembly impact, and authorize any necessary response.\u003C/p>\n\u003Ch2>Establish the old and new baselines\u003C/h2>\n\u003Cp>An ECO controls a transition between two identifiable states. Begin by recording the released product or assembly part number, the current baseline, and the proposed new baseline. Then list the exact documents and files that make up each state.\u003C/p>\n\u003Cp>Independent documents do \u003Cstrong>not\u003C/strong> need identical revision labels. A board drawing at one revision, a BOM at another, and firmware at a third can form a valid baseline if their identities and compatibility are explicitly recorded. Matching labels are not proof that the documents belong together.\u003C/p>\n\u003Cp>For each relevant item, capture the document or file identifier, revision or version, and enough information to distinguish the released copy from a similarly named draft. A checksum or controlled repository reference can help where the parties use one. Record the approval date and owner as well as any supplier-specific identifiers needed to locate the corresponding manufacturing data.\u003C/p>\n\u003Cp>Separate the list into:\u003C/p>\n\u003Col>\n\u003Cli>\u003Cstrong>Changed artifacts:\u003C/strong> Replaced, revised, added, or withdrawn by the ECO.\u003C/li>\n\u003Cli>\u003Cstrong>Unchanged but linked artifacts:\u003C/strong> Still valid for the new build and explicitly included in its baseline.\u003C/li>\n\u003Cli>\u003Cstrong>Not applicable artifacts:\u003C/strong> Considered and excluded, with a reason where useful.\u003C/li>\n\u003C/ol>\n\u003Cp>This distinction matters. If a BOM changes but the placement file does not, the release should say that the existing placement file remains applicable—not leave the assembler to guess.\u003C/p>\n\u003Ch3>PCB fabrication data\u003C/h3>\n\u003Cp>Consider the Gerber artwork, Gerber job file where used, drill and routing data, fabrication drawing, stackup, finish, board dimensions, and fabrication notes. A layout change can affect a fabrication drawing or panelization instructions even when the assembly BOM is unchanged.\u003C/p>\n\u003Cp>Ucamco’s \u003Cstrong>Gerber Job Format Specification, version 2020.08\u003C/strong>, describes a way to transfer PCB characteristics and fabrication attributes. It also states that missing information has no format defaults. If a job file is partial, do not infer unspecified requirements from it. Resolve missing requirements through the controlled release and supplier agreement; a job file does not authorize a BOM change or establish commercial terms.\u003C/p>\n\u003Ch3>Assembly, programming, and test data\u003C/h3>\n\u003Cp>Review the BOM and approved vendor list (AVL), centroid or component placement list (CPL), assembly drawing, orientation information, stencil data, and inspection requirements. Also consider programming files and instructions, firmware compatibility, test fixtures, test software, limits, and revision identification.\u003C/p>\n\u003Cp>A component substitution can leave coordinates unchanged while changing polarity interpretation, footprint compatibility, soldering requirements, or test behavior. Conversely, a firmware change may require no new placement data but may require a different programming image and test procedure. For procurement-specific checks, use the \u003Ca href=\"/en/blog/bom-error-checking-component-procurement/\">BOM error-checking guide\u003C/a>.\u003C/p>\n\u003Ch2>Assess the impact before authorizing cut-in\u003C/h2>\n\u003Cp>The product owner should assign the impact review to people with authority over the relevant design, quality, purchasing, and manufacturing decisions. The supplier should identify implementation constraints and report affected orders, material, and WIP within its agreed scope. Neither side should assume that the other has approved an undocumented change.\u003C/p>\n\u003Cp>Assess, as applicable:\u003C/p>\n\u003Cul>\n\u003Cli>\u003Cstrong>Electrical and functional:\u003C/strong> Ratings, interfaces, firmware compatibility, configuration, test coverage, and acceptance limits.\u003C/li>\n\u003Cli>\u003Cstrong>Mechanical and manufacturing:\u003C/strong> Footprint, orientation, clearance, assembly sequence, stencil needs, board fabrication, and fixture compatibility.\u003C/li>\n\u003Cli>\u003Cstrong>Quality and reliability:\u003C/strong> Inspection criteria, qualification needs, environmental or lifetime implications, and applicable product requirements.\u003C/li>\n\u003Cli>\u003Cstrong>Supply and traceability:\u003C/strong> AVL status, manufacturer part numbers, affected lots, existing stock, and the ability to distinguish old and new builds.\u003C/li>\n\u003Cli>\u003Cstrong>Commercial and schedule:\u003C/strong> Material exposure, rework, replacement quantities, price, and delivery effects.\u003C/li>\n\u003C/ul>\n\u003Cp>An impact estimate is not itself approval. Record any revised price, delivery date, cancellation charge, or other commercial treatment only when the parties with authority have agreed to it. If a PCN’s effect is unclear, hold the affected decision for review rather than treating the component manufacturer’s stated implementation date as your own product cut-in.\u003C/p>\n\u003Ch2>Decision table: choose the disposition, not just the revision\u003C/h2>\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Situation\u003C/th>\n\u003Cth>Decision needed\u003C/th>\n\u003Cth>Release control\u003C/th>\n\u003C/tr>\n\u003C/thead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>A changed file is ready, but technical approval is pending\u003C/td>\n\u003Ctd>Whether affected production must be held\u003C/td>\n\u003Ctd>Identify affected orders and prevent use of the draft as a released baseline\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>New BOM is approved; CPL is unchanged\u003C/td>\n\u003Ctd>Whether the existing CPL remains compatible\u003C/td>\n\u003Ctd>Link the exact CPL version to the new baseline and record the compatibility review\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>A component PCN affects an approved part\u003C/td>\n\u003Ctd>Whether the notified change is acceptable for this product\u003C/td>\n\u003Ctd>Map affected part numbers and lots, complete the product-owner assessment, and document the decision\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Old stock exists at the assembler or another supplier\u003C/td>\n\u003Ctd>Use, segregate, return, scrap, or otherwise disposition it\u003C/td>\n\u003Ctd>Record quantities and locations; do not substitute or consume material without authorization\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Assemblies are in WIP at cut-in\u003C/td>\n\u003Ctd>Continue old, convert, rework, hold, or scrap\u003C/td>\n\u003Ctd>Identify the affected units or lots and the approved disposition for each\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>First changed production is planned\u003C/td>\n\u003Ctd>What inspection, test, or first-build evidence is required\u003C/td>\n\u003Ctd>Agree on the verification plan and acceptance authority before release\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Price or delivery changes are proposed\u003C/td>\n\u003Ctd>Whether the commercial change is accepted\u003C/td>\n\u003Ctd>Obtain an authorized purchase-order change or other agreed written approval\u003C/td>\n\u003C/tr>\n\u003C/tbody>\u003C/table>\n\u003Cp>If a decision is unresolved, record the owner, affected quantity, and hold condition. Do not convert an unresolved field into permission to proceed.\u003C/p>\n\u003Ch2>Set effectivity and acknowledge the release\u003C/h2>\n\u003Cp>Effectivity specifies \u003Cstrong>where the approved change begins\u003C/strong>. Depending on the product and the available traceability, the parties might agree on a serial-number range, manufacturing lot, purchase order, or date. A date alone can be ambiguous when a build spans several days or multiple orders. If a date is used, define the event it refers to—for example, release to assembly rather than shipment.\u003C/p>\n\u003Cp>Document:\u003C/p>\n\u003Cul>\n\u003Cli>The old and new baseline identifiers.\u003C/li>\n\u003Cli>The effectivity method and exact boundary.\u003C/li>\n\u003Cli>Which open orders, lots, or serial numbers are affected.\u003C/li>\n\u003Cli>Whether mixed baselines are permitted within an order or shipment.\u003C/li>\n\u003Cli>How units without assigned serial numbers will be controlled until serial assignment.\u003C/li>\n\u003Cli>Any exceptions and who approved them.\u003C/li>\n\u003C/ul>\n\u003Cp>Send the controlled release to every affected party, not only the purchasing contact. Request acknowledgement from the assembler and, where applicable, the board fabricator, programming or test provider, and other relevant suppliers. Acknowledgement should identify the ECO and baseline received, the affected work understood, and any conflicts or inability to implement.\u003C/p>\n\u003Cp>Supplier acknowledgement confirms communication and feasibility as stated; it does not replace the product owner’s design approval or an authorized commercial agreement. Likewise, product-owner approval does not prove that every supplier has received the correct files.\u003C/p>\n\u003Ch2>Control inventory and WIP separately\u003C/h2>\n\u003Cp>Inventory and WIP can be affected in different ways. A new build may be approved while old components remain in stores, or a changed component may already be installed on partially assembled boards.\u003C/p>\n\u003Cp>For material, identify the manufacturer part number, approved source, quantity, lot or other traceability where available, location, and status. Address customer-owned stock, supplier-owned stock, material at subcontractors, and stock whose status or lot identity is uncertain. Segregate or otherwise control material until its disposition is authorized.\u003C/p>\n\u003Cp>For WIP, establish a snapshot by order, lot or unit identifier, quantity, production stage, and baseline last applied. Agree whether work must stop and what can happen next. Possible dispositions include completing to the old baseline, converting to the new baseline under approved instructions, reworking, scrapping, or continuing to hold.\u003C/p>\n\u003Cp>A conversion instruction should define the work, inspection and retest requirements, and how the resulting unit is identified. If units are scrapped, account for their removal and separately approve any replacement quantity. Do not assume the original purchase order automatically covers replacements or rework.\u003C/p>\n\u003Ch3>Illustrative cut-in: 100 planned assemblies\u003C/h3>\n\u003Cp>This is an illustrative allocation, not a customer case:\u003C/p>\n\u003Cul>\n\u003Cli>\u003Cstrong>40 completed\u003C/strong> to the old baseline.\u003C/li>\n\u003Cli>\u003Cstrong>20 in WIP\u003C/strong>, placed on hold pending disposition.\u003C/li>\n\u003Cli>\u003Cstrong>40 not started\u003C/strong>, eligible for the new baseline only after all required technical, supplier, and commercial approvals.\u003C/li>\n\u003C/ul>\n\u003Cp>The planned total remains \u003Cstrong>40 + 20 + 40 = 100 assemblies\u003C/strong>.\u003C/p>\n\u003Cp>The 20 held units do not become new-baseline units merely because the ECO is approved. Their disposition is still unknown: an authorized decision may permit old-baseline completion, conversion, rework, or another outcome. Similarly, the 40 not started are eligible for the new baseline only when the release conditions are met; eligibility is not evidence that they were built.\u003C/p>\n\u003Cp>Record the actual serial numbers or other agreed identifiers associated with each resulting baseline. If serial numbers are assigned later, control the interim lots and link them to serial numbers at assignment. The 40 completed old-baseline units are not retroactively changed by the ECO, and their completion alone does not establish shipment acceptance.\u003C/p>\n\u003Ch2>Verify the first changed build and retain evidence\u003C/h2>\n\u003Cp>Define verification according to the change and product requirements. It may include checking component identity and orientation, inspecting affected solder joints, confirming firmware version, running specified functional tests, or verifying drawing and fabrication attributes. Identify the sample or units to be checked, the acceptance criteria, the responsible party, and the required records before production proceeds.\u003C/p>\n\u003Cp>A first article inspection may be appropriate if the product owner and supplier agree on its scope. It is not a universal guarantee or an automatic requirement for every ECO. The \u003Ca href=\"/en/blog/pcb-first-article-inspection/\">PCB first article inspection guide\u003C/a> explains how to define that activity when it is needed.\u003C/p>\n\u003Cp>Maintain an evidence ledger that links the implementation back to the authorization. Depending on the agreed scope, entries can include:\u003C/p>\n\u003Cul>\n\u003Cli>Approved ECR/ECO and affected baseline list.\u003C/li>\n\u003Cli>Supplier acknowledgements and open exceptions.\u003C/li>\n\u003Cli>Inventory and WIP snapshots with approved dispositions.\u003C/li>\n\u003Cli>Verification results, deviations, and acceptance decisions.\u003C/li>\n\u003Cli>Lot or serial associations for old and new builds.\u003C/li>\n\u003Cli>Shipment records showing the applicable baseline or agreed traceability reference.\u003C/li>\n\u003Cli>Closure approval and unresolved follow-up actions.\u003C/li>\n\u003C/ul>\n\u003Cp>A failed or incomplete verification result should lead to the agreed containment and decision process. Closing the ECO should not erase the history of an exception or imply that unverified units passed.\u003C/p>\n\u003Ch2>What to put in the release or RFQ\u003C/h2>\n\u003Cp>Whether the change concerns an existing order or a new quotation, send a controlled package rather than a collection of loosely named attachments. Include:\u003C/p>\n\u003Col>\n\u003Cli>\u003Cstrong>Product and order identification:\u003C/strong> Assembly part number, affected purchase orders, quantities, and delivery destinations or shipment requirements as applicable.\u003C/li>\n\u003Cli>\u003Cstrong>Change identification:\u003C/strong> ECR/ECO identifier, revision, description, reason, approvers, and authorization status.\u003C/li>\n\u003Cli>\u003Cstrong>Baseline matrix:\u003C/strong> Old and new file identifiers, versions, changed versus unchanged status, and controlled file locations.\u003C/li>\n\u003Cli>\u003Cstrong>Effectivity:\u003C/strong> Agreed serial, lot, order, or date boundary; treatment of mixed baselines and units awaiting identification.\u003C/li>\n\u003Cli>\u003Cstrong>Material direction:\u003C/strong> BOM/AVL changes, approved alternatives, affected manufacturer part numbers, inventory ownership, and disposition instructions.\u003C/li>\n\u003Cli>\u003Cstrong>Production direction:\u003C/strong> WIP hold, permitted operations, conversion or rework instructions, and escalation contacts.\u003C/li>\n\u003Cli>\u003Cstrong>Verification and records:\u003C/strong> Inspection and test requirements, acceptance criteria, evidence to retain or supply, and required traceability.\u003C/li>\n\u003Cli>\u003Cstrong>Commercial response:\u003C/strong> Requested assessment of price, schedule, inventory exposure, and order changes, with approval still required before those terms apply.\u003C/li>\n\u003C/ol>\n\u003Cp>For an existing job, reference the original purchase order and state whether production is to be held while the supplier assesses the change. For a new RFQ, state the baseline to be quoted and flag any unresolved decisions that could alter the quotation. The \u003Ca href=\"/en/blog/pcb-assembly-quote/\">PCB assembly quote guide\u003C/a> helps compare quotation scope; it does not determine ECO effectivity.\u003C/p>\n\u003Cp>When discussing \u003Ca href=\"/en/products/turnkey-assembly/\">turnkey assembly\u003C/a> with HILPCB, provide the applicable controlled package and agree which procurement, assembly, inspection, programming, test, and traceability activities are included for the project. Use the \u003Ca href=\"/en/quote/\">quote request\u003C/a> for a defined package, or \u003Ca href=\"/en/contact/\">contact HILPCB\u003C/a> to clarify an affected order or proposed change. Any capabilities, records, price, and timing remain subject to the project agreement.\u003C/p>\n\u003Cdiv data-component=\"BlogQuickQuoteInline\">\u003C/div>\n\u003C!-- faq:start -->\n\u003Ch2>Frequently Asked Questions\u003C/h2>\n\u003Ch3>Is an ECO required for every PCB assembly change?\u003C/h3>\n\u003Cp>The organization’s controlled process determines when an ECO is required. Any change that affects the released product or production process still needs an appropriate authorization, implementation, and traceability method.\u003C/p>\n\u003Ch3>Do all manufacturing documents need the same revision letter?\u003C/h3>\n\u003Cp>No. Independent documents can have different revision labels. The release must identify the exact compatible versions that together form each approved baseline.\u003C/p>\n\u003Ch3>Does a component PCN automatically approve the changed part?\u003C/h3>\n\u003Cp>No. A PCN communicates the manufacturer’s change. The product owner must assess its effect and document any required acceptance or change to the assembly baseline.\u003C/p>\n\u003Ch3>Can WIP move to the new baseline as soon as the ECO is approved?\u003C/h3>\n\u003Cp>Not automatically. Identify the affected units and approve their disposition, including any conversion, inspection, and retest instructions, before work resumes.\u003C/p>\n\u003Ch3>Is first article inspection mandatory for every ECO?\u003C/h3>\n\u003Cp>No universal rule makes it mandatory for every change. Agree on verification and acceptance requirements according to the change, product requirements, and project scope.\u003C/p>\n\u003C!-- faq:end -->\n\u003Csection class=\"related-links\" aria-label=\"Related\">\u003Ch3>Related links\u003C/h3>\u003Cul>\u003Cli>\u003Ca href=\"/en/blog/gerber-data-preparation-pcb-manufacturing-quality/\">Gerber Data Preparation for Reliable PCB Fabrication\u003C/a>\u003C/li>\u003Cli>\u003Ca href=\"/en/blog/pick-and-place-file-checklist/\">Pick-and-Place Files: CPL Fields, Rotation and BOM Matching Checks\u003C/a>\u003C/li>\u003Cli>\u003Ca href=\"/en/blog/bom-error-checking-component-procurement/\">BOM error checking for component procurement: MPN matching, aliases, and lifecycle triage\u003C/a>\u003C/li>\u003Cli>\u003Ca href=\"/en/blog/pcb-first-article-inspection/\">PCB First Article Inspection: What to Check Before Production\u003C/a>\u003C/li>\u003Cli>\u003Ca href=\"/en/blog/pcb-assembly-quote/\">PCB Assembly Quote Guide: Files, Cost and Comparison\u003C/a>\u003C/li>\u003Cli>\u003Ca href=\"/en/products/turnkey-assembly/\">turnkey assembly\u003C/a>\u003C/li>\u003Cli>\u003Ca href=\"/en/quote/\">quote request\u003C/a>\u003C/li>\u003C/ul>\u003C/section>",[14,17,20,23,26],{"question":15,"answer":16,"answerText":16},"Is an ECO required for every PCB assembly change?","The organization’s controlled process determines when an ECO is required. Any change that affects the released product or production process still needs an appropriate authorization, implementation, and traceability method.",{"question":18,"answer":19,"answerText":19},"Do all manufacturing documents need the same revision letter?","No. Independent documents can have different revision labels. The release must identify the exact compatible versions that together form each approved baseline.",{"question":21,"answer":22,"answerText":22},"Does a component PCN automatically approve the changed part?","No. A PCN communicates the manufacturer’s change. The product owner must assess its effect and document any required acceptance or change to the assembly baseline.",{"question":24,"answer":25,"answerText":25},"Can WIP move to the new baseline as soon as the ECO is approved?","Not automatically. Identify the affected units and approve their disposition, including any conversion, inspection, and retest instructions, before work resumes.",{"question":27,"answer":28,"answerText":28},"Is first article inspection mandatory for every ECO?","No universal rule makes it mandatory for every change. Agree on verification and acceptance requirements according to the change, product requirements, and project scope.",[30,31,32],"engineering change order","PCB assembly","change control","pcba-engineering-change-order","en",[34,36,37,38,39],"de","cn","fr","ru",{"blog":41,"breadcrumb":50},{"@context":42,"@type":43,"headline":4,"description":5,"url":44,"datePublished":6,"dateModified":6,"timeRequired":11,"keywords":45,"articleSection":7,"author":46,"publisher":49},"https://schema.org","BlogPosting","https://hilpcb.com/en/blog/pcba-engineering-change-order/","engineering change order, PCB assembly, change control",{"@type":47,"name":48},"Organization","HILPCB",{"@type":47,"name":48},{"@context":42,"@type":51,"itemListElement":52},"BreadcrumbList",[53,58,62],{"@type":54,"position":55,"name":56,"item":57},"ListItem",1,"Home","https://hilpcb.com/",{"@type":54,"position":59,"name":60,"item":61},2,"Blog","https://hilpcb.com/en/blog/",{"@type":54,"position":63,"name":33,"item":44},3,1794062104826]