ELI + REVIT · DEVELOPMENT PREVIEW

Your Revit AI assistant.
Your decisions, in control.

Eli is designed to turn natural-language questions into supported model inspection and carefully reviewed actions. Esattia flags; the engineer decides.

AI IN REVIT

Discover Eli.

The Esattia mark becomes the assistant that moves with your workflow. Scroll to reveal Eli, then explore the supported-workflow approach below.

Scroll to transform
MODEL UNDERSTANDING

A clearer route from
question to review.

Explore model information and supported review workflows with Eli. Access and supported actions vary within the development preview.

01

Inspect

Understand selected elements, parameters, views and project information through supported read tools.

02

Analyze

Investigate supported model findings and checks. Results remain evidence for professional review.

03

Propose

Review the intended scope before a supported model change. Approval and execution are separate steps.

04

Verify

Read back the result and record what changed. A completion message alone is not independent verification.

EXTERNAL AI CONNECTIONS

Your assistant.
A controlled connection.

Development records describe selected read-only external-AI workflows through a configured connection. Supported clients and enabled operations need release-specific confirmation; this is not general access to the internal tool library.

Illustration of a planned external AI connection workflow

Development preview · Confirm the supported client, connection and enabled read-only tools before use. Compatibility does not imply endorsement.

SMART REVIT SETUP · DEVELOPMENT PREVIEW

Review the setup.
Before the model changes.

Review DXF plans and sections, inspect proposed levels and prepare the setup in Esattia. Creating elements in Revit is planned; this preparation step does not change the model.

Esattia Revit Setup showing drawing inputs, level preview and a withheld Create in Revit action.
Revit Setup · Drawing and level preparation. Creating elements in Revit is planned. Open full image ↗
Full overview · enlarge for details
01

Prepare the information

Bring project, template and drawing information together, then review the proposed levels before deciding what comes next.

02

Planned · Create in Revit

Creating levels, views and drawing imports in Revit is planned. Model changes will require a reviewed proposal and approval.

03

Broader workflow

Review views, datums, layouts, crop and scale settings through supported Revit workflows. Confirm the tools enabled for your beta account.

REVIT REVIEW · SCOPE TO CONFIRM

Turn a model question
into a reviewable finding.

Development inventories describe these review operations. They are examples of inspection workflows, not a promise that every check is enabled for customers or external AI clients.

Before issue

Pre-Issue Audit, Warning Triage and Sheet Audit help surface review candidates and missing information. They do not certify model compliance or completeness.

In the model

Clash Flag, Tag and Dimension Checks, and Link Audit provide scoped evidence. Confirm checked views, loaded links and geometry coverage before relying on a result.

Views and presentation

View Cleanup, Layout Organizer, Crop and Scale, and template/filter workflows address drawing organization. A suggestion or preview is separate from permission to change the model.

Tool availability is release- and workflow-specific. Internal operations, external read tools, navigation and approved model changes are different capability tiers.

CONTROL BY DESIGN

Inspect. Propose.
Approve. Verify.

Start with inspection. For a separately enabled and accepted write workflow, a trusted human reviews the exact proposal before execution and verification. The website does not establish that model-changing workflows are currently released or enabled.

Supported operations depend on the enabled workflow. Ask which tools are included before using a model-changing action.

CONNECTED BY ELI · TARGET WORKFLOW

A model question should
carry its context forward.

Eli helps investigate an element. The intended next step is a reviewed issue linked to a project and shared with the right colleague, then checked against a revised file.

  1. 01Inspect in Revit
  2. 02Review with Eli
  3. 03Prepare an issue
  4. 04Discuss with the team
  5. 05Review the revision

Development previews connect local project files, comparison findings and conversation references. Cross-office delivery and the complete issue lifecycle are planned.

REVIT AI ASSISTANT

AI for Revit.
Connected to the wider project.

A BIM automation workflow should keep model evidence and professional judgment together. Eli is designed to help inspect supported Revit information, prepare a review and keep proposed modifications visible before execution.

For example, an engineer can start with a question about an element or sheet. The intended connected workflow carries the reviewed finding into BIM issue management and team discussion, then checks the relevant revision in model or drawing comparison. Confirm supported clients, model-changing actions and workspace connections before starting a workflow.

Scroll to inspect the full image. Press Escape to close.