From a PDF in your inbox to a cited scope, ready to price.
Five steps, roughly fifteen minutes of your attention, on a manual that would otherwise take two days to read.
Create the tender, upload the documents
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.
Tenders
| Tender ID | Name | Bid due | Status |
|---|---|---|---|
| 26-104 | Riverside Medical Center | Sep 4, 2026 | Tendering |
| 26-098 | Carleton Transit Facility | Aug 27, 2026 | Quoted |
| 26-091 | Gatineau Water Treatment Upgrade | Jul 30, 2026 | Won |
Set your division scope and run extraction
Pick the divisions you're bidding. Only those pages are analysed, which keeps the run fast and the cost per tender sensible. It also means Division 01 general requirements get read properly, not 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.
Riverside Medical Center
Review the draft against the source
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.
Take off quantities on the drawings
Draw areas, linear runs and counts straight on the sheet, in the same tender file as the scope, so a quantity and the clause that governs it never end up living in two different tabs. Every shape snaps to the drawing's own vector linework — the same lines the sheet was drawn with — so a boundary comes out traced, not sketched.
Items split into sub-items the way a pour actually gets split — by pour, then by thickness within it — and concrete volume rolls up automatically from each piece's own area and depth. A purpose-built boundary-cut tool gets the perimeter right where an ordinary deduction doesn't: on a real 20-notch loading-dock slab, the two methods agree on area and disagree by 38% on perimeter, because an ordinary cutout counts no edge at all.
Quantities only, deliberately. No cost database, no pricing — where you price the job stays exactly where it already lives.
Export the confirmed scope for your bid
Export the confirmed scope two ways: a CSV working file listing every item and its status, so nothing that got excluded disappears without a trace — or a clean bid-letter export with confirmed items only, ready for your bid form, your estimate template, or the qualifications page nobody wants to write at midnight.
Fifteen minutes and one real manual is the whole test.
No credit card, no sales call, no data leaving Canada.
