How BIM, AI and project management connect during construction

Most Kenyan developers encounter BIM as something the architect does: a 3D model of the building that looks impressive in presentations. But BIM's real value emerges during construction, not design. When the structural engineer's columns clash with the MEP engineer's ducts, BIM detects the clash before the steel is fabricated. When the contractor submits a progress claim, the BIM model shows exactly what has been built versus what was planned. When a variation is proposed, the model quantifies the impact on every connected system.

The shift from BIM as a design visualisation tool to BIM as a construction management platform is the single largest productivity opportunity in Kenyan construction. It requires three things: a coordinated multi-discipline model, a project management system that connects to it, and a developer who understands what to ask for. REDM provides the project management layer that connects BIM coordination to cost tracking, variation management, and payment certification. Reference the bim-coordination-design-stage-kenya article for how the model is built at design stage.

A clash in a building model is when two elements occupy the same space: a structural beam running through an air-conditioning duct, a drainage pipe intersecting a foundation, a fire sprinkler blocked by a ceiling brace. In traditional 2D drawing coordination, these clashes are found on site when the contractor discovers that what the architect drew and what the engineer drew do not match. By then, the concrete is poured, the steel is fabricated, and the fix costs real money and real time.

BIM clash detection runs an algorithmic check across all discipline models and flags every spatial conflict. The architect, structural engineer, and MEP engineer resolve the clashes in a coordination meeting before a single tender is issued. AI tools accelerate this by prioritising clashes by severity and suggesting resolution options based on previous project data. On a typical mid-rise building in Mombasa, automated clash detection can identify 200 to 500 clashes that manual drawing review would miss. Each clash caught before construction saves between KES 50,000 and KES 500,000 in rework, depending on what is affected and when it is found.

REDM BIM management service coordinates this process: the model is the single source of truth for all disciplines, clash reports are tracked as project documents, and resolved clashes are signed off by the responsible consultant. The developer sees a dashboard of clash status rather than relying on verbal assurances that everything is coordinated.

Construction progress is traditionally tracked through site meetings, contractor reports, and the project manager's judgement. On a complex project with multiple subcontractors, these sources often disagree. The contractor claims 40 percent completion of the structure. The QS assesses 35 percent. The project manager thinks it is closer to 30 percent. The payment certificate becomes a negotiation rather than a measurement.

BIM-based progress tracking replaces estimation with evidence. The model is updated with as-built data as construction proceeds: which columns are poured, which slabs are cast, which MEP risers are installed. The project manager compares the as-built model against the planned programme and the cost loaded schedule. Progress is measured, not argued about. Payment certification becomes a calculation based on measured work done, not a negotiation based on contractor claims.

AI-assisted progress tracking takes this further by comparing site photographs or drone imagery against the BIM model to automatically detect progress. On large infrastructure or multi-building projects, this can reduce progress assessment from days of manual measurement to hours of automated comparison. The developer sees verified progress, not reported progress.

A variation on a construction project follows a chain: the contractor identifies something that differs from the contract documents, raises a Request for Information (RFI), receives a response, submits a variation quotation, the QS assesses it, the architect instructs it, and the contractor executes it. In a paper-based or email-based system, this chain breaks at multiple points. RFIs go unanswered. Variation quotations reference superseded drawings. Payment certificates include variations that were never formally instructed.

BIM and project management integration closes this gap. When a variation is proposed, the BIM model shows exactly which elements are affected and what the knock-on effects are on connected systems. The project management system tracks the RFI through its lifecycle: raised, responded, quoted, assessed, instructed, executed, certified. Every step is timestamped and attributed. The payment certificate references only instructed and assessed variations. The audit trail is complete.

REDM connects BIM coordination to ERPNext project management: the model identifies the clash or variation trigger, the project management system tracks the resolution, and the cost system captures the financial impact. Reference the variations-and-claims-construction-kenya and contract-administration-kenya-developers articles for the full contractual framework.

The developer does not need to operate BIM software. The developer needs to specify in consultant appointments and contractor contracts that the project will use a coordinated BIM model as the basis for clash detection, progress tracking, and variation management. This is a contractual requirement, not a technology choice.

Specifically, the developer should require: a BIM execution plan before design development starts, multi-discipline model coordination at each design stage gate, clash detection reports as contract deliverables, as-built model updates at each payment milestone, and variation assessments referenced to the BIM model. These requirements do not increase professional fees materially if specified at appointment. They reduce construction cost and time substantially by catching coordination problems before they reach the site.

If your current project is in design, ask your architect whether a coordinated BIM model is being produced. If the answer is no, discuss what it would take to introduce one before tender. The cost of BIM coordination at design stage is a fraction of the cost of resolving clashes on site. If your project is already in construction, ask your project manager how variations and progress are being tracked. If the answer is spreadsheets, discuss connecting to REDM for document and cost tracking.

Specify BIM requirements in consultant appointments at Stage 2, not Stage 4. Appointing consultants without BIM requirements and then requesting a coordinated model at tender stage is the most expensive way to introduce BIM. The model must be built as design develops, not retrofitted from 2D drawings.

Pair this guide with the BIM coordination article for design-stage methodology, the variations and claims article for the contractual framework, and the construction management article for the cost and programme tracking context.