You can create Revit sheets from an Excel drawing register with AI assisting the checks, not replacing them. The practical flow is: prepare a register with the right fields, reconcile conflicts against the Revit model, then create only the clean rows. AI helps map columns, verify title block types and views, flag duplicates or holds, and draft the sheet‑creation brief you’ll run.
Map Excel columns to Revit sheet numbers, names, and views
For a drawing register that cleanly drives sheet creation, keep these fields tight and mappable:
• Sheet Number (e.g., A101) — must be unique at creation time
• Sheet Title — maps to the Revit Sheet Name shown by the title block label
• Title Block Type — exact Family:Type name you use for that sheet
• Primary View (target) — the exact View Name or, preferably, a verified native element ID with its document context
• Viewport Title Override (optional) — if populated, sets the view’s displayed title on the sheet; if blank, leave the view’s own Title on Sheet as is
• Status — Approved, Reserved, or Hold
• Notes (optional) — clarifications for placement or coordination
Important distinctions you must honor:
• Sheet Name, View Name, and Title on Sheet are three different fields. In Revit, the View Name appears in the Project Browser, and the viewport’s displayed title can be independently overridden by the view’s Title on Sheet property. Autodesk explains this separation in its documentation; see Revit view name and Title on Sheet behavior.
• The register’s “Sheet Title” should map to the Sheet Name (title block label) only. Do not push it automatically to Title on Sheet.
• Use the optional “Viewport Title Override” column when you intentionally want the viewport’s displayed title to differ. If left blank, the existing Title on Sheet stays; if that’s empty, Revit shows the View Name.
• Names alone are weak identity. If your team can capture the view’s element ID, include it to avoid mis‑mapping views with similar names.
For context on automating view and sheet setups, see this complementary guide: Automate Sheet Creation and View Creation in Revit.
Check existing sheets, title blocks, and duplicate view placements
Fold these checks into your register review so that creation is a short, deterministic step:
• Numbering and placeholders
• Is the Sheet Number already in the model? If yes, treat as “Skip — Exists.”
• Is the number explicitly Reserved or a placeholder in your sequence? If yes, mark “Hold — Reserved.”
• Is there a duplicate within the batch or conflicting with an existing sheet? If yes, mark “Hold — Duplicate” until coordination assigns a free number.
• Title block family and type
• Verify the exact Family and Type exist. If the type is missing, keep the row on Hold until it’s created or a valid substitute is chosen.
• View existence and eligibility
• Confirm the referenced view exists (by ID or name) and is the correct one for the sheet.
• If it’s already placed on a sheet, your register should specify whether to reuse that sheet (usually skip) or proceed differently.
• Check practical placement constraints: printable crop region, orientation, and scale conventions for the discipline. These checks reduce avoidable placement failures but don’t guarantee every view can be placed repeatedly across sheets.
• Identity preservation
• Where possible, tie rows to view IDs and title block type names, not just labels. That prevents silent drift when names are edited mid‑batch.
Excel-to-Revit sheet example: review a four-row drawing register
This example is hypothetical.
This worked example shows the four decisions you’ll encounter most often. Each row lists the key fields and the pre‑creation outcome.
• Existing sheet — Skip
• Row: A101 | Sheet Title: “Floor Plan – L1” | Title Block: A1 30x42 | Primary View: “L1 – Arch Plan” | Status: Approved
• Model check: A101 exists; view already placed. The register’s Sheet Title differs slightly.
• Decision: Skip — Exists. If a separate metadata update is approved, update only the Sheet Name to “Floor Plan – L1.” Leave the viewport Title on Sheet unchanged unless your “Viewport Title Override” column is explicitly filled.
• Reserved number — Hold
• Row: S000 | Sheet Title: “Structural General Notes” | Title Block: S1 30x42 | Primary View: “S – Notes” | Status: Reserved
• Model check: Number is intentionally parked for front‑matter sheets.
• Decision: Hold — Reserved. No creation.
• Duplicate number — Hold for coordination
• Row: M201 | Sheet Title: “Level 2 Duct Plan – West” | Title Block: M1 30x42 | Primary View: “L2 – Duct (W)” | Status: Approved
• Model check: Sheet M201 already exists for a different view in the model.
• Decision: Hold — Duplicate. Coordinator assigns the next free M‑series number (e.g., M202) before creation proceeds.
• Clean, new sheet — Create
• Row: P101 | Sheet Title: “Plumbing Plan – L1” | Title Block: P1 24x36 | Primary View: “L1 – Plumbing Plan” | Status: Approved
• Model check: Number is free; title block type exists; the view exists and isn’t already placed; printable crop looks valid.
• Decision: Create. Sheet Name set from the register; view placed; viewport title uses the override only if that column is filled.
Create Revit sheets and place approved views from the register
Treat execution as three distinct stages:
• Creation (sheets only)
• Create sheets for rows marked Approved with no unresolved holds.
• Assign the specified Title Block Type and the Sheet Number.
• Set the Sheet Name from the register’s Sheet Title.
• Placement (views on sheets)
• Place the Primary View referenced by ID/name on its sheet.
• If the “Viewport Title Override” column has a value, set the view’s Title on Sheet to that value; if blank, leave the view’s own Title on Sheet unchanged.
• Do not assume a copied view is a frozen snapshot; duplicated views inherit parameters and can change later with edits.
• Documentation review
• Read every sheet in the small pilot in-app: number uniqueness, correct title block type, Sheet Name as intended, viewport title behavior as intended, and reasonable crop/scale for printability.
• After a small pilot is accepted, widen the batch using the same criteria.
How AI helps with spreadsheet-driven sheet creation
An assistant can:
• Parse your spreadsheet, standardize column headers, and normalize values (discipline codes, Family:Type names, and view identifiers).
• Cross‑check your register against the open model: detect existing numbers, verify title block families and types, and confirm referenced views exist and whether they’re already placed.
• Propose fixes (e.g., “Duplicate — suggest M202,” “Missing type — choose valid substitute?”) and assemble a clean brief listing only create‑ready rows.
• With your authorization, help create sheets and place views so your operator focuses on exceptions and review.
ArchiLabs users can also supply screen recordings with spoken explanation, annotated screenshots, selected Revit elements, PDFs, and spreadsheets to give the assistant precise context. See how ArchiLabs Desktop works alongside Revit on Windows for this assisted workflow.
For scope realism—what today’s tools do well versus what requires operator judgment—this overview is useful: What AI Can and Can’t Do in Revit Today: A Clear Guide.
Test a small drawing register before creating the full sheet set
Create a four‑row pilot register like the example above, reconcile it against your model, and run just that subset. Confirm the Sheet Name vs Title on Sheet behavior matches your standards, verify placement eligibility, and read each pilot sheet in detail. Once the pilot meets your criteria, extend the register to the next batch and repeat the same checks.
Learn how to automate sheet and view creation in Revit, and discover how ArchiLabs Studio Mode — a standalone, web-native CAD platform — streamlines documentation workflows.
Understand what Revit AI can do, where model access and source data limit results, and how to review geometry, parameters, and documentation.