From a PDF in your inbox to a priced, cited scope.

Give it your own tender number, the project name and the bid due date. Drop in the project manual, the drawings and every addendum as they're issued — single PDFs or a whole zip from the bid depository.

Documents are classified on the way in: spec, addendum, drawing set. A 900-page manual is split by CSI division with page ranges, so nothing downstream reads Division 22 when you're pricing concrete.

If a manual's table of contents doesn't parse — and real ones often don't — you set the division ranges by hand. It's a first-class part of the flow, not an error screen.

Pick the divisions you're bidding. Only those pages are analysed, which is what keeps the run fast and the cost per tender sensible — and it means Division 01 general requirements get read properly instead of skimmed.

You can also ask a narrow follow-up question against the same documents — “list every FF/FL requirement”, “where is cold-weather concreting addressed” — without re-running the whole extraction.

This is the part that matters. Every item comes with a citation and a confidence score; you work down the list, click through to the page, and mark each one reviewed, confirmed or rejected. The confidence score tells you where to look first — it is not a verdict.

When an addendum amends something you've already got, it shows up as a decision: possibly amends this item, 78% confident — confirm or reject. Once resolved it goes quiet and stops competing for your attention.

Two different numbers, never conflated: how sure the model is about the item, and how sure it is that an addendum replaces it.