June 12, 2026 · AEC workflow

Jobsite AI still needs a defined review lane

Construction AI is moving from demos into active project workflows. That is useful progress. It also makes the review boundary more important, because a tool sitting closer to the job can create cleaner drafts or faster mistakes.

The news

Suffolk announced its "Jobsite of the Future" initiative on June 9, describing AI engineers embedded with active project teams. The stated focus areas are design, schedule, and process, including participation in schedule updates, requisition reviews, submittal coordination, and shop drawing reviews. That is a high-confidence summary of Suffolk's announcement; the claimed productivity impact should be treated as vendor-reported until independently measured.

Kahua's June 11 Build Forward event points in the same direction: construction AI is being framed around practical use, project information, document workflows, security, trust, and governance. Primepoint's June 10 post makes the technical problem plain: construction review is not just reading one document. It is cross-referencing drawings, specifications, details, schedules, and field constraints.

The practical lesson

The signal is not "AI replaces project engineers." The signal is that AI belongs in the project workflow only when it has a defined lane. For submittals, that lane is comparing the submitted product data or shop drawing against the governing requirements and producing a draft exception list. For RFIs, it is locating the controlling source language and preparing a draft response. For project setup, it is organizing the source set so later work has a defensible basis.

The Reddit thread from r/ConstructionManagers is useful because it is less polished. A user shared Claude Code skills for PE tasks such as splitting specs, working with drawings, tabulating bids, comparing bids, and drafting contracts. The comments quickly turned to setup and liability. That is exactly where AEC firms need to spend time before rolling tools into real projects.

How this affects AECdesign.ai

AECdesign.ai should stay narrow by design. The remote MCP connection handles access, authentication, and tool discovery in Claude Desktop. The installed local runtime runs the review skills against the user's project materials. That hybrid setup is useful only if the firm also defines which project folders are in scope, which sources are frozen for citation, and who is allowed to run each review.

The live skills support that kind of lane: aec-project-setup, aec-data-room, aec-submittal-review, aec-rfi-response, and aec-get-review. They are review-support tools, not approval tools. A result can be a better-organized draft, a clearer citation trail, or a faster first pass. It is still a draft until the responsible reviewer accepts it.

What this means for AEC firms

Do not start with a broad instruction like "review the project." Start with one repeatable workflow, one source set, one reviewer, and one output format. If the tool cannot show what it used, who should review it, and what decision remains open, it is not ready for issued work. Practical AI in construction will be won by disciplined workflows, not by confident prose.

Sources

• Suffolk launches Jobsite of the Future - Informed Infrastructure (June 9, 2026; High confidence for announcement details, Medium for vendor-reported impact claims).
• Build Forward: AI in Construction - Kahua (June 11, 2026; High confidence for event topics and framing).
• ChatGPT Wasn't Built for Blueprints - Primepoint (June 10, 2026; Medium confidence as vendor analysis, useful for workflow framing).
• I made a few Claude Code skills for PE tasks - r/ConstructionManagers (observed June 12, 2026 as 5 days old; Low confidence as anecdotal practitioner discussion).

Draft, not determination. Every substantive AECdesign.ai result is a draft. A licensed engineer of record must review, revise, accept, or reject each finding before it is issued. AECdesign.ai never provides a sealed determination.