How do I audit linked models for shared coordinates and survey point agreement with AI?
Before a coordination publish, linked architectural, structural and MEP models are supposed to share one survey point and project base point, but one link often lands feet or a whole level off because someone acquired coordinates from the wrong file or moved the site after links were placed. Finding it mid-clash review wastes the meeting. Export each model's shared-coordinate and site settings, have Claude or ChatGPT normalize them into one table, and have Copilot in Excel or Gemini in Google Sheets flag models whose survey point, angle to true north or base-point offsets disagree past tolerances you set. How to fix the file stays with the BIM coordinator and the authoring team.
BIM Coordinator · BIM · Claude · ChatGPT · Microsoft Excel · Microsoft Copilot · Google Sheets
Content updated · Tool links listed below; vendor features and pricing change, so confirm with the vendor
Short answer
Use Claude or ChatGPT, then Copilot in Excel or Gemini in Google Sheets: Claude or ChatGPT reads each linked model's shared-coordinate and site settings into one Models table; Copilot or Gemini compares survey and base points and angle to true north against the host you pick and flags differences outside the tolerances you set, plus NOT SHOWN fields, origin-to-origin links and stale paths. Before a coordination publish, linked architectural, structural and MEP models are supposed to share one survey point and project base point, but one link often lands feet or a whole level off because someone acquired coordinates from the wrong file or moved the site after links were placed. Finding it mid-clash review wastes the meeting. Export each model's shared-coordinate and site settings, have Claude or ChatGPT normalize them into one table, and have Copilot in Excel or Gemini in Google Sheets flag models whose survey point, angle to true north or base-point offsets disagree past tolerances you set. How to fix the file stays with the BIM coordinator and the authoring team. A person still checks: every flagged model with the authoring team before republish; fixing shared coordinates and anything that affects a legal survey stay with the BIM coordinator and surveyor when control is involved.
AI tie-in
Tool: Claude or ChatGPT, then Copilot in Excel or Gemini in Google Sheets
Claude or ChatGPT reads each linked model's shared-coordinate and site settings into one Models table; Copilot or Gemini compares survey and base points and angle to true north against the host you pick and flags differences outside the tolerances you set, plus NOT SHOWN fields, origin-to-origin links and stale paths.
Prompt 1
Read these shared site setting exports or screenshots from linked BIM models [upload]. Build a table with one row per model: model name, discipline, survey N/E/elev, base N/E/elev, angle to true north, link positioning method and source file path as written. Copy numbers exactly and write NOT SHOWN instead of guessing. Do not move coordinates or say which file is correct.
Prompt 2
Here are the headers and a few sample rows of my Models tab [paste: model, discipline, survey N, E, elev, base N, E, elev, angle to true north, link method, path] and my Rules tab [paste: host model, position tolerance, angle tolerance]. Write Excel formulas (or a step-by-step Copilot plan) that compare every model to the host survey and base points, flag position or angle differences outside my tolerances, NOT SHOWN fields, origin-to-origin links and paths that look like old copies, and summarize by discipline. Use only my data; do not move coordinates or say which file is correct.
Human check: Every flagged model with the authoring team before republish; fixing shared coordinates and anything that affects a legal survey stay with the BIM coordinator and surveyor when control is involved.
The problem
Audit linked models for shared coordinates and survey point agreement with AI. This is a common, time-consuming task for a bim coordinator.
What this workflow does
Before a coordination publish, linked architectural, structural and MEP models are supposed to share one survey point and project base point, but one link often lands feet or a whole level off because someone acquired coordinates from the wrong file or moved the site after links were placed. Finding it mid-clash review wastes the meeting. Export each model's shared-coordinate and site settings, have Claude or ChatGPT normalize them into one table, and have Copilot in Excel or Gemini in Google Sheets flag models whose survey point, angle to true north or base-point offsets disagree past tolerances you set. How to fix the file stays with the BIM coordinator and the authoring team.
How it works: AI drafts or analyzes. A person operates the tools, checks the work, and takes action.
Your checkpoint: The audit only compares the settings you exported. A model can still be wrong in elevation internally, and acquiring coordinates the wrong way can look fine until the next link. Fixing shared coordinates, republishing and anything that affects a legal survey stay with the BIM coordinator and the responsible authoring team, with the surveyor when control is involved.
Before you start
- Access to the named tool; confirm license, version and cost with the vendor.
- A small, non-confidential sample to try the workflow on first.
- A qualified person to review the output before it is used.
Tools and access
Follow the steps
- From each linked Revit (or other BIM) model, export or screenshot the shared site settings: survey point N/E/elev, project base point N/E/elev and angle to true north, plus the link instance name, path and whether it is shared-coordinates or origin-to-origin. Use an AI account your firm allows for model data.
- Have Claude or ChatGPT read every export or screenshot into a Models tab: model name, discipline, survey N/E/elev, base N/E/elev, angle to true north, link positioning method and source file path as written. It copies numbers exactly and writes NOT SHOWN instead of guessing.
- Pick one host model as the reference (usually the civil or architectural shared site) and type your position and angle tolerances on a Rules tab yourself.
- Have Copilot in Excel or Gemini in Google Sheets compute the difference of each model's survey and base points from the host, and the angle difference, and flag anything outside your tolerances.
- Flag models with NOT SHOWN coordinate fields, origin-to-origin links that should be shared-coordinates, duplicate survey points that still disagree, and links whose path points at an old folder or detached copy.
- Send each authoring team the flagged rows with the host values to match, re-check after they republish, and record the clean publish in your coordination log.
Try a small example
Replace the bracketed fields with your own project details. No tested sample run is published for this workflow yet.
Sample input
Fill in the bracketed [fields] in the text below with your project data.
Starter prompt
Here are the headers and a few sample rows of my Models tab [paste: model, discipline, survey N, E, elev, base N, E, elev, angle to true north, link method, path] and my Rules tab [paste: host model, position tolerance, angle tolerance]. Write Excel formulas (or a step-by-step Copilot plan) that compare every model to the host survey and base points, flag position or angle differences outside my tolerances, NOT SHOWN fields, origin-to-origin links and paths that look like old copies, and summarize by discipline. Use only my data; do not move coordinates or say which file is correct.
Expected output
Not published yet. Treat any output as a draft and check it against the source documents.
Check the result
- Every value, citation or quantity traces back to a source document.
- Missing information is marked as missing, not filled in.
Limits and recovery
- The audit only compares the settings you exported. A model can still be wrong in elevation internally, and acquiring coordinates the wrong way can look fine until the next link. Fixing shared coordinates, republishing and anything that affects a legal survey stay with the BIM coordinator and the responsible authoring team, with the surveyor when control is involved.
- Check your organization’s data policy before sharing project files with third-party tools.
Stop or switch when: The source cannot be verified, permissions are missing, or the result contains unsupported facts.
Frequently asked questions
How does AI help with this?
Claude or ChatGPT, then Copilot in Excel or Gemini in Google Sheets: Claude or ChatGPT reads each linked model's shared-coordinate and site settings into one Models table; Copilot or Gemini compares survey and base points and angle to true north against the host you pick and flags differences outside the tolerances you set, plus NOT SHOWN fields, origin-to-origin links and stale paths. A person still checks: Every flagged model with the authoring team before republish; fixing shared coordinates and anything that affects a legal survey stay with the BIM coordinator and surveyor when control is involved.
How do I how do I audit linked models for shared coordinates and survey point agreement with AI??
From each linked Revit (or other BIM) model, export or screenshot the shared site settings: survey point N/E/elev, project base point N/E/elev and angle to true north, plus the link instance name, path and whether it is shared-coordinates or origin-to-origin. Use an AI account your firm allows for model data. Have Claude or ChatGPT read every export or screenshot into a Models tab: model name, discipline, survey N/E/elev, base N/E/elev, angle to true north, link positioning method and source file path as written. It copies numbers exactly and writes NOT SHOWN instead of guessing. Pick one host model as the reference (usually the civil or architectural shared site) and type your position and angle tolerances on a Rules tab yourself. The full step list is above.
Does this use an AI agent or regular software?
It is labeled AI assists: AI drafts or analyzes. A person operates the tools, checks the work, and takes action.
What tools do I need?
Claude, ChatGPT, Microsoft Excel, Microsoft Copilot, Google Sheets. Confirm license, version and cost with the vendor, and try it on a small non-confidential sample first.
Has this workflow been tested?
Workflow guide · not independently tested. Written from vendor documentation and practitioner use. Labels apply to the steps described here, not every feature of a product. Links were checked when the page was written.
Evidence and maintenance
Written from vendor documentation and practitioner use. Labels apply to the steps described here, not every feature of a product. Links were checked when the page was written.