QC Summary
PremiumFull QA dashboard — rooms, walls, doors, windows, forbidden elements, sill consistency. · Explore the live interface below - every control works exactly as it does inside Revit®.
Architecture
Structure
Steel
Precast
Systems
Insert
Annotate
Analyze
Massing & Site
Collaborate
View
Manage
Add-Ins
NexionTools
Select
Highlight
Rooms
Parameters
Sheets & Views
Data
Manage
QC
Test it Live - exactly as if you are in Revit
Loading interactive demo…
Get Started in Minutes
Four simple steps to bring QC Summary directly into your Revit® environment.
1
Create Account
Sign up for a free NexionTools account - no credit card required.
2
Download Installer
One installer, 52 professional Revit® tools. Under 15 MB.
3
Open Revit
QC Summary appears in your ribbon automatically - ready to use.
4
Activate License
Enter your Premium key to unlock full features.
Ecosystem · QC
Try NexionTools completely free.
Get full access to all 40 premium Revit® plugins. No credit card required.
Why QC Summary exists
Model checking before an issue is a list of things you already know to look for, done by hand, slightly differently each time. Unplaced rooms. Rooms with no name. Doors and windows that disagree with the schedule. Views that never made it onto a sheet. You find them by building schedules, scanning, and hoping you did not skip a floor - and the next person checks a different list.
How QC Summary works
Run QC Summary with the model open. It makes one read-only pass over the project, running around a dozen categorised scans.
The report opens as a scorecard: an overall grade and score, KPI tiles for rooms, walls and sheets, and charts for the per-floor breakdown and window-to-wall ratio.
A model information card covers the things that are easy to forget - levels, views, sheets, view templates, file size, worksets, type counts, unplaced rooms, unused families.
Findings are grouped into collapsible sections by area, each item colour-coded critical, warning or informational.
Clicking a finding selects the element in Revit, so you go from the report to the problem without searching for it.
Before
Each checker has their own routine, so what gets caught depends on who did the check and how much time was left.
After
The same checks run the same way every time, and the result is a scored report you can hand to someone else.
When to reach for it
- A pre-issue sweep before drawings go out.
- Taking over a model from another team and finding out what state it is actually in.
- A regular health check on a live model, so problems surface while they are still small.
What it does not do
- It reports. Nothing in the model is modified - deciding what a finding means is the part that needs you.
- The checks are the ones built in. It is not a configurable rules engine and does not replace a project-specific BIM execution plan check.
- Findings are only as meaningful as the model. A room left unplaced on purpose still appears.
- The untagged-rooms check only runs when the active view is a floor plan. From a 3D view or a schedule it reports none - not because there are none, but because it did not look there.
- The view and sheet naming checks match English naming patterns, so on a Revit running in another language a badly named view can slip past them.
- It scans the open document. Linked models are not audited - open the link directly to check it.
Questions
- How is this different from reviewing Revit warnings?
- Revit warnings tell you what Revit noticed while you modelled - overlapping elements, duplicate marks. These are documentation and data checks: unplaced rooms, coverage metrics, view and sheet hygiene, type diversity. The two lists barely overlap, which is why Warning Triage exists separately.
- Does it modify the model?
- No. The entire scan is read-only. The only thing it changes is your Revit selection, when you click a finding to jump to it.
- Can I get the results out of Revit?
- Yes, the report can be exported as plain text for pasting into an issue log or a review email.
- How long does it take on a large model?
- It is a single document pass with a progress splash, and the dialog warns that large files take a moment. It is designed to be run before an issue, not continuously in the background.