> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ideatura.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Schedules

> Build a door-schedule automation from an empty chat or a CSV reference, check the model data and save the workflow.

Ask Ideatura to create schedules for any category available to schedule in Revit—doors, windows, rooms, furniture or equipment—and propose a clear structure for the information you need. You can describe the schedule in chat or attach an existing CSV as a reference.

This example builds a reusable automation for a door schedule, starting from an empty chat.

## 1. Describe the schedule

Open your project and start a new chat with the correct Revit document connected. Explain which doors to include and what the schedule should show.

> Create an automation for a door schedule on \[level] in \[phase], using the host model only. Include door number, family and type, room names, width, height and fire rating where those parameters are available. Use millimetres, show one row per door and sort by door number. Propose the structure first and flag missing information rather than inventing values.

Start with one level so you can check the result before extending it to the whole project.

![Generated door-schedule automation; 1 opens its parameters.](https://mintcdn.com/ideatura/JNHm3Ld9n-R1QMJY/images/schedule-build/created.svg?fit=max\&auto=format\&n=JNHm3Ld9n-R1QMJY\&q=85\&s=f791444a06f737bedcb283d8966c5dd3)

## 2. Choose the information and structure

Think about who will use the schedule and what they need to find. A practical door schedule can include:

| Information | Example fields |
| - | - |
| Identification | Door number, family and type |
| Location | Level, from-room and to-room |
| Dimensions | Width and height |
| Specification | Fire rating, door and frame materials, finishes |
| Coordination | Hardware set, detail reference, comments |

Ask Ideatura to use your existing parameters and identify any missing fields before adding new ones.

For this example, keep **one row per door** so individual requirements remain visible. A separate summary grouped by type can provide quantities. Revit supports both itemised and grouped schedules. [Autodesk’s examples](https://help.autodesk.com/cloudhelp/2026/ENU/Revit-DocumentPresent/files/GUID-C9407EBB-C78C-45DA-AB6D-D9F6B09274C5.htm).

## 3. Start from an existing CSV

You can attach an office-standard CSV and ask Ideatura to recreate its structure as a native Revit schedule.

> Use this CSV as the reference for the door schedule’s headings and column order. Match its columns to the parameters in my model. Show me the mapping and identify missing or ambiguous fields before creating the schedule. Keep existing model values unchanged.

If you also want to transfer values from the CSV, specify how rows should match doors—for example, by a unique door number. Ask to preview changes and flag duplicate or unmatched numbers before updating anything.

![Ideatura maps CSV headings to existing Revit parameters.](https://mintcdn.com/ideatura/JNHm3Ld9n-R1QMJY/images/schedule-build/mapping.svg?fit=max\&auto=format\&n=JNHm3Ld9n-R1QMJY\&q=85\&s=6660f418625cb7400c4f302e43fb8ad2)

## 4. Make the automation reusable

Ask for controls you can adjust on another project:

> Add inputs for the level, phase, schedule name, fields and sort order. If the named schedule already exists, update it rather than creating another copy.

The form below selects **1 level**, **2 phase**, **3 schedule name**, **4 fields** and **5 sorting**. Check these choices, then select **6 Run**. This example includes host-model doors; ask for linked models or grouped totals if your project needs them.

![Inputs for level, phase, schedule name, fields and sorting, followed by Run.](https://mintcdn.com/ideatura/JNHm3Ld9n-R1QMJY/images/schedule-build/controls.svg?fit=max\&auto=format\&n=JNHm3Ld9n-R1QMJY\&q=85\&s=1a47ac17edb3c59604d43dd6835badab)

## 5. Check the schedule against the model

Run the automation and open the resulting schedule in Revit. This example contains **79 doors**. A second run updated the same schedule without creating another copy. Three sampled doors matched across all eight columns. Compare several rows with the corresponding doors in your own project.

Check door numbers, room associations, dimensions and the number of included doors. Confirm what the width parameter represents in your families: leaf width, nominal size or opening width.

Check fire ratings and hardware against the project information. Creating the schedule does not supply missing specification data.

![First rows of the native door schedule: door number, level, family and type.](https://mintcdn.com/ideatura/JNHm3Ld9n-R1QMJY/images/schedule-build/result-identification.svg?fit=max\&auto=format\&n=JNHm3Ld9n-R1QMJY\&q=85\&s=6373fc1dbba1fba1fee8eef01a9f2754)

![The same rows: room associations, width, height and fire rating.](https://mintcdn.com/ideatura/JNHm3Ld9n-R1QMJY/images/schedule-build/result-values.svg?fit=max\&auto=format\&n=JNHm3Ld9n-R1QMJY\&q=85\&s=ef7ce020409afa704113e9df25af1501)

## 6. Refine and save

Ask for a focused adjustment:

> Sort the doors by family and type, then by door number. Keep one row per door and retain the existing columns.

Inspect the revised schedule, then save the automation with a clear name. Save the Revit project separately. When reusing it, check that the new project has the parameters and scope the automation expects.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.