01General
Arcadis puts AEC agents through a six-month engineering trial before investing in Nomic
Story date: August 18, 2026
Arcadis invested in Nomic after a six-month trial involving about 150 engineers across disciplines, sectors, and countries. The consultancy will also help shape Nomic's product roadmap for architecture, engineering, and construction work.
The trial applied Nomic agents to drawing review against firm standards, code checks, submittal review, RFI research, and BIM tasks. The operating model combines agent processing with expert review rather than handing design judgment to an unattended system.
Arcadis described the trial as changing how 86% of participating engineers approached their work, while the report did not provide a project-level hours or cost baseline. The immediate implication is that AEC firms can evaluate agents against repeatable delivery tasks before committing capital or changing controls.
Why it matters: The important signal is not another AEC copilot launch; it is a large engineering consultancy using a defined trial to test whether agents fit regulated delivery work before taking an ownership position.
Practical AI use case or operational implication: An engineering practice can route incoming RFIs and submittals through Nomic for first-pass retrieval, then require the discipline lead to approve the cited clause, drawing reference, and response before release.
Suggested executive takeaway: Arcadis' digital-transformation lead should publish the trial's task-level accuracy, escalation, and time baselines before expanding the roadmap across client programs.
How large/medium/small GCs/subs could use this: Large GCs can benchmark agent review across a portfolio; midsize firms can pilot one discipline's RFIs; small subs can use a controlled document-review queue without rebuilding their whole stack.
Hashtags: #ConstructionAI #AEC #BIM #Engineering
View Source#ConstructionAI#AEC#BIM#Engineering
02General
CMiC earns ISO 42001 certification for the AI management system behind NEXUS
Story date: September 01, 2026
Construction ERP provider CMiC announced ISO 42001 certification for its AI management system, with independent certification performed by Schellman. The certification is tied to CMiC's NEXUS platform, which the company says is used by the vast majority of its customers and handles more than $100 billion in construction revenue annually.
The controls cover AI design, data selection, validation, deployment, monitoring, and continuous improvement. NEXUS uses large language models for workflows such as reconciliation, purchase-order matching, and cost coding, placing the AI inside construction financial records rather than in a standalone chat window.
ISO 42001 does not prove that every NEXUS output is correct or that a project has achieved a quantified return. It does give construction customers an independently assessed management-system reference for vendor diligence, incident handling, and lifecycle oversight as AI touches cost and project-delivery decisions.
Why it matters: Construction firms buying AI in cost control need evidence about how a vendor governs models over time, not just a feature list. CMiC's certification turns that procurement question into an auditable control conversation.
Practical AI use case or operational implication: A controller can map each AI-assisted cost-code or PO-match exception to the source transaction, reviewer, resolution, and model-change record before the amount reaches a job-cost report.
Suggested executive takeaway: CMiC should give customers a control-to-workflow crosswalk showing which NEXUS functions are covered by the certified management system and where customer validation remains required.
How large/medium/small GCs/subs could use this: Large contractors can add ISO 42001 evidence to enterprise vendor reviews; midsize GCs can require a model-change and incident log; small firms should keep AI output advisory until a manager verifies the source transaction.
Hashtags: #ConstructionAI #ConstructionERP #AIRisk #ISO42001
View Source#ConstructionAI#ConstructionERP#AIRisk#ISO42001
03General
AIA Contract Documents adds in-app AI guidance to a library supporting $100 billion in contract value
Story date: August 26, 2026
AIA Contract Documents launched an AI Assistant alongside an upgraded contract editor and appointed Arijit AJ Saha as chief technology officer. AIA says its standardized documents support more than $100 billion in construction contract value each year.
The assistant provides in-app guidance against a library of more than 300 standardized contract documents, while the editor is intended to move users from template selection to a signed agreement with less navigation. The capability is aimed at helping AEC teams understand and configure contract language inside the document workflow.
The announcement gives no measured reduction in disputes or negotiation time, so those outcomes remain company objectives rather than demonstrated project results. The operational change is a more searchable contract process for owners, designers, GCs, and subs, with legal review still needed for project-specific risk allocation.
Why it matters: Contract language is a construction control point: a faster answer is valuable only if it preserves the governing clause and does not blur the line between guidance and legal advice.
Practical AI use case or operational implication: A project manager can ask the assistant to locate the notice, payment, or change-order provision relevant to a live issue, then attach the cited clause to the internal review packet rather than pasting an uncited answer into correspondence.
Suggested executive takeaway: AIA Contract Documents should publish evaluation examples showing citation fidelity and escalation behavior on common construction contract questions before firms treat the assistant as a risk-control tool.
How large/medium/small GCs/subs could use this: Large GCs can connect contract guidance to legal-review queues; midsize firms can constrain use to AIA forms they already license; small subs can use it for clause discovery while sending interpretations to counsel or the prime contractor.
Hashtags: #ConstructionAI #Contracts #AEC #RiskManagement
View Source#ConstructionAI#Contracts#AEC#RiskManagement
04General
Sensera adds AI gate, license-plate, and material analysis to SiteCloud Insights
Story date: August 31, 2026
Sensera Systems expanded its SiteCloud Insights platform with jobsite monitoring features for contractors. The release covers gate monitoring, license-plate capture, and material analysis for active construction sites.
Gate monitoring records vehicles entering and leaving, identifies vehicle types and companies, and supports delivery verification. The material feature compares images over time to estimate changes in quantities, while license plates provide a repeatable vehicle identifier for site security and access review.
The product description does not provide accuracy, theft-loss, or inventory-variance measurements. It does, however, move camera data into construction logistics and security workflows where a superintendent or project administrator can investigate an exception instead of relying on occasional site walks.
Why it matters: This is a concrete example of construction AI expanding beyond progress photos: the same visual stream is being used to reconcile deliveries, access, and material movement, three areas that often sit in separate logs.
Practical AI use case or operational implication: A site logistics lead can compare a delivery vehicle's gate record with the day's material image and flag a mismatch for receiving review before the discrepancy becomes a pay application or schedule problem.
Suggested executive takeaway: Sensera should let contractors export the evidence chain from vehicle event to material exception so the AI alert can be audited during a claim, inventory review, or security investigation.
How large/medium/small GCs/subs could use this: Large GCs can integrate gate and inventory events with project controls; midsize contractors can start with one high-value laydown area; small subs can use image comparisons for material accountability on shared sites.
Hashtags: #ConstructionAI #Jobsite #SiteSecurity #ConstructionLogistics
View Source#ConstructionAI#Jobsite#SiteSecurity#ConstructionLogistics
05General
Lightcast defines 135 skilled-trade occupations as construction faces a data-and-labor bottleneck
Story date: September 06, 2026
Lightcast identified 135 occupations in a new standardized definition of the skilled trades, including construction roles. The report estimates roughly 20 million U.S. skilled-trade jobs, 2.1 million annual openings, and a workforce in which more than one-quarter of workers are at least 55 years old.
The construction relevance is tied to the data used for labor planning: regional demand, training completion, retirement exposure, and the trade mix required by infrastructure, manufacturing, and data-center investment. Lightcast says data-center growth added 315,000 skilled-trade workers over five years.
These are labor-market estimates, not a forecast of one contractor's staffing need or proof that AI will close the gap. For construction leaders, the practical implication is to connect AI deployment plans to apprenticeships, regional trade availability, and the specific competencies a project schedule assumes.
Why it matters: An AI rollout that ignores electricians, HVAC technicians, operators, and other scarce trades can create a digital plan with no executable workforce. Lightcast supplies a labor taxonomy that can make that risk visible before pursuit or mobilization.
Practical AI use case or operational implication: A workforce planner can compare the trade requirements in a data-center schedule with regional openings and training pipelines, then identify which packages need earlier recruiting or subcontractor engagement.
Suggested executive takeaway: Construction HR and operations leaders should convert the 135-occupation taxonomy into a project-level skills baseline and track where technology changes training demand rather than treating AI as a substitute for craft capacity.
How large/medium/small GCs/subs could use this: Large GCs can build regional skills forecasts into portfolio planning; midsize firms can use the taxonomy for two or three critical trades; small subs can pair a simple skills matrix with apprenticeship partners.
Hashtags: #ConstructionAI #SkilledTrades #Workforce #AEC
View Source#ConstructionAI#SkilledTrades#Workforce#AEC
06General
PlanRadar launches construction AI agents that draft RFI responses inside permissioned project data
Story date: September 05, 2026
PlanRadar introduced AI Agents for construction, real-estate, and facility-management projects. Users can create agents with natural-language prompts or select prebuilt options for recurring project tasks.
Its Response agent searches project documents, drafts an RFI response, and includes the relevant source, while activity is logged and attributed. PlanRadar says agents inherit the access permissions of their creator and can be tested before deployment, although the product description also says an agent can complete assigned actions without an approval step.
The company positions the feature as reducing initial RFI response time from hours to minutes, but that is a stated capability rather than a measured portfolio result. The operational implication is a choice between speed and control: firms need an explicit boundary for draft-only work versus actions that change the project record.
Why it matters: The permission and approval details matter more than the agent label. An RFI workflow can create contractual exposure if an automated action is mistaken for an authorized design or commercial response.
Practical AI use case or operational implication: A GC can permit the agent to retrieve the governing drawing and draft an answer, but route every response involving design intent, cost, or schedule relief to the responsible architect, engineer, or project manager.
Suggested executive takeaway: PlanRadar should expose configurable approval gates for high-consequence actions so construction teams can distinguish document retrieval from an externally binding project decision.
How large/medium/small GCs/subs could use this: Large GCs can create role-based agent policies; midsize firms can limit agents to draft and search functions; small subs can use the cited-document retrieval feature without granting write access to the prime's record.
Hashtags: #ConstructionAI #RFI #ProjectManagement #AgenticAI
View Source#ConstructionAI#RFI#ProjectManagement#AgenticAI