AI can help you compare an equipment submittal revision to what’s modeled in Revit by extracting geometry and connection information from the PDF/XLS, contrasting it with selected elements and schedule rows, then proposing updates. Keep procurement data isolated from geometry-driving parameters, verify the revision status and exact configuration/handing with the project authority, and only then apply accepted changes and document the delta.
How to compare an equipment submittal with a Revit model
When a revised submittal arrives, assemble three things: the approved (or conditionally approved) pages, the specific Revit element(s) or type(s) to evaluate, and the schedule rows actually published on sheets. An AI assistant can normalize the vendor documents, map fields to your parameter schema, and produce a side‑by‑side comparison. Group the resulting differences as:
• Geometry/placement: casing outline, rotation, and which face hosts each connection.
• Connectors: side and relative location; any stated hand.
• Engineering/nameplate: flows, pressures, voltage/phase, weight.
• Procurement/administrative: vendor, model/number, quote/PO, shipping date.
Treat product model/number as more than purchasing trivia: a changed product can imply geometry or engineering differences that must be confirmed before edits. Shipping date is typically administrative and should not drive geometry. Classification follows how the family is actually bound in your project and what the team uses those parameters for.
Gate the process correctly. The discipline lead or other designated authority (per your contract) confirms revision status and scope for the exact tag(s). Verify the exact configuration/handing stated in the submittal—options and handed variants are easy to misread—before you compare or commit any changes.
What AI can extract from a revised equipment submittal
AI is strong at submittal normalization (PDF/XLS), parameter mapping, and generating a concise change package with references to source callouts/pages. It can also draft a list of affected elements, views, and schedules so coordinators see what would change and why. With an integration such as ArchiLabs Desktop, teams can have the assistant create or update native model elements, route systems, and produce documentation inside existing Revit models. Integration availability depends on application version, plan, accounts, and permissions.
Connector changes often require supported family authoring and testing rather than ad‑hoc edits on a placed instance. Decide early whether to edit a family type or duplicate/create a new type; remember that a type edit updates every instance that uses it. Many steps here are team procedures (mapping fields, approving deltas, updating issue logs) rather than product button‑clicks, and they remain under the coordinator’s control.
Prepare submittal sources, field ownership, and comparison checks
Inputs
• Submittal revision (approved or approved as noted) with dimensioned drawings/schedules, plus the previously implemented revision for traceability.
• The Revit element(s) or type(s) that represent the equipment, and the exact schedule row(s) used on sheets.
• Your parameter standards: which fields drive geometry/connectors; which are informational or procurement‑only.
• Coordination context: nearby systems, access zones, pads/openings.
Roles
• Project authority: confirms revision status, scope, and configuration/handing for the tag(s) in question.
• Modeler/MEP coordinator: accepts/rejects proposed edits, performs any rerouting or family authoring, validates coordination.
• AI assistant: prepares the comparison, drafts proposed updates, and assembles references and deliverables.
Built‑in checks
• Confirm submittal tag/ID aligns with the Revit element ID/tag.
• Keep procurement/administrative changes out of geometry‑driving fields; map them to non‑graphical shared parameters or a linked register.
• Decide the approved type strategy before edits—type modifications affect every instance.
• Use an archived model or export to show “before”; a copied view does not freeze prior geometry. Schedule exports only reflect filters you explicitly apply, and row counts don’t equal element counts unless itemization/filters make that true.
For realistic boundaries on what assistants can and cannot edit inside Revit, see What AI Can and Can’t Do in Revit Today: A Clear Guide. To improve compare accuracy, standardize how you share model context with the assistant using the Revit Model Context Protocol.
Apply approved equipment changes to the Revit model
A practical cadence keeps the work reliable:
• Prepare context: select the equipment element(s); capture current schedule rows; provide both the approved revision and the previously implemented revision.
• AI extraction and delta list: the assistant extracts casing outline and which face hosts each connection, along with engineering and administrative fields, and cites the source page/callout for each.
• Proposals: it suggests whether to edit an existing type or create a new one; which parameters to change; and which views/sheets look affected. Connector location changes are proposed as family authoring tasks with testing steps.
• Acceptance: the project authority confirms status/scope; the coordinator accepts itemized deltas in scope now (e.g., casing outline and connection side) and defers purely administrative items as needed.
• Apply and validate: perform the agreed family/type edits, any necessary routing, then re‑compare to confirm resolved deltas. Refresh relevant schedules/tags and issue a dated change note to stakeholders.
Do not infer engineering validation from a warning count or a system color—run the checks you actually use for design acceptance.
Submittal revision example: a changed outline and connection side
Scenario (hypothetical)
• Tag AHU‑12’s revised submittal shows a changed casing outline and the supply/return switching to the opposite side. The document also adds a shipping date. Some secondary dimensions are not provided on the marked sheet.
AI compare output (what it should report, not execute)
• Geometry/placement delta: “Revised casing outline” with page and detail references; missing dimension X flagged as required before geometry parameters are changed.
• Connector delta: “Connection side flips” with the specific note/callout cited; no claim about exact offsets without the vendor’s figures.
• Procurement/administrative: “Shipping date provided” and “vendor/model updated,” treated as informational unless tied to a geometry/engineering change.
• Affected set: identifies all instances bound to the same family type if a type edit is proposed.
Proposed approach
• Decision: either create a new family type for AHU‑12 (preferred if other instances exist) or edit the current type, with a clear note that all instances of that type will update.
• Connector change: duplicate the family in a working file, implement the handed connection face in the family editor, and test connectors with a short routing check before swapping into the project.
• Hold: defer geometry parameter updates that rely on the missing dimension until the vendor provides it; keep the administrative shipping date in non‑graphical parameters.
Documentation
• Issue a one‑page internal change summary: before/after outline, itemized accepted/rejected deltas with their source references, and the list of affected instances/views. Archive the compared submittal pages with annotations.
Document submittal-driven model changes and unresolved items
Finish by producing:
• A dated delta log showing each accepted/rejected change with controlling revision IDs and source page/callout references.
• Updated Revit element(s)/type(s) reflecting the approved casing outline and connection side, applied via the agreed type strategy.
• Refreshed schedules for geometry/engineering fields; procurement‑only data updated in shared parameters without affecting geometry.
• Temporary plan/section views that illustrate the before/after outlines and notes on coordination touchpoints.
Pick a single unit with a recent submittal revision, package the approved pages, select the element and schedule row, and run a focused compare using your parameter map—then apply only the deltas that pass configuration and revision checks.
Understand what Revit AI can do, where model access and source data limit results, and how to review geometry, parameters, and documentation.
Learn about how Model Context Protocol (MCP) is changing the way we use tools like Autodesk Revit and the future of AI agents and architecture