Findings

Findings is the queue for everything the automated checks flagged on a project. One list, one triage flow, regardless of which check produced the row. Open it from the project sidebar.

Findings arrive from more than one producer. A VANTAGE run is one of them; document analysis and specification checks contribute rows too. The queue merges them and every row is triaged the same way, but a few actions differ by producer. Those differences are called out below.

Reading a finding

Each row carries a title, a one-line summary, its severity, its current status, and the tags that describe it. Selecting a row opens the review pane on the right, which adds:

• The full description and the recommended action.
• Citations. The documents, sheets, and pages the finding was derived from. Machine-produced findings are required to carry at least one.
• Source sheets. Every citation that resolves to a document becomes a link that opens that sheet in a new tab, at the right page where the page is known. View on document at the top of the pane opens the anchor document.
• A confidence score for the finding.

Findings are scoped to the current project.

Severity

The queue shows four severity levels. A VANTAGE run assigns severity per finding and it maps to the queue like this:

Run severity	Shown in the queue as
CRITICAL	Critical
HIGH	Warning
MEDIUM	Advisory
LOW	Info

Sorting by severity puts Critical on top, then Warning, Advisory, Info, with the newest first inside each band.

Status

Status	What it means
Open	Detected, nobody has picked it up
In review	Somebody has engaged with it
Accepted	Judged a real problem and taken on. Still part of the open backlog
Resolved	Fixed in the documents or addressed in the work
Dismissed	Judged not a real problem: false positive, duplicate, or out of scope
Accepted risk	Real, and the team is consciously proceeding without a fix

Open, In review, and Accepted all count as active backlog. Accepted means the team agrees it is a real problem, not that the work is done. Resolved is the closing state.

Findings a reviewer model suppressed during a run are recorded as Dismissed and are not shown by default.

Types

A finding is classified by what kind of problem it is.

Type	What it describes
Contradiction	Two documents state incompatible things
Coordination	Two disciplines conflict in space or in sequence
Calc failure	A stated calculation does not hold
Scope gap	Work that no document appears to cover
Compliance	A code or specified requirement is not met
Ambiguity	The documents allow more than one reading
Missing info	Something required is not stated anywhere
Cost risk	An exposure to cost
Schedule risk	An exposure to schedule
Data quality	A problem with the source document itself rather than the design

Row tags show the finding's category and the trades it affects.

Filtering the queue

A strip of counts sits above the toolbar: Open, In review, Accepted, Active critical, and Resolved. Each one is a filter. Click Open to show only open findings; click it again to clear. Active critical filters to critical findings still in the open backlog, and clears both filters together.

The toolbar composes on top of that:

• Search matches the title, the summary, the producing agent, and the tags.
• All severities narrows to one severity.
• All statuses narrows to one status, or to Active for the whole open backlog.
• All assignees, Assigned to me, Unassigned, or a specific member.
• Sort: Severity or Sort: Newest.

A line under the toolbar reads "N of M": how many rows survive the filters out of how many the project has. When filters match nothing you get "No findings match these filters" and a Clear filters button, which is a different statement from the project having none.

Grouping

The group control offers No grouping, or grouping by severity, status, discipline, document, assignee. Empty groups are omitted. Unclassified, No document, and Unassigned always sort last.

Grouping by discipline or by document resolves through the document a finding is anchored to. Findings produced by a VANTAGE run keep their document links on their citations rather than on the finding itself, so they collect under Unclassified and No document in those two groupings. Their Source sheets links still work.

List and board

List is the default: a grouped, scrollable list with the review pane opening as a slide-over. Board lays the same findings out as lanes, one per status, in lifecycle order. Dragging a card to another lane sets that status. If the write does not stick, the card snaps back to its real lane rather than showing a change that did not happen.

Triage

Open a finding and set its disposition in the pane footer:

• Dismiss. Not a real problem.
• Accept. A real problem, taken on.
• Resolve. Addressed.

Or set Status and Assignee directly in the pane's Details section. Selecting rows with their checkboxes turns on a bulk bar: Assign, Accept, Resolve, Dismiss, Clear.

What differs on a VANTAGE finding

On a finding produced by a VANTAGE run, Accept, Dismiss, and Resolve all work. Two things do not:

• Assignee cannot be set. Assignment is only supported on findings from document analysis. Assigning a VANTAGE finding, on its own or in a bulk action, returns an error and changes nothing.
• Open and Accepted risk are not available. There is nowhere to record them, so setting either returns an error. Use Dismiss or Accepted instead.

The Avoided loss field in the Details section has the same restriction as assignment: it saves on findings from document analysis and errors on a VANTAGE finding.

Everything on this surface is read only on the demo project.

Escalating to an RFI or an issue

Create RFI and Create Issue in the pane footer draft the record for you from the finding, including its citations, and open it for editing before anything is created.

• Create RFI drafts the question, a proposed solution, the responsible party, and cost and schedule impact. Edit them, then create. On a project that is not linked to Autodesk, the RFI is created in the project's RFI register. On a linked project it is created in Autodesk, and the modal tells you if the Autodesk connection needs attention before it can push. See Integrations.
• Create Issue drafts a title, description, type, subtype, priority, and due date. You must pick a type before Create Issue is enabled. It lands in Observations on a native project, and in Autodesk on a linked one.

Escalating does not change the finding's status. Set that yourself once the RFI or issue is out.

Exporting

Findings export from Reports, not from this page. Reports offers two formats:

• PDF register. A printable register, one row per finding.
• CSV. The same rows for a spreadsheet.

Both are produced from the same source, so a PDF and a CSV pulled a second apart cannot disagree. There is no spreadsheet workbook format, because the export does not produce one.

The register is built from the project's findings record. Findings produced by a VANTAGE checklist run are stored with their run and are not included in that file.

Troubleshooting

Fewer findings than you expected, with no explanation. A producer your organization is not entitled to contributes zero rows and says nothing about it. The two that gate this way are the VANTAGE add-on and the specification checks. If a project does not carry the VANTAGE add-on, no VANTAGE finding will ever appear here, and the queue will not tell you that is why. Check the project's add-on state in Project Settings. See VANTAGE.

"No findings yet." Nothing has been checked on this project. Run a Workflow or start an Investigate run, and findings land here when it finishes.

A status change came back as an error. Check whether the finding came from a VANTAGE run and whether the status you picked is one of the two that producer cannot record. See What differs on a VANTAGE finding.

A citation has no link. Not every citation resolves to a document in the project. Those stay as plain text under the finding rather than becoming a link that goes nowhere.

The finding points at the wrong revision of a sheet. Confirm which revision is current on the sheet, then dismiss the finding if it was derived from a superseded one and run the check again against the current set. See the sheet viewer.