Last updated: 12 November 2026

Free tool: runs in your browser

BIM AI assistant model-edit checklistbefore an AI assistant or MCP connection edits a live Revit or Archicad model

TimeBinder adds a layer of protection against AI and human fraud and disputes. Check the model copy you can restore, what the assistant may change and who approves it, where the data goes when you connect your own AI tool, and the dated copies you can still show.

Nothing you tick is sent anywhere. This page cannot inspect your model or tell you what an assistant changed. It is not a review of any product and not professional advice.

Check the copy, the approvals, the data path and the files you can still show

Tick what is true about your model, your team and the AI tool you plan to use. You get a shareable result and clear next steps. Nothing you tick is sent to TimeBinder.

Your choices stay on this page. Nothing you tick is sent anywhere or tied to your name.

Tick everything that is true before an AI assistant edits your live BIM model

This looks at the model copy you can restore, what the assistant may change and who approves it, where the data goes when you connect your own AI tool, and the dated copies you can still show. It is not a review of any product.

What to do now

What should architects check before an AI assistant edits a live BIM model? The short answer

Make a copy of the model state it cannot write to, set who approves changes, test a batch edit on a small set first, and check where the data goes. Graphisoft says every model-changing action in Archicad MCP (Beta) is carried out only after your explicit approval, and that data you share with your own AI desktop tool is governed by that tool’s terms. Autodesk says Revit assistant changes are labelled in the Undo menu and logged in the Revit journal. Check what applies to your version and plan.

This checklist cannot inspect your model or tell you what an assistant changed. A TimeBind of a file you already hold, such as an IFC export or an issued PDF set, can show that exact file existed no later than a recorded time and still matches. It does not show what an assistant changed or who approved it.

Why this came up in November 2026

On 9 November 2026 Graphisoft published “Archicad MCP: AI automation of repetitive BIM tasks for architects”, describing an agentic AI Assistant (Beta) inside Archicad and a public Archicad MCP (Beta) server that lets desktop AI tools such as Claude Desktop or Cursor work with live project data. On 10 November 2026 Autodesk’s AEC blog on Revit 2027.3 and 2027.4 described prompt-driven automation in Autodesk Assistant, Revit Public MCP Server add-ons in Technical Preview, and DynamoMCP. Autodesk’s post says the Revit Public MCP Server add-ons have Read, Write and Experimental extensions for querying and modifying a model.

Measured demand is current. On YouTube, Checked on 13 November 2026, about 2:20 AM Australia/Brisbane. “Archicad 30 First Impressions” (David Tomic, 30 October 2026) had 17,630 views and 175 likes, and “How to connect Claude with Revit in 5 minutes (FREE, NO CODING)” (Simulation Corner, 25 October 2026) had 14,481 views and 165 likes. Google autocomplete returned “archicad mcp server”, “archicad mcp claude”, “revit mcp server”, “revit mcp claude” and “revit ai assistant 2027”. Autocomplete shows what people type. It is not search volume.

The checks are written for the day you let an assistant or an MCP connection change a model that other people rely on. Always read the vendor’s current documentation for your version first.

Sources: Graphisoft, 9 November 2026 and Autodesk, 10 November 2026.

What this checklist does and does not do

The honest job of this page is to slow down a connection or a batch edit until you have a copy, an approval step and a note of what you asked, not to judge any product. See also the glossary entries for existed no later than and fingerprint.

Limits of the BIM AI assistant model-edit checklist
Part	What it does	What it does not do
The model copy	Reminds you to keep a copy and an IFC or PDF export of the current state that the assistant cannot write to, and to know how you would undo a batch change.	Restore your model, or tell you whether a change can be undone.
Approvals and scope	Reminds you to decide which changes need your approval, to test a batch edit on a small set first and to tell the others in a shared model.	Show what an assistant changed, or who approved it.
The data path	Reminds you that, when you connect your own AI tool, that tool’s own terms and privacy policy apply, and to check your contract or the client allows it.	Interpret any vendor’s terms, or say what a tool does with your data.
A TimeBind of a file you already hold	Records that an exact file existed no later than a recorded time and still matches, using a SHA-256 fingerprint made in your browser. The file stays on your device.	Show what an assistant changed, or that a model is correct.

If an export or an issued set is something you may need to show later

Before and after an assistant edits the model:

Keep dated IFC or PDF exports of the model and the issued drawings as they stand before the assistant is used.
Make a TimeBind of each exact file you already hold. The fingerprint is made in your browser and the file stays on your device. You can later download a Proof of Time Certificate.
Store the files, a note of the prompt, the scope and who approved it, and the certificate together, and note when each batch edit was run.

A TimeBind shows the exact file existed no later than the recorded time and still matches. It cannot show what an assistant changed or that a model is correct.

Make a TimeBind: first one free →

First Pooled TimeBind free, no card, then from US$5. An ASAP TimeBind is US$15.

What a TimeBind shows, and what it does not. It shows that an exact file existed no later than a recorded time and that a copy shown later still matches its fingerprint. It does not show who made the file, who owns it, that its contents are true, or whether AI was used to make or edit it. This is general information, not legal advice.

After an AI assistant edits a model, the free AI model dimension spot check log helps you spot check key dimensions against your source numbers. A pass is not a code or design check.

BIM AI assistant model-edit checklist: FAQ

Does this checklist review Archicad MCP or Revit Assistant?

No. It does not test or rate any product. It runs in your browser and only helps you plan the checks before an assistant or MCP connection edits a live model.

Does the assistant ask before it changes the model?

Graphisoft says every model-changing action in Archicad MCP (Beta) is carried out only after your explicit approval. Autodesk describes labels in the Undo menu, a journal log and a Stop button for Revit’s assistant. Check what applies to your version and connection.

Where does the data go if I connect Claude Desktop or Cursor?

Graphisoft says data shared with a connected AI application is governed by that application’s own license terms, privacy policies and data processing agreements. Read them for the plan you use.

Is my client’s information allowed to go to an AI tool?

That depends on your contract and your client. Check before you connect, and keep the answer in writing.

Does a dated record show what the assistant changed?

No. A TimeBind of a file you already hold, such as an IFC export, can show that exact file existed no later than a recorded time and still matches. It does not show what changed.

Is anything I tick sent to TimeBinder?

No. The checklist runs in your browser. Your ticks stay on the page.

Related guides and tools

Your file’s fingerprint, anchored to a global network secured by real electricity and cryptography.

Editing a file—including with AI—changes its fingerprint, not its existing network record.

How this works

Your file’s SHA-256 fingerprint, a short code worked out from its exact contents, is made in your browser, and the file itself stays on your device. A cryptographic commitment to that fingerprint, which may be combined with others, is then anchored in a block on the Bitcoin blockchain. Bitcoin is secured by proof of work: computers around the world spend real electricity to add each block, and changing an earlier block would mean redoing that work faster than the rest of the network. Until that block is confirmed, your proof is pending. Once the Bitcoin anchoring is confirmed, you can verify the proof against that recorded commitment. The confirmed record can then be checked; Pooled TimeBinds are checked through TimeBinder, while ASAP TimeBinds can also be checked independently. If you check the file later and its fingerprint still matches, that shows the file existed no later than the recorded time. The record doesn’t show who made the file, whether AI was used, or that its contents are true.

Your filestays on your device
FingerprintSHA-256
Network timestampon Bitcoin

Date the exact files you already hold

Add a layer of protection against AI and human fraud and disputes: a dated, checkable record of the model exports and issued sets, kept before an assistant edits anything.

Open the app and sign in with email or Google.
Add your files. They stay on your computer.
Seal them and download your Proof of Time certificates.

Open TimeBinder →

First Pooled TimeBind free, no card, then from US$5. See pricing.