Glossary
Some words in Structured look interchangeable and aren't. Each section ends with the distinction that matters; the rest of the page is reference. Use the search bar at the top to jump to any word.
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. A comment closes as Resolved (or shows as Not an issue); it can't be waived. |
| Criteria | The rule a check evaluates. A check has criteria; a run of it produces findings. |
| Issue number | The number on every issue card. By default it never changes, so re-runs leave gaps; a project setting can renumber 1 to X instead. |
| Open | An issue still to deal with. Counted in the open totals, drawn on the sheet and included in exports. |
| Resolve | Mark an issue fixed on the drawings. It leaves the open list; a later run can flag the same problem again on a new revision. |
| Waive | Close a finding that is correct but that the team is deliberately not acting on, with an optional reason (client preference, out of scope, superseded). It leaves the open counts and the drawing, and exports skip it unless you include waived issues in the export dialog. A re-run keeps it waived. Project owners and editors only. |
| Reopen | Send a resolved or waived issue back to Open. Undoes Resolve or Waive. |
| Issue status list | The statuses your issues use, with their colours: on cards, in filters, in exports and in Bluebeam. Each status counts as open, resolved or waived. An org owner can make the organization's list, and a team lead a team's own on the team's Statuses tab; a project uses its home team's list, else the organization's, else Structured's default. See Issues. |
| Feedback | A note on an issue card to the Structured team, not to your project team. It doesn't change the issue's status. Anyone on the project can send it, viewers included. |
| Not an issue | The This was not an issue (false positive) tick in Feedback. Tells us the check got it wrong; we review it and use it to correct the check. Resolve or waive the issue as well to clear it from your list. |
| Assign / My issues | Assigning puts a teammate on an issue and emails them. My issues, in the sidebar, lists everything assigned to you across every project. |
| Spelling issue | The one issue the spelling check raises per project, holding every misspelled word. Ignore adds a word to your team's dictionary so it isn't flagged again. |
| Confidence | How sure the check was of a finding: low, medium or high. Shown in the issue details and in the issues spreadsheet. |
| Verified | On a Shop Drawing Review discipline card: the results were reconciled against a schedule. A Needs review card was auto-detected and wants a spot-check. |
The distinction that matters: findings and comments both become issues and are triaged together, on purpose, so nothing gets reviewed twice. See Issues.
The distinction that matters: Waive is for your project team - the finding is right and you're choosing not to act on it, so it leaves your list. Feedback is for us - it tells the Structured team something about the finding and changes nothing on your project. If a finding is simply wrong, send Feedback with Not an issue ticked, then resolve or waive it to clear it. See Resolve, waive or reopen and Not an issue.
Severity
| Term | What it is |
|---|---|
| Severity | How much an issue matters: Critical, High, Medium or Low. Set by the check that raised it; sort and filter the issues table by it. |
| Critical | A code violation or a conflict that blocks construction; fix before issue. For example: a blocked egress path, a missing fire rating, a structural clash. |
| High | A coordination or compliance error likely to cause rework in the field. For example: a duct running through a beam, door hardware that fails accessibility. |
| Medium | An inconsistency between sheets or documents to correct in this revision. For example: a schedule that disagrees with the plan, a callout pointing to the wrong sheet. |
| Low | A drafting, labelling or documentation item with no construction impact. For example: misspellings, missing title-block fields, sheet names that drift from the sheet index. |
| Severity guide | Each check applies the four levels to its own subject, so a fire-rating check and a title-block check grade on the same scale. If a checklist grades something too high or too low for your team, say what it Should be in the Checklist editor. |
| Early-stage findings | On an early-stage project, checks don't drop or downgrade a finding because of the stage. A field that's naturally blank this early (a permit number, an approval signature) is still raised, and its description says it may be expected at this stage. |
| Summary groups | A layout of the issues panel that splits the issues into groups. Group by chooses how: Category (the default: Life safety, Code, Coordination, Revit model, then Minor / drafting, where low-severity issues always go), Label (your organization's own labels: those on the checklists, custom checks and check groups that found each issue, any added to the issue by hand, else its starter label; plus No label; see Labels on issues), Document (plus No document) or Assignee (plus Unassigned). An issue under two labels, documents or assignees appears in each of those groups. Every group header folds and unfolds, and Collapse all / Expand all fold every group at once; only Minor / drafting starts folded. The default layout when more than 30 issues are in view. |
| Significance | Compare Versions' own scale for a change between revisions: Critical, Major, Minor or Housekeeping (title block, dates, revision block; hidden by default). Older comparisons say High, Medium or Low. See Compare Versions. |
| Compare Against Control severity | Compare Against Control's scale for a difference from the control set: Critical, Major, Moderate or Minor. See Compare Against Control. |
The distinction that matters: Severity grades an issue; Significance grades a change between revisions. A Housekeeping change is not a Low issue - it isn't an issue at all until a check raises one.
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. |
| Checklist editor | Where you brief a checklist in your own words and rate the issues it found. The next run takes it in. See Checklist editor. |
| Project QAQC | The Tools-panel tool that runs consistency, completeness and coordination checks on a project. See QA/QC checks. |
| Universal QAQC | Our built-in checklist of general drawing checks, spelling and sheet layout among them, that works on any project. |
| Review intent / Just ask | What you want checked this time, typed in the Just ask box. Saved to the project and steers which checks run. See Review intent. |
| Project context | Project context for reviewers: facts about the set that every check treats as true. See Just ask or Project context? |
| Needs input | A badge on a check that needs something before it can run, such as a threshold, a standard or a missing document. The check's owner answers it. |
| Spec Audit | Checks that the drawings reflect the specifications. See Spec Audit. |
| Shop Drawing Review | Works out which drawings are under test and which they have to follow, and flags every place the two disagree. See Shop Drawing Review. |
| Comment Closure (Backcheck) | Checks each review comment against the submittal and confirms what's resolved and what still isn't. Reviewers call this step the backcheck; some firms' QC procedures call it verify or recheck. See Comment Closure. |
| Code Review | Checks the drawings against building codes in your code library. Also a source in the issues filter. See Code Review. |
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. Often called a go-by (a past project's set used as the model) or a prototype (a standard set adapted for each site). |
| Document kind | What a document is: drawing set, schedule / estimate book, specification book, report, building code, or mixed. Detected automatically; change it under Document type in the file tree. |
| Compare Versions | Lists every change between two revisions of a set, sheet by sheet, graded by significance. See Compare Versions. |
| Compare Against Control (Go-by / Reference Set) | Checks a set field by field against a control set, such as a go-by or prototype: Match, Different or Missing. See Compare Against Control. |
| Overlay | Stacks sheets on top of each other and aligns them, so you can see what moved between drawings or disciplines. See Overlay. |
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. You can set or correct a chain from the file tree's right-click menu: Mark as version of…, Manage versions… or Remove from chain. See Managing revisions.
Organization
| Term | What it is |
|---|---|
| Organization | Your firm's account. |
| Org owner | Runs it: invites, roles, grants, org-wide approvals. |
| Admin | In these docs, a Structured staff admin. Your organization has no separate admin role; the org owner is its top role. |
| Member | The normal role. |
| Viewer | Can open every project, drawing and finding they have access to, and ask questions in chat. Cannot upload, run checks, change findings or edit anything. |
| External collaborator (guest) | Someone outside your firm, such as a contractor or reviewer, invited to a specific project from its Share dialog. They can view, comment and chat, but can't run QA/QC, compare versions or upload. Org owners see them under Guests on the Organization page's Members tab. |
| Permissions | The table, on the Organization page's Settings tab, that says who in your organization may do each thing: one row per action, one column per role. Org owners tick the cells. See Permissions. |
| Custom role | A role your organization makes for itself, such as "QA lead", as an extra column in Permissions. An owner gives it to people in the Roles control on the Members tab. A new role allows nothing until its cells are ticked. See Custom roles. |
| Holding area | The Organization page tab that lists people who have issues assigned to them by email but haven't joined yet, with Invite and Reassign. They get their issues when they join. See Holding area. |
| Team | A named group - office, discipline, client, market - that people belong to and work can be shared with. A project placed in a team is open to that team's members. |
| Org tree | Your organization at the top with its teams and sub-teams below. Sharing flows down it. See The tree. |
| 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 projects, resource folders (checklists, workflows and more), codes, memory and members. See Teams. |
| Label | A tag for what something is about, like Mechanical or Telecom, on people, checklists and workflows. Labels only decide what you see first; they never give anyone access. |
| Requests | Where requests to join a team or to share something with a team or the organization wait for an answer. In the sidebar. |
| My Dashboard | Your own page, first in the sidebar: the Ask box and your pinned charts, your projects, your runs and your documents, then Memory, Labels and Settings. See My Dashboard. |
| Organization page | The page for the whole firm: its teams, members, settings and Permissions. For org owners only; anyone else who opens it is taken to My Dashboard. See Organization page. |
| Resources | The sidebar's shared library, in folders: Codes, Standards, Checklists, Workflows, My Documents, Toolbar tools and Shared documents, plus any folders your organization adds. See Resources. |
See How access works.
Everything else
| Term | What it is |
|---|---|
| Chat | Ask questions of a project's documents in plain words and get cited answers; it can also run work for you. See Chat. |
| Ask Structured | The button on an issue card that opens chat with that issue, asking it to explain the issue. |
| 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. |
| Organization memory | A house rule for your whole organization, saved only when you ask for it by name. Every member sees it; additions from anyone but the org owner wait for the owner to approve. See Memory. |
| Codes | The building code library: the Codes folder under RESOURCES in the sidebar. See Code Review. |
| Platform tour | A short guided tour of the platform. Start it from Help > Platform tour. See Getting help. |
| Create RFI | The button on an issue card, on Procore-linked projects, that drafts a Procore RFI from the issue. See Procore. |
| 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. |