Why a firm's BIM maturity is not measured by its tools alone

“We have Revit, Navisworks, and a cloud to share the models — we're pretty mature in BIM.” It is a sentence you often hear, and it confuses two different things: having the tools, and having the maturity to use them well. A firm can own the entire software stack on the market and remain, at its core, very far from a mature BIM way of working.

The illusion of maturity through tools

Tools are visible, measurable, easy to list on a website or a tender. Processes, on the other hand, cannot be seen from the outside: does each project have a clearly identified coordination lead? Are the client's information requirements formalised before starting, or discovered as things go along? Is the naming convention the same on every project, or reinvented each time depending on who is leading? None of this appears on a list of software.

What really makes maturity

A firm's BIM maturity comes down to four things, far more than to its software estate:

• Documented processes applied consistently from one project to the next, not reinvented each time
• Clear roles and responsibilities, not “more or less everyone takes care of it”
• Skills spread across the team, not concentrated in a single person
• Traceability of decisions and exchanges, not just neatly filed files

A firm can very well score low on these four points while having the latest tools on the market — and conversely, a firm with more modest tools but solid processes is often more effective day to day than an over-equipped but disorganised one.

A firm can own the entire software stack on the market and remain, at its core, very far from a mature BIM way of working.

The classic symptom: the firm that depends on a single person

The most telling sign of low maturity is not a lack of tools, but an excessive dependence: a single person really knows the firm's BIM setup, manages the Revit template, and knows why a given convention was chosen. The day that person is absent or changes role, half of the firm's know-how disappears with them. It is a problem of process and of how skills are distributed — never a tooling problem.

How to know where you really stand

The only reliable way out of subjective impressions (“we're pretty good”, “we're behind”) is to audit real practices, theme by theme: common data environment, information requirements, roles, coordination, information security, training. An overall score says little on its own — what matters is seeing precisely which themes pull the average down, so as to prioritise effort where it really counts.