I can already imagine the reaction: “BIM is dead? Wait. I have not even started yet.” Relax. The building information model is not about to vanish. But the BIM many of us grew up with — manual modelling, rigid workflows, endless field-filling, information copied from one interface into another — is beginning to look like a transitional technology rather than the final destination.
The distinction matters. Modelling is an activity. A model is a representation of knowledge. We may need less and less of the first while needing more and more of the second.
Buildings will still need trustworthy information. Owners will still need to know what exists, where it is, how it performs and what changed. Designers will still need to test decisions before concrete, steel and money make them expensive. Contractors will still need coordinated information. Facility teams will still need memory. What changes is the interface between that knowledge and the people who use it.
The future model may not always look like a single navigable 3D file. It may become a network of geometry, documents, sensor data, requirements, histories and semantic relationships that can be queried in ways we are only beginning to explore. The model survives. It simply stops pretending that everything meaningful has to live inside one authoring environment.
And this is where AI makes the conversation interesting.
Not because databases are suddenly useless. They are not. Structured information will remain fundamental whenever we need reliability, validation, interoperability, traceability and repeatable computation. But AI is weakening an assumption that shaped much of our digital work: that information must always be perfectly structured before a machine can help us make sense of it.
Large language models and other AI systems can work with messy, heterogeneous material in ways traditional rule-based systems could not. That does not eliminate the need for information architecture. It changes where human attention is most valuable. Maybe an engineer should spend less time wondering whether a field contains an underscore or a dash, and more time deciding whether the information in that field matters at all.
For years, many BIM workflows have depended on people acting as highly educated transcription devices: reading information in one place, interpreting a rule, typing it somewhere else, checking the format, repeating. We called it digitalisation. Sometimes it was simply bureaucracy with better graphics.
I say this as someone who actually likes order.
I find rules reassuring. I can happily disappear into a large spreadsheet, then spend the afternoon drawing, writing, doing yoga, making a physical model or watching a 3D printer. Order relaxes me. It is a form of active meditation. Which is probably why BIM made immediate sense to me: relationships, constraints, classifications, systems. A world in which things should have a place and a reason.
But order is useful only when it serves thought. When order becomes the objective, we build digital systems that consume enormous amounts of energy simply to preserve their own internal logic.
That is why I keep thinking about the old stereotype of the chaotic architect. I never really belonged to it. The idea that disorder is somehow proof of creativity has always seemed strange to me. Technical drawing demanded order long before BIM existed. CAD demanded it too, even when many offices preferred copy-paste archaeology over naming conventions and coherent templates. Before Ctrl+Z, a bad ink line could cost you several minutes with a blade. Precision was not a BIM invention.
If you already think in systems, BIM is not an intellectual revolution. It is a technological translation of habits that were already there: coherence, relationships, cause and effect, information attached to intent.
This is also why learning BIM today is not pointless, even if the tools we use now change dramatically in the next few years.
I sometimes think of BIM as ancient Greek. You may not use every form directly in your daily life, but the discipline changes the way you think. It teaches abstraction. Structure. Relationships. Roots. BIM can do something similar for technical professionals: it trains us to understand that a change is rarely isolated, that information has consequences, that systems behave through connections.
Those habits will still matter when the interface becomes a prompt, an agent or something we have not named yet.
And when Revit — or any other authoring tool — is no longer the centre of the workflow? Press F1 one last time, metaphorically speaking.
F1 has always been my favourite secret because it represents something larger than software help. It means: learn how the tool works. Discover another way. Increase your freedom. The more ways you know to reach a result, the less dependent you are on one button, one workflow, one vendor or one generation of technology.
Tomorrow the equivalent of F1 may be knowing how to question an AI agent, how to verify what it proposes, how to give it context, how to recognise a plausible mistake and how to take responsibility for the final decision.
That is the part of BIM I do not expect to die.
The manual work will shrink. Some interfaces will disappear. Many standards and workflows will evolve. New forms of automation will make today’s routines look oddly laborious. But the professionals who learned to think in systems, to connect information with purpose and to distinguish useful structure from ritualised complexity will not have wasted their time.
BIM may be ending. Or perhaps it is simply shedding the part of its skin that belonged to the limits of our tools.
Long live the model. Long live the information. Long live the ability to think before we automate.
And long live the people who remember that their value was never inside the software.
A small post-BIM survival checklist
- Learn how to ask better questions, not only how to write better prompts.
- Know more than one way to perform the operations you depend on.
- Experiment with automation and AI before urgency forces you to.
- Keep the mental discipline BIM taught you, even when the interface changes.
- Do not fear disorder. Learn when to structure it and when to leave it alone.
- Treat change as part of professional practice, not as an interruption to it.
- Remember: your value is not the software you operate. It is the judgement you bring to the system.
