Every model that arrives for coordination needs the same tedious check. Are the units right? Do the worksets match the standard? Are the views named correctly? Is the survey point where it should be? BIM managers do this manually — setting by setting, model after model, project after project.

Existing QC tools help find the problems. But finding isn't fixing. You still open each setting, compare it to the template, and correct it by hand. The report tells you what's wrong. You still do all the work.

Sentinel finds issues and fixes them. When it detects that your project units are set to feet but your standard says millimeters, it doesn't just flag it — it generates a targeted correction and offers it for your approval. You see the exact before and after values for every proposed change. You approve what you want. Sentinel applies the fixes in one click. And if anything isn't right, you roll back atomically — using recorded inverse patches that are independent of Autodesk® Revit® undo history and target only what Sentinel changed. Every action produces a tamper-evident receipt documenting what changed, when, and who approved it.

Sentinel enforces your firm's standards, not a generic checklist. You define what "correct" looks like in an Excel workbook — one sheet per QC category, with dropdowns and examples — and import it as a profile. Or, if you have Claude Desktop connected, you can extract standards from a reference model in one sentence. Point Sentinel at your firm's gold-standard project and it captures the configuration automatically — worksets, units, coordinates, view naming, text styles, object styles, everything. Either way, the result is a profile tailored to exactly what your firm expects.

At launch, Sentinel includes capabilities focused on model intake and everyday project setup. Seventy-two document-level capabilities coming soon. New capabilities are released progressively and plug into your existing profiles with no new workflows to learn.

Sentinel is one of the first MCP-integrated apps on the Autodesk App Store. Install Claude Desktop or Cursor, and Sentinel configures the MCP connection in one click. Then talk to your Revit model in plain language. "Inspect this model." "Are units consistent?" "Apply the fixes." "Roll that back." "Draft a message to the architect about the unit mismatch." You can extract standards, run inspections, review findings, apply fixes, and manage rollbacks entirely through conversation.

The AI assistant is optional — the desktop plugin works fully on its own — but it changes how fast and naturally you can work through QC. The same governed workflow applies regardless of which surface you use: approval gates, rollback, and receipts are identical.

Sentinel is built around a simple trust model. Every capability is classified into one of three tiers: Report-Only findings are presented for awareness, with no changes offered. Safe Fixes are bundled for one-click approval. Approval-Required fixes are presented individually with full before-and-after disclosure. New capabilities default to the most restrictive tier until validated. Nothing runs without your initiation. Nothing applies without your approval. Everything is reversible.

No geometry modification. No unattended execution. No background network activity. No AI inference at runtime — all inspection and remediation is deterministic code.

What normally costs a BIM team hours of manual checking becomes a confident, one-minute quality gate — governed, auditable, and reversible.

Note: This app uses a custom installer (and not the standard App Store installer).

Category	Details
App Model	Local MCP server
Data Storage + Retention	Profiles and receipts are retained locally until the user deletes them. The QC module exists only in memory during the Revit session and is cleared when Revit closes. Authentication tokens exist only in memory during the session.
Data Deletion	Users can delete profiles and receipts through the Sentinel UI or by removing files from the local AppData folder. Uninstalling via Windows Add or Remove Programs removes the plugin. Local data in AppData is preserved after uninstalling unless manually deleted.
Communication Scope	No background, automatic, or periodic network activity occurs.
External Communication	The plugin does not communicate with undeclared URLs or external services.
MCP Tool Data Access	All data access is local. No Autodesk data is sent to external services.
Network Transparency	No hidden or undeclared network communication exists.
Tool Justification	All declared MCP tools are necessary for the plugin’s functionality.