An ESD control plan for PCBA manufacturing should convert product sensitivity and customer requirements into a route that can be released, verified, and audited. It is not satisfied by a supplier saying that a factory is “ESD safe,” and it is not replaced by adding ESD protection devices to the circuit. The OEM needs to know which items are sensitive, where they are exposed, which controls apply, what evidence confirms those controls, and what happens if the planned condition cannot be maintained.
This is a build-release task because electrostatic-discharge risk follows material and assemblies through receiving, storage, kitting, feeder setup, SMT, manual insertion, inspection, rework, programming, test, packing, and transport. A workstation check at one stage does not define the rest of the route.
The objective is not to reproduce a full industry standard inside a purchase order. It is to identify the applicable standard and revision, state any product-specific limits, map them to the proposed route, and agree on the records and exception path before material is released. This article gives OEM engineering, quality, procurement, and program teams a practical structure for doing that.
Define the standard and product scope
The plan begins with exact items, sensitivity information, revisions, and customer requirements. Start by identifying the governing requirement rather than asking for generic compliance. The contract may reference an OEM specification, a customer specification, ANSI/ESD S20.20, IEC 61340-5-1, or another agreed document. Record the edition or revision, contractual hierarchy, and any approved tailoring. If the OEM requires controls beyond the supplier’s normal program, those differences need an owner, implementation decision, and effective date.
Use the correct standard boundary
The official ANSI/ESD S20.20-2021 description states that the standard provides administrative and technical requirements for establishing, implementing, and maintaining an ESD control program. That supports asking for a defined program and control plan. It does not prove that a particular supplier is certified, compliant, or suitable for a specific product.
The official IEC 61340-5-1:2024 scope covers organizations that manufacture, process, assemble, install, package, label, service, test, inspect, transport, or otherwise handle applicable electrical or electronic parts, assemblies, and equipment. It also states the general HBM and CDM withstand-voltage boundary and notes that items with lower withstand voltages can require additional control elements or adjusted limits. An OEM should therefore provide known sensitivity below the general program boundary rather than assuming the default program covers it.
Identify every in-scope item
Build the scope from the BOM, approved manufacturer data, product specifications, packaging requirements, and customer documents. Record static-sensitive components, bare or populated boards, modules, programming fixtures, service parts, and assemblies returned for rework. Include customer-supplied material and evaluation samples; ownership does not remove handling risk.
For each item, capture the relevant sensitivity information, packaging state, handling notes, and any condition that changes after opening. Do not infer an exact device withstand voltage from package type or circuit function. If required information is missing, label it as an open input and decide whether the supplier’s existing program boundary is adequate or a more conservative temporary control is needed.
The design discussion remains separate. This guide to ESD protection in PCBA design explains how circuit-level protection affects product robustness. The manufacturing control plan addresses exposure before the finished product is enclosed and operating in its intended environment.
Define the released build context
Tie the plan to the BOM revision, PCB revision, assembly drawing, build stage, quantity, route, participating sites, and planned subcontracted operations. A prototype built at one bench and a production order moving through several areas do not share the same exposure map. State whether the requirement applies only to exposed components, to every populated assembly, or to specified operations and packaging states.
The plan header should identify the owner, approval date, effective work-order or build revision, required reviewers, and next review trigger. If a customer standard conflicts with an existing route, the build should remain open until an authorized owner resolves the difference.
Map the protected route and handoffs
Receiving, kitting, assembly, inspection, test, and packaging need defined handoff controls. Create a route map from material receipt to shipment. For each operation, identify who handles the item, whether it is inside an ESD protected area, the equipment or workstation involved, the item’s packaging state, and the next handoff. This reveals gaps that a facility-level statement can hide.
Include material and logistics stages
Receiving may inspect packages, open containers, count parts, or transfer reels and trays. Storage may use original ESD protective packaging, controlled cabinets, dry storage, or ordinary shelving depending on the item and agreed program. Kitting and feeder preparation can expose devices before they reach the placement machine. Define when protective packaging may be opened, how partially used material is returned, and how suspect or nonconforming material is segregated.
Packaging and transport are also part of the route. State the required shielding, conductive or dissipative properties, closures, labels, and conditions for internal transfers, work-in-process containers, completed assemblies, returns, and shipment. Do not name a packaging type without confirming that it satisfies the applicable project and standard requirements.
Include automated and manual operations
SMT placement may be highly automated, but personnel still load feeders, handle trays, clear faults, inspect first articles, and move boards. Manual insertion, selective solder, touch-up, cleaning, conformal-coating preparation, inspection, rework, programming, fixture connection, and functional test can introduce additional handling points. The plan should name them.
For the underlying manufacturing mechanisms and common control concepts, see electrostatic discharge in PCBA manufacturing . The build-release plan uses those concepts to define responsibility and evidence for one product route.
Control boundaries between organizations
If material or assemblies move to a PCB supplier, programming house, test laboratory, coating provider, repair location, warehouse, or logistics partner, record the handoff condition and receiving acceptance. Identify who verifies the external operation, who owns an exception, and which records return with the product.
A transfer record should preserve item identity, quantity, revision, packaging condition, and applicable handling requirements. When evaluating a supplier before the PO, the OEM can use a PCBA traceability verification to align these expectations with the planned build record.
The route table below turns the map into a release decision.
Route stage
Exposure question
Required plan field
Release evidence
Receiving and storage
Is protective packaging opened, inspected, transferred, or returned?
Item identification, approved storage and opening condition, segregation rule
Receiving instruction and applicable area or packaging verification
Kitting and feeder setup
When do parts leave protective packaging and who handles them?
Protected-area boundary, personnel grounding, container and return rule
Workstation/control status and authorized work instruction
SMT and manual assembly
Which automated and manual contacts occur?
Equipment grounding, work surface, handling tool, personnel and insulator controls
Applicable qualification or compliance-verification record
Inspection, rework and programming
Are boards touched, moved, repaired, connected, or depanelized?
Protected work area, fixture and tool conditions, WIP container, exception route
Operation-specific check and product traveler reference
Test and final packaging
When can the assembly leave the protected route?
Test-station controls, packaging specification, label and transfer condition
Test/pack release record tied to the build
External or subcontracted step
Does another organization handle exposed ESDS items?
Handoff requirement, responsible owner, acceptance and returned evidence
Approved supplier/operation record and transfer confirmation
Specify control elements and acceptance limits
Grounding, work surfaces, tools, personnel, and insulators must match the applicable plan. The plan should name the control elements that apply at each stage and point to the governing requirement for their acceptance limits. Avoid copying numeric limits from a different standard edition or applying one test method to every item. The supplier’s ESD program owner should identify the approved equipment, qualification method, verification method, frequency, and responsible role.
Address grounding and equipotential bonding
Personnel, work surfaces, equipment, carts, fixtures, tools, and other conductors need an applicable grounding or bonding path within the protected operation. The selected personnel-grounding method may depend on whether the work is seated or standing, the footwear-flooring system, safety constraints, and the item’s sensitivity. The plan should identify the method and verification point without assuming a wrist strap is the only valid control.
Include temporary stations, repair benches, portable equipment, and maintenance work. A permanent line can have a mature program while a temporary engineering station or customer-return bench falls outside the documented boundary.
Address insulators and charge generation
Process-essential insulators cannot always be grounded. The plan should identify packaging, tapes, labels, fixtures, covers, plastic tools, documents, garments, and cleaning materials that may enter the protected area. Decide whether the item is prohibited, separated, replaced, treated, or controlled by ionization according to the applicable program.
Ionization is not a general substitute for grounding. If it is used, identify where it is required, what condition it controls, how performance is verified, and what happens when the device is unavailable or outside its acceptance range.
Address identification, training and access
Define how ESDS items, protected areas, WIP containers, and packaging states are identified. Personnel who handle in-scope items should have the training and authorization required by the applicable program and their assigned work. Visitors, maintenance staff, material handlers, and temporary operators need a defined access or supervision route rather than an assumption.
The OEM usually does not need every employee record. It needs evidence that the roles touching its product are covered and that an expired or missing authorization has a containment response. A remote or on-site PCBA factory audit can sample these controls against the actual route instead of relying on a capability slide.
Define verification evidence and release gates
Qualification and ongoing verification records support a traceable build-release decision. An ESD control element is not complete merely because it was purchased or installed. The program should distinguish qualification, periodic or event-driven compliance verification, routine operator checks, calibration where applicable, maintenance, and project records. The OEM should ask for the evidence needed to release its build, not an indiscriminate dump of facility documents.
Separate qualification from ongoing verification
Qualification establishes that a control item or method can meet the applicable requirement under defined conditions. Ongoing verification checks whether it continues to perform in use. Operator checks may occur before work, while periodic measurements may follow a schedule or event. Record which layer applies to work surfaces, personnel-grounding systems, flooring, ionizers, tools, carts, packaging, and other selected controls.
The ESD Association’s official ESD standards overview describes ESD TR53-01 as providing compliance-verification test procedures and troubleshooting guidance for protective equipment and materials. That supports requiring a documented verification method. It does not justify inventing a frequency or acceptance limit; those should come from the applicable plan, standard, manufacturer guidance, and risk decision.
Make records decision-ready
For each control item, record its identity or location, applicable requirement, method, acceptance criterion, verification frequency or trigger, last result, status, responsible role, and action for failure. Keep revision and date information so the project can tell whether the evidence applied when its material was handled.
Project evidence may include the approved plan revision, route or protected-area map, relevant qualification status, recent compliance-verification status, training authorization confirmation, special packaging approval, work-order reference, and exception records. Define retention and customer-access rules in the contract or quality agreement.
Use a release matrix
The release matrix should tell procurement, engineering, quality, and manufacturing whether a gap stops the build or needs a controlled decision.
Condition at review
Required action
Authorized outcome
Closure evidence
Applicable program and route are defined; verification is current
Link the approved plan to the work order
Release within the stated scope
Plan revision, route and current status record
Product sensitivity is below or outside the normal program boundary
Perform risk review and define additional controls or a different route
Release with approved added controls, or stop
Engineering/customer decision and updated plan
A control item is overdue, failed, missing or moved
Stop the affected operation, identify exposure and follow the failure response
Restore, substitute through approval, or quarantine affected scope
Reverification, disposition and affected-product record
Temporary or external operation is not covered
Qualify the operation and define handoff evidence
Approve a limited scope or reject the route
Approved operation record and transfer controls
Required evidence cannot be produced
Determine whether the condition is a record gap or an uncontrolled process
Hold, investigate, or approve a documented deviation
Root cause, risk decision and effective release
Before releasing an NPI build, the supplier intake should connect this matrix to the project package. The sequence described in what happens after BOM and PCBA files are uploaded is the right stage to identify missing handling and evidence requirements, before material commitment.
Control exceptions changes and repeat orders
The ESD plan needs a failure and change path. If a workstation check fails, grounding is interrupted, an ionizer is out of condition, packaging is damaged, an uncontrolled item enters the protected area, or material moves through an unapproved route, the operator should know when to stop, what to isolate, who to notify, and how to record the affected scope.
Define containment by exposure scope
Containment should identify the time window, area, equipment or control item, operators or operations involved, material lots, assemblies, and work orders that may have been exposed. Do not assume that passing visual inspection proves the absence of latent ESD damage. Engineering and quality should decide whether the appropriate action is record review, additional inspection or test, lot disposition, customer notification, or another approved path.
The response must remain proportionate. A missing document and a confirmed failed control item are different conditions. The record should state the evidence, uncertainty, decision owner, and rationale rather than applying one automatic disposition to every event.
Put change control before route changes
Review the plan when the BOM, component sensitivity, PCB revision, process sequence, workstation, tool, fixture, packaging, test method, area, supplier, subcontractor, customer requirement, or applicable standard changes. Maintenance and layout moves can also change grounding or protected-area boundaries. Define which changes require requalification, reverification, document update, or customer approval.
Temporary deviations should state quantity, lot, operation, location, time period, added controls, required verification, approver, and expiration. They should not carry into the next order without review.
Reconcile repeat orders
At repeat order, compare the current BOM and route with the last approved build. Confirm that control-plan references are current, overdue actions are closed, temporary deviations have expired or been converted to approved changes, relevant verification remains current, and packaging or external handoffs have not changed.
Review previous exceptions, nonconformances, rework, and customer feedback for any ESD-related signal. This is not proof of causation; it is an input to the risk review. The repeat-order release should identify what was rechecked and which unchanged controls continue under the standing program.
Conclusion
An ESD control plan becomes useful when it names the applicable standard and revision, identifies the sensitive items, maps every handling stage, assigns the required control elements, and defines verifiable release evidence. It should cover receiving through shipment, including manual work, temporary stations, test, rework, packaging, and subcontracted handoffs.
Before build release, require clear answers for five points: what is in scope, where exposure occurs, which controls and limits apply, how current status is verified, and who owns an exception. This makes the release traceable without turning it into an unfocused facility audit. Keep product-specific decisions separate from general facility claims, and recheck the plan when the product or route changes. Send the current BOM, assembly route, ESD sensitivity data, handling requirements, and evidence expectations for a structured PCBA project review.
Request an ESD Control Plan Review
FAQ
Who should define the ESD sensitivity level for a PCBA build?
The OEM should provide available component and product sensitivity information, customer requirements, and any limits that are more restrictive than the manufacturing program. The EMS provider should map those inputs to the proposed route, identify gaps, and obtain an authorized decision before material or assemblies enter an unsupported condition.
Does an ESD-safe workstation prove that the whole PCBA route is controlled?
No. The plan should cover every in-scope handoff, including receiving, storage, kitting, feeder preparation, SMT, manual assembly, inspection, rework, programming, test, packaging, transport, and any subcontracted operation. Each stage needs the applicable control elements and verification evidence.
What ESD records should an OEM request from a PCBA supplier?
Request records that are proportionate to the agreed risk and contract, such as the applicable control-plan revision, protected-area scope, relevant qualification or compliance-verification status, training authorization, exception records, and evidence tied to project-specific handling or packaging requirements. Avoid requesting unrelated facility documents without a defined purpose.
When should an ESD control plan be reviewed again?
Review it when the BOM, sensitivity data, board revision, assembly route, workstation or equipment, packaging, test method, handling location, subcontractor, customer requirement, or applicable standard changes. Repeat orders should also confirm that temporary deviations and corrective actions from the previous build are closed or explicitly extended.
