A measured step toward Smarter Construction decisions
🚀 KAI File Analyser Is Live The construction industry has never had more information at its fingertips. Every project generates drawings, revisions, consultant advice notices, engineering assessments, specifications, site photos and correspondence at an extraordinary rate. Yet despite this abundance of data, coordination failures remain common, commercial risks are often identified late, and teams continue to rely heavily on manual review and individual judgement to interpret critical information. Over the past two decades, construction technology has focused primarily on digitising workflows. RFIs became online forms. Drawing registers became searchable. Dashboards became more visual. These advancements have unquestionably improved accessibility and organisation. However, they have not fundamentally changed how decisions are made. In most cases, they have simply moved existing processes onto cleaner screens. If software only improves presentation without reducing cognitive burden or surfacing risk earlier, it does not materially alter outcomes. It refines administration rather than strengthening judgement. This is the context in which we are releasing KAI File Analyser. KAI File Analyser is now available inside Documentation → Project Documents. It allows users to attach drawings, reports, specifications site photos etc. already stored within the project environment, enter a structured prompt, and receive structured, decision-oriented output. Importantly, this occurs entirely within the system of record. There is no exporting of sensitive files, no copying into public AI tools, and no separation from established registers and permissions. While the interaction is straightforward, the underlying shift is meaningful. Instead of requiring teams to manually read, compare and synthesise documents, KAI assists in analysing them together, in context, and returning structured findings. This reduces the time spent interpreting large volumes of information and increases the likelihood that material risks are identified early. Consider several practical scenarios. A project team reviewing existing condition photos prior to demolition can prompt KAI to create a structured dilapidation report noting defects and damage. Rather than manually compiling observations across dozens of images, the team receives a consolidated and organised summary that can be reviewed, edited and issued as required. In pre-construction, where coordination risk between architectural and services packages has historically been a persistent industry challenge, KAI can be prompted to analyse drawing sets and highlight potential coordination risks that should be captured in a design risk register. The building industry has long struggled with this form of cross-discipline alignment. If software can assist meaningfully in identifying these risks before they manifest on site, that represents a substantial step forward. Similarly, when reviewing engineering documentation such as ISA and DSA reports, KAI can compare structural findings with current site conditions and categorise compliance risk. Instead of manually reconciling narrative reports with photographic evidence, project teams receive structured insight that supports clearer decision-making. These examples illustrate an important distinction. KAI is not intended to replace professional judgement. Rather, it is designed to support it by reducing friction, organising complexity and surfacing potential exposure earlier in the project lifecycle. It is equally important to acknowledge that core workflows remain critical. RFIs, site delivery processes and portals are foundational to effective project control, and we continue to prioritise improvements in these areas. Strong workflow execution remains non-negotiable. However, improving workflows alone does not address the deeper issue: the industry’s reliance on manual interpretation of increasingly complex documentation. If technology only helps teams execute the same processes slightly more efficiently, it will not fundamentally shift outcomes. The longer-term direction for KAI extends beyond document analysis. Over time, it will increasingly understand project sequence and relationships between records. It will assist in identifying when a Consultant Advice Notice should link to an RFI, when a Client Instruction is outstanding, or when a variation trigger may exist based on document content. It will support teams in recognising commercial and coordination implications earlier, before they become disputes or cost overruns. This progression is not about novelty. It is about building a system that supports clearer judgement within the realities of construction. KAI File Analyser represents the first visible step in that direction. It demonstrates how intelligence can be layered over structured project data to reduce cognitive load and improve clarity. As it evolves, its value will increasingly be measured not by how it looks, but by how effectively it helps teams identify risk, maintain sequence integrity and make better-informed decisions. The construction industry does not lack data. It lacks tools that meaningfully assist in interpreting that data at speed and in context. KAI is our response to that gap. We encourage you to explore the feature, test it against real project scenarios, and provide candid feedback. The ambition is not incremental improvement, but durable improvement in how construction decisions are supported. This release is the beginning of that journey.
How do you feel about this update?
