# Supplier Process Change Notification Request Template

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

## Short answer

A fill-in form a supplier completes before changing a process, material, site or tooling, with validation evidence and customer approval lines.

## Category

quality

## Audience

- Supplier quality
- Quality engineer
- Buyer

## Tool

**Kind:** template

**Output:** document

**Fields:**

#### Customer company

**Key:** customer

**Type:** text

**Default:** Acme Precision Ltd

#### Supplier company

**Key:** supplier

**Type:** text

**Default:** Northfield Castings

#### Notification number

**Key:** pcn_no

**Type:** text

**Default:** PCN-2026-014

#### Affected part numbers

**Key:** part_no

**Type:** text

**Default:** HSG-2210, HSG-2214

#### Type of change

**Key:** change_type

**Type:** select

**Options:**

- Raw material
- Manufacturing process
- Manufacturing site
- Tooling or equipment
- Sub-supplier
- Inspection method
- Packaging
- Other

**Default:** Manufacturing process

#### Planned implementation date

**Key:** planned_date

**Type:** date

**Default:** 2027-01-15

#### Description of change

**Key:** description

**Type:** textarea

**Default:** Move final machining of the housing from the older CNC cell to a new five-axis machine, with updated fixtures and program.

#### Reason for change

**Key:** reason

**Type:** textarea

**Default:** Capacity increase and reduced setup count.

#### Expected effect on form, fit, function

**Key:** risk

**Type:** textarea

**Default:** No expected change to form, fit or function. Surface finish and flatness may shift and will be verified.

#### Validation plan

**Key:** validation

**Type:** textarea

**Default:** First article inspection on five pieces, capability study on critical characteristics, and a pilot lot for customer line trial.

**Blocks:**

#### Supplier Process Change Notification {{pcn_no}}

**Body:** Customer: {{customer}}
Supplier: {{supplier}}
Affected part numbers: {{part_no}}
Type of change: {{change_type}}
Planned implementation date: {{planned_date}}

#### 1. Description of the change

**Body:** {{description}}

#### 2. Reason for the change

**Body:** {{reason}}

#### 3. Expected effect on form, fit and function

**Body:** {{risk}}

#### 4. Validation plan and evidence

**Body:** {{validation}}

#### 5. Requirements before shipment

**Body:** The supplier will not ship product made with the change until the customer has approved this notification in writing. Product shipped before approval may be rejected at the supplier's expense.

#### 6. Supporting documents to attach

**Table:**

**Columns:**

- Document
- Provided
- Reference

**Rows:**

**0:** Updated process flow and control plan

**0:** First article inspection report

**0:** Process capability study

**0:** Material certificates or test reports

**0:** Updated PFMEA

**0:** Revised work instruction or drawing

#### 7. Customer disposition

**Table:**

**Columns:**

- Decision
- Conditions
- Date

**Rows:**

**0:** Approved

**0:** Approved with conditions

**0:** More information required

**0:** Rejected

#### Approvals

**Signatures:**

- Supplier quality representative
- Customer supplier quality engineer
- Customer engineering
- Customer purchasing

**Notes:** A starting point for your own change control procedure, not legal advice. Align the lead time and approval requirements with your supplier quality agreement and with customer flow-down requirements such as AS9100, IATF 16949 or contract clauses.

## Content

**Intro:** Most surprise defects begin with a quiet change: a new sub-supplier, a moved machine, a different material grade. This template gives suppliers a structured way to tell you before they change anything, and gives you a record of what you approved.

**Sections:**

#### How to use the template

**Body:** Fill in the customer and supplier names, the notification number, the affected part numbers and the type of change. Describe the change precisely, the reason, and the expected effect on form, fit and function. Add the validation plan the supplier proposes. Export to PDF or Word, send it to the supplier, or have the supplier complete it. The customer disposition table records your decision, and the signatures block gives you an approval trail.

**Bullets:**

- Send it with your supplier quality agreement
- Require notice a set number of days before a change
- Attach evidence, not just promises
- Log each PCN in your ERP supplier record

#### What triggers a notification

**Body:** Typical triggers are a change of raw material or its source, a new or relocated manufacturing site, new tooling or equipment, a change in process parameters or inspection method, a new sub-tier supplier, and packaging changes that affect protection. Aerospace and automotive customers often require formal approval for these under AS9100 and IATF 16949 flow-downs, and electronics standards use similar product change notices. Define the list in your agreement so suppliers do not guess.

#### Approving the change

**Body:** Treat approval as a decision with conditions, not a signature. Ask for first article inspection, capability data on key characteristics and a pilot lot that is traceable. Decide whether to run the pilot on your line before full release. Use the disposition table to record conditions, such as extra inspection on the first three lots. Keep the signed form with the part record so an auditor can see what changed and who approved it.

#### Common mistakes

**Body:** Accepting a one-line description is the most frequent error, because it hides the real risk. Another is approving without any validation evidence. Also avoid indefinite approvals: tie the approval to the described change only, and require a new notification for anything else. If the supplier already shipped changed product, treat it as a nonconformance, open a SCAR, and decide on containment of parts in the field.

**Cta:** Netray can help tie change notifications to part and supplier records in your ERP, so a pending PCN can block or flag receipts until it is approved.

**Faq:**

#### What is the difference between a PCN and an ECN?

**Answer:** A PCN is a notice from a supplier about a change in their product or process. An ECN or ECO is your own engineering change to your design or bill of materials. A supplier PCN can lead to an ECN if the change affects your product definition.

#### How much notice should I require?

**Answer:** Many agreements ask for 60 to 180 days for major changes so you can qualify them, and shorter for minor ones. Choose a period that gives you time to test and to build safety stock if the change is risky.

#### Do I need to approve every change?

**Answer:** Not every change. Classify by risk. Changes that could affect form, fit, function, reliability, regulatory status or traceability need approval. Cosmetic or purely administrative changes may only need notice.

#### Can this be used for electronics components?

**Answer:** Yes, as a generic form. Component makers often send formal product change notices in their own format, in line with industry practice. Use this to record your review and decision for each one.

## Search terms

supplier process change notification template, pcn form supplier, supplier change request form, supplier change notification letter, change of process notification supplier, supplier change control form, supplier site change notice, material change approval form

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