Teach an AI Your Revit Workflow with a Screen Recording

You can teach an AI your Revit schedule workflow by recording a concise walkthrough that states the schedule’s purpose and rules, shows one included and one missing element, and defines permissible checks or proposals. Attach the schedule rows export and, separately, the schedule’s filter and itemization settings plus the element IDs you’re questioning. Ask the AI to explain exclusions, suggest safe instance-level edits, and return deltas and exceptions.

What to record when teaching an AI your Revit workflow

A short, narrated recording paired with source artifacts can help an AI assistant understand your investigation steps. In the recording, speak to:

• Purpose and scope: What the schedule is used for, which categories and phases are in-scope, and what must be excluded.
• Inclusion rules: The specific fields and filters that govern membership, not just what a view happens to display.
• Two examples: One element that’s included and one that’s missing, shown side-by-side with the Properties palette.
• Edit boundaries: Which instance parameters (if any) may be proposed for change, and which are off-limits.
• Acceptance checks: How you’ll verify any proposal and what you expect returned (delta notes, exceptions).

With that package, an AI can enumerate candidates, explain why each excluded element fails a rule, compare included vs missing parameters, draft a proposal limited to allowed instance fields, and produce an exceptions note for anything that shouldn’t be edited. The steps here are recommended team procedures and deliverables you can request—not product UI buttons or a guarantee that every task is supported in every environment.

If you use ArchiLabs Desktop, you can upload a screen recording with narration, annotated screenshots, selected Revit elements, PDFs and spreadsheets so the AI sees both how and why in one package. Integration availability depends on your application version, plan and permissions.

A 90-second screen recording plan for a Revit task

Use this as guidance, not a time guarantee.

• 00:00–00:10 — Show the issue and who cares
• On screen: Equipment schedule beside a model view (the model view is context; the schedule’s filters govern inclusion).
• Say: “This Equipment Schedule feeds the asset register. It shows 98 rows; we hypothesize 101 once rules and itemization are applied.”
• 00:11–00:22 — State the rules, not just what’s visible
• On screen: Schedule Properties > Fields, Filter, Sorting/Grouping, Formatting; confirm Itemize every instance.
• Say: “Include Category = Mechanical Equipment; Phase = New Construction; exclude Demolished; ‘Asset Required = Yes’; links off; itemize instances.”
• 00:23–00:35 — Demonstrate one missing candidate
• On screen: Select a chiller you believe should be included; keep the schedule visible; show Instance vs Type panels.
• Say: “This Level 02 chiller has ‘Asset Required = Yes’ but is missing from the schedule.”
• 00:36–00:47 — Show a valid included peer
• On screen: Select a similar chiller that is included; show the same fields.
• Say: “This near-identical unit appears. Compare the parameters and the schedule settings to investigate the exclusion.”
• 00:48–00:59 — Call out only drivers of inclusion
• On screen: Pause on Phase Created/Demolished, ‘Asset Required’, any ‘Include in Asset Register’, and whether Itemize is collapsing rows.
• Say: “Membership depends on Phase, inclusion flags, and itemization—not on reported capacity.”
• 01:00–01:12 — Define the fix boundary
• On screen: Return to the schedule.
• Say: “Allowed proposals: instance ‘Asset ID’ and ‘Comments’. Not allowed: Type edits, Phase edits, Design Option changes, From/To Room, or broadening filters. The 101 count is a hypothesis, not a target to force.”
• 01:13–01:30 — Ask for checks and deliverables
• On screen: Briefly highlight Filters and Itemize again.
• Say: “Please explain each missing ID against the rules, propose safe instance edits where appropriate, re-export rows, and include an exceptions note.”

Also export the schedule rows using the available Revit export or a verified spreadsheet integration and separately document the Schedule Properties (Fields, Filter, Sorting/Grouping, Formatting) plus whether Itemize every instance is on. A schedule export does not automatically include all filter or model settings.

Revit workflow example: find a missing Asset ID in an equipment schedule

Scenario (hypothetical): The Equipment Schedule for “Level 02 – Mechanical” shows 98 rows; you hypothesize 101 after correcting data. You believe three air handlers (IDs 492811, 492823, 492835) should be included.

Attachments you supply:

• Equipment_Schedule_L02_2026‑11‑04.csv (rows only).
• Two screenshots of Schedule Properties labeled “Fields/Filter/Formatting” and “Sorting/Itemize”.
• Two annotated Properties screenshots: one included AHU (AHU‑02A) and one missing AHU (AHU‑02C). Add source labels to each shown field, for example: Asset ID [Instance], Asset Required [Type], Include in Asset Register [Calculated], Equipment Class [Key], Phase Created [Instance]. These source labels help the AI reason which fields are safe to propose and which are governed elsewhere.

What you ask the AI to do:

• Validate rules vs the Schedule Properties you provided; do not infer from the model view.
• For IDs 492811, 492823, 492835, report the specific failing rule(s). Example outcomes it might find (hypothetical): Itemization was off causing type aggregation; the missing units have Asset ID = blank while a filter requires non-empty; one unit has phase data that does not match the schedule context.
• Draft a proposal limited to allowed instance fields: use only approved Asset ID values from the asset register where ‘Asset Required = Yes’ and Phase = New Construction are already true; never modify shared Type values to change selected instances.
• Return an updated rows export and a short delta note; list exceptions where an edit would violate the rules (e.g., wrong Phase) or where the value’s source is Type/Key/Calculated.

The “101” count remains a hypothesis until filters and itemization are validated. Row counts do not equal element counts unless itemization and filters establish that. A schedule of selected objects does not prove other objects stayed unchanged.

For more context capture practices, see the guidance in Revit Model Context Protocol. To streamline building the actual schedule outputs once rules are stable, you can adapt patterns from Auto‑Build Schedules and Sheets with AI this Weekend.

Pair your recording with Revit elements and source files

Video explains the operator's intent, but it may omit fields, filters or linked-model context. Read the relevant native properties and schedule configuration before drawing a conclusion. A calculated schedule field can differ from stored instance data, and a shared type value can affect many objects beyond the selected example.

Keep the exported rows and configuration screenshots together with the project document and version. A duplicated view is still a live view of the model, so it does not preserve a before state. Capture a real export before any approved edit and reread the affected objects afterward. Validate the entire proposed change set, rather than changing data until the expected row count appears.

A prompt template for a recorded Revit workflow

“Evaluate the attached Equipment Schedule workflow. Rows export (CSV) and separate screenshots show Fields/Filters/Formatting and Itemize. Analyze element IDs 492811, 492823, 492835 against the stated rules. Propose only safe instance edits (Asset ID, Comments). Do not alter Type, Phase, Design Option, or From/To Room. Return an updated rows export, a concise delta, and an exceptions note where edits are not appropriate.”