An electronic component may move from receiving to storage, kitting, assembly, inspection, packaging, and shipment without the buyer seeing the work area that handled it. When a buyer identifies a component or assembly as electrostatic-discharge sensitive, a supplier statement that it uses ESD protection is not enough. The buyer needs a defined evidence request that ties the stated handling controls to the product, revision, site, work area, and actual production event.
China supplier ESD handling evidence is a buyer-controlled record set for components or assemblies identified by the buyer’s product requirements as needing ESD-related handling. It can connect the product baseline, supplier work area, current instruction, supplier role, receiving and storage record, kitting or traveler record, inspection or packaging record, and any handling exception. It does not determine whether a component is ESD sensitive, whether an ESD program works, whether grounding is effective, whether material was damaged, or whether goods should be accepted or shipped.
NASA-HDBK-8739.21 provides guidance on limiting electrostatic discharge that may injure personnel or damage or destroy electronic components.1 An inactive NASA document, JSC-66552, describes identifying each ESD control work area and developing an ESD Control Plan for each area.2 DLA defines ESD as a transfer of electrostatic charges between bodies at different potentials. Its packaging guidance also states that drawings, specifications, technical sheets, and packaging or marking requirements commonly identify ESD-susceptible items, and it discusses special workstations, clothing, equipment, handling procedures, packaging, and marking in its DoD context.3 Those NASA and DLA sources do not set commercial requirements for China sourcing. They support a limited buyer approach: define the actual product scope, ask for relevant supplier records, keep plan-level and event-level evidence separate, and send technical questions to qualified owners.
Define the product and process scope first
An ESD evidence request starts with the buyer’s own controlled product baseline. Do not ask a supplier to decide whether an item needs special handling when the buyer has not identified the component, assembly, revision, or requirement source. The record should show why the request applies and which parts of the supplier process are in scope.
| Scope field | Buyer record purpose |
|---|---|
| Buyer component or assembly ID | Identifies the affected item |
| Product, BOM, or drawing revision | Ties request to the current technical baseline |
| ESD-status source | States where the buyer requirement came from |
| Supplier legal entity and site | Identifies the receiving factory or facility |
| Work-area ID | Identifies the stated station, room, or line |
| Pasos del proceso | Lists receiving, storage, kitting, assembly, inspection, packaging, or other stated steps |
| Packaging baseline | Links material handling to buyer-approved packaging instruction where applicable |
| Record owner | Names the buyer role responsible for the request |
| Review date | Sets a point to reassess the scope after changes |
The buyer should name the process stages it needs to review. A supplier that only packs finished assemblies needs a different evidence package than a supplier that receives loose devices, stores them, kits them, assembles them, tests them, and performs final packaging. Scope makes the request usable without turning it into an unsupported audit.
Request plan-level evidence for the stated work area
Plan-level evidence describes what the supplier says applies to a work area before a particular order is processed. It can include an area identifier, a current instruction reference, a responsible role, and a training or authorization record when the parties agree that it is relevant. The buyer should retain the instruction revision and effective date, not only a screenshot or general policy statement.
| Plan-level evidence | What it can show | What it cannot prove alone |
|---|---|---|
| Work-area identifier | The supplier named an area for the stated activity | That every activity occurred there |
| Current instruction reference | Supplier has a stated controlled procedure | That workers followed it for a given order |
| Responsible role | Who manages the stated area or process | That the role holder performed each task |
| Training or authorization record | Supplier records completion of a stated requirement | Technical competence or effective control |
| Station or equipment identifier | Supplier identifies a location or asset | ESD performance of that station |
| Packaging instruction | Supplier has a stated packaging baseline | That every unit was packed correctly |
| Controlled revision status | The stated record version is identifiable | That it matches the buyer’s requirement |
| Supplier acknowledgement | Supplier confirms scope received | That the process produced conforming goods |
A plan is useful because it gives the buyer a reference when an event record later names a different site, line, or packaging method. It is not a certification. A wrist-strap photo, a station label, or a supplier statement does not by itself show that a work area operated effectively or that a component has no latent damage.
Connect actual events to the supplier record
Event-level evidence tells the buyer what supplier record applies to the defined order or lot. Request links, not a large pile of generic photos. The supplier can connect the event to a receiving record, storage location, kit issue, production traveler, inspection entry, packaging record, or exception report.
| Event record | Buyer question |
|---|---|
| Receiving record | Did the supplier identify the ESD-sensitive scope on receipt? |
| Storage record | What stated location held the material before issue? |
| Kitting record | Which work order or assembly received the component? |
| Traveler or work order | Which stated process or line used the material? |
| Inspection record | What inspection event is linked to the in-scope work? |
| Packaging record | Which packaging instruction or revision applies? |
| Shipment handover record | What packed scope was passed to logistics? |
| Exception record | Was a site, process, packaging, or handling issue recorded? |
A buyer should record the limit of each item. A receipt record can show that material entered a supplier system. It does not prove the material was not damaged before receipt. A traveler can show a stated operation and date. It does not verify an ESD workstation. The value is the connection between product scope, supplier action, and a retrievable record.
Map evidence to each supplier process step
The buyer can ask for a short, proportional evidence map rather than impose a universal procedure. The map tells the supplier which record matters at each in-scope step and what decision it supports.
| Process step | Evidence request | Buyer use | Limit |
|---|---|---|---|
| Receiving | Item ID, source record, and defined status | Confirms in-scope material was identified | Does not prove condition before receipt |
| Almacenamiento | Stated location and status record | Links material to supplier custody record | Does not prove environmental or ESD performance |
| Kitting | Kit or issue record tied to work order | Maps component to planned assembly scope | Does not prove correct component use |
| Asamblea | Traveler, line, and instruction revision | Connects work to stated area and baseline | Does not certify process effectiveness |
| Inspection | Linked inspection record and scope | Shows a recorded check occurred | Does not prove all units conform |
| Embalaje | Packaging instruction and pack-out record | Connects shipment preparation to baseline | Does not approve packaging material |
| Handover | Quantity and shipment record | Reconciles stated packed scope | Does not release shipment |
Separate observations from technical conclusions
A buyer evidence process should distinguish a supplier plan, a supplier-recorded event, a photograph, a technical verification, and a commercial decision. This keeps the file honest and prevents a routine record request from being described as proof of ESD compliance.
| Record layer | Appropriate statement |
|---|---|
| Buyer requirement | Buyer identified stated component and process scope |
| Supplier plan | Supplier provided a current area or instruction reference |
| Event record | Supplier linked a defined order or lot to a stated record |
| Observation | Photo or document shows a stated condition at a stated time |
| Technical verification | Qualified owner documents an evaluation within defined limits |
| Buyer decision | Authorized owner records next sourcing, production, or review action |
The distinction matters when a record is incomplete. The supplier can state that it cannot find a packaging instruction or that a work order used a different line. The buyer can then decide whether to request more evidence, record an exception, or escalate the change. Neither side should fill the gap with a claim that an ESD program was compliant or that the component was not damaged.
Control change and exception records
The supplier should not silently move ESD-sensitive work to another site, line, packaging method, or instruction. A change is not automatically a failure. It is a reason to identify the new scope and decide which owner needs to review it.
| Change or exception | Record the known facts | Next owner action |
|---|---|---|
| New supplier site or line | New location, product scope, and start date | Review whether the current evidence request still applies |
| Changed packaging method | Old and new instruction or material reference | Route packaging and technical review as required |
| New component or revision | Component ID, revision, and stated reason | Confirm product scope before production use |
| Missing work-area record | Requested area, date, and supplier explanation | Request record or record controlled exception |
| Unclear instruction revision | Available reference and uncertainty | Obtain current controlled version |
| Supplier reports handling event | Known time, material scope, location, and action | Escalate to qualified technical or quality owner |
| Record mismatch | Product, line, lot, or revision difference | Determine whether more evidence is needed |
| Buyer changes requirement | Changed source, effective point, and supplier acknowledgement | Reissue the evidence baseline |
Do not turn every exception into an engineering verdict. The supplier record should show the specific gap, the immediate status, and the next responsible owner. Electrical engineering, ESD program, workplace-safety, testing, certification, and product-release questions need qualified review.
Use an escalation path that matches the issue
| Decision area | Typical owner | Supplier contribution |
|---|---|---|
| Record completeness | Buyer sourcing or quality owner | Provide linked work-area and event records |
| Work-area or instruction question | Supplier quality or process owner | Identify current instruction and actual location |
| Packaging baseline question | Packaging or technical owner | Provide packaging and pack-out references |
| Suspected handling event | Qualified technical or quality owner | Preserve known facts and relevant records |
| Product design or component change | Engineering and change-control owner | Do not use changed scope without required direction |
| Compliance, safety, or legal issue | Qualified specialist | Preserve records and follow approved route |
| Shipment status | Authorized shipment or release owner | Maintain stated hold or completion status |
A buyer can make the escalation path simple: name a record owner, a technical owner, and a commercial owner. The supplier knows who should receive a routine missing-record question and who must review a report that could affect production or shipment.
Supplier request wording
For [buyer component or assembly ID, revision, PO or work order, supplier site, and stated process steps], provide the agreed ESD handling evidence. Identify the supplier work-area ID, current instruction reference, responsible role, relevant training or authorization record where agreed, and the event records for receiving, storage, kitting, production, inspection, packaging, and shipment handover that apply to the stated scope. Record any site, line, instruction, packaging, or handling exception with known facts, current status, and next owner. Buyer review does not certify ESD compliance, electrical performance, safety, product condition, product acceptance, or shipment release.
Frequently asked questions
What is China supplier ESD handling evidence?
It is a buyer-controlled set of supplier records that connects a buyer-identified ESD-sensitive component or assembly to a stated work area, instruction, handling event, and exception process. It supports a review of records, not a claim of technical compliance.
Is a photo of an ESD workstation enough?
No. A photo can show a stated condition at a particular time. It does not prove workstation performance, operator behavior, applicability to a specific order, component condition, or absence of damage. Link it to the defined product and supplier record if it is used at all.
Does the buyer need every internal supplier record?
No. Request evidence that answers the buyer’s purpose. For a packaging-only supplier, packaging and handover records may be more relevant than kitting. For a supplier that handles components through assembly, the buyer may need a longer record path.
What if the supplier cannot provide a requested record?
Record the missing item, supplier explanation, affected scope, and current status. The buyer can request an alternative record, put the scope on hold under the agreement, or route the question to the appropriate technical or commercial owner.
Does reviewing ESD handling evidence release the shipment?
No. The record can support later quality or commercial decisions. It does not establish product conformity, ESD effectiveness, safety, regulatory status, customs readiness, or final release.
Review the record path, not a claim
China supplier ESD handling evidence gives buyers a practical way to ask what record applies to a buyer-identified ESD-sensitive scope. It connects the product baseline, work area, handling plan, actual event records, and exceptions without treating a statement or photo as proof of technical control.
Start with one ESD-sensitive component or assembly in the next production run. Define the component and revision, supplier site, process steps, required records, exception owner, and escalation path before material is issued. Supplier Ally can help buyers organize supplier evidence requests, production records, change notices, exception logs, and cross-border communication. Use qualified technical, safety, engineering, legal, compliance, packaging, and final-release owners for decisions beyond record review.
ES 
EN 