Deploying AI Across Every Revit User in a Global Practice

Watch the full walkthrough: https://youtu.be/Ybc5DknQZX8

TL;DR: A practice-wide AI deployment in Revit is operational today across every workstation, every office, and every region the firm works on, with any AI client the firm chooses to standardise on. Standards, framework, governance, and a method to scale across a global practice — the integration layer the industry is moving toward, already built, already deployed, already running. This is the direction the industry is going. We are already there.

---

A practice-wide AI deployment in Revit is operational today.

Every workstation. Every office. Every region the firm works on. With whichever AI client the firm chooses to standardise on.

Standards. Framework. Governance. A method to scale across a global practice.

The integration layer the industry is moving toward — already built, already deployed, already running.

This is what happens when a practice stops waiting for a single tool and builds the layer that connects every tool. The question every firm is asking — what would AI in Revit actually look like if it had to survive contact with a real practice? — has an answer now. It is not a single tool. It is a deployment.

What is operational today

The deployment connects every Revit workstation in the practice to any AI client the firm chooses to standardise on. Revit stays the canonical source of truth. The AI reads through the Revit API. Writes are allowlisted centrally and require user confirmation. Standards are enforced at the practice level — not at the individual workstation, not at the office, at the practice.

The AI client is interchangeable. The standards are not. Codex, Claude, Gemini — whichever the firm prefers — connect through the same framework, run against the same allowlist, return the same answer on every workstation in every office.

That is the design.

The four layers

The deployment is not one tool. It is four layers running together across the practice.

• Read-only tools — sheets, title blocks, rooms, doors, views, warnings, schedules, legends, view templates, sheet parameters. The AI reads what is in the model. It does not guess.
• QA tools — door data, room data, sheet standards, view naming, title block data, overall model health. The AI checks the model against the practice's standard and reports on what is missing or misaligned.
• Prepare-only workflow tools — RCP, General Arrangement, Finishes, full sheet packages. The AI plans the work. Nothing changes in the model until a user approves it.
• Integration with the existing sheet automation tool the practice already uses. Same standards, new interface, same answer on every workstation in every office.

Same standards. Same answer. Every workstation. Every office. Every region.

Three prompts that make it concrete

"Prepare a Level 1 RCP sheet." The AI returns a structured plan — sheet number, title block, views, templates, warnings. Nothing changes in the model. Same plan on every workstation.

"Check whether the model has the required workplace documentation sheets." The AI checks the current sheet set against the practice's standard. Flags what is missing. Flags what is named incorrectly. Reports against the standard the practice has already defined.

"Review door data and identify missing or duplicate values." The AI returns a clean list of doors with missing or duplicate values, grouped by issue. Real data, read directly from the model.

The pattern that emerged

A working demo is not a deployment.

A deployment is what an entire practice can use, in every office, on every project, under the same standards, with the same controls, every day, without supervision.

That is the gap most AI-in-Revit work falls into. Beautiful demos on a single workstation. No path to rollout. No governance to survive a firm. No consistency across users.

The pattern that works is the opposite. Build for deployment first. The demo is the by-product.

Why governance is the part that matters at scale

Write tools are disabled by default. Allowlisting is explicit and set centrally. Every action that would modify a Revit model requires user confirmation.

That is not a limitation. That is the design.

An AI that can quietly edit any model in the practice is not an assistant. It is a liability. Governance is the part most AI demos skip. It is the part that decides whether a deployment survives contact with a real firm — especially a firm operating across multiple offices, multiple time zones, and multiple project teams.

Standards at the practice. Allowlists at the practice. Confirmation at the practice. Not at the individual workstation. Not at the office.

This is what AI at scale actually means. Not more users. More control.

The pattern other firms can replicate

The integration layer between Revit and AI is something every practice will need. The pattern is not proprietary. It is replicable.

The CAD/BIM platform ships the foundation — the API surface, the open MCP layer, the governance hooks. The practice builds bounded skills on top — the naming conventions, the revision workflow, the playbooks for each project type. Foundation from the platform. Standards from the practice.

Any firm that wants to run this play can run it. The deployment we built is the proof that it is possible at the scale of a global practice. The next firm that builds it will not have to start from scratch.

This is where the industry is going. The practices that build first set the convention.

Where this is heading

The current toolset is the foundation. The next phase is project-type playbooks.

I am reviewing completed project PDFs to build a workplace interiors playbook. The playbook teaches the AI what a typical drawing set looks like — sheet sequences, schedules, legends, numbering, elevations, details, room packages.

Once the playbook is in place, the questions change.

Today a user asks: create a sheet, then create a view, then place the view.

Soon a user can ask: build the workplace documentation set for this level.

The same logic extends across every sector the firm works on. Each project type carries its own conventions. The playbooks make those conventions legible to the AI. Once one playbook is shipped, the others follow — across every office, every region, every project type the practice operates in.

Reflection

A global practice — with offices on multiple continents, with hundreds of Revit users, with project deadlines that do not move because a vendor roadmap shifts — needed a deployment that worked at its scale. So the practice built it.

Standards. Framework. Governance. A method to scale across the whole firm. Connected to whichever AI client the firm standardises on. Operational across every workstation, every office, every region the practice works on.

This is the direction the industry is going.

We are already there.

Key Takeaways

• A practice-wide AI deployment in Revit is operational today — every workstation, every office, every region — with whichever AI client the firm chooses to standardise on.
• Standards, framework, governance, and method live at the practice level. Not at the individual workstation. Not at the office. At the practice.
• Write tools are disabled by default. Allowlisting is explicit and set centrally. Every action that would modify a Revit model requires user confirmation. AI at scale means more control, not more users.
• The next phase is project-type playbooks. Workplace interiors first, then every sector the firm works on. The shift is from create a sheet, then a view to build the workplace documentation set for this level.
• The pattern is replicable. Foundation from the CAD/BIM platform, standards from the practice. Any firm that wants to run this play can run it. The practices that build first set the convention.

This is the direction the industry is going. We are already there.