# PCBA Engineering Change Notice (ECN) Template

> Source: https://netray.co/tools/pcba-engineering-change-notice-template
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

A fill-in ECN for PCB assembly changes covering BOM, fabrication data, process impact, inventory disposition and approvals.

## Category

engineering-plm

## Industry

Electronics Manufacturing

## Audience

- Design engineer
- Process engineer
- Configuration manager

## Tool

**Kind:** template

**Output:** document

**Fields:**

#### Company

**Key:** company

**Type:** text

**Default:** Lakeshore Electronics Assembly

#### ECN number

**Key:** ecn_no

**Type:** text

**Default:** ECN-2026-0142

#### Date raised

**Key:** date

**Type:** date

**Default:** 2026-10-20

#### Assembly part number

**Key:** assy_pn

**Type:** text

**Default:** PCBA-20418

#### Current revision

**Key:** rev_from

**Type:** text

**Default:** C

#### New revision

**Key:** rev_to

**Type:** text

**Default:** D

#### Change type

**Key:** change_type

**Type:** select

**Options:**

- BOM component change
- PCB fabrication data (Gerber / stackup)
- Assembly drawing or process
- Firmware / test program
- Obsolescence replacement

**Default:** Obsolescence replacement

#### Priority

**Key:** priority

**Type:** select

**Options:**

- Routine
- Urgent
- Emergency (line down)

**Default:** Urgent

#### Reason for change

**Key:** reason

**Type:** textarea

**Default:** Manufacturer issued end of life notice for the 0.5 A buck regulator at U7. Last time buy window closes 2026-12-31.

#### Description of change

**Key:** description

**Type:** textarea

**Default:** Replace U7 with the pin compatible alternate from the AVL. No change to footprint. Output inductor L3 value unchanged. Update BOM, pick and place data and assembly drawing note 5.

#### Impact assessment

**Key:** impact

**Type:** textarea

**Default:** Fit and function unchanged per datasheet comparison. Reflow profile unaffected (same MSL 3 rating). Requires a first article inspection and in-circuit test program regression. Customer notification required.

#### Inventory disposition

**Key:** inventory

**Type:** select

**Options:**

- Use up existing stock
- Scrap existing stock
- Rework WIP to new revision
- Return to supplier

**Default:** Use up existing stock

#### Effectivity

**Key:** effectivity

**Type:** text

**Default:** Work orders released after 2026-11-02, or serial number 40500 and above

**Blocks:**

#### Engineering Change Notice {{ecn_no}}

**Body:** Company: {{company}}
Date raised: {{date}}
Assembly: {{assy_pn}}
Revision: {{rev_from}} to {{rev_to}}
Change type: {{change_type}}
Priority: {{priority}}

#### Reason for change

**Body:** {{reason}}

#### Description of change

**Body:** {{description}}

#### Impact assessment

**Body:** {{impact}}

#### Documents affected

**Table:**

**Columns:**

- Document
- Affected
- Revision
- Owner

**Rows:**

**0:** Bill of materials

**0:** Gerber / fabrication data

**0:** Assembly drawing

**0:** Pick and place / centroid file

**0:** Stencil design

**0:** Test program / fixtures

**0:** Work instructions

**0:** Approved vendor list

#### Inventory and effectivity

**Body:** Inventory disposition: {{inventory}}
Effectivity: {{effectivity}}

#### Approvals

**Signatures:**

- Originator
- Design engineering
- Process engineering
- Quality
- Purchasing
- Customer (if required)

**Notes:** This template is a general starting point. Match it to your configuration management procedure and any customer change control clauses, which may require advance notice or approval for form, fit or function changes. Not legal advice.

## Content

**Intro:** Every change to a PCB assembly, from a swapped passive to a new stackup, needs a record that shows what changed, why, who approved it and what happens to stock. This ECN template covers the fields that cause problems when they are skipped.

**Sections:**

#### How to fill it in

**Body:** Start with the assembly number and the revision change, then pick the change type and priority. State the reason in plain terms, such as obsolescence, a yield issue or a customer request. Describe exactly which reference designators and files change. The impact section is where you decide whether a first article, new test program or customer notice is required. Finish with the inventory disposition and effectivity, because that is where manufacturing most often gets surprised.

**Bullets:**

- List reference designators, old part number and new part number.
- State whether the change affects form, fit or function.
- Define effectivity by date, work order or serial number.
- Decide what happens to WIP and stock before approval.

#### Why the documents table matters

**Body:** A PCB assembly is defined by more than the BOM. The pick and place file, stencil, test program, work instruction and approved vendor list all need to move together. If one is missed, the line builds boards that match the old drawing or fail a test that has not been updated. The affected documents table forces the originator to check each one and name an owner, which is the cheapest control against partial implementation.

#### Worked example

**Body:** A buck regulator goes end of life. The originator raises ECN-2026-0142 as an obsolescence replacement, selects an alternate from the AVL and notes that the package and reflow rating are unchanged. Process engineering confirms a first article is required, test engineering confirms a regression run on the in-circuit program, and purchasing sets the last time buy quantity. Existing stock is used up first, with the new revision effective on work orders released after the stated date.

#### Common mistakes

**Body:** A frequent error is writing a vague description such as update BOM, which leaves production guessing. Another is missing customer approval clauses: many contracts require notice before changing a part on a controlled design, even for like for like alternates. Also avoid mixing multiple unrelated changes in one ECN; a single change per notice keeps approvals and rollback clean.

**Cta:** If your BOMs and revisions live in an ERP or PLM, we can help generate and route change documents from the system of record instead of retyping them.

**Faq:**

#### What is the difference between ECN and ECO?

**Answer:** Practice varies by company. Many treat the engineering change order (ECO) as the request and approval record and the engineering change notice (ECN) as the notification that the change is released. Some use the terms interchangeably. Follow your own procedure and be consistent.

#### Do I need a new revision for a part alternate?

**Answer:** If the alternate is already approved on the AVL and the BOM allows it, many companies do not change the assembly revision. If the change affects form, fit or function, or the customer controls the BOM, a new revision and notice is normal.

#### Who should approve a PCBA ECN?

**Answer:** At least design, process and quality engineering, with purchasing for cost and supply impact. Add the customer when contract terms require it. Approval authority should be defined in your configuration management procedure.

#### How should existing inventory be handled?

**Answer:** Decide before release: use up, scrap, rework or return. For safety or reliability changes, stock usually must be quarantined. For cost or supply changes, using existing stock until it runs out is common and is controlled by effectivity.

## Search terms

pcba engineering change notice template, ecn template electronics, pcb ecn form, engineering change order pcb assembly, bom change notice template, eco ecn form electronics manufacturing, component obsolescence change notice, pcb revision change form

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json