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.
Key Facts
- Purpose: Generate plan, section, and 3D view sets from selected Revit Scope Boxes.
- Product family: One of eight independent add-ins in ub.Suite Edition 1, covering the suite's "views" workflow area.
- View set: For each Scope Box, up to six views: one plan, four sections, and one 3D view. Only the selected output types are created.
- Scale: Standard scales, or a custom scale from 1 to 5000 that defaults to 1:50 and is checked before creation.
- Reversibility: Each creation run is committed as one Revit transaction and can be undone with Revit Undo.
- Licensing: Perpetual license by Edition. Updates within the Edition are included, and major Edition upgrades are optional. Single-activation and two-activation options are offered.
- Documentation: The product page links to setup and documentation. underbim also has a Downloads area, a Customer Portal, and a public GitHub repository for signed releases and update manifests.
The Product Idea
The tool is built on one idea: use the Scope Box as the spatial instruction. ScopeViews starts from the project scope you've already defined. Each selected Scope Box becomes the shared spatial basis for the views you choose to create and for the display rules applied to them. The process moves through four stages: Scope (selected Scope Boxes), Views (plan, sections, 3D), Represent (templates and scale), and Result (a named, marked view set).
Workflow: Select the Scope, Build the View Set
One setup screen controls what is created, how it's displayed, and how the result is reported:
- Scope Boxes: Select one or more project Scope Boxes as the spatial source. Select All and Clear make it quick to set up or reset a run.
- View types: Choose plan, sections, and/or 3D. At least one output type is required.
- Templates: Use a separate view template for each view type, or reuse one template across the set.
- Scale: Choose a standard or custom scale, and decide whether it overrides the template's scale.
- Create: Generate the chosen views and apply the scope, display settings, and marker data.
- Review: Read the Status output for created views, naming adjustments, and template or scale conflicts.
The Generated View Set: One Scope Box, Up to Six Views
The selected Scope Box drives the geometry of every chosen output. The plan, sections, and 3D view all stay tied to the same spatial definition, with no manual setup view by view:
- Plan: Creates one plan on the level closest to the Scope Box's minimum Z (its lowest point) and applies the selected Scope Box.
- Four sections: Creates two sections along the box's length and two along its width, placed at the box's edges and facing inward.
- 3D: Creates one isometric 3D view that uses the selected Scope Box as its spatial extent.
- Selective output: Plan, sections, and 3D are independent options, so you create only what you need.
Because several Scope Boxes can be processed in one run, a multi-zone project can get a full, consistent set of views for every zone in a single operation.
Templates and Scale
How the views look is decided before they exist. Templates and scale are resolved during creation, and any conflicts are reported instead of interrupting you with extra pop-ups:
- Separate templates: Plan, sections, and 3D can each use their own compatible view template.
- Same template: Reuse the plan template across the plan, section, and 3D outputs. The template's properties are applied to the views, but the views aren't left permanently linked to the template.
- Scale precedence: By default, the template's scale wins. Turning on Override View Template Scales forces the scale you chose, and the Status area reports the result.
Naming, Marking, and Status
- Naming: Generated views are named after their Scope Box, for example "Scope - Plan" and "Scope - 3D." If a name is already taken, a unique name is used instead.
- ub_SVMarker: ScopeViews makes sure a marker parameter exists on views and writes a Scope Box–specific value to each view it creates. This makes the generated views easy to identify later.
- Status: Created views, warnings, naming adjustments, and template or scale conflicts are reported in a Status area instead of through repeated dialogs.
- Undo: Each creation run is committed as one Revit transaction, so you can undo it in one step.
Place Within ub.Suite 1
ub.Suite 1 includes FilterToSchedule, ModelData, InterferenceInvestigator, ProjectManager, ConstraintScanner, ScopeViews, Elevations, and BackupMover. ScopeViews fits alongside two related tools:
- ProjectManager: Audits scope boxes, V/G filters, view templates, and views. It classifies them as used, unused, or unreferenced and supports controlled cleanup. ScopeViews is the creation side of this pair: it generates views from Scope Boxes, while ProjectManager reviews and cleans them up.
- Elevations: A separate view-related tool in the suite. ScopeViews generates sections, not elevations, which fits underbim's approach of splitting view workflows into specialized tools.
ScopeViews follows the suite's shared design approach. Choices are made up front, each run can be undone in one step, and results are reported clearly. The Status area replaces repeated pop-ups, and the ub_SVMarker parameter keeps generated views traceable after the dialog closes.
Compared with Native Revit Tools
Open Questions
- Does it create dependent views or reflected ceiling plans, or only the plan, section, and 3D outputs described?
- Can it update or regenerate an existing view set after a Scope Box changes, or only create new views?
- Can view naming be customized beyond the "Scope - Plan" pattern, for example with prefixes or discipline codes?
- Does it place generated views on sheets?
- Does it work with Scope Boxes from linked models?
- How are rotated Scope Boxes handled when placing sections and the 3D extent?
Bottom Line
ScopeViews targets a common, time-consuming part of Revit documentation: setting up consistent views around project zones. It turns each selected Scope Box into up to six views. Templates, scale, and naming are decided before creation, conflicts are reported in one Status area, and each run can be undone in one step. For BIM coordinators managing large, multi-zone projects, it's a focused tool for faster, more consistent view setup.
Sources
- ub.ScopeViews product page
- ub.Suite 1 overview
- ub.Suite 1 launch announcement
- underbim signed releases repository
- Revit Add-ons: ProjectManager summary
- Autodesk Help: Create a Scope Box
- Mashyo: Scope Box in Revit guide
- Autodesk Community: Scope box visibility issue
- Autodesk Community: Scope boxes on dependent views
Advertisement
No comments:
Post a Comment