Skip to main content

Issues & comments

Everything flagged in a project, automated check findings and manual markups alike, lands in one list, so nothing gets reviewed twice or slips through.

The issues table​

Open Issues - it's pinned at the top of the project's Tools panel. Each card is a finding or comment with its number, severity, sheet, status, assignee and discussion thread. Click a card to jump to the exact spot on the drawing.

Narrow the list to work through a review systematically:

  • Source - All, Project QAQC, Spec Audit, Code Review or Comments.
  • Status - Unresolved, Resolved or All.
  • Severity, assignee (including Unassigned) and check.
  • Label - your organization's labels: the ones on the checklist, custom check or check group that found each issue, any added to it by hand, or its starter label. Open a card and use Add label to put a label on that one issue; see Labels on issues.
  • On this page - only the issues that cite the sheet you have open.
  • Search and sort - by newest, severity, page, assignee or issue number (low to high or high to low). Any sort other than severity shows one list in that order.

The list updates live: a colleague's assignment, status change or reply shows up without a reload.

The Issues panel with source tiles, filters and issue cards

Issue numbers​

Every issue carries a number, so a finding can be named in an email or a meeting - "number 14" - rather than described from scratch. The same number is used on the card, the drawing, the annotated export and the review letter.

By default a number never changes, so re-running a check leaves gaps in the sequence. If you'd rather have 1 to X with no gaps, open Project settings and set Issue numbering to Always number 1 to X. Numbers are then reassigned whenever a check is re-run or issues are removed, so a number you quoted earlier may point to a different issue.

Assign & track​

Assign any issue to a teammate and they're emailed straight away, with a link to each finding. Assign several at once and they get one email listing them all.

  • Discuss in the issue's comment thread so the context stays attached to the finding, not buried in email.
  • Everything assigned to you, across every project, is in My issues in the sidebar. See Requests & My issues.

Use case: assign a fire-rating issue to the architect, and watch it move to resolved.

Updated video coming soonAssign & track issues

Resolve, waive or reopen​

  • Resolve an issue once it's fixed on the drawings. Resolved findings show on the sheet as green clouds when the status filter is Resolved or All; the default Unresolved view hides them.
  • Waive it - with an optional reason - when the finding is correct but the team is deliberately not acting on it. Waived findings leave the drawing.
  • Both leave the list straight away, with an Undo. Switch the status filter to Resolved to find them again and Reopen one.

What each one does, and does not do:

  • Resolve means done. If a later run finds the same problem on a new revision, it can be flagged again.
  • Waive keeps the issue waived on this project. A re-run that finds the same finding keeps it waived; a finding worded differently can still appear. The reason is recorded for the Structured team to review. Waiving does not retrain anything or change how checks run.
  • Feedback goes to the Structured team, not to your project team.

Not an issue​

If a finding is simply wrong - a false positive - open Feedback on the card and tick This was not an issue (false positive), with a note if you like. That tells the Structured team the check got it wrong, and they review it to improve the check. It doesn't change the issue's status: resolve or waive it as well to clear it from your list.

Working on many at once​

Tick several cards and use the bar that appears to Assign, Resolve, Waive, Reopen or Comment on all of them. Comment posts the same comment to every selected issue. Feedback sends one note to the Structured team about every selected finding - it goes to us, not to your project team.

Spelling​

When the spelling check has run, a project carries one Spelling issue rather than one per word. Expand it to see every misspelled word with its suggested correction and how often it occurs. Step through the occurrences on the drawing one at a time, or click a word to jump to it. Ignore marks a word as not a misspelling and adds it to your team's dictionary, so it isn't flagged again.

Export issues​

Filter the list to the issues you want and export. Open findings are included by default; tick Resolved issues or Waived issues to add those too, and they're labelled on the sheet.

To export just some issues, tick their cards first: the export dialog then offers Export only N selected issues (on by default). Untick it to export everything the list is showing.

You can also ask the chat - for example "export all the mechanical issues". It checks that you want this zip, then selects the matching issues in the Issues tab and starts the same export for you. The export runs in the background with a progress bar, and you get a single zip containing:

  • An annotated plan set - <drawing>_annotated.pdf for each source document, with every finding marked on the sheet.
  • A plan-review letter - issue_list.pdf, a formal, numbered comment list matching the annotations.
  • A spreadsheet - issues.xlsx, the same issue list as data, for tracking outside the platform.

Send the GC an annotated PDF and a numbered comment letter from one export, and keep the spreadsheet for your own log.

The columns of issues.xlsx, in order (new columns are only ever added at the end, so macros built on the column letters keep working):

  • # - the issue's callout number, the same one on the annotated sheets.
  • Title and Description - the finding as written.
  • Severity - Critical, High, Medium or Low.
  • Status - open, resolved or waived.
  • Document - the file the issue sits on.
  • Sheet - the sheet's drawing number from its title block, or the file name when the title block was not read.
  • Sheet Name - the sheet title from its title block.
  • Check - the id of the check that raised it.
  • Also on - other sheets the same finding is marked on.
  • Confidence - how sure the check was of the finding.
  • Assignees - who it is assigned to.
Updated video coming soonExport issues
The Export issues dialog: the Connected textboxes and Issue list per sheet styles, the What to include choices (Only sheets with markups, Whole document), the Resolved issues and Waived issues options, and Markups & comments

Two choices worth knowing​

Annotation style changes how findings appear on the sheet:

  • Connected textboxes (the default) - each issue in a textbox linked to its highlight by a leader line. Easier to read on a sparse sheet.
  • Issue list per sheet - a numbered badge at each finding, plus an "Issues on this sheet" list on each sheet and a detailed legend at the front. Better on a busy sheet, or when many findings sit close together.

Your choice is remembered for next time.

Video / photo coming soon

The two annotation styles on the same sheet

Which pages you get from each document, under What to include (the same in both styles):

  • Only sheets with markups (the default) - every sheet with something drawn on it: Structured's issues, markups you or your team drew or imported, and anything chat drew. A sheet with only an issue on it is included, and so is a sheet with only a markup, so nothing you drew is left out. Markups are always included with this choice. If nothing is drawn on the document yet, this choice is greyed out (and the viewer's one-click Export downloads the drawing as it is).
  • Whole document (all pages) - every page, so the export is a complete set someone can flip through. On a large set that means a much bigger file and a longer wait.
  • Page range (exporting one document only) - type the pages you want, for example 5-6 or 1, 3, 9-12, using the page numbers shown in the viewer. Useful for pulling out just the structural sheets. Issues on those pages are drawn; markups follow the Markups & comments box. Write ranges low to high.

One issue, several places​

An issue is annotated at every location it references, not just its primary anchor, and carries the same number everywhere. Where a finding spans more than one page of the same PDF, the annotations link to each other ("Also see: A-102"). Where it spans two documents, each side gets a note pointing at the other ("See M-201 in M-Series_annotated.pdf"). Nobody has to reconstruct which mark goes with which.

Publishing instead of exporting​

If your team works elsewhere, findings can go to them natively rather than as a PDF. Each connector is switched on per organization - see each page.

  • Bluebeam Studio - publish as native PDF markups. See Connect Bluebeam.
  • Autodesk Construction Cloud - publish as native ACC Issues, triaged in Build. See Connect ACC.
  • Procore - turn findings into Procore RFIs with Create RFI on the issue card. See Connect Procore.

Ask the chat​

The chat can work on issues too. Click Ask Structured on a card to talk a finding through, ask for "issue 14" by number, or ask it to move an issue that landed in the wrong place. Project owners can ask it to delete findings they don't want, and to put them back if they change their mind.

Where issues come from​