Reference · PCN operations

PCN impact report: a standard structure

Once a supplier notice has been assessed, the result is an impact report: the record of what is affected, what it means, who owns the response, and what was decided. A consistent structure makes that report reviewable before action, auditable afterward, and ready to feed a formal change. This reference lists the sections a PCN impact report should contain and the principles behind them.

Structure and depth vary by organization and quality system — treat this as a checklist of what to include, not a fixed form.

§ Report sections

What a PCN impact report contains

The sections below move from the source notice, through exposure and risk, to the decision and the evidence — everything a reviewer or auditor needs in one place.

Source notice summary: Manufacturer, notice number, notice type, and key dates, with a link to the original document so the source is always one click away.
Affected parts: The affected manufacturer part numbers and any affected date or lot codes.
Change summary: The change category, a plain-language description, the reason for the change, and the form-fit-function impact.
BOM and product exposure: Which BOMs, products, and assemblies are affected, at which revisions, and where known, the quantities involved.
Critical dates: Effective, last-time-buy, last-time-ship, and customer response-by dates — the deadlines that drive urgency.
Risk assessment: Severity, whether qualification is required, and any customer or regulatory impact.
Recommended disposition: The proposed action — accept, last-time buy, qualify, redesign, or no action — and the rationale behind it.
Owners and actions: The assigned owners, required actions, due dates, and current status for each affected product.
Decision and approval: The final disposition, who approved it, and when.
Evidence and attachments: The original notice, qualification data, and relevant correspondence kept with the report.
Audit trail: A record of who changed what and when, so the report can be reconstructed later.

§ Principles

What makes an impact report useful

The structure matters less than these four properties.

Keep it one connected record: Don't scatter the notice, the exposure, and the decision across email, spreadsheets, and folders. They belong together.
Make it reviewable before action: A reviewer should be able to confirm the parts, dates, and exposure from the report alone, without re-reading the source PDF.
Make it audit-ready: Months or years later, the report should still explain what changed, who decided, and why.
Feed it into formal change: When a controlled change is required, the report is the structured input to the PLM change request — not a fresh start.

Producing the report

However you assemble it — a document template, a PLM/QMS record, or dedicated PCN software such as PCNshark, which keeps the notice, exposure, owners, and disposition connected and exportable — the value is in keeping these sections together as one record. See the PCN fields & status codes and roles & RACI references, or browse more in Learn.

Last reviewed 2026-06-29