Glossary
Three sets of words in Structured AI look interchangeable and aren't. Those are worth learning; the rest of this page is reference.
Findings and markups
| Term | What it is |
|---|---|
| Issue | Anything flagged on a project, whatever raised it. The one triage table. |
| Finding | An issue raised by an automated check, with evidence cited on the sheet. |
| Comment | An issue a person placed by hand, or one imported from a reviewer's markup set. |
| Criteria | The rule a check evaluates. A check has criteria; a run of it produces findings. |
The distinction that matters: findings and comments both become issues and are triaged together, on purpose, so nothing gets reviewed twice. See Issues.
Checks and the things made of checks
| Term | What it is |
|---|---|
| Check | One question asked of the drawings. "Does every door have a fire rating?" |
| Custom check | A check you built, rather than one from our library. |
| Checklist | A list of checks, usually imported from a document your firm already uses. Kept in your library and runnable on any project. |
| Workflow | A saved multi-step review procedure - a sequence, not a list. |
| Check library | The checks your organization has, grouped by discipline. |
The distinction that matters: a check answers one question, a checklist works a list of them - and every check you create lives in one - and a workflow is a whole procedure. See Checklists & custom checks, Workflows.
Projects and documents
| Term | What it is |
|---|---|
| Project | One job. Holds every document, revision, finding, markup and output for it. |
| Document | One file in a project. Identified by its folder path as well as its name. |
| Sheet / page | One page of a document. |
| Version chain | The sequence of revisions of the same set. What Compare Versions diffs. |
| Project stage | Where the project is in its design life, with an optional percent complete. |
| Control set | A reference or template set another set is verified against. |
The distinction that matters: a new revision is a document in a version chain, not a new project. Getting that right is what makes comparison work. Chains are proposed automatically; you can correct one from the Files panel's right-click menu. See Organize, which is switched on per organization.
Organization
| Term | What it is |
|---|---|
| Organization | Your firm's account. |
| Org owner | Runs it: invites, roles, grants, org-wide approvals. |
| Member | The normal role. |
| External collaborator | Someone outside your firm, scoped to what they've been given. |
| Team | A named group - office, discipline, client, market - that people belong to and work can be shared with. |
| Sub-team | A team nested beneath another team, as deep as your organization needs. Behaves like a team: its own page, members and queue. |
| Team lead | Approves what's shared with their team and curates its page. |
| Team page | A team's page: its checklists, workflows, resources and codes. |
| Steward | Approves code books into the organization's library. |
See How access works.
Everything else
| Term | What it is |
|---|---|
| Citation | The link from a finding or an answer to the exact spot on a sheet. Every finding has one. |
| Board | A shared canvas in a project for sketching and marking up beside the drawings. |
| Generated output | Anything the platform produced for you: a report, spreadsheet, annotated set, letter, or filled-in form. |
| Project memory | Facts you've told the chat about how to work this project. Applied to conversations and to check runs. |
| Review intent | What you're reviewing for on this project, in your own words. Steers which checks run. |
| Run | One execution of a check, comparison, audit or agent task. |
| Annotated set | Your drawings exported with every finding marked and numbered. |
| Plan-review letter | The formal numbered comment letter that matches an annotated set. |