AI readiness assessment for architecture practices and design studios

Walk through a design studio and count the screens. On one, a concept render. On another, a council's request for further information. On a third, a half-written specification. At least one of those probably has an AI tool involved, and whether that tool was chosen by the practice or found by an enthusiastic designer is rarely written down anywhere. That is a reasonable thing to want to know, and an easy one to find out.

This AI readiness assessment for architecture practices is a short survey that everyone in the studio completes on their phone in about eight minutes, from directors to the newest graduate and the person running the office. The owner receives one branded report with six scored areas, a register of the tools actually used, and a plain 30/60/90 day roadmap. Individual answers are never shown. You receive a plain-language report that you can read in an afternoon.

Where AI shows up in architecture and design practices

Concept imagery and client presentations

Image generators produce moodboards and concept visuals quickly. Worth finding out who uses them, what prompts and reference images they upload, whether client sites or unreleased designs are included, and whether clients know that generated imagery appears in presentations. These choices are small and creative, which is why they often escape any formal tool review.

Planning submissions and council responses

Statements of environmental effects, design reports and responses to council requests are text-heavy and repetitive. Ask who drafts these with AI, whether planning controls and clause references are checked by a person, and what site or client detail goes into the tool. Council correspondence has deadlines, so drafting help is attractive. That is the moment checking matters most.

Specifications, schedules and product research

Specification writing, finishes schedules and product comparisons involve long documents and supplier information. Find out whether AI is used to draft clauses or summarise manufacturer data, and how the architect confirms that claims about products and compliance are accurate. Product claims change, and a confident summary of a data sheet can still be out of date or incomplete.

Models, drawings and software features

Modelling, rendering and drawing software increasingly includes AI features, sometimes switched on by default. Ask which are active, whether project files are sent to the vendor's cloud, and whether anyone has read the terms on who may use uploaded designs. Defaults change with each software update, so a setting chosen once may not stay the same.

What puts architecture and design practices at risk

Ownership of designs and generated content

Practices treat their designs as intellectual property, and clients often hold rights under the appointment. Uploading drawings or concepts to external tools raises questions about who may use them next. Generated imagery raises its own questions about copyright and similarity to other work. Appointment terms differ between clients, so it is worth knowing what is going into tools before reading the contract again.

Client confidentiality and site information

Briefs, budgets, site details and unreleased developments are commercially sensitive, and some clients are public bodies or private developers with strict terms. Staff using personal AI accounts with that material is the point to check, early. A single leaked concept can matter a great deal to a developer, and the survey tells you how likely that is to be a live issue.

Professional responsibility and insurance

Registered architects remain responsible for documentation issued under their name. A specification clause or code reference produced by a tool still has to be right. Professional indemnity insurers and clients may ask how practices manage technology risk, and a documented answer helps. The report gives you an honest description of current practice, which is a better base for that conversation than a general assurance.