Summary
Schema is a Revit add-in designed to streamline BIM project setup by automating the reuse of standard sheet and viewport arrangements. It addresses a common source of repetitive work for BIM managers, template administrators, and project teams: rebuilding the same drawing set structure on every new model. Instead of manually laying out sheets, viewports, and schedules project after project, teams can define a standard arrangement once and apply it consistently across future Revit models.
Core Purpose
In many BIM environments, drawing set organization is standardized across projects, but the setup process still requires substantial manual effort. Sheet names, viewport placements, schedule locations, and drawing arrangements are often recreated from scratch even when a proven layout already exists. Schema captures the structure of an established drawing set and converts it into a portable schema file that can be reused without transferring model geometry, project-specific content, or full template files.
Two-Step Workflow
Schema works through a two-step process: first capturing a layout from a source model, then assembling that layout in a target model. This approach separates drawing set standards from project-specific data, allowing teams to maintain reusable documentation layouts that can be safely shared, versioned, and applied across different projects.
Edit Schema: Capture the Source Layout
The workflow begins in a Revit model that already contains the desired sheet and viewport arrangement. Using the Edit Schema command, Schema scans all sheets, viewports, and schedule instances and displays the complete drawing set on an interactive canvas. Viewports appear as gold rectangles, while schedule instances appear in blue, giving users a visual representation of the exact geometric arrangement of their documentation set.
Within the Schema Editor, users can review the detected layout and make adjustments to viewport or schedule positions if needed. Once the layout is approved, it is saved as a portable .schema.json file. This file stores sheet names, viewport positions, viewport sizes, view types, and schedule placement data, but it does not include model geometry or sensitive project-specific information. As a result, the schema can be safely shared across teams, archived for future use, or managed in version-control systems.

























