BOM Checklist

This checklist is prepared for use in material list (Bill of Materials – BOM) creation and verification process. The goal is to ensure that each component is fully defined, available, manufacturable, and programmable. A complete BOM is the foundation of production, procurement, quality control, and maintenance processes.

Component Definitions and Identification​

1. Does each component have quantity, reference code, and description information?​

Minimum information for each component on BOM should include:

If this information is missing, the risk of wrong component placement, missing parts, or incorrect stock management increases during production or assembly. Additionally, the description field should include component tolerance, power rating, and mounting type (THT / SMD).

2. Are qualified part numbers listed for special or high supply-risk parts?​

For critical components or those with limited supply chain, manufacturer part number (MPN) and alternative qualified parts (cross-references) should be clearly specified in BOM.

This information ensures production continues without interruption during supply crisis or stock depletion. Additionally, matching parts with suppliers through approved vendor list (AVL) is recommended. For certified parts, certificate of conformance (CoC) or RoHS/REACH compliance should be noted.

3. Is package type clearly defined for each part?​

Physical package/footprint type should be specified for each component in BOM.

Without this information, the manufacturer cannot select correct footprint or assembly profile. Additionally, package type information should be consistent with PCB library and 3D model. Incorrect package information leads to reflow profile errors, assembly incompatibilities, or mechanical conflicts. Therefore, BOM file should be prepared to automatically synchronize with CAD library (e.g., Altium, KiCad, OrCAD BOM export formats).

Manufacturer Information and Alternatives​

4. Are recommended manufacturer(s) listed for all components?​

At least one approved or recommended manufacturer should be defined for each component. This information should appear in "Manufacturer" or "Vendor" column in BOM document.

Manufacturer name plays critical role in supply planning and maintaining quality standards. Approved manufacturers should be determined through AVL (Approved Vendor List) based on quality history, certification, and delivery performance. This information facilitates transition to alternative manufacturer during supply chain disruptions.

5. Are alternate manufacturers and part numbers specified?​

At least one alternate manufacturer or equivalent part number (Alternate Part Number – APN) should be defined for each critical component.

Alternate part information is important especially for components with long lead time or end of life (EOL). This information should be clearly included in BOM's "Alternate Manufacturer / Alternate P/N" field. Procurement department can use this information to switch to alternative supply channel without production interruption.

6. Is electrical parameter compatibility of equivalent components verified?​

Alternative components should be added to BOM only after electrical, mechanical, and thermal parameter compatibility is confirmed. This check is particularly critical for these component groups:

• Voltage regulators and converters (Pin layout and dropout voltage differences can affect circuit stability),
• Op-amps and comparators (Bias current, offset voltage, or gain bandwidth differences change system performance),
• MOSFET / BJTs (RDS(on) and VGS(th) values, thermal limits affect switching losses).

Therefore, datasheet comparison should be made for each alternate part and approval process should be documented with "Engineering Change Request (ECR)" record.

Programmable Components and Software Information​

7. Is software/firmware information added for programmable devices?​

In BOM or production document, relevant firmware or configuration file information should be present for each programmable component. This information should be provided with device type, software version, and file name.

Production line uses this information to verify that each board is programmed with correct software version. Missing software definition causes post-production functional test errors or version confusion. Additionally, software version information should also be processed into labeling or production database (MES).

8. Are programming method, code format, and programmer tool defined?​

For each programmable component, programming method, file format, and programmer device used should be clearly specified. This information is typically included in "Programming Notes" or "Production Instruction" document.

These definitions ensure software tools used in production line work with correct versions. Missing definition leads to serious production errors such as programming time inconsistency, verification errors, or wrong version loading. Additionally, pinout and connector type (SWD, UART, SPI, etc.) for each component should be shown in assembly drawing.

9. Is checksum or version control specified for each programmable component?​

To avoid confusion during firmware or configuration changes, checksum, CRC value, or version number should be defined for each programmable component. This information is checked during post-flash verification step.

Checksum or version information should be automatically recorded in both test software and production report. This practice ensures test results match correct software version and maintains traceability principle.

Price and Availability (Procurement Viability)​

10. Are price and stock status of all components verified?​

Price and stock status of each component should be verified through current supplier data before production. During mass production planning, price analyses should be made including not only unit cost but also minimum order quantity (MOQ), shipping, taxes, and currency effect.

Additionally, it should be ensured that components have economically and sustainable supply conditions in long term. This check is critically important to prevent cost fluctuations especially in high-volume productions.

11. Are parts with long lead time marked?​

Parts with long lead time (e.g., 8–12 weeks) should be marked as "critical component" on BOM.

This information ensures early purchasing or safety stock creation in production planning. Since lead time can differ for each manufacturer or supplier, current data should be recorded in purchasing system. Production schedule should be revised according to this duration for critical parts.

12. Are equivalents of out-of-stock components determined for production or assembly?​

Electrically, mechanically, and financially compatible equivalents should be predetermined for out-of-stock or delayed components. Following criteria should be checked when selecting alternative parts:

• Electrical equivalence (Voltage, current, tolerance, pinout),
• Mechanical compatibility (Package type, pin spacing, routing),
• Cost compatibility (Price difference should be within ±10% range).

This information should be defined in "Alternate Part / Replacement" column of BOM. Additionally, alternative part usage approval should be documented through engineering change form (ECR).

13. Are End-of-Life (EOL) or Obsolete components checked?​

Lifecycle status of all components should be checked; parts in EOL (End-of-Life) or NRND (Not Recommended for New Design) status should be removed from BOM. This information should be verified through manufacturer or supplier PCN (Product Change Notification) reports.

Alternatives to be used instead of EOL components should be added to project records. This check is critically important for long-term maintenance and production sustainability of the product.

14. Is supplier diversity available in price analysis?​

At least two supply sources should be identified for each component if possible.

This approach reduces dependency on single supplier and provides supply flexibility in emergencies. Additionally, price comparisons should be made not only on instantaneous cost but also on logistics reliability and delivery time criteria.

Supplier diversity is also accepted as part of quality system within ISO 9001 and IPC-2612 requirements.

Documentation and Traceability​

15. Are BOM revision number, date, and preparer information added?​

Revision number, date, and preparer information should be present in each BOM document.

This information is mandatory for revision tracking and version control during production process. When revision information is missing, using old BOM versions can lead to production errors. All changes should be listed in Revision History table with description and approval information.

16. Is datasheet link or page number available for each component?​

Datasheet link (URL) or page reference should be present in BOM for each component. This information is essential especially for custom manufactured, rare, or components with critical parameters. This practice enables production engineers and quality control teams quick access to technical specifications.

All links should be archived in "Documentation" folder along with project files.

17. Is BOM file prepared in electronic format?​

BOM data should be prepared not only in PDF or written form but also in digital transferable format. CSV, XLSX, or ERP/PLM compatible XML formats are preferred. This allows direct transfer to production line, inventory management, or purchasing software.

Format standard should be defined project-wide and comply with BOM Export Template document.

18. Is information in BOM exactly compatible with schematic and PCB files?​

RefDes (reference code) and quantity values on BOM should be completely compatible with schematic and PCB design. After changes made in CAD environment, updated BOM should be automatically taken from CAD software (e.g., Altium, KiCad).

RefDes differences can cause missing or excess assembly errors during production. Design–production consistency should be systematically verified with "Design–BOM Consistency Check" step.

19. Are lifecycle and revision history tracked for each component?​

Production lifecycle status of each part should be regularly tracked:

Additionally, component's own revision history (e.g., manufacturer update or package change) should be processed into project documentation. This information forms the basis for long-life production planning of the product.

20. Is AML / AVL (approved manufacturer list) created for critical parts?​

Approved Manufacturer List (AML) or Approved Vendor List (AVL) should be prepared for critical components. This list should specify approved manufacturer(s), MPNs, and alternative supply sources for each component. AML / AVL documents should be stored version-controlled within quality management system.

This practice minimizes supply chain risks and provides traceability in quality audits.

21. Are Conflict Minerals and RoHS/REACH compliance declarations added?​

For product compliance with European and US regulations, Conflict Minerals, RoHS (Restriction of Hazardous Substances), and REACH declarations should be obtained from manufacturer. These documents should be added to project documentation and stored in supplier evaluation file. Missing compliance documents can cause delays in product export or certification processes.

22. Is monitoring plan defined for EOL / NRND components?​

Monitoring plan should be created for parts in EOL (End of Life) or NRND (Not Recommended for New Design) status in BOM. This plan should include alternative component research, stock reservation, and last time buy strategies. EOL monitoring schedule should be defined as reminder in production planning software.

23. Is supply chain risk classification performed?​

All components should be separated into criticality levels according to supply risk:

This classification optimizes purchasing strategies and inventory management. Risk classification should appear as separate column in supply planning reports.

24. Is BOM data version-controlled in ERP / PLM system?​

BOM data should be stored version-controlled not only file-based but also in ERP (Enterprise Resource Planning) or PLM (Product Lifecycle Management) system. This way, each change becomes traceable with date, user, and description information. Version management provides Single Source of Truth between production, quality, and supply teams.