1. Separate Test Changes from Other PCN Categories

Start by obtaining the manufacturer's notice that actually applies to the required part. Record its identifier, revision and affected-code reference before describing the event as a test-method change. A family name or supplier message may locate the document, but the purchasing decision needs its actual coverage and the design owner's requirement.

ADI's PCN17_0003 Rev.A, published in 2018, provides a historical example. It lists test-platform migration separately from die, datasheet and assembly changes. Read the categories independently instead of reducing the whole notice to a new tester label. This old notice does not set a current purchasing deadline.

For the applicable notice, identify what is changing and which supporting document addresses each category. Keep the manufacturer's description separate from the buyer's interpretation of its effect. A change to production testing and a change to an electrical specification are different review questions, even when they appear in the same notice.

Ask the responsible design or quality owner which categories require a disposition for the application. Do not infer that every specification changed, or that none requires attention, from the notice title alone. The requirement record should preserve the unanswered questions until the relevant evidence and reviewer decision are available.

2. Retain Notice and Attachment Revisions

Keep the main notice and each attachment as separately identified documents. Record their revisions and dates, with the manufacturer links or retained source copies. A file downloaded recently can still be a historical revision; the download timestamp should not replace the event and revision information in the document.

The historical ADI notice names its affected-model appendix and revision-history appendix. Its test-correlation attachment carries its own Rev.B identification. Preserve these distinct references. A notice revision and a report revision should not be combined into one unexplained latest-version field, because they can describe different documentation changes.

Read the revision description to establish what was corrected. In this example, the notice records corrections to attachment documentation. That demonstrates why a changed file needs a scope check rather than an automatic conclusion that the entire physical product changed again. Keep the exact wording available for the responsible reviewer.

Maintain a review list showing which document supports each question and which sections have been examined. Mark an unread attachment or missing revision explicitly. A report title cannot fill in the contents of pages that have not been reviewed, and a different attachment should not silently replace the one referenced by the applicable notice.

3. Keep Correlation Evidence within Its Coverage

Identify what the correlation report says it evaluates before using it as supporting evidence. The first two pages of the historical Rev.B attachment describe a production test-platform evaluation and identify the relevant products. They establish the report's stated scope; this checklist does not reproduce the later results or plots.

Reconcile the report's model list with the notice's affected-code appendix. The historical report includes repeated entries in one model block, so row count should not be used to expand coverage. Match the complete ordering codes individually and retain a discrepancy for clarification rather than treating every repeated line as another affected variant.

Keep a manufacturer's platform-correlation record separate from testing of a particular shipment. The former addresses its documented manufacturing evaluation. A seller's report, if supplied, needs its own unit or lot references, method, date and coverage. Neither should be relabelled as the other merely because both contain the word test.

Where further results are needed for the application review, obtain and examine the relevant material through the appropriate owner. Record what has actually been reviewed and what remains missing. Do not turn an unread qualification summary, manufacturer's general assurance or attachment filename into a completed acceptance decision.

4. Record the Required Design-Owner Disposition

Prepare a PCN-specific decision record linking the exact purchase requirement, notice revision, affected codes, change categories and supporting documents. Assign each open question to the responsible technical or quality reviewer. This keeps the manufacturer's change description connected to the buyer's application without treating publication of the notice as approval.

Preserve effectivity and transition information from the notice that applies to the actual inquiry. If a supplier proposes material before or after a transition, request the relevant identification evidence and written offer scope. Do not assign the historical example's dates to present inventory or infer a stock transition from a device's date code alone.

After the reviewer makes a disposition, retain its scope with the released BOM and procurement requirement. Keep unresolved models or conditions outside an unexplained approved grouping. If another notice or revised requirement arrives, identify which earlier decision it affects instead of allowing an old approval reference to cover new circumstances silently.

For an ICULTRA sourcing enquiry, provide the exact code and authorised PCN-review reference, including unresolved notice or attachment questions. Ask the offer to identify the material and available records relevant to the requirement. Manufacturer change review, supplier evidence and commercial confirmation each need their own clearly recorded outcome.

Sources and further reading

ADI PCN17_0003 Rev.A and the first two pages of its Rev.B correlation attachment are historical 2018 examples. They are not a current implementation notice or a seller's lot-test report.