Measure the review against your change log

For review leads: use the team's own change log as ground truth to see what the review catches and misses — and seed new checks.

View as Markdown (for AI/KB) Whole knowledge base (llms.txt)

This page is for whoever owns the quality of the review.

The best ground truth for a review is what was actually fixed in the design. Probe’s design log lets you measure the review against the team’s own change log.

Why the change log is the best ground truth

The designer’s change log lists the faults that really existed and were fixed. Measuring the review against it shows you not just what Probe found, but what it should have found.

Import the log

You import the change log with a column map and tie it to a revision. Probe then sets the review against the log and shows what both found and what’s only in the log (i.e. was missed).

Judge and seed new checks

For each row, a reader judges whether the review found or missed the fault. The misses can be classed into fault classes and used to seed rule drafts — so what a review missed once becomes a check the next time.


Related: the rulebook and the guides.

Probe is E-Sharp’s design-review engine. The review is calibrated against what was really fixed, not against a feeling.

Book a demo of Probe

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

Prefer to email? info@esharp.se