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.

Video / 1:30Issues: triage to export
Coming soon

Filter the list, open an issue, assign it to a teammate, set one of your organization's statuses, and export the annotated PDF and spreadsheet.

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:

  • Search - the Search issues & comments... box.
  • Filter - next to the search box. It opens the filter panel over the top of the list; the button shows how many filters are on, and Clear all at the foot of the panel turns them all off. In the panel:
    • Status - Unresolved, Resolved or All. Waived issues count as resolved here. If your organization or team has its own status list, the menu also lists those statuses under Project statuses, grouped by what each counts as; tick one or more to narrow the list (and the drawing) to them, or pick Every status to clear them.
    • Severity and Assignee (including Unassigned).
    • 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.
    • Document - All documents, This document (the drawing open in the viewer), or tick any number of documents in the list. Each one shows how many issues it holds.
    • Source - the tiles All, Project QAQC, Spec Audit, Code Review and Comments. Each tile counts the open issues of that kind across the whole project; a tile with nothing in it is greyed out. When the panel is too narrow for all five, the row shows only the selected tile with an arrow beside it that steps to the next tile with something in it.
  • From this check - the dropdown under the search box (All checks to start with) narrows the list to the issues from one check.
  • This document and On this page - quick chips beside it. This document shows only items in the drawing set open in the viewer; On this page shows only the issues that cite the sheet you have open, including findings whose own page is elsewhere.
  • Sort - Newest, Severity, Page, Assignee, Issue # (low to high) or Issue # (high to low).

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

The Issues panel with the Filter panel open over the list: Status, Severity, Assignee, Document and the source tiles

Summary or All issues​

The switch on the right of the toolbar changes how the list is laid out:

  • Summary - the list split into groups, each with a header you can fold. Pick what to group by with Group by: Category (the default: Life safety, Code, Coordination, Revit model and Minor / drafting), Severity, Label, Document or Assignee. Minor / drafting starts folded. Collapse all and Expand all fold or open every group at once.
  • All issues - one flat list.

A long list (more than 30 issues) opens in Summary, a shorter one in All issues, until you pick one yourself. Choosing any sort other than Severity switches to All issues, since a sort only holds inside each group; click Summary to bring the groups back.

The colour Key​

Key explains the colours on the cards and the drawing: Critical, High, Medium, Low / Info and Suppressed. On the drawing, a cloud is the issue itself in its severity colour, with the issue number on its corner; a box is evidence the issue cites, in the same colour with the same number.

Click a colour in the Key to bring the cards of that colour to the top of the list. Click it again to put the list back.

If your project uses its own colours for resolved or waived issues, the Key also shows them under This project's status colours, with who set them. To change those colours, ask the chat, for example "make resolved issues light pink". They apply to this project's viewer, PDF exports and Bluebeam, and Project settings shows them under Issue status colours.

The Issues panel's colour Key open, with the severity rows and the project's status colours

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.

Issue statuses​

Every issue has a status, and every status counts as one of three things: Open, Resolved or Waived. Out of the box a project uses Structured's three, but your organization can replace them with its own list - for example "Open", "Double Check", "Back-checked" and "Not applicable" - each with its own colour.

The list a project uses comes from its home team: the team's own list if it has one, otherwise a parent team's, otherwise the organization's, otherwise Structured's default. The same statuses show on the cards, in the filters, in exports and in Bluebeam.

Changing an issue's status​

  • The one-click buttons on a card set the default status of each kind. With Structured's statuses they read Resolve, Waive and Reopen; with your own list they carry your default status's name instead.
  • When your list has more than one status of a kind, the card also has Set status: a menu of every status on the project's list, grouped by what it counts as.
  • A card shows its current status, and who set it.

Managing status lists​

  • The organization's list is on the Organization page's Settings tab, under Issue statuses, for the org owner. Use Create org list to start one, or Use Structured's default to remove it. See Organization page.
  • A team's list is on the team's Statuses tab, for the team's leads and the org owner. Use Create team list to give a team its own, or Use the inherited list to go back to the parent's.

In the editor, each row has a Colour, a name under Status, and what it Counts as. Add status adds a row; the arrows change the order. The first status of each kind is its Default: the one the one-click buttons set, and where new findings start. Every list needs at least one status that counts as each of Open, Resolved and Waived.

If your team already has a Bluebeam status set, Import .bpx reads it from a Bluebeam profile file and fills the list for you, with a Bluebeam state for each status. Check what each one counts as, then Save imported statuses. The statuses of an imported set come from its .bpx file, so import it again to change them.

Nothing is lost when a list changes. Before you save, the editor shows how many existing issues and markups will read differently. If you delete a status that is still in use, pick where its issues should go and choose Move and save; Bluebeam is updated too. Moving a project to a team with a different list moves each issue to the status there that counts as the same thing.

A team's Statuses tab with a custom status list, its colours and Counts as column

Assign & track​

Assign any issue to a teammate and they're emailed a link to each finding. The email waits until 15 minutes after your last assignment to that person in the project, so assigning issues one by one still sends one email listing them all. While emails are waiting, the Issues tab shows you who is waiting to be emailed, and Send notifications now sends them straight away. An issue you unassign before the email goes out is left out of it. Assigning an issue to yourself emails you at once.

  • Discuss in the issue's comment thread so the context stays attached to the finding, not buried in email. Paste a screenshot into the comment box, or use Attach image, to add up to 5 images to a comment.
  • 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

Edit an issue's wording​

If a finding is right but worded badly, people who can edit the project can rewrite it. Expand the card and use Edit title or Edit description, then Save. An edited issue shows Edited; hover it to see the original wording. The new wording is what appears on the drawing, the letter and the spreadsheet.

Make a repeatable check​

Make repeatable check on an issue card turns the issue into a check that looks for the same condition again. It shows when your organization can make custom checks and you can edit the project. Edit the Check name and What the check looks for, then choose where it goes under Where the check goes:

  • This project - saves it to your library and runs it on this project now. The run is charged to your organization's balance.
  • Organization library - saves it to your library and asks to share it with your organization. Your org owner reviews the request, unless you are an owner.

Press Save check.

Resolve, waive or reopen​

  • Resolve an issue once it's fixed on the drawings. Resolved findings show on the sheet as green clouds (or your project's resolved colour) 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, and it appears in the spreadsheet's Reason column. Waiving does not retrain anything or change how checks run.
  • Feedback goes to the Structured team, not to your project team.

Only people who can edit the project can change statuses, assign or edit issues.

One issue, several places​

Some issues sit in several places - the same misspelling on six sheets, say. When an issue has two or more places, its card lists them with a check-off for each, so you can tick off the ones that are fixed while the rest still read as work to do. The card shows progress as "3 of 6 checked off". Click a place to see it on the drawing, or use Check off this sheet to tick every place on the sheet open in the viewer.

Checking off places never changes the issue's status: resolve it yourself when the review is complete. If you resolve it while places are still open, the card asks first. While an issue is resolved or waived its check-offs are kept but locked; reopen it to change them.

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:

  • Assign - add people to every selected issue.
  • Unassign - lists the people on the selected issues and how many each is on. Pick who to remove; everyone else on those issues stays assigned.
  • Resolve (with the number selected) and Waive, or your own default statuses' names. Waive asks for one reason, attached to every selected finding. With the status filter on Resolved, the pair is replaced by Reopen. When your list has more statuses, Set status applies any of them to the whole selection.
  • Deselect - clears the selection.
  • 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.

Selected comments have their own bar, with Assign and Delete.

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 click Export. Open findings are included by default; tick Include Resolved or Include Waived to add those too, and each one is labelled with its status on the sheet. With your own status list, the boxes name your statuses instead, for example "Include Back-checked".

To export just some issues, tick their cards first: the export dialog then offers Export only N selected issues (on by default). The selected issues are exported whatever their status, so the Include boxes are hidden while it is ticked. Untick it to export everything the list is showing, and the Include boxes come back.

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 letter and the spreadsheet carry each issue's title and description, not its Required action. Open an issue's card in the Issues tab to see its required action.

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 - the issue's status as your project names it, or Suppressed.
  • 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.
  • Found by - for an issue that several checks found and that was merged into one, which checks found it.
  • Reason - the reason typed when the issue was waived; blank otherwise.
  • Run - the check run the issue came from.
  • Merged findings - the wording of the findings merged into this issue, as each check filed it.
  • Comments - every comment on the issue, one per line, in thread order.

When the issues come from more than one check run, a second sheet, Runs, lists each run with its checks and how many of the listed issues it raised.

Updated video coming soonExport issues
The Export issues dialog: the two annotation styles, What to include, the Include status 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.

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.

Arrange the callouts yourself​

When you export a single document with Connected textboxes, the dialog also offers Customize layout…. It opens Edit callout layout: the sheets with each issue's callout on them, so you can place every callout exactly where you want it before the PDF is made.

  • Drag a callout to move it, and drag its corner handle to make the box wider or narrower; the text reflows.
  • Callout text size (Smaller / Larger) sets one font size for every callout.
  • Reset positions puts every callout back where Structured placed it.
  • When you're happy, Export PDF downloads the annotated PDF exactly as laid out.

Issues that could not be placed on a sheet are listed at the side under Not located on a sheet.

The Edit callout layout editor with callouts being arranged on a sheet

One issue, several places, in the export​

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.

Changes like these are recorded in the project's History, next to every other change made in the project.

Where issues come from​