We’ve delivered 20 Revit models across European countries

When we finished our 20th Revit model delivery across Europe, nothing really happened. No big announcement, no celebration. We just moved on to the next project, like we always do.

But later, when we actually paused and looked back, it hit us that those 20 projects taught us more than any course or certification ever could.

We worked across different countries, dealt with completely different standards, and handled all kinds of client expectations. Every project felt new in some way. And yet, through all of that, one thing stayed consistent: our BIM workflow.

So this isn’t a technical guide. It’s more of a reflection on what we learned, what worked, what didn’t, and what you should know if you’re planning to deliver Revit models across Europe.

Why working in Europe feels different

The first thing you notice is simple: there’s no “European standard” you can rely on.

Every country does things its own way. Building codes change. Documentation styles change. Even how teams communicate can feel different from one place to another.

For example, a project in Germany doesn’t feel anything like one in the Netherlands. And a healthcare project in the UK comes with a completely different set of expectations compared to France.

At first, we thought our existing Revit setup would work everywhere with minor tweaks. That didn’t last long.

On our third project, a residential development in the Netherlands, we realised our template just wasn’t enough. The client expected a different level of detail and a cleaner data structure. We had to rework things mid-project, which slowed us down.

It wasn’t ideal. But it taught us something important: you can’t just export your local workflow into Europe and expect it to work.

What those 20 projects actually looked like

Over time, we ended up working in the UK, Germany, the Netherlands, France, Spain, Poland, and a few smaller markets.

The project types were just as varied.

Some were commercial office spaces. Others were hospitals, universities, or large residential buildings. In a few cases, we handled full BIM coordination of architecture, structure, and MEP all together.

In other projects, we were simply converting 2D drawings into usable Revit models.

That mix forced us to stay flexible. No two projects felt exactly the same.

Client expectations 

One thing we didn’t expect was how different clients would be depending on the country.

UK clients, for instance, were very structured. They knew exactly what they wanted, mostly because BIM standards have been in place there for a while. That made things clearer but also more demanding.

German clients were different. They focused heavily on detail. Documentation had to be precise, and there wasn’t much room for shortcuts.

On the other hand, in countries like Spain and Poland, some clients were still getting comfortable with BIM. So instead of just delivering models, we often had to guide them through the process and explain how to use what we delivered.

Each market came with its own learning curve.

What actually helped us stay consistent

After a few early mistakes, we started tightening our process.

First, we made sure every project started the same way, with the same setup, the same checklist. Units, grids, naming conventions, and shared coordinates are all locked in from day one. It sounds basic, but it saved us a lot of trouble later.

Then, we stopped jumping straight into modelling. Instead, we spent more time upfront understanding local standards.

For example, Germany required DIN standards. The UK needed alignment with ISO 19650. Other countries had their own expectations.

Doing this research early made a big difference. It reduced back-and-forth and made client conversations much smoother.

We also became strict about reviews. Every model, no matter how small, went through checks, clashes, data, naming, and level of detail.

Some teams skip this when timelines are tight. We didn’t. And honestly, that consistency is probably why we avoided major rejections.

The challenges no one really talks about

Not everything was technical.

Time zones, for example, became a daily headache. When your team is coordinating with people in Warsaw, Amsterdam, and London, even scheduling a meeting can take effort.

Language was another factor. Yes, most communication happens in English. But local regulations don’t. And sometimes, understanding a requirement meant digging through documents in German or French.

Then there’s handover, which turned out to be very different depending on the client.

Some wanted fully detailed, COBie-ready models. Others just needed something clean and usable for construction.

We learned to clarify all of this early. Otherwise, things get messy at the end.

What we really learned

Looking back, one thing is clear: Revit skills alone aren’t enough.

You need structure. You need adaptability. And you need to manage expectations constantly.

At the same time, you can’t keep changing everything for every project. You need a core process that stays stable, even when everything else changes.

Also, in many cases, you’re not just delivering a model. You’re helping the client understand BIM itself. That became part of the job whether we expected it or not.

Final thoughts

Working across Europe changed how we approach projects.

It’s not just about modelling anymore. It’s about understanding how different teams think, how different systems work, and how to bring everything together without losing consistency.

Every project taught us something new. And even after 20 deliveries, it still feels like we’re learning.

Ready to find out what your project will cost? Find out here.