Automate Revit Sheet Creation and Numbering in 2026

The best way to automate Revit sheet creation depends on what must happen after the first successful run. Use Dynamo for a project-specific batch, pyRevit for a script your technical team can own, an established suite for a standard workflow, or a managed custom add-in when firm rules, deployment, and ongoing releases matter.

The upside can be large. In one vendor-documented residential tower example, a script placed more than 200 floor plans on sheets in under an hour, compared with a week of manual work. Treat that as a case study rather than a universal benchmark, but the workflow is real: create sheets, assign numbers and names, choose title blocks, place views, and catch conflicts before committing changes. Remote AE documents the example and its Dynamo setup.

Revit does support sheet lists and placeholder sheets, but Autodesk describes placeholders primarily as a way to represent sheets that are not yet in the model. They do not automate the full sequence of creating production sheets and placing views. Autodesk's sheet-list guide explains the native workflow.

• Best fit: One project or occasional batch; Approach: Dynamo; Main tradeoff: Fast to prototype; package and graph dependencies need an owner
• Best fit: Reusable tools owned by a technical team; Approach: pyRevit; Main tradeoff: Flexible; the team owns deployment, testing, and support
• Best fit: Standard sheet workflows; Approach: CTC or Ideate; Main tradeoff: Mature and supported; the workflow follows the vendor's product
• Best fit: Firm-specific workflow used by a team; Approach: Managed custom add-in; Main tradeoff: Encodes your rules; requires clear requirements and release ownership

Option 1: Dynamo for a project-specific batch

The common Dynamo graph reads a sheet list from Excel or model data, creates sheets, assigns a title block, and places views by a matching rule. It is a strong first choice when one person needs to process one project and can inspect the result immediately.

The risk appears when the graph becomes shared infrastructure. A change in title-block families, view naming, Dynamo itself, or a third-party package can create a second branch of the graph for the next project. A 2026 Dynamo forum thread captures the maintenance problem: an upgrade from Revit 2023 to 2026 left a user working through dependencies across roughly 30 scripts. The responses recommend auditing custom packages and reducing unnecessary dependencies. Read the full thread and the fixes that followed.

If you choose Dynamo, keep the graph in version control, record its package versions, test it against a copy of the model, and name an owner. SheetCreator_FINAL_v2.dyn on a shared drive is a distribution method, not a maintenance plan.

Option 2: pyRevit for a technical team

A pyRevit command can handle conditional numbering, duplicate checks, discipline-specific rules, and error messages that become awkward in a large visual graph. It can also expose the workflow as a familiar ribbon command.

pyRevit has real team-deployment machinery. Its CLI can clone and update a controlled source, attach it to installed Revit versions, and manage extensions. The current pyRevit developer guide documents the supported clone workflow. That makes pyRevit much more than a personal-script folder.

The firm still owns the operational layer: extension releases, endpoint packaging, compatibility testing, support, and the response when a custom command fails on a live model. This is a good trade when a design technology team already wants that responsibility.

Option 3: Buy a supported suite

Commercial suites are the straightforward answer when their sheet workflow already matches yours. CTC's BIM Project Suite includes Sheet Assistant for repeatable sheet creation and view placement, and its public shop currently lists the suite at $410. See CTC's Sheet Assistant capabilities and current shop price.

Ideate SheetManager supports batch creation from existing sheet compositions. IdeateApps is currently $495 per year for a standalone license, with network and volume options. See the IdeateApps product and current pricing.

The buying question is simple: does the suite encode enough of your real standard? If your exception list is longer than the setup guide, you may still need a custom tool for the gap.

Option 4: Build a custom add-in around your rules

A compiled add-in makes sense when sheet setup is a recurring firm workflow with stable rules: for example, read an approved sheet list, apply a discipline-level-sequence numbering pattern, use the firm's title block, flag collisions, place eligible views, and produce a review log.

Conduit's Sheet Manager starter gives a BIM/VDC lead a structured way to describe that workflow. Conduit plans the app, generates it through a pull-request and build gate, stores versioned releases, and deploys Conduit-built apps to assigned users through the Desktop Runner. The Runner verifies the exact bundle hash, performs a structural smoke test, and reports installation and runtime health.

There are two boundaries worth stating. Conduit does not import and manage every third-party add-in already in a firm's stack. A new Revit release can still require a compatible build and validation; no platform removes API changes.

Choose based on the operating model

Use Dynamo when the person building the graph will also run and inspect it. Use pyRevit when a technical team wants a flexible scripting platform and accepts ownership of its deployment. Buy CTC or Ideate when the standard product covers the workflow. Use a managed custom add-in when the value comes from encoding firm-specific rules and delivering the same release to a wider team.

Whichever path you choose, write the exceptions before writing the automation. Define the trigger, inputs, outputs, numbering conflicts, excluded sheet types, and owner. Most failed sheet tools are technically capable; they fail because a rule such as "skip presentation sets" lived only in one person's head.

Frequently asked questions

Can Revit create multiple sheets without an add-in?

Revit can create and manage placeholder sheets through a sheet list. Turning those placeholders into production sheets, assigning title blocks, and placing views still requires additional steps. Dynamo, pyRevit, or an add-in can automate that sequence.

Should a sheet automation write directly to the live model?

Start with a copy and produce a preview or validation report before creating anything. At minimum, check duplicate sheet numbers, views already placed elsewhere, missing title blocks, excluded sheet types, and transactions that partially fail.

When is Conduit the wrong choice?

If this is a one-time batch, use Dynamo. If an off-the-shelf tool already matches the standard, buy it. Conduit fits recurring, firm-specific workflows that need a generated tool plus versioned delivery and operational visibility.

Conduit's Sheet Manager starter is available in the template gallery. Describe your sheet rules and start with 100 trial credits. No credit card is required.