EC-24.1 From Schematic to Netlist: Capture, Symbols and Choosing Parts
The standard opening treatment of schematic capture: readable drawings, symbols and footprints, the netlist, part selection and the bill of materials, September 2026
What this is and why it exists
The introduction module taught you to read a schematic. This one is about drawing one other people will build from.
That is a different job with different failure modes. A drawing only you can follow is not finished, because a reviewer cannot find the mistake and a manufacturer cannot check the result.
Almost every board that arrives unusable failed at this stage. A footprint that does not match the part. A pin one marker in the wrong corner. A component that stopped being made between design and production.
The vocabulary
- Capture — drawing the schematic in a tool that can produce a netlist.
- Symbol — the drawn representation of a component, with numbered pins.
- Footprint — the copper pattern the physical part will be soldered to.
- Netlist — the machine-readable list of which pins are connected.
- Reference designator — the label identifying one component on the board.
- Hierarchy — organising a schematic into sheets, one function each.
- Bill of materials — the orderable list of what goes on the board.
- Lifecycle status — whether a part is new, mature or being discontinued.
The mental model
A readable schematic follows conventions rather than taste. Signal flows left to right. Supplies go up, grounds go down. One function per sheet. Nets are named rather than dragged across the page as long wires. None of this affects the netlist, and all of it affects whether anybody can review the drawing.
The symbol and the footprint are the two halves of a library part, and they are connected only by the pin numbering you entered. Get that mapping wrong and the tool will faithfully produce a board that connects the wrong pins. Checking the numbering against the manufacturer's own drawing catches the most expensive class of mistake there is.
The netlist is the contract. Everything the layout tool knows about connectivity comes from it, and a mistake in the schematic is manufactured faithfully. On a small board, reading the netlist directly is a fast and surprisingly effective check.
Choosing parts is not the same as finding parts. A component with one supplier and a long lead time is a risk to the whole product, whatever its specification. Stock levels and lifecycle status belong in the selection decision, not in a purchasing conversation six months later.
The bill of materials is what turns a design into an order. A reference designator, a quantity, a manufacturer part number and a description are the minimum somebody needs. A list of values with no part numbers guarantees that the wrong components arrive.
Finally, run the schematic checks before laying anything out. Unconnected pins, outputs driving outputs and missing supplies are caught in seconds. Finding them here rather than on a manufactured board saves a revision.
What you should now be able to explain or do
- Draw a schematic that follows the conventions a reviewer expects.
- Build a library part and verify its symbol against its footprint.
- Explain what the netlist is and why it is the contract with layout.
- Choose a component on availability and lifecycle as well as specification.
- Write a bill of materials somebody else could order from.
- Run and interpret a schematic-level design rule check.
Check yourself
What connects a symbol to its footprint?
Only the pin numbering you entered. If that mapping is wrong, the board is manufactured with the wrong connections and nothing else will catch it.
Why check availability during selection rather than at purchasing?
Because changing a part later can change its footprint, its behaviour and the layout. Discovering an unavailable component after layout costs a revision.
What is the minimum a bill of materials must contain?
A reference designator, a quantity, a manufacturer part number and a description. Values alone are not orderable and lead to the wrong parts arriving.
Why read the netlist directly on a small board?
Because it is what the layout tool actually uses. Reading it checks the connectivity you meant, rather than the drawing you think you made.
Go deeper
We haven't checked most of these for screen reader use yet.
Back to From Schematic to Netlist: Capture, Symbols and Choosing Parts: work through the checklist