ScopeViews: Scope Box–Driven View Creation for Revit

Overview

ScopeViews is an Autodesk Revit add-in from underbim, a Portugal-based BIM consultancy that has worked in BIM, Revit training, consulting, and software development since 2001. It is one of eight independent add-ins in ub.Suite Edition 1, which launched in late October 2026, and is positioned as a view creation tool. Its tagline, "Define the scope. Generate the views," sums up the approach. It turns selected Revit Scope Boxes into repeatable sets of plan, section, and 3D views. View templates, scale, and naming are all set before the views are created.

Note on sources: This summary is based mainly on underbim's full ScopeViews product page, which covers the workflow, feature explorer, generated view set, templates and scale, naming, and licensing. The background on scope boxes comes from Autodesk documentation and community forums. An independent review or hands-on test was not found, and the gaps are listed under Open Questions.

The Problem Area: Views and Scope in Revit

In Revit, view "scope" is mainly controlled by scope boxes and crop regions. A scope box is a 3D region drawn around part of the model. Assign it to views and their crop extents follow the box, so changing the box once updates every view that uses it. Assign it to grids, levels, and reference planes and they appear only in views whose cut plane intersects the box. The difference is often summed up as "a crop region belongs to one view, a scope box belongs to the project." Documentation and user forums point to several recurring pain points:

• Repetitive view setup: Large or multi-zone projects need many plans, ceiling plans, and dependent views cropped consistently. Cropping views by hand often leaves them slightly misaligned on sheets.
• Assignment limits: Scope boxes can only be created in plan views. Since Revit 2023, users report they can no longer assign or change scope boxes on dependent section views and some other dependent views, though dependent floor plans still work.
• Finding and tracking scope boxes: Scope boxes appear only in views they intersect. Forum users report "losing" a scope box after deleting the views where it was visible, and they have no easy way to see which views use which box.
• Greyed-out or conflicting settings: The Scope Box parameter can be unavailable, for example when a view template controls it, which makes troubleshooting harder.
• Bulk work needs add-ins: Creating dependent views from scope boxes, reassigning scope boxes across many views, or copying scope boxes from linked models is commonly done with third-party add-ins or Dynamo, not native tools.

ScopeViews tackles the repetitive-setup part of this problem. It uses the Scope Boxes you've already defined as the spatial basis for generating complete, consistently set-up view sets, so you don't have to create and crop each view by hand.

ConstraintScanner: Inspecting Constraints in Revit Projects

Overview

ub.ConstraintScanner is an Autodesk Revit add-in from underbim, a Portugal-based BIM consultancy that has worked in BIM, Revit training, consulting, and software development since 2001. It is one of eight independent add-ins in ub.Suite Edition 1, which launched in late October 2026, and is positioned as a model diagnosis tool. Its tagline, "See the relationships. Inspect what they mean," sums up the approach. It scans Revit constraints, dependencies, and model conditions, narrows the results to the relationships that matter, and lets users go straight from the evidence to the elements involved, without changing the model.

Note on sources: This summary is based mainly on underbim's full ConstraintScanner product page, which covers the workflow, feature explorer, coverage, and licensing. The background on Revit constraints comes from Autodesk documentation and community forums. An independent review or hands-on test wasn't found, and gaps are listed under Open Questions.

The Problem It Addresses: Constraints in Revit

Constraints build intelligence into a Revit model by setting relationships between elements. They're powerful, but they're also a common source of confusion and unexpected model behavior. Autodesk's documentation and user forums describe several traits that make constraints hard to manage at project scale:

• Several kinds of constraints: Explicit constraints (locked alignments, locked dimensions, and EQ equality constraints) always hold, and conflicts with them cause errors. Looser relationships, such as unlocked dimensions and alignments, may be dropped without notice when a conflict occurs. Implied constraints, such as walls attached to roofs or joined at corners, are managed by Revit itself.
• Constraints exist apart from dimensions: Constraints don't belong to a specific view and can exist without the dimension that created them. Deleting a dimension doesn't always remove the constraint, so "hidden" constraints can remain in the model. Several locked dimensions between the same two references can also map to a single constraint.
• Hard to trace: Revit's native Reveal Constraints mode shows constraints only temporarily, in the current view. Users on Autodesk forums report they can't find which locked dimension or view controls an element, or "take me to" the source of a constraint.
• No native bulk review: Revit has no built-in way to list, filter, or unlock constraints across a whole project. Users have turned to Dynamo scripts or the Revit API, where constraints sit in a separate category from dimensions.
• Over-constraining and unpredictable behavior: Leftover or unnecessary locks can make elements resist edits or move unexpectedly. In workshared models, a constraint can't be edited if any constrained element is in a workset the user can't edit.

ConstraintScanner is aimed at this gap. It helps BIM managers, coordinators, and modelers inspect and understand the constraints and dependencies already in a model, instead of discovering them one at a time when an element won't move.

ProjectManager: Project Cleanup with Context Attached

Overview

ProjectManager is an Autodesk Revit add-in from underbim, a Portugal-based BIM consultancy with experience in BIM, Revit training, consulting, and software development since 2001. It is one of eight add-ins in ub.Suite Edition 1, released in late October 2026, and can be purchased individually or as part of the suite. underbim summarizes its purpose as “Know what is in the project. Decide what stays.” The add-in audits recurring Revit project resources—V/G filters, scope boxes, view templates, and views—classifies them as used, unused, or unreferenced, shows their dependencies, and supports batch view management and controlled cleanup. Its defining principle is “audit first, change second”: discovery and filtering are kept separate from destructive operations, every change can be previewed before it is applied, and an applied operation retains a single Revit Undo path.

This summary is based primarily on the text of the official ProjectManager product page, supplemented by underbim’s website, suite overview, and announcement. The product page is marketing material: the Views workflow and delete behavior are described in detail, while some feature areas are summarized briefly. No user guide, independent review, or hands-on testing was available, so the remaining gaps are listed as open questions rather than filled with assumptions.

Core Concept: Audit First, Change Second

ProjectManager brings recurring project-management operations into one place, so the target set can be understood before anything is renamed, detached, or deleted. The product page frames this in four stages:

• Find: search, filters, and project content.
• Classify: used, unused, and unreferenced.
• Review: dependencies, protection, and preview.
• Act: batch changes, delete, and Undo.

Six-Step Workflow

underbim describes the workflow as “Find the target set. Understand it before acting.” Discovery and filtering are separated from destructive operations so that project cleanup remains an explicit user decision:

1. Audit: read the current project content across the supported resource areas and views.
2. Filter: reduce the list by usage, search criteria, or native Revit view properties.
3. Understand: review usage counts, dependencies, sheet placement, references, and protected conditions.
4. Select: build the working set manually or from the current filtered result.
5. Preview: see what will be deleted, skipped, or detached before the Revit document is modified.
6. Apply: commit the selected operation, review the result, and retain a single Revit Undo path.

InterferenceInvestigator: Interference Management in Revit

Overview

InterferenceInvestigator is an Autodesk Revit add-in from underbim, a Portugal-based BIM consultancy with experience in BIM, Revit training, consulting, and software development since 2001. It is one of eight add-ins in ub.Suite Edition 1, released in late October 2026, and can be purchased individually or as part of the suite. underbim summarizes its purpose as “See the clash. Understand the pair.” The add-in focuses on the work after interference detection: moving from an interference result to the exact host and linked elements involved, locating them in the Revit model, recovering enough surrounding context to understand the problem, tracking a review state for each occurrence, and turning the investigation into an actionable result. Reviewed results can become a native Revit schedule, a .ubr result package, or input to ModelData.

This summary is based primarily on the text of the official InterferenceInvestigator product page, supplemented by the ModelData and FilterToSchedule product pages, underbim’s website and suite announcement, and Autodesk documentation on the native Interference Check. The product page is marketing material: several feature areas are described in detail, while others are only named. No user guide, independent review, or hands-on testing was available, so the remaining gaps are listed as open questions rather than filled with assumptions.

Core Concept: A Clash Becomes Useful When You Can Investigate It

underbim states that InterferenceInvestigator is “built for the work after detection”: identifying the pair, reaching the actual elements, understanding their model context, and deciding what needs to happen next. The product page frames this as four stages:

• Result: a structured interference set.
• Pair: host and linked participants with their identities.
• Context: select, isolate, and Focus 5%.
• Continue: schedule, .ubr, or ModelData.

The page’s coordination-workflow graphic illustrates a pair consisting of a host structural beam and a linked service element, labeled “Status · Open,” following a path of pair → model → context.

ModelData: A Schedule-Centered Data Workbench

Overview

ModelData is an Autodesk Revit add-in from underbim, a Portugal-based BIM consultancy with experience in BIM, Revit training, consulting, and software development since 2001. It is one of eight add-ins in ub.Suite Edition 1, released in late October 2026. underbim positions it as a “data workbench” to “build, inspect, calculate and refine Revit schedule and model data with more control over the logic behind the result.” Rather than replacing Revit schedules with a separate data viewer, ModelData extends the schedule workflow with richer field sources, logical filters, grouping, calculated and combined values, investigation in the model, and reusable definitions and results. It is sold individually or as part of the complete ub.Suite.

This summary is based primarily on the text of the official ModelData product page, supplemented by underbim’s website and suite announcement. The product page is marketing material: it describes capabilities at a high level, and some feature areas are named without detailed explanation. No user guide content, independent review, or hands-on testing was available, so those gaps are identified in the open-questions section rather than filled with assumptions.

Core Concept: Work with the Logic Behind the Schedule

The product idea is to extend Revit’s schedule workflow “with filters, grouping, derived values and model context — while keeping the native Revit schedule at the centre.” underbim frames this as four connected layers:

• Input: native and semantic fields.
• Logic: filters and structure.
• Data: calculated and combined values.
• Context: investigation in the model.

The product page includes an illustrative data-workbench preview listing walls with Element, Level, Calculated, and Status columns, in which one row is flagged “CHECK” while the others show “OK.” This suggests that calculated values and status-style results can be used to flag items for review. Because it is a marketing preview, the specific rules behind such a status column are not explained.

Six-Step Workflow

underbim describes a connected workflow in which each step, “from source data to final output,” remains part of the same process:

1. Fields: choose native, semantic, and derived data sources.
2. Filter: build conditions and logical groups around the result.
3. Structure: sort, group, and organize the schedule output.
4. Calculate: create concatenations and calculated data where needed.
5. Investigate: move from rows and values back into model context.
6. Output: keep the Revit schedule or continue into reusable results.

FilterToSchedule: Revit Schedule Snapshots With OR Statements

Overview

FilterToSchedule (F2S) is an Autodesk Revit add-in from underbim, a BIM consultancy with experience in BIM, Revit training, consulting, and software development since 2001. It is one of eight add-ins in ub.Suite Edition 1, released in late October 2026, and can be purchased individually or as part of the suite. underbim summarizes its purpose as “Filter once. Keep the result.” The add-in turns defined Revit filter results into persistent native Revit schedule snapshots that can be reviewed, refreshed, duplicated, and carried into the next workflow, either as a stored .ubr result or directly in ModelData.

This summary is based primarily on the text of the official FilterToSchedule product page, supplemented by the ModelData product page, underbim’s website and suite announcement, and Autodesk documentation on native schedule filters. The product page is marketing material: some feature areas are described in detail, while others are only named. No user guide, independent review, or hands-on testing was available, so the remaining gaps are listed as open questions rather than filled with assumptions.

Core Concept: Make the Result Persist

underbim observes that a filter is useful while it is being evaluated, but its result is not otherwise retained. FilterToSchedule turns that result into a native Revit schedule snapshot with its own identity, provenance, and controlled lifecycle. The product page frames this in four stages:

• Scope: model, category, and context.
• Logic: Filter A and Filter B with AND/OR.
• Result: a native Revit schedule snapshot.
• Continue: refresh, create a .ubr, or open in ModelData.

The page’s workflow graphic shows source elements passing through Filter A (parameter, operator, value), an AND/OR connector, an optional Filter B, and a stored, persistent schedule snapshot. This indicates that a result is built from one or two parameter conditions; the page does not state whether more conditions or nested groups are possible.

BPM — BIM Production Manager: A Dashboard for Managing Drawing-Sheet Production Inside Revit

Overview and Purpose

BPM, short for BIM Production Manager, is a Revit add-in from BREVIT LLC focused on managing drawing-sheet production inside the authoring environment. It brings sheet status, tasks, assignments, production phases, reference links, notes, sketches, PDF export, and print-set preparation into a single dashboard. Its scope is drawing-production coordination rather than geometric modeling, engineering analysis, or clash detection.

Dashboard and Sheet Management

• Modeless interface: the dashboard can remain open while users work in Revit, reducing the need to repeatedly close a dialog to return to the model.
• Sheet-set visibility: sheet cards provide an overview of the drawing set and its production status, with a detail panel for selected-sheet information.
• Grouping: sheets can be organized into groups and moved between them to support the team’s production structure.
• Sheet metadata: the documented detail workflow includes editing sheet number, sheet name, and a Reference / Link field.
• Bulk selection: selecting several sheet-row checkboxes switches the panel into bulk-edit mode. Sheet numbers and names are locked in this mode to prevent accidental collective renaming.
• Sheet duplication: a Duplicate Sheet action is documented.

Tasks, Progress, and Production Phases

• Sheet-based tasks: tasks can be added to an individual sheet or applied across multiple sheets, supporting repeated production checklists without entering the same item separately on every drawing.
• Task completion: users can check and uncheck tasks. Completion stamps record the user and time, providing context for checklist updates.
• Progress tracking: the dashboard exposes sheet-production progress. The reviewed source excerpts do not specify the calculation formula, task weighting, or whether progress can also be entered manually.
• Phase assignment: sheets can be associated with production phases and filtered to focus on the phase being prepared.
• Live phase filtering: removing a sheet from the active phase removes it from the filtered list immediately; adding a sheet to that phase brings it into the list without a manual refresh.

Revit Add-ons Eclipses 4,000 Post Mark!

We recently made our 4,000th post about a week ago with Product Roundup: Karo Modum. We knew we were close, but still ticked past the landmark. At an average of one post per day, that would be about 11 years of posts. We now sit at 4,009 published posts and slightly over 4.8 million pageviews. That makes us happy. Thank you readers!

Advertisement

LengthMEP: Measure and Tabulate the Lengths of MEP Elements

Overview

LengthMEP is a focused Autodesk Revit add-in from DQ Projects for measuring and tabulating the lengths of mechanical, electrical, and plumbing elements. Its documented capabilities combine length checks on preselected elements with the creation of category-specific and multicategory quantity schedules. The publisher also describes measurement in views and updating total values by diameter or size. Its primary purpose is quantity reporting rather than system design or engineering calculations.

Supported Revit Categories

• Electrical: conduits, wires, and cable trays.
• Mechanical: ducts and flex ducts.
• Plumbing and piping: pipes and flex pipes.

These are the seven categories explicitly identified in the Autodesk Marketplace description. Fittings, accessories, equipment, fabrication parts, and linked-model elements are not expressly identified as supported measurement categories. Their treatment should therefore be confirmed rather than assumed.

Principal Commands and Outputs

• LengthMEP command: creates quantity schedules for the supported categories, creates a multicategory schedule, and updates total values by diameter or size. This provides a reporting-oriented workflow for reviewing accumulated lengths rather than inspecting elements individually.
• Selection command: displays total length for supported elements that the user has already selected. Preselection is an explicit prerequisite in the publisher’s description, making this command suitable for focused checks of a chosen group of elements.

The two-command interface separates quick measurement from schedule-based reporting. However, the available description does not explain the schedule field layouts, sorting and filtering rules, treatment of mixed categories, or whether the reported results refresh automatically after model changes. Because an update function is explicitly mentioned, users should verify when it must be rerun.

BNotes: Advanced Keynote Manager

Overview

Bnotes—Advanced Keynote Manager is a Revit add-in from BREVIT LLC that provides a visual interface for searching, editing, organizing, and maintaining keynote text files. It retains Revit’s external .txt keynote-file workflow while reducing the need to maintain that file manually in a separate editor. Its main capabilities combine hierarchical browsing, usage indicators, inline editing, reference updates, file recovery, and coordination tools for cloud-hosted keynote files. 

Keynote Browsing and Editing

• Hierarchical tree view: Keynotes appear in a collapsible parent/child structure. The Marketplace listing identifies blue entries as used, red entries as unused, and black entries as parent or category headings. This makes project usage visible without reviewing a flat text file.
• Live search: Entering part of a keynote key or description filters the tree. The listing describes debounced searching intended to remain responsive with thousands of entries.
• Inline editing: Users select an entry and change its key or description in the detail panel. Changes can be written back to the keynote file and applied to Revit. The guide distinguishes Update Selected, Reload From File, Refresh, and Save & Apply to Revit controls.
• Adding and reorganizing notes: Users can add child or sibling entries, edit a parent key to move an entry within the hierarchy, and delete entries with confirmation. New keys are automatically numbered to follow the existing scheme, according to the listing.
• File-wide text-case tools: Descriptions can be converted to Title Case, UPPERCASE, or lowercase. These are broad standardization operations across the file, rather than selective editorial corrections.

Usage Checking and Reference Coordination

• Usage navigation: Users can click usage indicators to reach the sheets and views where a keynote is used. This provides a connection between library maintenance and placed documentation.
• Bulk reference updates: Renaming a keynote key updates placed references across sheets in one Revit transaction. The precise coverage of element assignments, annotations, and project-specific conditions should be verified in a trial.
• Orphan detection: Identification of missing-key references and entries no longer referenced. These conditions should be treated differently: an unused library note may be intentional, whereas a placed reference with a missing key requires investigation.
• Keynote types: The product page explicitly identifies element and user keynotes. The reviewed material does not clearly establish equivalent material-keynote support; firms requiring that workflow should confirm it directly.

Free ModelMedic: Model-Health Checks and Selective Remediation

Overview

ModelMedic is a model-health and QA/QC toolkit for Autodesk Revit published by ME Solutions, identified in its privacy policy as Mohamed Elzaiat. It brings six focused tools into one add-in: ModelCheck, LinkTrace, Warnalyzer, ModelMop, GridSync, and JoinMaster. Together they address repeatable model checks, link-coordinate investigation, selected warning fixes, targeted cleanup, element-to-grid alignment, and geometry join order. Its distinguishing proposition is the combination of inspection and remediation: users can identify selected problems and then address supported cases within Revit rather than collecting a report alone. The current marketplace lists the add-in as free. [1, 2]

ModelMedic - Main Window

1. ModelCheck — Repeatable Model-Health Reviews

ModelCheck lets teams set project thresholds, run health checks, review pass/fail results, share settings, and export reports to Excel (.xlsx). The developer describes a distributed workflow in which a BIM manager defines thresholds and exports settings, team members import them and run checks, and results return for review. This could support recurring coordination checks and pre-issue reviews using consistent criteria. However, the retrieved product material does not enumerate the complete metric library, threshold ranges, weighting, check-setting format, or report schema. It should not be assumed to validate arbitrary client requirements, every BIM execution plan provision, or all information-delivery standards. [1, 3]

ModelMedic - ModelCheck Settings

Product Roundup: Karo Modum

From the Karo Modum website:

Karo.ModelGuard

Prevents model degradation in real time — before bad changes reach central. Enforces modeling discipline across multidisciplinary teams with instant alerts and audit trails, without disrupting daily Revit drafting. | $99/mo or $990/yr

Karo.Segments

Parametric modeling and architectural detailing for flashings, trims, parapet copings, and facade panels. Transforms manual 2D line work into accurate, scheduled 3D elements snapped to host geometry. | $19/mo or $149/yr

Karo.WhatsChanged

Audits and tracks geometry shifts, coordinate changes, and parameter modifications whenever consultants reload linked models. Pinpoints exact additions, modifications, and deletions without cloud processing or file size limits. | $15/mo or $120/yr

Karo.WhyHidden

Instantly diagnoses why an element is invisible in your active view and guides you directly to the fix. Eliminates minutes of manual troubleshooting through nested visibility graphics, design options, and phase settings. | $9/mo or $69/yr

Advertisement

Karo.Segments: Creating & Managing Architectural Segments as Plates on Host Geometry

Overview

Karo.Segments is a Revit add-in from Karo Modum for creating and managing user-defined architectural segments as plates on host geometry. Its advertised applications include flashings, trims, parapet copings, cover strips, drips, panels, cassettes, and sheet-material layouts. It combines face-and-edge-based placement, a mark-based catalog, dimensional editing, overlap controls, schedules, and display management. The central proposition is a connected modeling-and-documentation workflow for repeated envelope components, rather than a collection of separately modeled details. The vendor’s manual and demonstration are the principal evidence for this summary; they do not constitute independent testing. [1, 2]

Placement and Editing Workflow

1. Choose or define a segment: Select an existing catalog mark or enter type parameters. The placement form foregrounds type and length, with additional fields available in an expanded view.
2. Reference model geometry: Placement uses a selected planar face and reference edge. The manual describes magnetic snapping near segment ends and face corners, with other positions moving along the edge in 5 mm increments.
3. Set orientation: Rotation and mirroring controls support positioning relative to the host. The manual distinguishes the add-in’s rotation control from Revit’s native Rotate command, which it says is blocked for Karo plates.
4. Place and manage: The segment appears in the model and catalog as a Karo plate. Selecting a catalog row selects matching elements; selecting a plate highlights the corresponding catalog entry.
5. Edit dimensions and data: Parameters can be edited in the hub, Revit Properties, or native schedules using shared fields. The manual says invalid values are reverted with a notification.
6. Refine joints and documentation: Adjust overlap and side-offset settings, review geometry and appearance, and prepare schedules with profile illustrations. [1, 2]

Karo.ModelGuard: Enforce Selected BIM Standards While Users Work

Overview

Karo.ModelGuard is a team-oriented Revit add-in from Karo Modum that enforces selected BIM standards while users work. Rather than waiting for a scheduled model audit to report problems after they have entered the central model, ModelGuard intercepts configured actions at transaction time. Depending on policy, it can block the action, require a written justification, allow it, or record it. The vendor positions the product for protecting coordination references, datum elements, documentation integrity, and modeling standards across multidisciplinary teams. Its emphasis is prevention and traceability, not general-purpose model-health analysis.

Operating Model

1. Define policies: A BIM administrator configures a centralized policy matrix for the team’s protected Revit actions.
2. Assign an enforcement mode: Each rule can be configured to prevent an action, require an explanation, or permit it under the chosen governance model.
3. Distribute centrally: Policy files are stored in a shared on-premises network folder. The vendor states that connected users receive policy updates without a Revit restart and without a separate database server.
4. Intercept user actions: ModelGuard evaluates configured changes as users attempt them, before problematic edits reach the central model.
5. Respond in context: A user sees an immediate alert. A strict rule stops the action; a justification rule requires a reason before an exception proceeds.
6. Record the event: The shared audit trail captures details such as user identity, time, affected element IDs, action, and stated reason.
7. Monitor deployment: A workstation monitor reports connected clients and policy status across the team.

Karo.WhyHidden: A Visibility-Diagnostics Add-in

Overview

Karo.WhyHidden is a Revit visibility-diagnostics add-in from Karo Modum. It investigates why a known element does not appear in a particular view, bringing together checks that would otherwise require opening several Revit settings dialogs. The vendor describes 16 visibility checks covering direct hiding, graphics settings, spatial clipping, worksets, phasing, design options, linked-model display, and view-template control. Findings appear as diagnostic cards identifying relevant settings, filters, or worksets. Selected issues have one-click fixes; others receive guidance. The product is primarily a troubleshooting aid rather than a model-wide QA engine or an automatic redesign of view standards. [1-3]

Typical Workflow

1. Identify the element: Select it in a view where it is visible, or use its element ID. This is a targeted investigation of a known object, not a search for an unidentified missing object.
2. Activate the problem view: Switch to the plan, section, elevation, or 3D view where the element should appear.
3. Run Why Hidden: Launch the command from the Karo ribbon tab.
4. Review diagnostics: Read the cards identifying visibility blockers and the settings responsible. Multiple conditions may apply at the same time.
5. Resolve appropriate conditions: Use an available quick fix or follow the guidance, retaining control over office templates and shared standards.
6. Verify and communicate: Confirm the intended display and copy the formatted diagnostic report into a team chat or task tracker. [2]