AI for architects: briefs, room schedules and drawing evidence

Organize work by the evidence it needs

An architect's week includes client notes, room schedules, geometric checks and visual presentations. AI can assist across these tasks, but a persuasive result in one does not prove competence in another. A well-written room description cannot establish its area.

Choose one output and name the source it must follow. For text, that may be approved meeting minutes. For a schedule, it may be a model export with stable room IDs. For measurement, it is geometry with a stated boundary convention and units.

This division also helps set up a trial: choose a small task whose accepted output you can describe before starting.

Use ChatGPT and Claude with a known file route

ChatGPT and Claude offer document and image workflows. Their processing paths matter more than a generic claim that they “read PDFs.” OpenAI documents visual PDF retrieval, while Anthropic explains file handling in Claude. Check the current route and test the content needed for the task.

Use a known note, small dimension and schedule row as a reading trial. If a document's embedded image is not available to the chosen route, supply a suitable PDF or image crop. Retain the page number and revision so the extracted information stays traceable.

Ordinary chat, a script and a configured CAD connector are distinct workflows. A connector can expose model actions that an attachment does not. Ask which document is active and which objects were read; do not infer native drawing access from a fluent answer.

For ARAI work originating in Revit, export the relevant views to DWG and sheets to PDF, with a matching schedule if needed. Confirm the export's units and visible content. This is an export-based workflow, not a promise of native RVT support.

Make room schedules auditable

Preserve room identifiers exactly, including leading zeros and suffixes. Group by an agreed classification, not by names the model has silently rewritten. Two rooms called “Store” are not duplicates merely because their names match.

Record the area convention: which face defines the boundary, how openings or recesses are treated, and which rooms are excluded. Keep raw values for calculation and round at the agreed stage. A sum of rounded display values may differ from a rounded sum of raw areas.

Ask for source IDs beside totals and an explicit exception list. A useful schedule can show missing areas, repeated IDs, unclassified rooms and excluded rows without inventing replacements. See drawing quality control for closing issues against a frozen package.

Worked example: a revised room programme

Suppose revision D has twelve offices, two meeting rooms and a support-space group. The client wants totals by group and a list of changes from revision C. Some room names have changed, but their IDs remain stable.

Compare the supplied revision C and D room exports by room ID. Preserve names and units from each source. Return additions, removals, name changes and area differences. Sum revision D by the supplied group field, listing blank groups and excluded rows separately. Do not infer room use from its name or fill missing areas. Include the source row for every exception.

Review all additions and removals, then independently total one group. Check that the area delta reflects actual boundary changes rather than a new export filter. If a room was split, document the relationship between old and new IDs instead of forcing a one-to-one match.

The accepted result includes both the schedule and its source revision. When the plan changes again, the old reconciliation remains evidence for revision D only.

Write descriptions from accepted facts

Prepare a fact register before asking for a design narrative: building use, storeys, spaces, areas, materials and source locations. Ask the assistant to leave missing decisions open. “Technical room” should not become a named plant function because the model expects one.

Keep client requirements, architect proposals and confirmed decisions visibly separate. For code research, use the actual jurisdiction and applicable edition, with accessible passages and conditions. A general statement that accessibility or fire requirements are satisfied needs project evidence, not polished phrasing.

Visual concepts need a similar distinction. Compare proposals against the approved geometry, checking entrances, openings and circulation. Record which choices the client accepted, then carry those choices into drawings and specifications. The image itself is not the material schedule.

Start with a drawing question in ARAI

ARAI can inspect supported DWG/DXF files and prepare reviewable outputs. Prepare an architectural drawing task. Attach the current drawing, state your measurement rule and review the unsent draft. Accept the result by checking boundaries, exceptions and a control calculation.