Autodesk also provides guidance on the Assistant’s intended scope. When asked about its limitations, the Assistant returns a lengthy list of tasks it cannot currently perform, followed by a clear summary of where it is designed to be most effective:
“What I'm best at: querying your model, analysing elements, modifying parameters, creating views and schedules, organising documentation, and answering how‑to questions about Revit workflows.”
This clarification usefully sets expectations, positioning the Assistant as a tool for model querying, coordination, and light automation rather than full model authoring or more complex decision‑driven workflows.
Once familiar with its range of capabilities, the Assistant can be genuinely useful, but effective use depends on writing clear and specific prompts. Requirements such as naming and numbering conventions must be explicitly stated, particularly when creating views or sheets. More complex tasks often need to be broken into multiple steps for example, creating sheets first and then issuing follow‑up prompts to change title blocks or adjust naming and numbering.
The potential of the AI‑driven Assistant is significant, but it needs to be tested carefully against real projects and workflows. One area where it may add value is in model checking and data aggregation tasks, such as:
- Verifying whether COBie parameters have been completed
- Checking that parameter values follow the correct format
- Populating parameters by combining values such as Room Number, Type Mark, and a sequential identifier
- Highlighting elements where required data is missing or incorrect
Whether the Assistant can replace established add‑ins and scripted workflows remains debatable. Experienced Revit users can often complete the same tasks just as quickly. if not quicker, using familiar tools, and purpose‑built add‑ins with task‑specific interfaces are likely to remain more efficient for repeated use than continually re‑prompting an AI tool.
The Assistant also relies entirely on standard Revit functionality. It cannot load families or perform broader model edits, and actions such as tagging or view placement are carried out using existing Revit tools.
For less experienced users, the Assistant may provide a quicker way to find answers to common questions than searching documentation or online resources.
Overall, it feels like a sensible first step, pitched at an appropriate level given current industry caution around AI. As with any AI‑based tool, its outputs should be reviewed carefully, and it should not be relied upon for business‑critical tasks. Each team will need to assess where it meaningfully reduces time spent on their most repetitive or time‑consuming activities.