How to Implement BIM Workflows in Architectural Projects

Three years ago I was sitting in a project meeting watching two engineers argue about which version of the structural model was current. One had downloaded it Tuesday. The other had downloaded it Thursday. They were different files. Nobody knew which one the architect had actually coordinated against.

That project had BIM in the contract. It had Revit licenses. It had a server folder labeled “BIM Models.” What it did not have was any kind of actual workflow. And that difference, between having BIM software and actually running a BIM workflow, cost that project weeks of rework and a lot of strained relationships.

If you are setting up BIM on an architectural project for the first time, or trying to fix a workflow that has slowly stopped working, this is what actually matters.

Start With a Plan Nobody Skips

The single most common reason BIM workflows fall apart is that the project started without anyone properly agreeing on how it would work.

Everyone assumed someone else had sorted it. The architect assumed the project manager was handling file protocols. The MEP consultant assumed the architect would tell them what software version to use. The contractor assumed the models would be properly coordinated when they arrived. None of those assumptions was checked. All of them were wrong.

Before a single wall gets drawn in Revit, someone needs to sit everyone down and agree on the basics.

What Needs to Be Agreed Before Modelling Starts

• What software everyone is using and which version, because Revit 2022 and Revit 2024 do not play nicely together and finding that out three months in is nobody’s idea of fun
• What level of detail is expected at each project stage, concept looks very different from construction issue and everyone needs to know the difference
• Who owns which model and who has permission to change what
• How files get named because a folder full of files called “Arch Model Final v3 REVISED” is not a BIM workflow
• How often the whole team comes together to coordinate, weekly, fortnightly, whatever works, but it needs to be fixed and it needs to actually happen

This is what a BIM Execution Plan is supposed to do. Not a document that gets written and filed away. A working agreement that everyone on the project actually follows.

Give Everyone One Place to Work From

Half the coordination problems I have seen on BIM projects come down to people working from different versions of the same file without realising it.

Someone downloads the architectural model on a Monday, spends two weeks designing their services around it, then discovers the architect issued an updated model on the Wednesday of that first week. Two weeks of MEP design built around a model that has already moved on.

A Common Data Environment fixes this. One platform, one folder structure, one place where every model and every drawing lives. BIM 360, Procore, even a well-organised SharePoint if the budget is tight. The platform matters less than whether everyone actually uses it and whether the folder structure makes sense.

The Folder Structure That Actually Works

• Work in progress for anything still being developed that others should not be relying on yet
• Shared for files that are ready for other disciplines to coordinate against
• Published for formally issued information
• Archived for old versions that need to be kept but should not be mistaken for current

Simple. But only useful if everyone respects the difference between those folders and does not just dump everything in one place because it is quicker.

Coordinate Every Week Not Just When There Is a Problem

This is where most BIM projects quietly stop working properly. The coordination meetings that were supposed to happen every fortnight start slipping. One gets moved because someone is on holiday. Another gets cancelled because the deadline is close and everyone is too busy. Before long nobody has actually looked at a federated model for six weeks.

And then someone goes to site and finds a duct running straight through a beam.

Regular coordination is not optional. It is the whole point.

What Good Coordination Actually Looks Like

• Models get federated on a fixed day every week or fortnight, not whenever someone gets around to it
• A clash report gets run before the meeting so the team arrives knowing what needs to be discussed
• Every clash gets assigned to a specific person with a specific date to resolve it, not added to a list that nobody owns
• The next meeting starts by checking whether last week’s clashes were actually fixed in the model
• Someone keeps a running log of every clash, who owns it, and where it is up to

That last point feels like extra admin until the first time a subcontractor disputes a variation and you have a complete record of every coordination decision made on the project.

Sort Your Templates Out Before Anyone Starts Modelling

This one saves so much time and almost nobody does it properly at the start.

If four architects are all starting Revit models from scratch with their own settings, you end up with four models that have different units, different coordinate origins, different view naming conventions, and different shared parameter files. Federating them is a nightmare. Finding anything in someone else’s model takes twice as long as it should.

Things Worth Setting Up Once Properly

• A project Revit template with agreed units, view templates, and shared parameters that everyone starts from
• Shared coordinates set up and agreed before any modelling begins, because fixing misaligned models later is genuinely painful
• A naming convention for views, sheets, and elements that makes the model readable to everyone not just the person who built it

A day spent on this at project start saves weeks across the life of the project.

The People Part Is Harder Than the Technology Part

I want to be straight with you about this because it is the thing that catches people out most often.

You can have perfect templates, a beautifully organised CDE, and a clash detection process that would make a BIM manager cry with joy. And if two disciplines on the project are not actually engaging with the coordination process, none of it works.

BIM coordination only works when everyone is doing their part. One team that is always late updating their model, or that keeps working from a local copy instead of the shared environment, or that treats coordination meetings as optional creates gaps that affect everyone else.

What Actually Helps With This

• Tell people why it matters for them personally, fewer site queries, less rework, less stress, not just that it is a contract requirement
• Make the process as simple as possible because if accessing the CDE is complicated people find workarounds
• Deal with problems early and directly, a consultant who is not keeping their model updated needs a conversation in week three not week twelve

Final Thoughts

Getting BIM workflows right on architectural projects does not require perfect technology or unlimited budget. It requires someone to set up the process properly at the start, make sure everyone understands it, and then actually hold the coordination together when the project gets busy and everyone starts looking for shortcuts.

The projects where BIM genuinely delivers are not always the most technically advanced ones. They are the ones where the whole team is working from the same information, coordinating regularly, and dealing with problems while they are still cheap to fix.

That is it really. Everything else is details. Ready to find out what your project will cost? Find out here.