Audit scope boxes and crop region settings across all views. · Explore the live interface below - every control works exactly as it does inside Revit®.
Four simple steps to bring View Matrix directly into your Revit® environment.
Sign up for a free NexionTools account - no credit card required.
One installer, 52 professional Revit® tools. Under 15 MB.
View Matrix appears in your ribbon automatically - ready to use.
Enter your Premium key to unlock full features.
Get full access to all 40 premium Revit® plugins. No credit card required.
View governance is invisible until it goes wrong. Which views are not on a sheet. Which have no scope box. Which are dependents of something that moved. Which have a template applied and which quietly do not. Every one of those questions is answerable in Revit, and every one is a different dialog, a different filter, and a browser tree you scroll for ten minutes.
Run View Matrix and it scans the project's plan, section, elevation, 3D and detail views into one table with status badges - up to a hundred and fifty rows at a time, so on a big project you filter first. Sheets, schedules and legends are not in it.
Filter to the views that matter - dependents only, no scope box, not on a sheet, or views carrying warnings.
Select any number of rows and apply a change across all of them: assign a scope box, apply or strip a view template, turn crops on or off, line viewports up on their sheets, swap a titleblock, set which revisions show, duplicate sheets, copy legends and schedules onto them, create dependent views, delete unplaced views - fourteen operations in all.
Sheet duplication is its own small tool inside the matrix: one to fifty copies, a naming pattern built from tokens, optional legend and schedule copying, and viewports re-placed keeping their relative positions. It warns above two hundred new sheets and refuses above a thousand.
Everything is visible in one grid, so you are comparing views against each other rather than opening them one at a time.
View hygiene is checked by scrolling the project browser and opening properties, so it gets done once before issue if at all.
One table shows every view against every governance question, and fixes apply across a multi-selection.