← Insights

Design review

Review a board without a CAD licence

A review rarely fails on engineering skill, but on what the reviewer is allowed to do with the board. Looking is solved — asking is what's missing.

2026-07-24 · 6 min · Article

Most design reviews don’t fail on judgement. They fail on what the reviewer is allowed to do with the board. Seeing a design is a solved problem — viewers are everywhere, often free. What’s scarce is being able to act on the design.

A viewer shows shapes and net names. It can’t follow a signal through a series resistor and a plane to where it actually lands. It can’t tell you one pin is a supply and another an open-drain output. It can’t check a supply resistor against the device’s operating current. And the findings end up in a comment thread or a meeting, detached from the net they concern, and gone by the next revision.

What a review without a CAD licence needs

The real board, open to every reviewer. Real connectivity and real components, without a CAD seat and without the designer at the wheel.

A board you can ask. Follow nets through passives and buffers, see which functional block a component belongs to, and find unconnected inputs, undriven pins and supplies that can’t deliver current. A viewer lets you look; a review requires you to ask.

Findings fixed to the design, not to a page. A finding pinned at a net or a component — say U12 pin 14 on net P1V8_VCCO — can be acted on. A finding in a thread can’t.

Findings that carry evidence and persist. The difference between “this looks wrong” and a record: a supply pin reaches its supply only through a 200 kΩ resistor, and the datasheet page says the device needs more current. The record should outlive the meeting and still be there at the next revision.

None of this requires the tool that drew the board. It requires reading the board as a design, not as a drawing.

Why the single-CAD-seat review stalls

Routing the review through the one person with a full CAD seat has four costs. The review goes single-threaded — everyone waits for a driver, and the reviewers with the sharpest questions wait most. It gets late and then rushed, because setting up a session is a chore, so it’s pushed to just before release. The feedback gets shallow, because you can only comment on what’s shown on screen. And the discipline erodes — a process that’s a chore gets run worse over time.

Give every reviewer a board they can open and ask, and the bottleneck disappears instead of the checklist needing to get better.

ODB++ makes it neutral

ODB++ is the neutral manufacturing format the design already produces for the board shop. It’s already in the flow — no new export step. It’s tool-neutral — one review process covers a mixed toolchain and an EMS handover. And it carries connectivity, not just geometry: it describes nets and components, which an askable review needs and a flat image or a Gerber set can’t give. More on that in ODB++ or Gerber for review.

How Probe does it

Probe reads ODB++ — or an early schematic and a BOM before the layout exists. The board opens to every reviewer without a CAD licence. You follow a net through connectors and planes to where it lands, see the function a component belongs to, and search the whole board. Findings are fixed to the net or component and carry their evidence — checked, not claimed. The review is unlimited, and self-hosting keeps design data on your network. Probe reads the neutral ODB++ export and isn’t tied to a CAD tool; verified exporters are Xpedition/PADS, Allegro, KiCad, Altium and OrCAD.

Better checklists and more discipline can’t fix a review where the board is an inert object. The solution is a board reviewers can ask, and findings that stay put.

Want to try? Book a session — we load schematic, BOM and ODB++ (or just schematic and BOM for a pre-layout design) and run a review live.

Book a demo of Probe

Show us your board — we review it and go through the findings together.

Prefer to email? info@esharp.se