AI for BIM Workflows: 8 BIM Tasks Worth Automating First

AI for BIM is the use of large language models to automate the document, data, and coordination work that surrounds the model, not the modelling itself. In practice that means drafting BIM Execution Plans from Exchange Information Requirements, triaging thousands of clash results into a prioritised list, auditing file and object naming against ISO 19650, cleaning COBie asset data, and writing coordination reports. The modelling stays in Revit, Archicad, or Tekla. The paperwork, which is where most BIM managers actually lose their week, moves to AI.

This distinction matters because most articles on this topic promise AI that generates buildings. That is not what is shipping in UK practice in 2026. What is shipping is a set of unglamorous but genuinely time-saving workflows, and this guide covers the eight that deliver the fastest return, with the prompts and the guardrails you need to run them safely.

This is the overview guide in our BIM AI series, and three companion guides go deeper. AI for BIM model checking and QA covers checking the information in the model, including how to turn EIR clauses into checking rules. The BIM AI copilot guide compares the three types of copilot and how to set one up. AI assistant for BIM sets out what to ask an assistant at each RIBA stage.

Where AI actually fits in a BIM workflow

The useful mental model is this: AI is excellent at text, structure, and pattern matching across large volumes of records. It is unreliable at geometry, spatial reasoning, and anything requiring a source of truth it cannot see. A BIM workflow is mostly the former wrapped around a core of the latter.

The pattern is consistent. AI takes the first pass at anything that is fundamentally a document or a list, and a human takes the decision. If you keep that boundary, the workflows below are safe. If you blur it, you will eventually issue a BEP that commits your team to a level of information need nobody agreed to.

The eight AI-assisted BIM workflows worth setting up first

These are ordered by return on the time it takes to set them up.

1. Drafting the BIM Execution Plan from the EIRs

The pre-appointment and post-appointment BEP is the single biggest document drain on a BIM manager. Most of it is boilerplate that varies slightly per project: the federation strategy, the CDE workflow, software versions, the level of information need, the responsibility matrix, and the information delivery plan.

The workflow: paste your standard BEP template alongside the client's Exchange Information Requirements and the project brief, then ask the model to produce a first draft that answers every EIR clause explicitly and flags any requirement your template does not cover. That last instruction is the valuable one. AI is very good at spotting an EIR clause your standard response quietly ignores, which is exactly the clause that causes an argument at Stage 4.

Budget an hour of review on a draft that would previously have taken two days. See the wider AI for BIM managers collection for the surrounding prompts.

2. Turning EIRs into a responsibility matrix

Closely related, but worth separating because it is a different output shape. Feed the EIRs, the appointed party list, and the RIBA Plan of Work stages, and ask for a Task Information Delivery Plan style table: information container, responsible party, stage, level of information need, and due date.

AI produces the grid quickly and consistently. What it cannot do is know that your MEP subcontractor is not appointed until Stage 4, so every date it generates needs a pass against the actual appointment programme.

3. Clash detection triage and reporting

This is the highest-value workflow on the list. Your clash engine (Navisworks, Solibri, or Autodesk Construction Cloud) returns the clashes. It does not tell you which forty matter out of four thousand.

Export the clash report to CSV, then give the model the columns and ask it to group by root cause rather than by instance. Two hundred pipe-versus-steel clashes in one plant room are usually a single coordination failure, not two hundred problems. Ask for output as: cause group, affected disciplines, likely owner, severity, and a one-line description suitable for pasting into the coordination log.

The severity call is where you stay in the loop. AI will reasonably rank a 5mm duct clash as low, which is right until you know that duct sits inside a fire-rated shaft where tolerance is zero. Give it that context up front and the ranking improves sharply.

4. ISO 19650 naming audit

ISO 19650-2 naming conventions are strict, tedious, and exactly the kind of pattern a language model handles well. Paste a file list or an object schedule export, state the convention (project, originator, functional breakdown, spatial breakdown, form, discipline, number), and ask for every non-compliant string with the specific field that fails and a suggested correction.

This catches the drift that creeps into every project by Stage 4, when a new starter at a subconsultant begins uploading files named their own way. Run it monthly against the CDE export. It takes ten minutes and prevents the pre-handover panic where nobody can find anything.

Naming is the first of several information checks. Classification, parameter completeness and checks against the EIR follow the same pattern, and our guide to AI-assisted BIM model checking and QA covers them, along with how to configure the rules your model checker runs.

5. Coordination meeting minutes and action tracking

BIM coordination meetings generate a stream of decisions that nobody writes down properly because the person chairing is also the person sharing their screen. Record rough notes during the call, then convert them into structured minutes with owners and dates.

The generate meeting minutes workflow has the prompt. The important addition for BIM specifically is asking the model to separate model-related actions (revise, re-issue, re-federate) from process actions, because they go to different people on different cycles.

6. COBie and asset data cleaning

COBie deliverables fail validation for boringly consistent reasons: inconsistent manufacturer names, blank warranty fields, type versus component confusion, and units entered as free text. AI is good at spotting all four.

Paste the COBie sheet contents (or a representative sample, since these files get large) and ask for a data quality report: which required fields are empty, which values are inconsistent across rows that should match, and which entries look like placeholders. Then ask for a normalised version of the columns that are safe to normalise, such as manufacturer name spelling.

Do not let AI invent missing asset data. If the warranty period is blank, the answer is to go and find it, not to have a model guess a plausible number. This is the workflow with the highest downside risk on the list, because bad asset data goes straight into the operational phase and the golden thread. Treat AI output here as a to-do list, never as the data itself.

7. Drawing register and CDE housekeeping

Revision control questions eat hours: what changed between P03 and P04, which drawings are still at S2 that should be at S4 by now, and which containers have been sitting in Shared status past their approval date.

Export the register, describe the status codes, and ask for the exceptions. This pairs well with AI for document control, since the same export answers both teams' questions.

8. Golden thread and handover narrative

Under the Building Safety Act, higher-risk buildings require a coherent, auditable information trail. Much of the underlying data lives in your models and CDE already. What is missing is the narrative that explains it.

AI drafts that narrative from your records: what was designed, what changed, what was verified, and where the evidence sits. This is a drafting aid on a legal document, so the review burden is heavy and the sign off is a named person, not a tool.

Which AI tool for which BIM job

The practical setup for most UK BIM managers is a model checker for the deterministic work and a long-context language model for everything textual. They are complements, not competitors. A ruleset knows whether a door is 900mm wide. It does not know whether the EIR asked for that to be recorded at Stage 3.

If you are choosing between a copilot built into your platform and a general-purpose model you brief yourself, the BIM AI copilot guide compares the options side by side.

A worked UK example: clash triage on a school project

A BIM manager on a two-form entry primary school in Birmingham, RIBA Stage 4, runs a federated clash on the architectural, structural, and MEP models in Navisworks. The result is 3,180 hard clashes. The coordination meeting is in two days.

Previously this meant a full day of manual filtering and a report that still missed things.

The AI-assisted version: export to CSV with columns for clash ID, grid reference, level, the two clashing elements, discipline pair, and distance. Paste it in with this framing:

"You are supporting a BIM manager on a UK primary school at RIBA Stage 4. Below is a Navisworks clash export. Group these by root cause, not by instance. For each group give: a short cause description, the disciplines involved, the level and approximate location, the likely owning party, a severity of high, medium, or low, and the number of instances. Treat any clash inside a fire-rated construction or a riser as high severity regardless of distance. Return it as a table sorted by severity then instance count. Do not invent grid references that are not in the data."

The output is 31 cause groups. The top six account for 2,400 of the 3,180 clashes:

• Group 1 (high, 780 instances): MEP services routed at 2,850mm through the classroom wing where the structural downstand beams sit at 2,700mm. Single design coordination failure across the whole wing, owner MEP consultant.
• Group 2 (high, 410 instances): Sprinkler main clashing with the primary steel at level 1 grid C to F, likely a stale linked model, owner fire consultant.
• Group 3 (medium, 390 instances): Containment versus ductwork in the plant room, plant room coordination session needed.
• Group 4 (high, 310 instances): Drainage through the ground beam without sleeves modelled, owner structural.
• Group 5 (low, 290 instances): Ceiling hanger versus small-bore pipework, resolvable on site.
• Group 6 (medium, 220 instances): Door swings versus radiators, owner architect.

The BIM manager spends forty minutes verifying: checking three grid references against the model, confirming Group 2 really is a stale link (it is, the fire consultant re-issued four days ago and it was never re-federated), and downgrading Group 4 from high to medium after confirming sleeves exist in the schedule but not the model.

Total time from export to issued coordination report: just over an hour, against most of a day. Just as importantly, the report is now organised the way the meeting needs to run, by owner and cause, rather than as an undifferentiated list of 3,180 rows nobody reads.

Note what AI did not do. It did not run the clash, it did not open the model, and it did not make the fire-rating call. It clustered and drafted. The BIM manager decided.

Writing prompts that work on BIM data

Four things separate a prompt that produces something usable from one that produces plausible noise.

Give it the role and the stage. "You are supporting a BIM manager at RIBA Stage 4 on a UK school project" changes the output materially compared to no framing. Stage tells the model what level of detail is reasonable to expect.

Name the standard. ISO 19650, BS 1192 legacy conventions, the client's own EIR, PAS 1192-6 where safety data is in scope. Models handle named standards far better than vague requests for compliance.

Forbid invention explicitly. "Do not invent grid references, asset tags, or values that are not present in the data. Where something is missing, write MISSING." This one line prevents the most common failure mode in BIM work, which is confidently fabricated detail sitting in the middle of otherwise correct output.

Specify the output shape. A table with named columns, sorted a stated way. BIM outputs almost always feed into another system, whether that is a coordination log, an issue tracker, or a report, so shape matters more than prose quality.

The risk register workflow shows the same structure applied to project risk, and new prompts go out in our free weekly newsletter. For the prompts that change through the project, see what to ask an AI assistant for BIM at each RIBA stage.

Turning a prompt into a repeatable BIM workflow

A prompt that worked once is not yet a workflow. BIM workflow automation starts when the same task runs the same way every week, whoever runs it. The simplest way to get there is a workflow file: one saved document per workflow that holds everything needed to run it.

Keep the workflow files in the CDE or a shared team folder, not in one person's chat history. Once they exist, there are three levels of automation to choose from:

1. Manual, from the saved file. Someone exports the data, pastes the brief and the prompt, and reviews the result. Every workflow should start here.
2. A project space in the AI tool. With Projects in Claude, or the equivalent in other tools, the brief and the prompt are saved once, so each run only needs the new export.
3. Scripted. A script picks up the export, sends it to a model through its API and saves the output for review. Only worth doing for workflows that run every week and have been stable for a while, such as naming audits or automated coordination reports.

Automation on the model side, such as Dynamo or pyRevit scripts that rename views or fill in parameters, is a separate discipline. A language model can help write and explain those scripts, but the script makes the change, not the model, and it should be tested on a copy of the model first.

Compliance guardrails you should not skip

Three constraints apply to every workflow above.

Confidentiality. Client models, EIRs, and cost data are commercially sensitive, and some are security sensitive under the Building Safety Act regime. Check your appointment for restrictions on third-party processing before pasting anything into a public tool. Enterprise tiers with no training on your data are the baseline for project work.

Records and traceability. Anything AI drafts that becomes a project record needs the same review and approval trail as anything a person drafted. The document does not become lower risk because a model wrote the first version. For safety-critical documents, see how the same principle applies to the construction phase plan and to RAMS under CDM 2015.

Competence. CDM 2015 places duties on appointed parties to be competent. Using AI does not transfer or dilute that duty. The named person signing the BEP is accountable for its content regardless of what drafted it. This also applies to anything feeding the quality control process.

Common mistakes

• Asking AI to check geometry. It cannot see the model. It only sees what you exported. Every spatial claim it makes is inferred from your text, not observed.
• Pasting a clash export with no context. Without the fire-rating rule, the stage, and the discipline map, severity ranking is guesswork.
• Trusting COBie output. Cleaning is safe, filling gaps is not.
• Running it once. These workflows compound. A naming audit run monthly is worth ten times one run in a panic before handover.
• Skipping the "do not invent" instruction. The single cheapest guardrail available.
• Treating a drafted BEP as a finished BEP. It is a first draft that saves two days, not a document you issue unread.

Getting started in one week

Day one: run a naming audit against your current CDE export. It is the lowest risk workflow and it will find problems, which builds the case internally.

Day two and three: take your next clash export and run the triage prompt above. Compare the output against how you would have done it manually.

Day four: draft the next BEP from your template plus the EIRs. Time both the draft and your review.

Day five: write down what worked, fix the prompts, and save them somewhere the rest of the team can reach. The value is in reusable prompts, not one-off conversations.

Two of these workflows running reliably will save a BIM manager most of a day a week. That is the realistic prize, and it is available now, which is more than can be said for the generative design demos.

Frequently asked questions

What is AI for BIM?

AI for BIM is the use of artificial intelligence, mostly large language models, to automate the document and data work around a BIM process: drafting BIM Execution Plans, triaging clash detection results, auditing ISO 19650 naming, cleaning COBie asset data, and producing coordination reports. It does not generate or edit model geometry, which stays in authoring tools such as Revit, Archicad, and Tekla.

Which BIM workflows should you automate first?

Start with the ones where the input is a single export and the output is easy to check by hand. An ISO 19650 naming audit against the CDE file list is the lowest risk first step, then clash triage on the next clash export, then BEP drafting from the EIRs. Coordination minutes make a good fourth. Leave COBie cleaning until the others are running reliably, because bad asset data carries the highest risk.

How do you automate a BIM workflow with AI?

Write the workflow down first: the input export, the project brief, the fixed prompt, the output format, the reviewer's checks and a log. Run it by hand from that file for a few weeks. Once it is stable, save the brief and prompt in a project space in your AI tool, and only script it through an API for workflows that run every week. A person still reviews every output before it is issued.

Is using AI compatible with ISO 19650?

Yes, provided the information management process is unchanged. ISO 19650 governs how information is produced, reviewed, approved, and exchanged. It does not specify what tool creates the first draft. The review and authorisation steps must still happen, with the same named responsible parties, and the audit trail must still exist in the CDE.

Will AI replace BIM managers?

No. The parts of the role that AI handles well, drafting documents and sorting lists, are the parts most BIM managers would happily give up. The parts that define the role, setting the information strategy, making coordination decisions, and holding appointed parties to their obligations, require judgement and accountability that a model cannot carry. The realistic effect is fewer hours on paperwork and more on coordination.

What is the best AI tool for BIM work?

For document-heavy work such as BEPs, EIR analysis, and large clash exports, a long-context model like Claude handles the volume best. For quick reformatting and Dynamo scripting help, ChatGPT is fast. For model checking against defined rules, use a purpose-built checker such as Solibri rather than a language model, because rule checking should be deterministic. Most teams run one language model plus their existing model checker.

Is it safe to paste client models or EIRs into AI tools?

Check your appointment first. Many UK client appointments restrict third-party processing of project information, and buildings in scope of the Building Safety Act may carry additional security requirements. Use enterprise tiers that contractually exclude training on your data, avoid pasting anything identifying a higher-risk building's security arrangements, and if in doubt, anonymise the project references before pasting.