Claude for architects: reviewing DWG drawing packages

Give Claude a defined review job

Before a drawing issue, an architect may need to reconcile room names, equipment labels or notes across several sheets. Claude can help organize that comparison when the relevant information is supplied in a readable form. Choose one question with a clear completion condition: “List tags present on the plan but absent from the equipment schedule” is a stronger brief than “Find every problem.”

There are three distinct routes from DWG to an answer: review rendered sheets, analyze exported object data, or use configured tools that can query the CAD file. Ask which route was used. A response describing a drawing’s appearance does not establish that dimensions, blocks or references were read from CAD objects.

Anthropic’s upload guidance documents PDF and image analysis, with visual handling depending on the supported model and document conditions. Export the relevant sheets and check that known details are readable. Do not treat ordinary DWG attachment handling as an established native CAD reader.

Assemble a revision-controlled package

Keep the source DWG untouched and make a review copy. Include the references needed for the selected sheet, a PDF plot and a short manifest listing drawing numbers and revisions. For a long issue set, start with one floor rather than relying on a single request to cover the entire project.

Export structured data when the question needs exact labels or quantities. An equipment inventory might contain block handle, tag, type and layer. A room inventory might contain room number, name and source contour identifier. Keep the raw export alongside any cleaned table so a reviewer can trace a surprising value.

State model units, area units, coordinate basis and the intended drawing scope. A sheet showing a scale of 1:100 is not sufficient to interpret raw coordinates. If a reference is absent, list what its absence prevents you from checking.

Prompt: compare plan tags against a schedule

Compare the equipment tags on sheet M-201 revision B with equipment_B.csv. Review only the main floor shown on this sheet. Return separate lists for plan-only tags, schedule-only tags, duplicates and unreadable tags. For each item give the sheet zone or crop reference, exact visible text and matching source row where available. Do not infer a missing tag from a nearby symbol. Do not count an unreadable tag as absent. Finish with the input revisions and checks you could not complete.

Check a few known tags first, including a duplicate and one absent from the schedule. If the text is too small, provide a better export or crop and repeat the affected portion.

Ask for proposed actions separately from observations. “Tag unreadable” may need a drawing correction; “tag not in schedule” may need coordination with another discipline. Keeping them separate makes the register easier to assign and close.

Move to scripts when the task is repeatable

A generated CAD routine can be useful for extracting attributes or applying an approved layer mapping. Specify the CAD product, exact release, operating system and scripting environment. Request the complete selection logic and a read-only preview before any write operation.

For example, ask for a routine that lists blocks on two named layers with their handles and tag attributes. Review the code, then run it on a copy. Compare the returned block count with a manual CAD selection and inspect nested blocks or external references explicitly. Avoid a generic “all objects” selection when the job concerns only the host model.

If you later authorize changes, require an old/new log and a list of skipped objects with reasons. Reopen the saved drawing, measure a known distance and plot a comparison sheet. File creation alone does not prove that a routine changed the intended objects.

Connectors can extend access, but inspect the actual tools

Anthropic describes connectors as a way to give Claude access to external tools and data. A configured CAD integration may offer object queries or editing; its capabilities depend on the server and permissions. Check the installed connector’s tool list before requesting a DWG operation.

Before trusting one, ask it to name the open file, list its available drawing operations and return a known object’s properties. Keep initial access read-only. Product documentation search, file storage access and a live CAD connection are different services even when they appear in the same chat interface.

If you only have a PDF, establish whether it is vector-based or scanned. AutoCAD’s import documentation distinguishes imported vector objects from attached raster images. Converting a page is a separate geometry task requiring calibration and readback, not a consequence of Claude understanding the picture.

For PDF-to-DWG reconstruction in an ARAI environment with the reconstruction skill enabled, provide the source sheet, known dimensions, target units and acceptable deviation. Open the result in CAD and compare it with the PDF.

Check your drawing in ARAI

Attach the DWG, a matching PDF and the external references needed for the selected floor. Specify the floor or layers to inspect and the input units. Ask ARAI for a read-only inventory of drawing objects, layers and external references, with object identifiers for checking in CAD.

Inspect drawing objects in ARAI. Attach your files to the draft before sending. Check the inventory against a known CAD selection. See the Revit export guide.