Project Review reads the drawing set your team is producing and tells you what is wrong with it — before it goes out the door.
It is one of three parts of quality management in Pirros:
Project Review — checks a drawing set against the codes, standards, and reference documents you selected for that project.
Firm Standards — the documents your firm uploads once, which every review then checks against.
Model Performance — a separate view of the health of the Revit model itself: warnings, counts, and the elements causing them.
What a review looks at
Every review runs against a set of inputs you choose. Nothing is assumed and nothing is pulled in automatically:
The model you pointed the review at.
The drawing set you selected out of that model — the print set configured in Revit, such as your DD set or your A200 series.
The codes you selected for the project. Pirros processes IBC, ADA, AISC and regional codes; you pick which ones apply.
Your firm standards, as uploaded on the Standards page.
The references you loaded for the project — the specifications, consultant models, and other-discipline drawing sets.
Every issue it raises traces back to one of those five things. That is deliberate: a finding you cannot trace to a source is a finding you cannot defend when someone questions it.
What it does not look at
Project Review checks what you point it at. It does not draw on anything else in Pirros or anything from your firm's past work.
Specifically, a review does not use:
Your detail library or family library as review context
Anything you did not select for this particular review
Your firm's previous projects or review history from other projects
Your library does reach reviews, but through one specific route: Firm Standards. If your standards document says how your firm details a condition, the review checks against that. Mira can help you write that document by reading your existing models and templates — see No standards document yet? Have Mira write one.
Where issues come from
Every issue is labelled with its source, so you always know why something was flagged:
Code checks — tied to the specific code books selected for that project.
Firm standards — the clauses extracted from the documents you uploaded.
Default rules — spelling, inconsistencies with drawing conventions, details that are never referenced in the set.
Constructability — things that would be difficult or impossible to build as drawn.
Mira reasoning — real problems where no clause says it word for word. A back-check on what nobody was thinking about.
Where to start
If you are setting Pirros up for the first time, work in this order:
Upload your firm standards. This is done once for the whole firm.
Set up a project and add the model you want reviewed.
Add your reference documents — the spec book and any consultant drawings or models.
Select the codes that apply to the project.
Run a review, either once or on a recurring schedule.
Before you run your first review, it is worth reading How a review actually runs: the drawing set first, the model second. It explains what kind of problems Project Review finds and what kind it does not, which is the most common source of mismatched expectations.
Frequently Asked Questions
Q: Do we need to upload code books?
A: No. Pirros processes IBC, ADA, AISC and regional codes centrally. You select which ones apply to each project — you never source or upload a code document yourself. Firm standards work the opposite way: those are your documents, and you upload them. If an existing code that you use does not exist in the pre-defined list, reach out to the support team and we will add that code in our backend.
Q: Does it look at our detail and family library?
A: Not as review context, no. The one route your library reaches a review is through your firm standards — if your standards document describes how your firm details a condition, the review checks against that. Mira can read your library to help you write that document, but the review itself only sees the standards you uploaded.
Q: What is the difference between Project Review and Model Performance?
A: Project Review checks your drawing set — the deliverable. Model Performance checks the Revit model itself, reporting warnings and the elements causing them. Different questions, usually different people. See What Model Performance checks.
Q: Do we need an Autodesk connection to use this?
A: No. You can upload a model directly and run reviews on it. A linked model does give you more — scheduled reviews, live model reading, and current model health — so it is worth having if your firm can. See Add a model: Forma-linked vs. local upload.
Q: Can we review part of a set rather than all of it?
A: Yes, and for your first review you should. You choose which drawing set to review, so you can scope it to a single sheet series. A full permit set produces a lot of findings; one series produces a result you can actually read through.
Q: Do we have to upload reference documents?
A: No, but a review with your specification and consultant drawings loaded can resolve things a review without them has to leave alone. The spec book in particular is worth loading.