Issues & comments
Everything flagged in a project, automated check findings and manual markups alike, lands in one triage table, so nothing gets reviewed twice or slips through.
The issues table
Every issue carries a stable 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 annotated export and the review letter.
Open Issues & Comments from the tools rail. Each row is a finding or comment with its sheet, location, status, assignee, and discussion thread. Click any row to jump to the exact spot on the drawing.
Filter by status, sheet, discipline, or assignee to work through a review systematically.
Assign & track
Assign any issue to a teammate; they get an email automatically with a link straight to the finding.
- Track status as issues move from open to resolved.
- Discuss in the issue's comment thread so the context stays attached to the finding, not buried in email.
Use case: assign a fire-rating issue to the architect, and watch it move to resolved.
Export issues
Select the issues you want (the filters above the table decide what's included) and export. You get a single zip containing three things:
- An annotated plan set - one PDF per source document, with every finding marked on the sheet.
- A plan-review letter - 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.
Two choices worth knowing
Annotation style changes how findings appear on the sheet:
- Callout (the default) - a comment card with a leader line pointing at the finding. Easier to read on a sparse sheet.
- Numbered - a small numbered badge at each finding, plus an "Issues on this sheet" legend box. Better on a busy sheet, or when many findings sit close together.
The two annotation styles on the same sheet
Scope decides how much of each document you get:
- Whole document (the default) - every page, so the export is a complete, self-contained set someone can flip through.
- Issue-bearing sheets only - just the pages with findings on them, for a shorter document to email.
One issue, several places
An issue is annotated at every location it references, not just its primary anchor, and carries the same comment number everywhere. Where a finding spans more than one page of the same PDF, the annotations cross-reference each other ("Also see page 12"). Where it spans two documents, each side gets a note pointing at the other ("See #14 in M-Series.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:
- Bluebeam Studio - publish as native PDF markups. See Connect Bluebeam.
- Autodesk Construction Cloud - publish as native ACC Issues, triaged in Build. See Connect ACC.
Where issues come from
- Project QAQC and custom checks create issues with evidence linked to the sheet.
- Comments and markups you place by hand.
- Comment Closure tracks externally-supplied review comments alongside them.