Circuit Board Design Workflow From Start to Finish

Designing a circuit board is a sequence of decisions where each one narrows the options for the next. Teams that treat it as a single activity end up revisiting decisions they thought were finished, and the schedule absorbs the cost. The workflow below is the sequence that minimises that rework, and every step in it produces something the next step depends on.

Requirement Analysis

The first step is a written statement of what the board has to do. That includes the functions, the performance targets, the interfaces, the supply arrangement and the environmental conditions. It also includes the constraints that come from outside the electronics: the enclosure, the connector positions, the mounting points and the height available for components.

Requirement analysis is also where the cost target and the production volume are recorded, because both influence decisions that follow. A board built in hundreds can be assembled by hand or with a simple process; the same board built in hundreds of thousands justifies tooling, test fixtures and a design optimised for a machine. Discovering the volume after the layout is complete usually means redesigning the panel and the test access.

Component Library Preparation

Before the schematic is drawn, the library has to be ready. A component library contains the schematic symbols, the footprints and the links between them, and every one of those elements has to be verified against the manufacturer data. A footprint that is one pad pitch too narrow produces a board that cannot be assembled, and the error is invisible in the schematic because the connection is correct.

Library work is unglamorous and it is where a large share of avoidable errors originate. The discipline that pays is to verify each new footprint against the mechanical drawing before it is used, and to keep the verified parts in a controlled library rather than allowing each project to create its own variant. The dimensional rules that a footprint has to satisfy are described in this article on PCB pad design standards.

Schematic Capture and Netlist

The schematic expresses the logical connections between components without reference to their positions. It should be drawn so that it can be read: signals flowing left to right, supplies shown at the top, grounds at the bottom, and functional blocks separated visually as well as logically.

The netlist derived from the schematic is the contract that the layout implements. It should be verified before layout begins, because an error in it propagates into everything downstream and cannot be corrected by layout work. The common checks are that every net is connected to at least two pins, that no pin is left unconnected without a documented reason, and that the power and ground connections follow the intended architecture rather than being distributed by default. The relationship between the schematic and the fabrication data is described further in this discussion of PCB design and fabrication.

Layout in Stages

Layout is best executed in stages with a review at each boundary. The mechanical stage fixes the outline, the mounting features and the keepout regions. The placement stage positions the connectors, the core device, the power section, the clock and analog groups and the interfaces, in that order. The power stage routes the supply and ground, which are the least flexible nets. The signal stage routes the remainder, starting with the fastest and most sensitive nets.

Reviewing between stages is what makes the sequence work, because a problem found after placement costs minutes to fix while the same problem found after routing costs hours. The specific items to check at each stage are the ones set out in this article on placement order and pad positioning.

Verification

Verification covers more than the connectivity check built into the layout tool. It includes the impedance of controlled nets, the length matching of any group that must arrive together, the current capacity of the power paths, the thermal behaviour of the components that dissipate power and the emissions behaviour of the fastest nets. Some of those can be checked analytically, and some require a prototype.

A useful verification practice is to review the artwork itself rather than the design rules report. Looking at the ground plane, the return paths and the clearances on the finished artwork catches things that a rule check will not, particularly the cases where a rule was satisfied but the intent was not. Where the design includes a fast interface, the routing techniques described in this article on PCB routing techniques should be verified on the actual geometry.

Release and Documentation

The design is released when it can be built and tested without further explanation. That means a current schematic, an artwork set generated from the released version, a stackup drawing with materials and thicknesses, fabrication and assembly drawings, a bill of materials with approved alternatives, and a test programme. Any deliberate departure from the standard rules should be recorded with its reason, so that a reviewer or a fabricator does not mistake it for an oversight.

Documentation is what makes the second revision cheaper than the first, and it is also what allows a different engineer to maintain the product. The engineering outputs that must accompany a design are described in this discussion of PCB design guidelines.

Schedule Control

Most of the schedule in a board design is consumed by work that is repeated rather than work that is new. Re-drawing a footprint, re-routing a block that was placed before a constraint was known, and re-checking a design after a late schematic change are the three largest contributors. Each of them is reduced by the same measure: settle the inputs before starting the corresponding stage, and review between stages rather than at the end. The practices that shorten the process furthest are described in this article on multilayer design rules.

Inputs That Must Be Settled Early

Three inputs determine how much of the workflow can proceed without interruption: the mechanical envelope, the interface list and the power architecture. Where any of them is still moving, the corresponding part of the layout will be provisional, and provisional work is work that gets repeated. Recording which inputs are considered frozen and which are still open is a simple practice that prevents a great deal of wasted effort, because it tells the designer which decisions are safe to build on.

It also helps to define what “frozen” means for each input. A mechanical drawing that is pending a small change to a mounting boss is effectively frozen for placement purposes, while a connector that has not been selected is not. Distinguishing between the two allows the layout to start earlier without risking the parts of the design that depend on the undecided items.

FAQ

What is the most common cause of rework in a board design? Requirements that were discovered late. The enclosure dimensions, the connector positions, the production volume and the test method all constrain the layout, and each of them is expensive to accommodate after the layout is complete.

Why is the component library separate from the schematic work? Because a footprint error is invisible in the schematic and only appears when the board is assembled. Verifying the library once, against the manufacturer data, prevents that error from being repeated on every project that uses the same part.

When should layout start? After the netlist has been verified and the mechanical envelope is known, not before. Starting the layout against an unsettled netlist or an unsettled outline guarantees that part of the work will have to be repeated.