Accuracy

How we test accuracy

Accuracy is the first question everyone asks, and it should be. Here's exactly what OneRound checks, how we test it today, and where its limits are.

What every review checks

The review follows a written standard: a GC project engineer's review playbook, plus trade checklists for the deepest sections (see coverage).

How we test it today

We built a fictional misc metals test package, Acme Misc Metals, with 10 problems planted on purpose: the kinds of issues that get real submittals returned. On that test package, OneRound caught all 10. You can see the full result in the sample report.

A planted test is a starting point, not proof on real work. That's what the beta is for: trades are running real packages and telling us what the review caught, what it missed and what the architect returned. We'll publish those results once we have enough real reviews to be meaningful, and we won't publish numbers we can't back up.

Rules the review follows

Known limits

When it misses

That's what the OneRound Guarantee is for. Fix everything in your paid report, and if the architect still returns it Revise and Resubmit for something we should have caught, we'll refund that report or re-review your resubmittal free. Every report also has a feedback box, and every miss you report goes straight into the next version of the review.

Check your package before the architect does.

Upload your spec section and submittal. The first check is free, with no account.

Check my submittal free See a sample report