Code Review
Reviewing against the code means having the code at hand. Structured AI turns building codes into a searchable library your team shares, with tables, figures and clause numbering all kept intact.
Use case: pull up the exact occupancy table while you review a life-safety plan.
Where codes live
Open Building Codes from your account menu. That's the library - a project doesn't have its own code browser; it draws on the same books.
Two things stock it:
- A built-in catalog of common codes (IBC, NFPA and others), available without uploading anything.
- Your own uploads - the state amendment, the county ordinance, the client standard, the manufacturer manual nobody else has.
Uploading a code
Drop a PDF in and pick where it should live. This is the one decision that matters, and it's made at drop time:
| Destination | Who can see it | Use it for |
|---|---|---|
| Mine (the default) | Only you, until you ask for it to be published | Anything you're not sure about yet, and anything you'll want on the next job too |
| This project | Anyone with access to this project | A code that genuinely only applies to one job |
| Organization | Everyone, once approved | The books your firm reviews against as standard |
Mine is the default on purpose. Before it existed, a code uploaded for one job could only ever be used on that job - so somebody who uploaded a state bridge manual for one project had to upload it again for the next one. A book in Mine is private to you and reusable by you, and sharing it is a separate, deliberate act.
The destination picker at code upload
Moving a book between destinations later is a metadata change: it never re-processes the book, so you can change your mind after ingest finishes.
You can also upload several books at once rather than one at a time.
What ingestion preserves
The platform reads the book section by section and keeps:
- Tables: occupancy loads, fire-resistance ratings, fixture counts, as real tables rather than mangled text.
- Figures: diagrams and illustrations, shown inline where the code references them.
- Structure: chapters, sections and clause numbering, so a citation resolves to the exact clause.
Ingestion takes a while on a big book, and you can cancel a run that's going wrong.
Publishing to the organization
Anyone can upload. Publishing to the whole organization goes through review, because an org-wide code book is a statement about what your firm reviews against.
A book moves through four states:
Private → Pending review → Published, or Declined
- You request publication when the book is ready.
- A library steward (or an org owner) reviews the queue and either publishes it or declines it with a reason, so you know what to fix.
- You can withdraw a request while it's pending - that's also how you pull an org-destined book back to being private.
- A declined book can be fixed and re-requested.
If your organization has teams, a published book can be narrowed to specific teams, so the Texas office's amendments don't clutter the Ontario office's library. See How access works for the same pattern applied to everything else.
Browsing and searching
Navigate a code like a book or search it like a database: jump to a clause by number, search by topic, and read tables in place. Books are flagged by jurisdiction, so you can tell the 2021 IBC from your state's amended edition at a glance.
Your codes
Mark the books you actually review against as yours. It's one labelled toggle per book, and it does one thing: those books come first, and they're what the platform reaches for by default.
There is deliberately no organization-wide ranking. Which book applies is stated as a fact on the book's own row, and in the rare case where an authority genuinely allows two editions as alternatives, the choice is offered right there rather than resolved for you somewhere else.
The Library Console
For anyone managing the library rather than just reading it, the Console is the dense view: books grouped by place with a jump strip, counts per group, and a filter bar over discipline, jurisdiction, uploader and status.
- Coverage tells you what the library does and doesn't have.
- Staleness flags books that have been superseded by a newer edition.
- Saved views let you name a set of filters and come back to it - the "Ontario, published, fire" view you check every week.
- Books shared with your organization are listed; a book another member uploaded privately is shown locked, rather than hidden as if it didn't exist.
- The review queue is where a steward works through pending publication requests.
The Library Console
Codes in chat and checks
The library isn't just for reading:
- Ask the codes chat a question across the whole library: "what does the code require for corridor width at this occupancy?" It cites the clause. This one is rolling out gradually and isn't switched on for everyone yet - ask a project chat the same question in the meantime.
- Ask a project chat a code question in context, and it reasons over the drawings and the code together.
- Code-compliance checks reference the ingested code directly, so a finding points at both the spot on the drawing and the clause it breaches. Those findings land in Issues alongside everything else.
Uploading is open to everyone (books land private to you). Publishing to the organization needs a steward or an owner to approve it. Stewardship is granted per person - see How access works.