Key takeaways
- A prototype proves the design works; DFM/DFT proves it can be built and tested at volume.
- Run the review before design release — fixing a footprint on paper costs minutes, on a panel it costs a respin.
- Group the 23 checks into six categories so nothing falls between disciplines.
- Test access is the most-skipped category and the most expensive to retrofit.
- Bring your EMS into the review early — their line constraints shape several checks.
Why a prototype is not a product
A hand-assembled prototype tolerates things a production line will not: a tweezer-placed 0201, a reworked footprint, a single board nobody had to test in 30 seconds. Volume manufacturing removes that slack. The DFM/DFT review is the disciplined pass that finds those weak points while they are still cheap to fix — on the schematic and layout, not on a populated panel.
Run it as a formal gate before design release. Below are 23 checks we apply, grouped so each engineering discipline owns its share.
The 23-point checklist, by category
| Category | # | Check |
|---|---|---|
| Footprints & land patterns | 1 | Footprints match IPC-7351 land patterns for the chosen package |
| 2 | Pad-to-pad spacing supports the assembly line’s minimum, not just the datasheet | |
| 3 | Polarity and pin-1 markers present on silkscreen and assembly drawing | |
| 4 | Courtyards prevent component-body collisions at placement tolerance | |
| Tolerances & spacing | 5 | Trace width / spacing meet the fab’s class without exception waivers |
| 6 | Annular ring and drill sizes within standard capability | |
| 7 | Solder-mask dam width holds between fine-pitch pins | |
| 8 | Component-to-edge clearance respects depaneling tooling | |
| Panelization | 9 | Panel format (tab-route vs V-score) chosen for the line and the board |
| 10 | Fiducials present at panel and board level for vision systems | |
| 11 | Tooling holes and rails sized for the assembler’s conveyor | |
| 12 | Break-away stress kept away from sensitive components (e.g. crystals, BGAs) | |
| Test access (DFT) | 13 | Test points on every net you need to verify, at probe-able size and pitch |
| 14 | Single-sided probing where possible to cut fixture cost | |
| 15 | Boundary-scan / JTAG chain accessible for digital coverage | |
| 16 | Programming and debug headers reachable in-fixture | |
| Thermal & RF clearances | 17 | Thermal reliefs / copper pours sized for reflow and in-service heat |
| 18 | Keep-outs honored under and around the antenna | |
| 19 | Ground stitching and reference planes continuous under RF traces | |
| 20 | High-power parts spaced for derating and rework access | |
| Documentation & BOM | 21 | BOM has approved manufacturer part numbers, not generic descriptions |
| 22 | Assembly drawing, pick-and-place and Gerber/ODB++ agree with each other | |
| 23 | Revision control and change history on every released artifact |
The category that trips most teams: test access
Footprint and tolerance errors are caught by fab DRC tools. Test access is not — and it is the category teams most often defer. The result is a board that builds perfectly and cannot be verified at speed, forcing manual benches or, worse, shipping untested units. Decide your test strategy (in-circuit, flying-probe, functional, boundary-scan) before layout, then reserve the test points and access it needs. Retrofitting test access after the first panel almost always means a respin.
Bring manufacturing into the room early
Several of these checks depend on facts only your assembler knows: minimum component spacing on their placement machines, preferred panel rails, conveyor width, depaneling method. A DFM review with your EMS before design release turns those constraints from late surprises into design inputs. It is the single highest-leverage hour in the prototype-to-production transition.
Treat the checklist as a gate, not a wish list
The point of 23 named checks is accountability: each is owned, each is signed off, none is assumed. Pair the DFM/DFT review with a clear hardware development process and you convert a working prototype into a design that a line can build and a fixture can verify — repeatably, at volume.
Where Fundamentum fits
Once the design is manufacturable, the next question is operating the fleet it ships into. Fundamentum, our Canadian IoT platform, handles fleet provisioning and device identity at the line, then governed OTA and an audit trail after the unit leaves the factory — inside a SOC 2 Type II perimeter, and able to interface with AWS, Azure or Google Cloud if your architecture requires it. See the platform →
Frequently asked questions
What’s the difference between DFM and DFT?
DFM (Design for Manufacturing) ensures the board can be built repeatably on a production line — footprints, spacing, panelization. DFT (Design for Test) ensures it can be verified quickly — test points, probe access, boundary-scan. You need both; this checklist covers them together.
When should I run a DFM review?
Before design release, as a formal gate — not after the first panel comes back. Catching a footprint or test-access issue on the layout costs minutes; catching it on a populated panel costs a respin and weeks of schedule.
Why is test access the most-skipped category?
Because fab DRC tools catch footprint and tolerance errors automatically, but nothing automatically flags missing test points. Teams defer test strategy and discover too late that a board builds perfectly yet can’t be verified at speed. Decide your test approach before layout.
Should my EMS be involved in the DFM review?
Yes — early. Several checks depend on facts only your assembler knows: minimum component spacing on their machines, preferred panel rails, conveyor width, depaneling method. An EMS DFM review before design release turns those constraints into design inputs instead of late surprises.
Does a 23-point checklist apply to a simple board?
The categories always apply; the depth scales with complexity. A simple two-layer sensor board may clear many checks trivially, but you still want each explicitly signed off rather than assumed. The value is accountability — nothing falls between disciplines.
Related reading
Talk to an IoT engineer — free
Book a FREE 30-minute consultation with our team. No slides, no obligation — a working session on your connectivity, platform or compliance questions.
