Uploading client drawings to AI: a practical approval workflow

Decide the task before choosing the upload

A drawing can contain much more than the geometry you want checked: client names, site coordinates, room uses, access arrangements, consultant details and linked references. Start by defining the deliverable. Measuring one courtyard does not normally require the full project archive.

Then confirm that the proposed processing is permitted under the client's agreement and your organization's rules. The relevant question is whether this project information may be shared with this service in this configuration. The absence of the words “artificial intelligence” from a contract does not answer that question.

Record the approved service, account or workspace, permitted information and task owner. If the job requires a particular region, retention arrangement or processor, verify that arrangement before uploading. A convenient alternative service is not automatically an approved substitute.

Read the terms for the actual service

Consumer accounts, organizational workspaces and APIs can have different processing arrangements. Check the product you will actually use, the current contract and your administrator's settings. Avoid copying an assurance from a vendor's API page into a policy for a personal chat account.

OpenAI's enterprise privacy page explains its business-data commitments. Anthropic's Privacy Center provides product-specific data-use guidance. These are starting points for checking the selected service, not evidence that a client's drawing is authorized for transfer.

Keep several questions separate: use for model training, retention, human access, subprocessors, geographic processing and deletion. A statement about one does not settle the others. Where the project's terms require a specific answer, record the actual contractual or administrative evidence rather than an assistant's interpretation.

Prepare a minimum useful package

Work on a copy and preserve the source issue unchanged. Remove information that is unnecessary for the task, then inspect the result. Hiding a layer or drawing a rectangle over text is not proof that the underlying information has been removed.

For a DWG, consider external references, block attributes, layouts, embedded objects and file properties. For a PDF, inspect annotations, attachments and searchable text as well as the visible page. If you change coordinates or remove identifiers, record what changed so the result cannot later be mistaken for a project-ready source.

Cropping can remove information essential to interpretation. Keep the legend, dimensions and adjacent objects needed to understand the question. If extracting a DWG would break referenced geometry, use an approved self-contained copy and check it opens correctly.

A prompt that limits the work

Inspect this approved drawing extract for the stated task only: compare room identifiers with the attached schedule. Preserve identifiers exactly. Report missing, duplicate and ambiguous matches with sheet and row references. Do not infer the project location or seek additional project files. List unreadable material and any extra information needed before continuing.

This instruction helps bound the engineering task. It does not replace access controls or change the service's processing terms. Use technical and organizational controls for those requirements.

Check the output before sharing it onward. A report can reproduce sensitive labels or coordinates even when the original attachment is no longer visible. Treat derived tables, previews and measurement files according to the same project rules.

Make the decision repeatable

A bureau's upload record can be short: task, approved service configuration, authorized owner, source revision, information removed, retained dependencies and output destination. Add the date of the terms check and a trigger for reviewing it, such as a service change or new client restriction.

For ongoing use, test the process with a non-sensitive sample first. Confirm that a recipient can trace each result back to the supplied source and that the limited package still supports the task. Time spent preparing and reviewing the extract belongs in the assessment of whether the workflow is worthwhile.

ARAI accepts drawing-based tasks using DWG/DXF, but uploading to ARAI still requires the same project-specific permission check. Once that is settled, prepare a bounded drawing request. The draft stays editable; attach only the package you have authorized.