What Spain's BIM Plan demands of a mid-sized engineering firm in 2026

What exactly binds you today

The hard facts are short. They come from Spain's BIM Plan for public procurement, approved by the Council of Ministers; the thresholds in force are those of the update of 1 January 2026.

Two details change the result of that calculation more often than you would think. The first: it applies to works, to concessions, to site supervision, to technical assistance and to project design, almost the whole technical chain. If your firm does not build, this still reaches you through the services door, and in linked or preliminary contracts the level is set by the works, not by the size of your fee.

The second: in contracts split into lots, it is the estimated value of each lot that counts, not that of the whole file. The decision to split into lots has direct consequences for the level of information that can be demanded, and it is almost never analysed while the file is being prepared.

Who it reaches and who it does not

Here it pays to be honest. The BIM Plan has the effect of an internal instruction for the Spanish central government and its bodies and public-law entities; for the rest of the state public sector it is a recommendation. A regional government, a provincial council or a town council is not bound by it.

That does not mean you can ignore it outside central government. Within one and the same administration you will find tender documents that have required BIM methodology for years, with their information manager named in the contract, and eight-figure works tenders that never mention the word. There is no rule per administration: there is one per file, and it has to be read.

There is a sentence in the plan itself that explains a good deal of what is going to happen over the next two years:

“The contracting authority must apply to its internal management of the contract the same BIM level it has required in the tender. If the contracting authority has not yet reached that BIM level, it may call on technical assistance to support the management of that contract.”

Translated: whoever asks you for the model has to be in a position to read it, and many are not. That asymmetry produces tenders with copied requirements and handovers that get stuck.

What it means in practice

When the tender documents ask for it, they ask in this vocabulary: coordination under ISO 19650, delivery in IFC, a common data environment, security compliant with the National Security Framework. Behind that there are four concrete things.

Exchange information requirements. The document where the client says what information it needs, what it is going to use it for, when it wants it and by what criteria it will accept it. It is the start of the chain: when it is missing, or when it is a list of formats with no purpose, everything downstream gets improvised.

BIM execution plan. Your answer to the above: who produces what, when, under what naming convention and through which review flow it passes before going out. A plan that repeats the tender document in other words is not a plan, and on site it protects you from nothing.

Common data environment. The single place all information goes through, with states (work in progress, shared, published, archived), version control, access control and traceability of who approved what and when.

Roles. Someone is answerable for the information management of the contract, someone coordinates the models from the different disciplines and each discipline answers for its own. It can be two people or three, but the roles have to be assigned with a name and with hours, not handed out by habit.

And the deliverables: IFC for the model, BCF for issues, COBie or an equivalent schema when the end recipient is going to operate and maintain the asset, and quantities that come out of the model and not out of a spreadsheet on the side. That last point is the one that moves the most money.

Four typical mistakes when answering a tender with BIM requirements

1. Working out the level from the wrong figure

From the total of the file instead of from the lot. From your fee instead of from the works your service is linked to. It is a two-minute mistake that governs the effort of the entire delivery and, if you come up short, it surfaces when there is no margin left to correct it.

2. Answering with software instead of with procedure

The bid lists programs and versions, attaches the usual org chart and treats the section as done. The tender is not asking what you buy: it is asking how you produce, review, approve and deliver information. If the execution plan does not say who reviews the model before publishing it and by what criteria, you have not answered.

3. Calling a shared folder a common data environment

Change and version control during delivery is the obligation most often breached in practice, and the one that costs the most. The day you have to prove which version was in force when a unit was built, either there is traceability or there is an argument that lasts months.

4. Leaving the acceptance criteria open

Clauses of the kind “in formats compatible with those used by the client” are the most dangerous in a tender: whether the final delivery is accepted depends on an interpretation that today is not written down anywhere. That gets closed at the start, with a meeting and minutes, not at handover. The same goes for the as-built: delivering geometry with no asset data meets the letter of the tender and wastes all the value for whoever is going to maintain the facility for the next thirty years.

What you can do with the team you already have

More than you think, and less than you are being sold. A mid-sized design office that already models can, without hiring anyone: settle on a single naming convention and apply it; write the responsibility matrix for the next contract in an afternoon; set up a common data environment with states and version control on tools it already pays for; establish that nothing is published without a review against written criteria; and export to IFC regularly during the project instead of at the end. That last change alone avoids most delivery frights: if the IFC is generated every fortnight, classification and property problems show up while they can still be fixed.

Now what you cannot do. You cannot appoint as information manager someone who is already at one hundred per cent on production: that is the most common way for coordination to end up being a weekly email. You cannot audit by hand, at every milestone, that a model meets what was required: that check is repetitive, and either a program does it or it does not get done. And you cannot decide the asset data schema the month before handover, because the data is captured while the work is being built.

After six years doing this on HS2, Sydney Metro West, Red Sea and Trojena, my view is that the hard part was never the software: it was agreeing the data, writing the procedure and holding to it when the job gets tight.

How to tell whether you are ready: an honest checklist

Ten questions, yes or no and no shades of grey, thinking about the last contract you delivered. With four noes you are in time. With seven, the problem turns up in the next tender, not the one after.

• Do you know the estimated value and the level required, lot by lot, of the contracts you will bid for this year?
• Do you have a BIM execution plan of your own, one you can tailor in two days, rather than one copied from the last tender you won?
• Is there a named person answerable for information management, with hours allocated in the contract budget?
• Is the naming convention for files and elements the same across your last three projects?
• Can you say, today and without asking anyone, which version of each model is published and who approved it?
• Have you ever exported your model to IFC and opened it in a viewer other than the program you built it in?
• Are coordination issues managed in BCF with an owner and a date, or do they live in meeting minutes?
• Did the quantities in the last valuation come out of the model or out of a parallel spreadsheet?
• Do you know what asset data whoever operates what you deliver actually needs, and are you capturing it during delivery?
• Does someone check the deliverables against the tender before sending them, using a written list rather than from memory?

The list does not measure theoretical maturity or certifications. It measures whether the information in your own house is under control: a tender with BIM requirements is no more than someone asking exactly that in writing.

And if you can only do one thing this month: take the last tender with information requirements, underline every concrete demand, compare it with what you actually did and write the difference down on one page. That page has to exist before the next tender, because discovering the gap during delivery costs another order of magnitude.