A finished review gives you a list of issues. This article explains how to read it and how to get it down to the things you should act on.
Why the number is large
If you reviewed a full permit set, expect a lot of findings. That is what a full set contains.
Scope matters more than anything else here. The same project reviewed at the level of one sheet series produces a handful of issues rather than hundreds. If the volume feels unusable, the answer is usually to review less at a time, not to filter harder afterwards.
Pirros is also deliberately inclusive. Something missed at this stage gets more expensive at every stage afterwards, so the bias is toward surfacing rather than suppressing.
The five sources
Every issue is labelled with where it came from:
Code checks — from the code books selected for this project. IBC, ADA, AISC, regional codes.
Firm standards — from the clauses extracted out of the documents your firm uploaded.
Default rules — spelling, inconsistencies with drawing conventions, details that are drawn but never referenced anywhere in the set.
Constructability — things that would be difficult or impossible to build as drawn.
Mira reasoning — real problems where no clause states it word for word. This is the back-check on what nobody was thinking about, and it is where findings come from that a rules engine could not produce.
Filtering by source is one of the fastest ways to make a large result manageable. If you are doing a code review, look at code checks. If you are checking the set against house style, look at firm standards and default rules.
Filters
You can filter by:
Status — defaults to open and in progress, so resolved and dismissed issues are out of the way
Assignee — what has been delegated, and to whom
Source — the five categories above
Severity — high, medium, low
Run — results from a particular execution
Sort by sheet number
Sorting by sheet number lets you walk the set the way you already read it — take a sheet, clear everything on it, move to the next. For anyone used to redlining a printed set, this is usually the most natural way to work.
One issue, many instances
A violation that occurs in forty places is one row with a count, not forty rows. Open it and you can move through the individual instances, each with its own location and its own reasoning.
This is worth knowing before you react to a total. A large number of findings is often a much smaller number of distinct problems.
A note on search
Search currently matches issue titles only. It does not search the reasoning or the detail of an issue. If you are looking for something specific, filtering and sorting will serve you better.
Frequently Asked Questions
Q: Why did our review return so many issues?
A: Usually scope. A full permit set contains a lot; the same project scoped to one sheet series returns a handful. If the volume feels unusable, review less at a time rather than filtering harder afterwards.
Q: Does a violation in 40 places create 40 issues?
A: No. It is one row with a count. Open it to move through the individual instances. A large total is often a much smaller number of distinct problems.
Q: What does "Mira reasoning" mean as a source?
A: Real problems where no clause states it word for word — a back-check on what nobody was thinking about. These are findings a rules engine could not produce, which is why they are labelled separately.
Q: Why can't I find an issue by searching for something in its reasoning?
A: Search matches issue titles only today. Use the filters and sheet-number sorting instead.
Q: What am I looking at by default?
A: Open and in-progress issues. Resolved and dismissed ones are filtered out until you ask for them.
Q: What is the best way to work through a big result?
A: Two approaches work well. Filter to high severity and clear that first, or sort by sheet number and walk the set the way you would redline it on paper. Filtering by source is also useful when you are doing one specific kind of check.