Revit 2027 AI Doesn't Know Your Standards.

TL;DR: Revit 2027 ships with an AI assistant (tech preview) built on MCP. It handles generic Revit tasks through natural language: querying models, creating schedules, tagging elements. But it does not know firm-level standards. At dwp, we built a system that connects Claude to Revit using the same protocol, bounded to our naming conventions, revision workflows, and drawing register. The future of AI in BIM is not one assistant. It is connected tools, each scoped to what it knows best.

---

Revit 2027 ships with an AI assistant built into the title bar. You click the icon, type a prompt, and the assistant responds. It can answer questions about the model, create views, generate schedules, tag elements, and automate repetitive tasks through natural language.

This is not a concept demo or a roadmap promise. It is shipping software. Autodesk calls it a tech preview, which means it is clearly still early. But it is inside the product, and it works.

What the Autodesk Assistant can do

The assistant covers a broad range of generic Revit operations. You can ask it to find and filter elements by category, family, level, or parameters. You can ask it to create floor plans, section views, and 3D views. It can move, rotate, and copy elements. It can create schedules, add filters and sorting, and export to CSV. It can tag doors, windows, and rooms.

For someone learning Revit, this is a real shortcut. For experienced users, it removes some of the repetitive clicking that fills a working day.

But everything it does is generic. It knows Revit. It does not know how your office works.

The gap that matters in practice

The assistant can create a sheet. But it does not know that your architectural sheets start with A, your interiors start with I, or that your sheet numbers follow a four-digit series with no dash. It does not know your title block. It does not know your revision workflow. It does not know your drawing register.

Every firm has naming conventions, numbering systems, revision procedures, and sheet organization rules. These are the systems that keep a project coordinated across dozens of people. They are different at every firm.

A generic assistant cannot enforce what it does not know.

This is not a criticism of what Autodesk built. It is an observation about where firm-level value actually lives. Standards enforcement happens at the practice level, not the software level. It always has.

What we built at dwp

At dwp, we built an add-in called Beyond Revit. It connects Claude to Revit using the same protocol that Autodesk is now adopting: MCP, the Model Context Protocol.

The difference is that our tools are bounded to our standards.

When I ask Claude to create a sheet, it does not just make a blank sheet. It follows dwp naming conventions. A1001 for an architectural plan. I3002 for an interior section. It sets the sheet group parameter automatically. It forces the sheet name to uppercase. It assigns the correct title block.

When I need to issue drawings, I ask Claude to assign a revision to the sheet set and update the drawing register. It marks the SEQ parameters, tracks issuance across every sheet, and keeps everything consistent. One prompt handles what used to be a manual process across multiple dialogs.

Claude Skills as standards enforcement

We also load our company standards as a Claude Skill. This is the same structured file that we use for AI training videos and Notebook LM knowledge bases. One source of truth that feeds multiple outputs.

When Claude is connected to Revit and has the standards Skill loaded, it can enforce conventions in real time. If someone asks "What is the naming convention for structural sheets?" the answer comes directly from the current version of the standards file. If Claude is creating sheets, it follows those conventions automatically.

The Autodesk assistant tells you how Revit works. Our system tells Claude how our office works.

MCP is the connection point

What makes this moment interesting is the protocol. Autodesk chose MCP. Anthropic uses MCP. It is the same open standard connecting both systems.

This means the future of AI in Revit is not one assistant doing everything. It is multiple tools connected through a shared protocol, each one scoped to what it knows best.

Autodesk's assistant will get better at general Revit tasks. It should. But the firm-level systems, the standards, the naming conventions, the coordination rules, those will always need to come from inside the practice. No vendor can ship your firm's standards.

What this means for BIM Managers

If you manage BIM standards at your firm, Revit 2027 is a signal. AI is no longer outside the tool. It is inside it. The question shifts from "Will AI work in Revit?" to "How do we connect AI to our own systems?"

The Autodesk assistant is a starting point. MCP is the mechanism. The firm-level integration is where the real value lives.

Key Takeaways

• Revit 2027 includes an AI assistant (tech preview) that handles generic tasks through natural language
• The assistant is built on MCP, the same protocol Claude uses to connect to Revit
• Generic software knowledge is useful but does not replace firm-level standards enforcement
• Connecting AI to your own naming conventions, revision workflows, and documentation systems is where the value compounds
• The future is connected tools scoped to what they know best, not one assistant trying to do everything

The goal isn't just better models. It's better buildings.