How to Verify a Netlist and BOM Automatically (Before Layout)

By Joseph Ogbonna
Updated November 6, 2026
Circuit schematic beside a bill of materials spreadsheet, accompanying a guide on how to verify a netlist and BOM automatically.

Netlist verification before layout means checking that every net, pin, and part in your exported netlist and BOM (bill of materials) is connected, rated, and specified the way the component datasheets require.

The reliable way to automate it is to export the netlist and a BOM with manufacturer part numbers from the same schematic revision, run both through a checker that cross-references connectivity, voltages, and part data, and then review the flagged items as a team.

Most hardware teams already run an ERC (electrical rules check) in their ECAD (electronic computer-aided design) tool.

ERC only sees symbol pin types, though, so a 4.7 kΩ pull-up that is too weak for a heavily loaded fast-mode I2C (Inter-Integrated Circuit) bus, or a BOM line whose part number disagrees with the schematic value, passes without a warning.

The sections below cover which checks matter, how to automate them, and where each type of tool stops before PCB (printed circuit board) layout begins.

What Does Netlist Verification Check Before Layout?

Netlist verification checks that every connection in the schematic is complete, intentional and electrically valid for the parts on it.

In practice, that means six groups of checks: single-pin nets and floating inputs, power and ground pin connections, net name mismatches, pin assignments against the datasheet, voltage domain crossings, and pull-up values on communication buses.

Each group catches a different class of error, and most of them are invisible to a standard ERC.

How Do You Find Single-Pin Nets and Floating Inputs?

A single-pin net is a named net that touches only one pin, and it almost always means a missing wire, a mistyped label, or a sheet port that was never connected.

A netlist checker finds them by counting the pins on every net and listing any net with a count of one, along with every input pin that has no driver.

A typical example is a RESET_N input on an MCU (microcontroller) that carries a net label on its own sheet, while the reset supervisor on another sheet drives a net spelled differently.

Floating inputs matter beyond logic errors.

Texas Instruments’ application report Implications of Slow or Floating CMOS Inputs shows an 18-bit transceiver with 36 floating I/O pins drawing 150 mA to 200 mA from VCC, and it notes that slow or floating inputs can make outputs oscillate.

The same report recommends holding unused inputs at a valid logic level with a pull-up or pull-down resistor, suggesting 1 kΩ to 10 kΩ for bus lines.

How Do You Check Power and Ground Pin Connections?

Every power and ground pin on every IC (integrated circuit) must land on the correct rail, and every supply pin pair needs its decoupling capacitor on the same net.

Multi-supply parts are where this breaks most often, because a device can have separate VDD, AVDD, VDDIO, and VCORE pins that each expect a different rail or filter.

A common miss is an AVDD pin tied to a net that looks right by name but is fed from a different regulator than the datasheet sequencing assumes.

Decoupling is the second half of this check.

Microchip’s dsPIC33CK512MP608 family datasheet, for example, requires decoupling capacitors on every pair of power supply pins (VDD/VSS and AVDD/AVSS) and recommends a 0.1 µF (100 nF), 10 V to 20 V ceramic capacitor.

A netlist check can confirm that each supply pin shares a net with a capacitor to ground, while physical placement close to the pin remains a layout check.

How Do You Catch Net Name Mismatches?

Net name mismatches happen when two labels that should be the same net differ by a character, so the ECAD tool silently creates two separate nets.

Typical examples are I2C_SDA on one sheet and I2C1_SDA on another, or a power symbol named 3V3 on the processor sheet and +3.3V on the regulator sheet.

Neither error triggers an ERC violation if each net still has at least one driver and one load.

An automated check compares every net name against every other name and flags near-duplicates, such as names that differ only by a space, an underscore, a suffix or letter case.

It also flags hierarchical ports and off-sheet connectors that exist on only one sheet, which is the usual sign of a broken connection between sheets.

How Do You Verify Pin Assignments Against the Datasheet?

Pin assignment verification compares the net on each pin with the function the datasheet gives that pin number, for the exact package on the BOM.

This is the check that catches a UART (universal asynchronous receiver-transmitter) wired TX to TX, a strap pin left in the wrong boot state, or an exposed thermal pad that was never tied to ground.

Package variants are a frequent source of errors, because the same device can have a different pinout in a QFN (quad flat no-lead) package and a TSSOP (thin shrink small outline package).

MCUs and FPGAs (field-programmable gate arrays) add another layer.

A peripheral signal such as SPI (Serial Peripheral Interface) SCK must sit on a pin that can actually be muxed to that function, and pins the datasheet marks as “do not connect” must stay unconnected.

ERC cannot see any of this, because it only knows the electrical type assigned to each symbol pin, not what the manufacturer specifies.

How Do You Detect Voltage Domain Mismatches?

Voltage domain checks trace each signal from its driver to its receivers and confirm that the driver’s output levels suit the receiver’s supply voltage and input tolerance.

Texas Instruments’ Selecting the Right Level-Translation Solution sets three conditions for a valid interface: the driver’s VOH must exceed the receiver’s VIH, the driver’s VOL must be below the receiver’s VIL, and the driver’s output must not exceed the receiver’s I/O voltage tolerance.

A classic failure is a 3.3 V sensor output wired straight into a 1.8 V processor input with no level shifter.

The same TI report explains that some inputs are overvoltage tolerant, and you can identify them because their maximum input voltage in the datasheet is independent of VCC.

An automated check needs the rail voltage of every net and the input ratings of every receiver, which is why it depends on datasheet data rather than on the schematic alone.

How Do You Check Pull-Up Values on I2C and Other Buses?

A pull-up check confirms that the resistor on each open-drain line falls between the minimum value the drivers can sink and the maximum value that still meets the bus rise time.

TI’s I2C Bus Pullup Resistor Calculation gives the limits as Rp(min) = (VCC − VOL(max)) / IOL and Rp(max) = tr / (0.8473 × Cb).

For a fast-mode bus at 3.3 V with 200 pF of bus capacitance, TI’s worked example gives a valid range of about 967 Ω to 1.77 kΩ.

A 4.7 kΩ pull-up on that bus produces a rise time of roughly 800 ns, well beyond the 300 ns fast-mode limit in the same document.

The opposite error is just as common: when two modules each add their own 1.5 kΩ pull-ups, the parallel value of 750 Ω drops below Rp(min), and the drivers can no longer pull the line low enough.

How Do You Check a Netlist and BOM for Inconsistencies?

You check a netlist and BOM for inconsistencies by matching the two files on reference designator, then comparing the part data on each line with what the schematic and its nets expect.

Every reference designator in the netlist should appear exactly once in the BOM, every BOM reference designator should exist in the netlist, and the part number, value, package, and DNP (do not populate) status should agree.

This cross-check matters because the BOM is what the assembler builds, while the netlist is what the layout follows, so any disagreement between them ends up on the physical board.

Do the Reference Designators Match in Both Files?

Reference designators match when the set of designators in the netlist and the set in the BOM are identical, with no orphans and no duplicates on either side.

Orphans usually appear after a late schematic change: a capacitor added to the schematic but never added to a hand-edited BOM, or a resistor deleted from the schematic that still sits on a BOM line.

Duplicates appear when designators are reannotated on one file but not the other, so C12 refers to a 100 nF decoupling capacitor in the netlist and a 10 µF bulk capacitor in the BOM.

A related BOM verification check compares the quantity column with the number of designators on each line.

A line that says quantity 4 but lists C12, C13, and C14 is a sign that someone edited the BOM by hand, and it should be reconciled before purchasing or layout.

Are DNP and Variant Settings Consistent?

DNP settings are consistent when every part marked do not populate in the BOM is also optional in the circuit, meaning the design still works without it.

The dangerous case is a DNP resistor that turns out to be the only pull-up on a reset or enable line, which leaves that input floating on the assembled board.

Another is a pair of 0 Ω option resistors where the BOM populates both, shorting two rails that were meant to be alternatives.

Variant builds make this harder, because one schematic can produce several BOMs, for example a base model and a version with an extra CAN (Controller Area Network) transceiver.

Each variant BOM should be cross-checked against the netlist separately, since an error that is harmless in one variant can leave a net undriven in another.

Does Each Part Number Match the Schematic Value and Footprint?

Each MPN (manufacturer part number) in the BOM must describe the same component the schematic shows: the same value, a rating that suits its net, and a package that matches the footprint and symbol pinout.

A common mismatch is a resistor line whose MPN is a 1 kΩ part while the schematic value reads 10 kΩ, often because a similar row was copied and only the description was edited.

Ratings are the next layer: a 6.3 V capacitor on a 12 V input rail, or an LDO (low-dropout regulator) with a fixed 3.3 V output whose output net is named 1V8, will pass any connectivity check and still fail on the bench.

Package checks catch an MPN for a five-pin SOT-23 regulator placed on a symbol drawn for the six-pin version, where the pin numbers no longer line up.

BOM and netlist analysis can also flag parts whose lifecycle status is obsolete or not recommended for new designs, which is cheaper to fix before layout than after the first build.

Generic passive entries such as “10k 0402” with no MPN cannot be checked for tolerance, power rating or voltage rating at all, so they should be resolved to real part numbers first.

How Do You Analyze a BOM and Netlist Automatically?

To analyze a BOM and netlist automatically, export both files from the same schematic revision, feed them to a checker that parses connectivity and part data, let it pull datasheet parameters for each MPN, and review the flagged items by severity.

The workflow has four stages, and the first two, export and BOM preparation, decide how useful the results of the last two will be.

A clean export and a complete BOM are what make the results trustworthy.

Which Netlist Should You Export?

Export the netlist directly from the released schematic revision, in a format your checker can parse, and never from a layout database that may already contain manual edits.

Most ECAD tools offer several netlist formats, and the right one is the format that keeps reference designators, pin numbers and full net names intact.

Flattened net names from hierarchical designs should stay unique, so a local net called EN on two different sheets does not merge into one net during export.

Record the schematic revision in the netlist file name and in the BOM, so the two files can be matched later without guesswork.

How Should You Prepare the BOM for Automated Checks?

Prepare the BOM so that every reference designator has at least one MPN, a manufacturer name and a clear populate or DNP status.

Automated checks read ratings, packages and pinouts from the part number, so a line with only a value and a package size gives the checker nothing to verify.

Keep one consistent structure throughout, either one row per reference designator or grouped rows with a designator list, and avoid merged cells or notes typed into the MPN column.

If you allow alternate parts, list them in their own column, because an alternate with a different pinout or voltage rating needs the same checks as the primary part.

What Should an Automated Netlist Checker Run?

An automated netlist checker should run every connectivity, datasheet and BOM cross-check that a careful reviewer would do by hand, on every net and every part.

At a minimum, the run should cover this checklist:

  • Single-pin nets, undriven inputs and unconnected pins not marked as no-connect
  • Supply and ground pins on the correct rails, with decoupling on every supply pin pair
  • Near-duplicate net names and one-sided hierarchical ports
  • Pin functions, strap pins and exposed pads against the datasheet for the exact package
  • Driver and receiver voltage levels on every net that crosses a voltage domain
  • Pull-up and pull-down values on I2C, SMBus (System Management Bus), reset and enable lines
  • Reference designator, quantity, value, package and DNP agreement between netlist and BOM
  • Component ratings (voltage, current, power) against the net they sit on

How Do You Triage the Results?

Triage the report by fixing confirmed errors first, then checking warnings against the datasheet, and documenting every item you accept as intentional.

An intentional exception, such as a deliberately unconnected GPIO (general-purpose input/output) pin, should be marked with a no-connect flag in the schematic so it stops appearing in future runs.

Assign each flagged item to an owner and record the decision, because that record becomes the evidence of review that customers and auditors ask for.

Rerun the full check after every ECO (engineering change order), since a single late change can break a net that passed in the previous revision.

Which Software Checks Netlist and BOM for Inconsistencies?

Four kinds of tools check netlists and BOMs before layout: manual peer review, the ERC built into ECAD tools, custom scripts, and AI schematic analysis platforms that read component datasheets.

They differ mainly in whether they understand the parts on the schematic or only the shape of its connections.

DRC (design rule check) is often mentioned alongside them, but it checks physical layout rules such as clearances and trace widths, so it runs after the stage this article covers.

The table below compares the four approaches on the checks that matter most before layout.

MethodConnectivity checksDatasheet-level checksNetlist-to-BOM cross-checkSetup effortMain limitation
Manual peer reviewYes, by eyeYes, if the reviewer opens each datasheetPossible, but slowNoneTime and consistency on large designs
Built-in ERCYes, based on symbol pin typesNoNoLowCannot see voltages, values or ratings
Custom scriptsYes, if writtenOnly with hand-built part tablesYes, by designator and MPNHigh, with ongoing upkeepEvery rule and part must be coded
AI schematic analysisYesYes, from datasheets retrieved per MPNYesExport two filesFlags still need engineer review

The main takeaway is that ERC and scripts check structure, while datasheet-aware tools check whether the structure is correct for the specific parts used.

The KiCad schematic editor documentation describes ERC as automatic detection of incorrect and missing connections, with typical errors such as a power input pin that is not driven by any power output pin.

Nothing in that process compares a driver’s output voltage with a receiver’s rating, which is why a 3.3 V output on a 1.8 V input passes cleanly.

Manual review remains the reference standard for judgment calls, but it does not scale well to a board with hundreds of components and thousands of pins.

Most teams get the best result by combining agentic schematic review for full coverage with a focused peer review of the flagged items and the critical circuits.

What Are the Most Common Netlist and BOM Verification Mistakes?

The most common mistakes are checking files from different revisions, treating a clean ERC report as proof of a correct design, skipping DNP parts, and leaving generic passives in the BOM.

Each one either hides real errors or buries the report in false ones.

All four are process problems, so they are cheap to fix once a team knows to look for them.

Why Should the Netlist and BOM Come From the Same Revision?

The netlist and BOM must come from the same schematic revision, because any mismatch between them produces errors that do not exist on the real design and hides errors that do.

This happens most often when the BOM lives in a spreadsheet maintained by purchasing while the netlist is exported fresh from the ECAD tool.

A reviewer who sees fifty orphaned designators tends to dismiss the whole report, including the one real missing pull-up.

Generate both files in the same session, label them with the same revision, and treat a revision mismatch as a blocking error.

Why Is a Clean ERC Report Not Enough?

A clean ERC report only proves that pin types do not conflict, not that voltages, values or part choices are correct.

ERC will accept an output pin driving an input pin even when the output swings to 5 V and the input is rated for 3.6 V, because both pins carry valid electrical types.

It also has no view of the BOM, so it cannot see that the 10 kΩ resistor on the schematic was ordered as a 1 kΩ part.

Treat ERC as the first gate in pre-layout schematic review, not the last one.

Why Do DNP Parts Need Their Own Review?

DNP parts need their own review because removing a part changes the circuit, and the netlist still shows the part as connected.

A reviewer reading the schematic sees a pull-up on the enable line and moves on, without noticing that the BOM marks it as not fitted.

The safest approach is to review the circuit as built, by checking each net with all DNP parts removed, and to confirm that no net loses its only driver, pull-up or termination.

Repeat that check for every assembly variant that ships.

Why Do Generic Passives Weaken BOM Verification?

Generic passives weaken BOM verification because a line that says “100nF 0402” has no voltage rating, dielectric, tolerance, or temperature range to check.

The assembler or contract manufacturer will choose a part, and that choice may not suit the net it sits on, for example, a capacitor rated below the rail voltage.

Resolving every passive to a specific MPN before layout lets an automated check confirm ratings against each net.

It also stops two builds of the same revision from using different parts with different behavior.

How Do Automotive, Medical and Industrial Designs Change Netlist Verification?

Regulated industries need the same netlist and BOM checks, plus part-grade checks specific to the sector and a written record showing that every flagged item was reviewed.

The cost of a missed schematic error also rises sharply in these sectors, because a fix after release can mean a recall or a field repair rather than a new prototype.

The checks below are worth adding to the standard list for each industry.

What Does Automotive Hardware Add?

Automotive hardware adds part qualification checks and a stronger need for traceable verification records.

ISO 26262-5:2018 sets requirements for product development at the hardware level for safety-related electrical and electronic systems in series-production road vehicles, including hardware design and its verification.

On the BOM side, a useful automated check confirms that every MPN is the automotive-qualified version the design intends, not a commercial-grade part with a nearly identical number.

On the netlist side, CAN and LIN (Local Interconnect Network) bus lines, battery-connected inputs and wake-up pins deserve their own review, since they connect directly to the vehicle harness.

What Does Medical Device Hardware Add?

Medical device hardware adds isolation and safety checks tied to how the equipment connects to the patient and to mains power.

IEC 60601-1 is the general standard for the basic safety and essential performance of medical electrical equipment.

A netlist check can confirm that no net crosses between the patient-connected section and the mains-referenced section except through the intended isolation components.

The review record matters as much as the check itself, since the device’s design records have to show what was verified and how each finding was closed.

What Does Industrial Automation Hardware Add?

Industrial automation hardware adds checks on field-facing interfaces, because connectors to sensors and actuators are exposed to wiring faults, long cables and noise.

A practical automated check confirms that every pin on a field connector reaches some protection on its net, such as a TVS (transient voltage suppressor) diode or a series resistor, before it reaches a logic input.

Ratings checks matter here too, for example confirming that every input sitting on a 24 V field signal is rated for that voltage and not just for the logic rail behind it.

Long product lifecycles also make BOM lifecycle status checks more valuable, since an industrial controller may stay in production for many years.

Ready to Automate Netlist and BOM Checks?

Netlist verification before layout comes down to confirming that every connection is complete, every part suits its net, and the netlist and BOM describe the same board.

Automating those checks gives full coverage on every revision and leaves engineers free to focus on the judgment calls.

As an AI schematic analysis platform, CADY checks your netlist and BOM against component datasheets and more than 1,000 design rules to flag connection integrity, voltage mapping and communication protocol errors before layout begins.

The How to Use CADY page shows how to export the netlist and BOM from Altium, OrCAD, Xpedition, KiCad and other ECAD tools.

Start a free trial of CADY or contact the CADY team to run it on your own design.

Frequently Asked Questions

How do I verify a netlist before PCB layout?

Export the netlist and BOM from the same schematic revision, then check every net for single-pin connections, undriven inputs, near-duplicate names, and power pins on the wrong rail. Next, compare each pin’s connection and voltage level with its datasheet, and confirm the BOM matches the netlist by reference designator, value, package and DNP status before layout starts.

What does a netlist checker look for?

A netlist checker looks for connections that are missing, unintended or electrically invalid. Typical checks cover single-pin nets, floating inputs, unconnected power pins, near-duplicate net names and broken hierarchical ports. Datasheet-aware checkers go further, verifying pin functions, voltage levels between domains, pull-up values on buses such as I2C, and component ratings against the voltage on each net.

How do I analyze a BOM and netlist automatically?

Export the netlist and a BOM with a manufacturer part number for every reference designator, then load both into a tool that parses connectivity and retrieves datasheet data for each part. The tool cross-checks designators, values, packages, and ratings against the nets, and returns a report of errors and warnings for the design team to review and close.

Which software checks netlist and BOM for inconsistencies?

ECAD tools include ERC, which checks pin-type conflicts but not datasheet values or the BOM. Custom scripts can compare designators and part numbers. AI schematic analysis platforms such as CADY take an exported netlist and BOM, read component datasheets automatically, and check the design against more than 1,000 rules, returning an interactive report of errors and warnings.

Does ERC catch netlist and BOM errors?

ERC catches some netlist errors, such as unconnected pins, undriven power inputs, and conflicting output pins, because it works from the electrical type of each symbol pin. It does not check voltage levels, resistor values, component ratings, or datasheet pin functions, and it never reads the BOM, so netlist and BOM inconsistencies need a separate check.

About the author

Joseph Ogbonna

Joseph Ogbonna is a PCB design expert specializing in schematic capture, board layout, and design reviews for electronics products. Beyond hands-on design work, Joseph mentors aspiring hardware engineers, helping them build practical skills in circuit and PCB design.
Schematic analysis

Check your next schematic before layout

Upload your Netlist and BOM, run the analysis, and review the findings in an interactive report. We never store your Netlist or BOM files, nor train models on them.

Back to
Share this Article
Read Next

Advantages of Running CADY Analysis on Your Schematic Design Before Board Production

Before moving to production, validating your schematic through simulation testing is essential to catch issues early and save time, cost, and resources.

Common Drawing Mistakes in Schematic Design and How to Avoid Them

Well-designed schematics are essential for clear, efficient circuit development, as avoiding common design mistakes improves collaboration, reduces errors, and ensures smoother implementation.