How to Review a PCB Design Without a CAD License

Seeing the board was the old problem, and it’s mostly solved. A firmware engineer, a test lead, or an EMS partner can open a modern design read-only without a paid seat — read-only viewing is increasingly available, and often free. The picture is no longer scarce.

What’s scarce is everything you’d want to do with it. A viewer shows you shapes and net names. It won’t follow a signal through a series resistor and a plane to tell you where it really ends up. Nor will it tell you that pin 14 is a supply pin and pin 15 an open-drain output. And it won’t check the resistor feeding that supply against the part’s operating current. And when a reviewer does spot something, the finding lands in a comment thread or a meeting — detached from the net it’s about, and gone by the next revision.

That’s the real gap. Not access to the image, but access to the design: its connectivity, the function each component plays, and a place for findings to live that isn’t a chat log. A clean rule check won’t close it either — that’s a separate problem.

What a PCB review without a CAD license actually needs

Strip the tooling away and a good review needs four things. A read-only viewer gives you the first, half. It gives you none of the rest.

• The real board, open to every reviewer. Not a plot, not a rendering — the actual connectivity and components, available without a CAD seat or the designer driving.
• A board you can question. Trace a net across the passives and buffers in its path. See which function block a component belongs to. Find every unconnected input, every pin with no driver, every supply that can’t deliver current. A viewer lets you look; a review needs you to ask.
• Findings attached to the design, not to a page. A finding pinned to a net or a component — U12 pin 14, net P1V8_VCCO — is actionable and unambiguous. A comment on slide 7 of a PDF is neither.
• Findings that carry their proof, and that persist. “This looks wrong” is an opinion. “This supply pin reaches the rail only through a 200 kΩ resistor — here’s the datasheet page that says it needs more current” is a record. It should outlive the meeting and be there when the next revision opens.

None of this requires the tool that drew the board. All of it requires reading the board as a design rather than a drawing.

	A viewer	A review tool
Shows you	Shapes and net names	The connected design — nets, components, functions
Lets you	Look	Ask — trace a net, find undriven pins, check a supply
A finding lives	In a comment thread	Pinned to the net or component, with its proof
Next revision	Gone	Still there

Why the single-CAD-seat review still stalls

Even when reviewers can see the board, routing the review through the one person with a full CAD seat imposes four costs.

• A single-threaded review. Every “can you go to the power section and zoom in?” waits on the one driver. The review moves at one person’s pace — and the reviewers with the sharpest questions are the ones most often waiting.
• Late, then rushed. Because setting up a session is work, the review gets pushed to just before release, where deadline pressure quietly turns thorough into cursory.
• Shallow feedback. A reviewer who can only see what’s on screen can only comment on what’s on screen. The subtle issue two hops down a net never gets raised, because nobody could go and look.
• Erosion. A review process that’s tedious to run is a review process people stop running well. Discipline decays fastest where the mechanics are painful.

Give every reviewer a board they can open and interrogate on their own, and all four costs fall away at once. Not because the checklist improved — because the bottleneck is gone.

ODB++ makes it neutral

The file that makes a PCB review without a CAD license practical is one the design already produces: ODB++, the neutral fabrication format exported for the board house. Reviewing from it brings three advantages.

• It’s already in the flow. ODB++ isn’t an extra artifact created for review — it’s the same package that goes to fab. No new export step, no new burden on the designer.
• It’s tool-neutral. One review process serves a mixed toolchain and a handoff to an EMS partner, without every reviewer needing the specific CAD and version that drew the board.
• It carries connectivity, not just geometry. ODB++ describes nets and components — exactly what a queryable review needs, and exactly what a flat image or a Gerber set can’t give you.

A review workflow without a CAD license

Here’s what the review looks like once the board isn’t inert.

• 1. Export the schematic and BOM early; add ODB++ after layout. Review shouldn’t wait for a finished board — the connectivity and part choices are reviewable before any copper is placed.
• 2. Load it into a neutral review tool that reads connectivity, not just shapes. The difference between a viewer and a review tool is whether it understands the board as a netlist and a set of devices, or only as outlines.
• 3. Give every reviewer direct, parallel access. No designer in the loop to fetch views. Everyone searches the same board at the same time.
• 4. Raise findings against specific nets and components, with proof attached. The netlist line, the layout location, the datasheet value — pinned to the thing they’re about. This is also where a review checklist earns its keep: worked against the live board, not from memory.
• 5. Keep the findings. Persistent and searchable across projects, so a review becomes a record the next design can learn from instead of a thread that scrolls away.

How Probe approaches the problem

We built Probe to be that tool. It loads ODB++ — or an early-stage schematic and BOM, before layout exists — and opens the board to every reviewer without a CAD license. From there you can follow a net through connectors and planes to where it actually lands, see the function a component belongs to, and search the whole board.

Findings attach to the net or component they’re about and carry their proof: the netlist line, the layout location, the datasheet value — checked, not asserted. Reviewing is unlimited and free, and Probe self-hosts, so the design data stays on your network. It reads the neutral ODB++ export, so it isn’t tied to any one CAD tool. It’s verified today on Xpedition/PADS, Allegro and KiCad, with other ODB++ exporters supported on request.

The point

Better checklists and more discipline won’t rescue a review where the board arrives as something you can only look at. The fix isn’t a stricter process on top of an inert artifact — it’s giving reviewers a board they can question, and findings that stick. That’s what a PCB review without a CAD license should mean in 2026: not just an open board, but one the whole team can interrogate. Do that, and the rest of the review gets better on its own.