June 14, 2026 · Source control

Document control is the first AI review control

AI review does not start with the model. It starts with the project record: which files are current, which sources are frozen for review, and who is allowed to issue a decision from the draft.

The news

Recent construction AI coverage keeps coming back to the same operational point. Palcode's June 11 document-control guide separates document storage from document control: storage is where files live; control is who approved them, which version is current, who can see them, and what the record shows when something goes wrong. That is a high-confidence summary of the article's position.

USAII's June 9 construction AI article makes a related point from the project-system side: AI is more useful when it can work near drawings, specifications, RFIs, submittals, schedules, cost information, and project communications instead of forcing teams to export and re-upload material. Nomic's June 2026 built-world roundup describes the broader AEC market moving toward grounded workflows: agents for submittal review, RFI cleanup, daily logs, and contract review, plus a clear governance concern around delegated design decisions.

The practical lesson

The lesson for firms is not "buy AI first." It is "control the record first." A model cannot know that a drawing was superseded if the folder does not make that clear. It cannot respect a deferred submittal requirement if the source set is incomplete. It cannot produce a defensible draft if the reviewer cannot tell which spec section, drawing revision, or RFI response it used.

The Reddit discussion around Claude skills for project-engineer tasks is useful for the same reason. Practitioners are trying to automate spec splitting, drawing work, bid tabulation, and drafting. Those are reasonable support tasks, but the comments keep circling back to setup, trust, and liability. That is the right concern. Workflow discipline has to come before speed.

How this affects AECdesign.ai

AECdesign.ai's hybrid architecture should be used with that discipline. 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. The firm still needs to decide which folder is in scope, which documents are current, which sources are frozen, and who reviews the draft.

The live skills map to that sequence. aec-project-setup organizes project context. aec-data-room supports source organization. aec-submittal-review and aec-rfi-response prepare draft findings or responses. aec-get-review retrieves prior review output for follow-up. None of those tools turns a draft into an issued determination.

What this means for AEC firms

Before running a review, name the source set. Freeze the applicable files. Record the revision status. Assign a reviewer. Then treat AI output as a working draft that must be checked against the source. If the tool cannot show what it used, the firm should not rely on what it concluded. In AEC review, document control is not admin overhead. It is the first quality-control step.

Sources

• Best Practices for Document Control in Construction Projects - Palcode.ai (June 11, 2026; High confidence for document-control framing, Medium for vendor-specific claims).
• AI Transformation in Construction: Helping Project Teams Put More Work in Place - USAII (June 9, 2026; High confidence for stated project-system examples).
• AI in the Built World - Nomic June 2026 (covers Apr. 21-Jun. 5, 2026; Medium confidence as curated industry synthesis).
• I made a few Claude Code skills for PE tasks - r/ConstructionManagers (observed June 14, 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.