June 13, 2026 · AEC workflow

Construction AI should support the reviewer, not replace the reviewer

The useful pattern in construction AI is becoming clearer: let tools handle document-heavy support work, but keep scope, interpretation, and issued decisions with qualified people.

The news

A June 2026 Russ Hadick construction recruiting article makes a practical point: AI is showing up in project management because teams are buried in RFIs, submittals, daily reports, change orders, safety documentation, and coordination messages. The article lists drafting, summarizing, reviewing spec sections, organizing submittal information, and preparing first drafts as reasonable support tasks. It also states the limit directly: every output still needs review by someone who understands the project.

That matches the June 11 Kahua Build Forward framing around AI in construction: practical workflows, trust, security, governance, and project data. Suffolk's June 9 Jobsite of the Future announcement is another signal that AI is moving closer to active project teams. The direction is real. The risk is treating proximity to the work as authority over the work.

The practical lesson

Construction does not have a shortage of text. It has a shortage of cleanly bounded review time. A tool can summarize meeting notes, draft a clean RFI response, extract a submittal requirement, or organize a source set. None of that means the tool understands the commercial consequences, design intent, code context, field condition, or professional duty behind the decision.

The current Reddit discussion around Claude Code skills for PE tasks shows the same split in the field. The original post describes useful automation for splitting specs, handling drawings, tabulating bids, and drafting contracts. The practitioner value is real, but the conversation also exposes setup, trust, and liability questions. That is where firms need process, not slogans.

How this affects AECdesign.ai

AECdesign.ai should stay on the support side of that line. 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 means setup is not a formality. The firm still needs to define allowed users, project folders, source status, and review responsibility.

The live skills fit bounded support work: aec-project-setup, aec-data-room, aec-submittal-review, aec-rfi-response, and aec-get-review. They can prepare a better draft and a clearer citation path. They cannot approve a substitution, resolve a design conflict, or issue a sealed determination. Those remain human responsibilities.

What this means for AEC firms

Use AI where the workflow has a clear input, a defined source set, and a named reviewer. Avoid open-ended prompts that ask the model to "review everything." The better test is simple: can the reviewer see what the tool used, what it concluded, what it did not decide, and what still needs professional judgment? If not, the workflow is not ready for issued work.

Sources

• AI in Construction Project Management: Useful Tool or Overhyped Distraction? - Russ Hadick & Associates (June 2026; High confidence for stated support-not-substitution framing).
• Build Forward: AI in Construction - Kahua (June 11, 2026; High confidence for event topics and governance framing).
• Suffolk launches Jobsite of the Future - Informed Infrastructure (June 9, 2026; High confidence for announcement details, Medium for vendor-reported impact claims).
• I made a few Claude Code skills for PE tasks - r/ConstructionManagers (observed June 13, 2026; 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.