Construction has worked for decades with a layered chain: client, main contractor, subcontractors, suppliers. That chain is used to dividing responsibility and delivering work in phases. That makes the sector in certain respects better prepared for AI than other sectors — there is discipline in planning, in quality control, in recording agreements. But that same chain makes data fragile. Drawings, calculations, schedules and progress reports originate with different parties, in different systems, with different versions of the truth. An AI application that has to run on that data runs on something that is often not complete, not current or not centralized.
That gap between organizational discipline and data maturity is precisely where many AI pilots in construction stall. A project manager tries to deploy an AI tool for schedule optimization, but the input data comes from three systems that don't connect to each other. A work planner wants calculations checked automatically, but the historical data is spread across separate Excel files per project. The pilot doesn't stall because the technology doesn't work, but because the organization isn't yet prepared for it.
AI maturity doesn't just measure whether an organization uses tools, but whether the foundation underneath is in place. That starts with the organization itself: is there a clear owner for digitalization, is knowledge shared between projects, or does every project remain an island. Next comes the IT infrastructure: are systems connected to each other, is there a foundation on which new applications can run without everything needing to be retyped manually. Only after that comes data management: is the data that exists reliable, current and accessible to those who need to work with it.
This sequence isn't a preference, it's how it works. An organization that wants to improve data management without the IT infrastructure supporting it is building on quicksand. An organization that wants to deploy AI applications without the organization itself knowing who owns which process ends up with a tool nobody maintains. In construction this pattern is visible: the sector often has the organizational will, but the infrastructure and the data lag behind. That explains why pilots often succeed at project level and stall at organizational level — the fundamental dimensions haven't grown along with the ambition.
The hybridresourcing.com maturity measurement looks at seven dimensions, from organization and infrastructure to the more dependent layers such as process automation and decision-making. Each dimension is assessed at one of five levels: baseline, foundation, activation, insight or intelligence. In construction, the picture is often unevenly distributed across those dimensions. A company can be far advanced at the organizational level — clear roles, a digitalization agenda, support from management — and yet still be at baseline on data management, because project data has never been brought together centrally.
That inequality becomes visible in the plotting round, in which multiple people within the organization score separately. A director and a site supervisor can assess the same company very differently, and that spread is itself information. If the CIO thinks the data is in order and the work planner struggles daily with scattered files, that reveals a bottleneck that a single conversation would not have exposed. In a sector where work is spread across projects and parties, that spread is often larger than average — and therefore more informative.
This measurement says nothing about which tasks AI can take over or how much time that saves. It concerns the question of whether the organization can carry AI: is the foundation in place, is the infrastructure ready, is the data reliable enough to build on. That question is more relevant for construction than in sectors where data is by nature already recorded centrally. Compare it with the installation sector, where project-based work and fragmented data create similar bottlenecks, or with manufacturing industry, where production data and organizational structure show a different balance. The transport sector also has a comparable tension between operational discipline and digital foundation, which shows that this pattern is not unique to construction, though it occurs with its own intensity due to the chain structure.
The tool with which this is measured is under construction. Anyone who wants to complete the measurement once it becomes available can sign up for the waiting list. Nothing is being offered here that doesn't yet work, and nothing is promised about the outcome — only an honest picture of where the organization stands now, dimension by dimension.
If it turns out that the fundamental dimensions are in order, or on their way there, another question becomes relevant: which part of the work itself is suitable to be taken over by AI. That is a different measurement from this one. Where hybridresourcing.com looks at whether the organization can carry AI, the work scan from FTE TO AI calculates per task which part of the work can be taken over — not as an estimate, but as the outcome of a task analysis. For a construction company that knows where its foundation stands, that is the logical next step: first the foundation, then the question of what can be built on it.
Vraag maar wat er moet staan voordat AI in uw organisatie kan landen.
Answers come from this site’s knowledge base. Not tailored advice, and not a scan of your company.