Skip to main content

Code Review

Reviewing against the code means having the code at hand. Structured 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.

Updated video coming soonCode

Where codes live​

Open Codes and Standards at the top of the sidebar. Inside a project, the same library is under Building Codes and Standards in 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). Structured turns on access to each code family for your organization, so there's nothing to upload.
  • Your own uploads - the state amendment, the county ordinance, the client standard, the manufacturer manual nobody else has.

The library has three views: My codes (books you uploaded plus books you pinned), Org codes and All codes. Your team pages also have a Codes tab, and My Dashboard > Documents has your own uploads.

Uploading a code​

Anyone can upload. There are two ways in, and each asks where the book should go.

From the library, press Upload a code. You can upload several books at once. Under Who can use this code:

  • Only me (the default) - private to you, and reusable on any of your projects.
  • These teams - sends a share request to each team's lead. Members see it once accepted. Shown when your organization has teams.
  • Everyone - offered to org owners, and shares it with the whole organization straight away.

From a project, use Add new code in Project QAQC. Under New codes go to:

  • This project only (the default) - for a code that genuinely applies to one job.
  • Saved to my codes - private to you, and reusable on your other projects.
  • Organization library (draft) - an org owner approves it before the organization sees it.
Upload a code, with Who can use this code set to These teams and two teams ticked. Only me and Everyone are the other options

A book you added to one project can be shared to the organization library later without being read again.

Book details​

Use Edit details on a book to set its display name, edition year, place, region, document type and coverage. Reviews cite the book by the name you set here. A book's key (its short code) is not one of these details and can't be edited here.

A book's labels are changed with Labels… on its row (also in Edit details). Anyone who can add books to the organization library can label any book in it, built-in books included. A label only changes who sees the book first, never who can open it.

Once a book is shared with the whole organization, only an org owner can change those details. A team lead can still rename it: on a shared book their Edit details shows the name alone. An org owner can switch this off by letting only org owners approve organization-wide sharing (Organization → Settings).

Sharing with your organization​

Anyone can upload. Sharing with the whole organization goes through an org owner, because an org-wide code book is a statement about what your firm reviews against.

  1. Press Share on the book's row. The Share window offers Everyone in the organization and Share with a team.
  2. A request to share with everyone shows Waiting for approval until an org owner looks at it.
  3. The owner either shares it or declines it with a note telling you why. A declined book still says who has it (Private, or the teams it is shared with), with Request to share with everyone was declined under it, and you can fix it and ask again.
  4. You can Withdraw a share from the same window.

An org owner's own share goes straight through, with no review step.

Video / photo coming soon

The Share window for a code book

Sharing with a team​

If your organization has teams, you can share a private book with one or more teams instead of everyone. The team's lead approves it on the team page's Codes tab - Approve, or Review to decline with a note - and then the team's members can use it. A book shared with the organization reaches everyone, however it's tagged. 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.

Each row shows where the book applies (Applies in a place, Amends a parent code, or Amended locally in other places) and what kind of document it is: base code, local adopted code, referenced standard, federal regulation, design manual, client standard or permit condition. So you can tell the 2021 IBC from your state's amended edition at a glance.

My codes​

Use the plus at the left of a row to Add to My codes, your personal shelf. My codes is offered first when you add codes to a project. Pinning is personal: it never changes what your organization uses, and a review always reads the project's own code list.

There is deliberately no organization-wide ranking. Which book applies is stated on the book's own row. Where an authority genuinely allows two books as alternatives, the row says so ("Only one applies") and offers Use this one, rather than resolving it for you somewhere else.

Finding your way around​

For anyone managing the library rather than just reading it, the list is built to be dense: books grouped by place with a jump strip and counts per group, and a filter bar over place, document type and uploaded by, plus search. Like every list, the library starts narrowed to books that share one of your labels or carry none; the bar above it says how many are hidden, and Show all shows everything.

  • Coverage notes when a file is only part of a code (for example "Ch. 2 and 3 only"), so nobody mistakes a partial upload for the whole book. It shows as a warning everywhere the book is offered.
  • may be out of date flags a book nobody has checked against a newer edition in over a year. newer edition means a later edition is also in the library - which edition a review reads is set per project, so holding an older one isn't a mistake.
  • Saved views let you name a set of filters and come back to it - the "Ontario, fire" view you check every week. You can share a saved view with your organization.
  • used by N checks shows which books your checks rely on.
  • You see books shared with your organization, your own uploads, and books shared with your teams. Teams you aren't in are shown Locked; click one to ask its lead to add you.
  • Org owners get a Review queue of books waiting to be shared. Open one to read it, download the original PDF, and Share it or Decline with a note. Share requests also arrive in your Requests.
The Codes and Standards library with filters, groups and row markers

Codes in chat and checks​

The library isn't just for reading:

  • Run a code review on a project. In Project QAQC, the Codes section on Pick it myself lists the books on the project. Tick one and run it. Progress reads like "Reviewing · 3 of 12 areas done", and a book that's still being read starts its review on its own when it's ready. Each finding points at both the spot on the drawing and the clause it breaches, and lands in Issues alongside everything else.
  • Ask a project chat a code question in context, and it reasons over the drawings and the code together.
Who can do what

Uploading is open to everyone (books land private to you, or on the one project). Sharing with the organization needs an org owner to approve it, and sharing with a team needs that team's lead. Once a book is shared with the organization, team leads can rename it (the name only), unless your organization lets only org owners approve organization-wide sharing. Anyone who holds a book can remove it from their own codes. Deleting it for everyone is for org owners, and for a lead of a team it is shared with while it isn't shared with the whole organization. See How access works.