Unapproved manufacturer risk begins when the exact maker, full MPN, source evidence, technical approval, or effectivity cannot be confirmed for the intended PCBA application.
An unapproved manufacturer state is not proof that a component is defective. It means the project cannot yet show that the exact manufacturer and MPN, supporting evidence, approval authority and effectivity match the intended PCBA decision.
Two parts with the same value or broad package description can differ in electrical limits, thermal performance, package details, lifecycle, process response, traceability or system behaviour. Its significance depends on the actual circuit, environment, manufacturing route and validation scope.
At this gate, the review should therefore identify the decision object first, then trace technical, sourcing, process and test mechanisms. Containment should protect unrelated work while holding the affected material or build release.
Before comparing parts, freeze the circuit position, application conditions and build scope that make the decision meaningful. Evidence for one assembly, environment or revision should not be extended to another without an authorised review of the affected differences.
Use application conditions to bound every comparison. Voltage, current, temperature, switching rate, environment, lifetime expectation and software interaction may determine which datasheet differences matter. The review should name the relevant conditions and leave unrelated parameters outside the decision. This produces a focused validation plan and avoids both blanket acceptance and unnecessary full-system testing.
Identify the Exact Manufacturer and Full Part Number
Identify the proposed manufacturer and full ordering code before evaluating an alternate. Compare the applicable package option, suffix, source documents, and approval-list state with the intended part. A shorthand cross-reference or a matching nominal value can omit distinctions that the application’s reviewer needs. Keep the original and proposed identities visible throughout the comparison.
Use components management records to connect the proposal to the actual purchasing source and material scope. Resolve conflicting descriptions before asking whether the items are interchangeable. An unapproved state means the project’s required decision is open; it does not prove that the item is counterfeit or defective. The first useful outcome is a clear comparison object, with known missing fields assigned to the owner who can establish them.
Obtain the complete ordering identity of the proposed component before comparing it with the approved item. Include relevant manufacturer and suffix information from the controlling sources, and separate an incomplete proposal from a verified mismatch. A distributor shorthand or nominal description may not identify the exact offered object. If the identity remains unclear, request clarification before evaluating suitability. The immediate control is to prevent an unidentified substitution, not to label the component counterfeit or defective without supporting evidence.
Evaluate Unapproved Manufacturer Risk in the Actual Circuit
Unapproved manufacturer risk should be evaluated against the actual circuit role, ratings, margins, environment, lifetime, and failure consequence.
Compare the characteristics relevant to the actual circuit position and operating conditions. Nominal values alone may not cover the limits, tolerances, timing, thermal behaviour, or other characteristics the design relies on. Ask the technical owner to identify which differences matter and to reference the applicable manufacturer information rather than copy a broad catalogue comparison.
Record unanswered questions in the BOM risk report , with the analysis or evaluation needed to close them. Keep a proposed verification separate from an observed result, and state the conditions under which evidence applies. A difference in a datasheet is a reason for a scoped review, not automatic proof that the application will fail. Conversely, a similar headline specification does not establish that every relevant condition has been considered.
Select parameters according to the actual circuit and operating conditions. Ask the design reviewer which differences could affect the intended use and what evidence would resolve each question. A table of nominal values may help organize the comparison, but matching a few values is not an approval decision. Record the source and revision of the data used and any verification still required. Keep the conclusion bounded to the identified application rather than claiming the alternate is universally interchangeable.
Electrical comparison: review rating, tolerance, thermal, application against the active project records. Trace Unapproved Manufacturer Risk Through Package and Assembly
Check the exact package and ordering option against the assembly’s land pattern, orientation, handling, and applicable process instructions. Similar outlines can conceal details that matter to the receiving process. Identify the specific difference and ask the responsible engineering or manufacturing owner whether existing instructions remain valid, need revision, or require a defined evaluation.
Bring relevant information from the component lifecycle risk review into this review when product status changes the proposed option or source. Do not use lifecycle evidence as a substitute for package compatibility. Record the configuration and conditions of any assembly observation, together with its limits. A result from one sample or process setting should support only the conclusion its reviewer can justify, not an unrestricted claim that the alternate is universally interchangeable.
Follow one relevant parameter from manufacturer data through circuit use to the bounded analysis or test that can support the project decision.
Potential difference
Compare against the intended application
Reviewer
Pause substitution when
Part identity
Exact maker and MPN, including relevant ordering suffixes
Engineering and sourcing
The proposed item cannot be identified unambiguously
Electrical or thermal behavior
Applicable ratings, tolerances and operating conditions
Design authority
A required parameter or verification remains unresolved
Assembly interaction
Package drawing, termination and process requirements
Manufacturing engineering
Nominal package naming is the only compatibility evidence
Source exposure
Supplier identity, trace records and dated lifecycle information
Sourcing and quality
Required source evidence is absent or inconsistent
Check lifecycle source and traceability evidence
Supplier-specific notices, such as the TI product-change notification policy , can expose a source change for an affected TI part but cannot close unapproved manufacturer risk for the project.
Review the proposed item’s dated source and lifecycle evidence under the project’s purchasing requirements. Identify the issuer, exact ordering code, stated status, source, and any required traceability relationship. Keep a general web listing separate from a current supplier response. If the evidence concerns a different package option or source, record that mismatch rather than carrying its conclusion across by assumption.
Use engineering change control to control a proposed departure from the approved basis. Sourcing and quality should identify the evidence each role needs, while the authorised technical owner handles suitability. A missing record keeps the relevant decision open; it does not establish a finding of counterfeit material. Preserve the actual gap and the response that would resolve it so the next reviewer can act on a specific question.
Separate the technical comparison from the source review. A technically acceptable item may still require purchasing-source approval, trace records or clarification of its offered status under the project’s requirements. Record who supplied each statement and when it was issued. If lifecycle information conflicts with a quotation, assign the discrepancy to an owner instead of choosing the more convenient answer. The review should establish the basis available for this proposed purchase, without implying guaranteed availability or an authorized channel that has not been verified.
Package compatibility: review outline, land pattern, pinout, assembly against the active project records. Reopen Test, Firmware, and System Validation Selectively
Ask which programming, test, or system checks depend on the changed characteristic. The relevant dependency may involve configuration, identification, measured behaviour, or interpretation of a result. Link the proposed difference to the affected input before selecting a verification activity. This avoids both accepting an alternate from an unrelated test and reopening every check without a technical reason.
Define the method, configuration, operating conditions, expected evidence, and decision owner for a necessary evaluation. Record why other checks remain applicable. Keep sample observations and analysis within their stated limits, and distinguish a completed check from final permission to use the alternate. The review should explain what remains unresolved without reporting a functional failure or successful validation that the project has not actually established.
Map each relevant difference to the function or control it could affect. The reviewer may identify a firmware dependency, a calibration assumption or a test condition requiring verification; unrelated functions need not be reopened merely because the manufacturer changed. State the rationale for the selected scope and retain the applicable input versions. If existing evidence is reused, explain why it remains relevant to the alternate. This produces a bounded validation decision instead of an unexamined demand to repeat every historical test.
Set Material and Build Effectivity for Unapproved Manufacturer Risk
Separate the proposed alternate from material already ordered, received, issued, or assembled. Establish where each item could enter the active work and which configuration the approval would cover. Use the available lot, order, work-order, build, or serial references to describe that boundary. If the records are incomplete, retain the uncertain interval and identify the reconciliation required.
Ask the authorised owners to decide the treatment of existing stock and work in process. A new approval does not automatically dispose of earlier commitments, and an earlier exception does not automatically cover future purchases. Align the approved-list entry, material records, and receiving instructions with the same effectivity. This makes the change usable by operations without forcing a purchaser or operator to infer permission from a general approval date.
Trace one approved manufacturer change into the AML, receiving controls, material records, and build instructions, then verify that each record carries the same effectivity.
Evidence outcome
Next decision
Containment scope
Evidence to retain
Difference is understood and acceptable
Seek authorized approval for the defined application
Named part and product revision
Comparison basis and required verification
Application impact is uncertain
Resolve the specific parameter or operating condition
Affected substitution only
Question, reviewer and test or analysis plan
Material is already received
Separate proposed material from approved stock
Identified lot and locations
Identity checks and disposition authority
Material has entered production
Assess units exposed to the alternate
Traceable work-in-process and completed units
Impact assessment and authorized disposition
Physical verification: review sample, fixture, method, record against the active project records. Limit Exceptions to Named Authority and Effectivity
A limited exception should explain exactly what may proceed while the broader review remains open. Identify the part, source, configuration, permitted operation, material or build scope, supporting evidence, conditions, and expiry. State the unanswered question and the authority accepting the bounded action. The permission should be narrow enough that its users can determine whether a proposed activity falls inside it.
Keep the exception visible in the records that purchasing and production actually consume. Do not turn sample permission into routine approval by copying it into later orders or builds. If the planned work exceeds the boundary, request another explicit decision. Retain the exception’s history and its closing or reopening condition so temporary use cannot silently become the project’s permanent manufacturer baseline.
If the project permits a temporary exception, define its purpose before material is used. Identify the proposed part, product revision, units or quantity, allowed operation and the approval that remains outstanding. Add the required expiry and reopening condition, and name the authority that can issue the exception. Shortage pressure alone is not that authority. The next process owner should be able to determine whether the intended work falls inside the permission without interpreting a vague instruction to proceed at risk.
Release after evidence and independent readback
Close unapproved manufacturer risk only after the exact identity, evidence, approving role, effective material, and affected build are independently read back.
Release the alternate only when the named reviewers have closed the required questions and the implementation records reflect the authorised scope. Link the exact identity, technical disposition, source decision, remaining conditions, and effectivity to the controlling row. Preserve the evidence and decisions separately so a later reader can distinguish what was observed from what was permitted.
Ask another authorised reviewer to retrieve that path through the normal system and compare it with a real receiving instruction. Include any excluded stock, configuration, or operation in the readback. Correct conflicting active records before the dependent work continues. The final record should identify the reviewed scope and reopening triggers; it should not imply universal equivalence or approval of later uses outside the actual decision.
Close the review by matching the approved identity to the material and instructions at the point of use. Check the active list row, applicable source decision, verification evidence and first affected build. If the proposed item was rejected or remains unapproved, make that state clear in the purchasing and material records. If approval is limited to one application, preserve the limitation. The final readback should prevent either approval or rejection from being generalized to unrelated products or later substitutions.
Lifecycle evidence: review status, source, date, owner against the active project records. Challenge Unapproved Manufacturer Risk Before Release
Build the comparison around one application-relevant difference, not a generic claim of equivalence. The engineer records the exact manufacturer, full MPN, datasheet revision and circuit position, then identifies the operating condition that makes the parameter important. Follow that parameter into an analysis, measurement, assembly observation or system test with a stated acceptance boundary. Differences outside the named application remain outside the decision.
When manufacturer data conflicts, retain both source revisions and assign the technical question. Do not average limits or substitute a distributor description. Manufacturing and quality should separately review package, termination, moisture, traceability or inspection effects that apply to the project. The proposed alternate remains blocked for the affected material or build until the named evidence closes; unrelated work can continue.
FAQ
Does unapproved mean the component is counterfeit?
No. It means approval or evidence is absent or incomplete for the project. Counterfeit determination requires separate source, inspection and investigative evidence.
Is the same package and value enough to approve an alternate?
No. The review should use exact manufacturer and MPN plus application-relevant electrical, thermal, lifecycle, source, process and validation evidence.
Must every manufacturer change repeat all product testing?
No. Validation should follow the identified mechanism and affected system path. The authorised engineering and quality owners define the necessary scope.
What should be held while approval is open?
Hold the affected purchase, material issue, build or release line. Preserve unrelated approved work unless a documented dependency shows that the gap affects a broader scope.
For a proposed alternate, compare one application-relevant difference through to a measurable or reviewable outcome. Link the datasheet field to circuit use, assembly process, test limit or lifecycle decision, then name the evidence that closes it. This prevents a generic equivalence statement from replacing the specific engineering and quality judgement required for the project.
Bring the active records to the unapproved manufacturer PCBA risk review
Provide the exact manufacturer and MPN, application conditions, datasheet sources, relevant differences, process impact and proposed validation. Use the plain contact page for a project-scoped alternate review.
For this check, the decision may approve, reject, validate, conditionally allow or hold the proposal. No result applies beyond the named assembly, environment, source, material and authorised effectivity.
Use the risk checklist to connect the proposed manufacturer change with part identity, circuit use, package fit, assembly process, sourcing status, and lifecycle evidence. Apply any approval or containment only to the assembly, environment, source, material, and effectivity supported by current project records.
