By task
AI for drawings: choose a task you can verify
The useful question is what the assistant will return: a transcription, an issue list, a measured table or a new drawing file. Each needs a different check.
Contents · 7
Four jobs hidden inside “AI for drawings”
A project architect receives a revised floor plan and wants help before coordination. Reading the sheet, checking it, editing it and reconstructing it from an image are four separate jobs. A tool that explains a plan has not necessarily measured its objects or changed a drawing.
Define the deliverable in a sentence: “List missing door references on these five sheets” is testable; “check the design” is not. Include the input revision, scope, expected output and reviewer. This makes it possible to judge whether the work saves time after verification, rather than simply producing a fluent answer.
Match the input to the operation
A screenshot carries visible marks. A PDF may contain selectable text, vector paths, raster images or a mixture. A DWG contains objects, properties and references that a picture does not expose. Confirm which representation the assistant actually used.
Autodesk’s PDF import options distinguish vector geometry, text and raster images. Importing a sheet is therefore not the same as recovering the original CAD structure. Choose the original drawing when the task depends on object identity or measurement.
| Task | Useful input | Expected output |
|---|---|---|
| Read notes | Legible PDF or crops | Transcription with page locations |
| Reconcile schedules | Tables with stable IDs | Matched, missing and conflicting rows |
| Measure geometry | Supported CAD file | Values, units and selected objects |
| Make a bounded edit | Drawing plus explicit instruction | New file and change evidence |
For image reading, ask a few known questions before assigning a large extraction: identify a small dimension, a room tag and a reference bubble. This checks whether the chosen input is usable for the actual job.
Distinguish chat, scripts and configured CAD access
An ordinary chat works with the representations it receives. An exported table exposes selected fields; a checked script can perform a defined calculation; a configured CAD connector may query or change objects in its connected environment. Ask which route ran, which document it used and which operations it completed. A file attachment or a product name alone does not establish object access.
Autodesk documents a Revit public MCP server as a technology preview. That is a product-specific capability, not evidence that every assistant reads native models. For ARAI work originating in Revit, export the relevant DWG views and PDF sheets, preserving units and revision context.
For PDF-to-DWG work, ARAI has a reconstruction skill subject to an installed-capability check. Define output geometry and acceptance separately from reading the page. A reconstructed drawing needs calibration, overlays and independent dimensional checks.
Start with document consistency
A practical first trial is a reference check. Give the assistant a frozen sheet index and the sheets it covers. Ask it to list references that have no destination, duplicated sheet numbers and mismatched revisions. Keep a distinction between an absent detail and a detail it could not read.
The output should include issue ID, source sheet, location, observed text, expected reference and status. Add an owner only when the project team has assigned one. A model should not silently decide which consultant is responsible.
Do not call this a complete technical review. It checks consistency within the supplied set. A missing discipline package, unresolved authority requirement or incorrect design assumption may be invisible in those files.
Worked example: check a room schedule
Suppose revision C contains 18 room tags and a schedule with 17 rows. The task is to locate the mismatch, not to invent the missing room’s use or area. Include the measurement convention if areas are part of the comparison: internal finish face, structural face and other conventions can produce different valid figures.
Compare the room tags on A-101 revision C with schedule S-01 revision C. Match by room ID, preserving leading zeros. Return missing IDs, duplicate IDs and name conflicts, with sheet locations. Keep unreadable tags separate. Do not calculate areas from the PDF or fill missing rows by inference.
The reviewer checks all exceptions, then confirms the total number of matched unique IDs. If the assistant reports 17 matches and no issues, ask how it accounted for the eighteenth tag. Totals and exclusions are useful independent controls.
After correcting the schedule, repeat the reconciliation against the revised files and close each issue with evidence. A corrected spreadsheet alongside an unchanged drawing is an unresolved coordination problem.
Treat edits as a new deliverable
For a CAD edit, specify allowed layers and objects, what must remain fixed and how the output will be checked. Preserve the source. Require a new drawing, a change list and a preview where appropriate. Open the result in the receiving CAD workflow and verify that dimensions, text and references still behave as expected.
For revision review, use a native comparison tool when available and explain its coverage. A visible difference is a lead to investigate; a blank comparison is meaningful only within the tool’s documented scope. See AI and DWG for object-level checks.
Try one bounded task in ARAI
ARAI can inspect supported DWG/DXF drawings and perform engineering tasks with saved outputs. A useful first request is a geometry inventory, specified distance or bounded area check. Ask for units, selection evidence and unresolved objects so you can accept the result.
Prepare a drawing task in ARAI. Attach the current file and define one check before sending. For regulatory questions, identify the actual jurisdiction and source edition separately; an English interface does not establish local code coverage.
Ask ARAI about your project
Prepared by ARAI’s editors with AI assistance. Product information was checked against official sources as of the update date. Report an error at hello@arai.build.