# Issues

> Every issue from a design quality review is verified against the documents before it reaches your queue, with cleanup items shelved and evidence attached.

Source: https://docs.specset.com/docs/issues · Section: Issues & Estimating · Last updated: 2026-10-18

Every issue identified during a [design quality review](https://docs.specset.com/docs/design-review) or deep design quality review, collected in one list. Issues live in the project sidebar and stay current as agents run. Open **Issues** for the overview, or **Issues → List** to search, sort, and filter. Use **Export** to share selected issues.

The list opens to a review queue that holds the issues that need someone on the design team to make a call. The chips above the list split everything by where it stands, from **Needs review** through **Confirmed**, **Dismissed**, and **Cleanup**.

![Issues list with review chips and an AI Verification column showing AI confirmed badges](https://docs.specset.com/images/docs/issues/docs-issues.png)

> Ask the agent to draft an [RFI](https://docs.specset.com/docs/rfis) straight from any issue it found, or roll issues up into a dashboard of rework cost exposure.

## Work through the review queue

1. Open **Issues → List** and choose **Needs review**. Narrow the list by discipline, severity, assignee, or other filters to focus on one coordination task.
2. Click **Review** to walk through the findings. To review a particular group, select those rows first.
3. Read the issue and suggested resolution, then open its drawing or specification references. **Auto-open** opens a referenced document as you move through the queue; turn it off when you prefer to open references yourself.
4. Add a reason if it will help the next reviewer, then record your decision.

| Decision | Use it when |
| --- | --- |
| **Confirm** | The finding is valid and needs to be tracked. |
| **Trivial** | The condition is real but does not warrant a coordination decision. |
| **Not an issue** | The finding is a false positive or the documents already resolve it. |
| **Skip** | You need more information before deciding. The issue remains unreviewed. |

A decision advances to the next issue. To ask a teammate without deciding, write a note, use **@** to mention them, and choose **Comment only**. This also moves you forward in review mode. You can revisit a decision with **Change**, or **Clear** it to return the issue to an unreviewed state.

![Issue review panel with the conflict, suggested resolution, and Confirm, Trivial, and Not an issue actions](https://docs.specset.com/images/docs/issues/docs-issue-triage.png)

## Assign and follow through

**Review** records your judgment of the finding; **Status** tracks whether the work is resolved. Confirming an issue does not mean it is closed. The **AI confirmed** badge is also separate from your team's review decision.

Use **Edit** to set the assignee, severity, and status. For several issues, select the rows, choose **Edit**, and select the field to update. Leave a team note when the next step or resolution needs explanation.

If a formal design-team answer is needed, choose **Promote to RFI** from the issue's actions menu. This opens a new chat with the issue and a request to draft an RFI already filled in. Review and send the request, then work with the agent on the RFI. The linked RFI remains accessible from the issue.

Use **Archive** to remove an issue from the active list while keeping its record. You can find archived issues through the archive filter and **Unarchive** them later.

## AI verification

Design reviews cast a wide net on purpose. Before a finding reaches your queue, a second, independent AI verifies it: it goes back to the cited sheets and spec sections and tries to disprove the issue, checking drafting conventions and looking for the answer elsewhere in the documents.

- **Confirmed issues** carry an **AI confirmed** badge. Hover it to read what was checked and why the finding stands, then click through to the full verification session if you want the complete trail. Verification also gives severity a second opinion, so ratings reflect real impact.
- **Disproven issues** are archived automatically with the reasoning saved as the archive note. They never crowd your queue, and you can always review them under the Archived filter and restore any you disagree with.
- Your judgment outranks the AI's: once you confirm an issue, a verification verdict will never archive it.

![Hovering an AI confirmed badge shows the verification summary citing the sheets checked, with a link to the verification session](https://docs.specset.com/images/docs/issues/docs-issue-verification.png)

_Hover any verification badge to see the evidence behind the verdict._

## The Cleanup list

Some findings are real but resolve on their own as the project moves along: typos, leftover spec boilerplate, placeholders a later revision will fill in, details a vendor will work out. These are routed to the **Cleanup list** instead of the review queue, and the Issues overview shows a card with the count.

Nothing is hidden. Click the **Cleanup** chip (or **View all** on the overview card) to browse the list, and move any item back into the queue if you think it deserves a decision.

![Cleanup list containing minor drafting and boilerplate findings](https://docs.specset.com/images/docs/issues/docs-cleanup-list.png)

## Export marked drawings

1. Select the issues you want to share in the issue list and choose **Export**.
2. Set **Format** to **Annotated drawings (.pdf)**.
3. Turn on **Include issue index** if you want a compact list of issues with links to their marked sheets. It is off by default.
4. Turn on **Flatten annotations** only if you want the comments baked into the pages. Flattened markups can't be moved and don't appear in a markups list, such as Bluebeam's. It is off by default, and a flattened export always draws the comments on the page.
5. Leave **Show comments on the page** on to draw each issue's caption in a text box with an arrow to its mark, or turn it off to draw only the mark and keep the full comment in its hover note.
6. Turn on **Add Bluebeam columns** to give each mark **Specset Issue #**, **Specset Severity** and **Specset Link** columns in Bluebeam's Markups list.

Steps 5 and 6 aren't offered when flattening.
7. Click **Export** and keep the window open until the download starts. Large exports may take a few minutes.

**Show comments on the page** and **Add Bluebeam columns** start from the project's defaults under **Project Settings → Drawings → Annotated Drawing Exports**. Bluebeam shows the columns saved in a PDF instead of your profile's columns for that file.

The PDF includes only drawing sheets with visible annotations for the selected issues. Each sheet appears once, with issue numbers and short captions beside the marked locations. Each mark's hover note starts with its issue number and caption, followed by the detail for that sheet. Its text box and arrow are grouped with it, so a markups list shows one item per mark. Issues that mark the same location share one cloud, unless Bluebeam columns are on: then each issue keeps its own cloud and row. Issues without marked drawing sheets are omitted from the PDF; the completion notice tells you how many were left out.

![Exported drawing detail with a red cloud around a door and column, linked to a boxed caption explaining their conflict](https://docs.specset.com/images/changelog/issue-drawing-pdfs/cover.png)

_A sample drawing shows the issue beside its location, ready to share in the compiled PDF._

Choose **Excel (.xlsx)** or **CSV (.csv)** instead when you need a tabular issue report. Excel also offers optional cropped annotation images.