# Review before layout

> What you can review with schematic, BOM and netlist before the layout exists — and how the pre-layout take becomes an ODB++ take on the same design line.

_Source: E-Sharp (esharp.se) · Probe guide_


You don't have to wait for the layout to start reviewing. With the right material, Probe runs a meaningful review at schematic level already.

## What's required

A **pre-layout take** needs **schematic + BOM + netlist**. Then you have the connectivity (what's connected to what), the component identity (reference designators, packages) and the design intent via the schematic.

## What can be checked — and what waits

Checks that build on connectivity and device behaviour can run already: domain and voltage reasoning, open-drain in a chain, a missing pull-up, drive conflicts. Checks that need physical geometry — stackup, impedance, IR-drop, creepage — **wait for the layout** and run once an ODB++ arrives.

## From pre-layout to ODB++

When the layout is done you upload the ODB++ export as the next take on the **same design line**. What's already been worked out and still applies carries forward (see [boards, takes and the design line](/en/probe/support/boards-takes-and-the-design-line)), so the pre-layout work isn't wasted.

---

Next step: [upload an ODB++ design](/en/probe/support/upload-an-odbpp-design).

*Probe is E-Sharp's design-review engine. A rule without enough data abstains rather than passes.*
