Claude for Revit: Model Queries, Scripts, and Review

Claude can help Revit users draft Dynamo scripts, query model data, review documentation, and work through Revit API calls. There is no Anthropic-built Revit plugin; the workflow involves drafting in Claude and running the result in Revit yourself. Every model change needs a human check before it goes into a project file. Tools like fenbs keep requirements, assumptions, and approved model changes recorded so the next engineer or assistant starts from the agreed baseline.

Revit projects carry high stakes. A script that moves elements incorrectly, changes parameter values, or deletes worksets can create problems that reach far downstream. Treat Claude's output as a draft for review, not as production-ready code, until you have tested it in an isolated environment.

What Claude can help with in Revit work

• Writing and debugging Dynamo scripts for parameter management, element filtering, and reporting.
• Drafting Revit API code in Python or C# for custom add-in tasks.
• Explaining Revit API classes, methods, and typical usage patterns.
• Reviewing documentation for consistency with model data you supply.
• Drafting issue lists from a pasted set of markup or review notes.
• Writing scope-of-work descriptions, specification sections, and model delivery protocols.

Drafting Dynamo scripts

Describe the task in plain language: what you need to select, what you want to read or change, and what the output should be. Include the relevant Revit version and whether you are working in Dynamo Sandbox or the version embedded in Revit. Claude will produce a node-based description or Python script node content depending on what you ask for.

I am working in Revit 2024 with Dynamo Player. Write a Python script node that collects all rooms on the Ground Floor level, reads the Department parameter, and writes the results to a CSV at a path I supply. The Department parameter is a shared text parameter.

Test every script in a copy of the model before running it in the live project file. Review the logic before execution, not after. If a script modifies elements, run it on a small filtered selection first to confirm behavior.

Revit API questions and add-in drafts

Claude is useful for navigating the Revit API when you know what you want to do but need to find the right class or transaction pattern. Paste a specific question with the Revit version, describe the goal, and ask for a minimal example. Cross-check the class names and method signatures against the Revit API online documentation before committing them to production code.

The Revit API changes between versions. A pattern that works in 2022 may be deprecated in 2024. Tell Claude which version you are targeting, and verify any version-specific claims on Autodesk's developer documentation.

Model queries and reporting

For reporting tasks, export the data you need from Revit as a schedule or CSV and paste it into Claude. Ask Claude to identify discrepancies, missing values, or patterns that need review. This is safer than asking Claude to script a live model query until you have validated the script on test data.

Keep a record of what was queried, when, and what the results showed. Model data changes over time, and a report that was accurate at issue stage may not match the current model. Date your queries and note the model version.

Reviewing documentation and specifications

Paste a section of your BIM execution plan, deliverable schedule, or specification section and ask Claude to check it for internal consistency, missing items from a supplied checklist, or alignment with a project standard you paste alongside it. This is a useful step before submitting documentation for client review.

Claude cannot check your documentation against the live Revit model. That comparison still requires Revit tools or a dedicated clash and compliance tool. Use Claude for text-based review and Revit for model-based checks.

How to do this with fenbs

1. Create a free account and add a project for this Revit scope.
2. Record modeling requirements and project standards as context notes so they are available to review before each work session.
3. Add approved model changes and decisions — such as which parameter structure was agreed with the client — as Decisions and rules entries.
4. Track open script tasks, outstanding checks, and documentation reviews on the board.
5. Note the model version alongside each decision so you know which baseline the decision applies to.

Revit family and shared parameter questions

Revit families and shared parameter files are common sources of friction in project delivery. Ask Claude to help you debug a family formula, explain how a particular parameter type behaves, or draft a shared parameter file entry for a parameter you need to add. Paste the relevant formula or parameter definition and describe the behavior you are seeing versus what you expect.

For shared parameters specifically, paste the text content of the .txt file alongside your question. Claude can identify duplicate GUIDs, explain why a parameter is visible in one category but not another, and suggest the correct parameter group for a given use. Check any suggestion against Autodesk's shared parameter documentation before making changes to a file used across multiple projects.

What Claude cannot do in Revit

Claude does not connect to Revit directly, cannot see your model, and cannot verify that its scripts produce the correct result in your specific model. It is useful as a drafting and explanation tool. The judgment about whether an output is safe to run in a live project is yours. See what is Claude AI for context on what Claude can and cannot access.