AI for architects is most useful far from the drawing board: in the brief, the fee proposal, the planning statement, the client update, the specification clause and the tender response. Those documents eat the hours that are not design and are not billable at design rates. An assistant that drafts them from your facts, in your register, gives a small practice back a working day a week. It does not design buildings, it does not check codes for you, and anything it writes about structure, fire or accessibility is a draft for a qualified person to verify.
This guide is for practising architects and small studios. It covers the tasks where an assistant pays off, the prompts that work, what to keep out of it, and how the five modes in Ask Mio map onto an architect’s week.
Where AI for architects actually saves time
A quick inventory of a typical week in a small practice shows where the text is:
- responding to enquiries and turning a conversation into a written brief;
- writing fee proposals and scope descriptions;
- drafting design and access statements, planning cover letters and heritage statements;
- weekly client updates and meeting minutes;
- specification clauses and schedules;
- tender and competition submissions, including practice bios and project descriptions;
- reading long documents: planning policy, consultants’ reports, contracts, product data sheets;
- quick visuals for early concept conversations, before any CAD work.
Every item on that list is either writing, summarising or research, which is exactly what a general assistant does well. The design itself stays with you and your tools.
From enquiry to brief
A new client arrives with a wish list and a budget that do not match. The first useful document is a structured brief that makes the gap visible. Paste your meeting notes and ask:
Turn these notes into a written brief with sections: client objectives, site facts, spatial requirements (list, with areas where given), constraints, budget and programme, open questions. Use only what is in the notes. Where the notes are unclear, put a question in the open questions section rather than guessing.
The “open questions” instruction matters: it stops the assistant filling gaps with plausible assumptions and gives you the agenda for the next meeting. Keep the brief in a project in Ask Mio with the site photos and any survey, and every later document for that job starts with the same context. Our guide to projects and memory covers the setup.
Fee proposals and scope
Fee proposals are repetitive in structure and specific in content, which is the ideal case for an assistant. Give it your standard stage descriptions, the scope for this job, exclusions and the fee basis, and ask for a proposal in your house format. Then ask it to list every assumption it had to make; those become the clarifications section.
What not to let it do: set the fee. The percentage, the hourly rate and the stage split are your commercial decisions. The assistant formats and explains them. If you work under a national fee framework or standard appointment documents, paste the relevant clause names so the proposal uses the right terms.
Planning and statutory documents
Design and access statements, planning statements and heritage statements follow a known structure and must respond to specific policies. The workflow that works:
- Upload the local plan chapter or policy document in Research mode and ask for a list of the policies that apply to this type of proposal, with the policy number and a one-line summary of each.
- Paste your design description and ask the assistant to draft the statement section by section, responding to each policy by number.
- Ask it to flag any policy it could not address from the information given.
Then verify every policy reference against the source. Assistants can misnumber or paraphrase a policy, and a planning officer notices. If you want the method for keeping citations honest, read how to research with AI and get cited sources.
The same approach works for pre-application letters and for responding to officer comments: paste the comment, paste your proposed change, ask for a courteous, specific reply.
Client updates and minutes
Clients remember how informed they felt more than most details of the building. A short weekly update that says what happened, what is next and what is needed from them is cheap to produce with an assistant and valuable to receive. Give it your notes and a fixed format: progress, decisions needed, next milestones, risks. Keep the tone plain. For meeting minutes, paste the notes or the transcript and ask for decisions and actions with an owner and a date each; our guide to AI meeting notes has prompts that work.
Specifications and schedules
An assistant will not know your preferred products, and it should not choose them. What it does well:
- rewrite a clause from one specification format to another;
- produce a consistent door, window or finishes schedule from a messy list;
- check a draft for contradictions (“clause 3.2 says 50 mm, the schedule says 40 mm”);
- explain a manufacturer’s data sheet in plain words and extract the figures you need into a table.
Performance requirements, fire ratings and standards references must be verified against the current standard and the manufacturer’s current document. Treat the assistant as a careful junior who formats and spots inconsistencies, not as the person who signs the specification.
Early concept visuals
Design mode generates images from a sentence. For architects the useful cases are narrow but real: mood images for a first client conversation, material and atmosphere studies, a quick illustration for a competition board, a diagrammatic site sketch. The limits are equally real. Generated images do not respect your site, your brief or any dimension; they are evocative, not accurate; and clients can mistake a pretty render for a design. Label them as mood images, never present them as the scheme, and keep them out of planning submissions. The prompting craft is in how to write AI image prompts that work. For diagrams you can edit, an assistant can also produce simple flowcharts and process diagrams as SVG, which suits programme and process illustrations better than a rendered image.
Tenders, competitions and practice profiles
Submissions reuse the same material: practice description, team bios, project descriptions, method statements. Keep the approved versions in a project and ask for each submission’s variant from them: “Adapt our practice description to 300 words for a school competition, leading with education projects.” For quality questions in a tender, the assistant drafts from your actual procedures; it must not invent certifications, insurance levels or past projects. Read every submission against the facts before it goes out. The AI for construction companies guide covers the contractor side of the same documents and is useful if you also work in design-and-build.
Reading long documents
Consultants’ reports, party wall documents, lease clauses, planning conditions and product certificates all arrive as long PDFs. Upload them and ask specific questions: “List every planning condition that must be discharged before commencement, with its number.” “What does the structural report say about the existing foundations?” “Summarise the fire strategy’s assumptions about the stair.” You get an index to the document, not a replacement for reading the parts that matter. For contracts, a plain-language summary helps you prepare questions for your lawyer; see AI contract check for what that can and cannot tell you.
What stays off limits
Some things an assistant should never do in an architectural practice, not because it is bad at them but because responsibility cannot be delegated:
| Task | Use an assistant? | Why |
|---|---|---|
| Briefs, proposals, updates, statements | Yes, from your facts | Text tasks with a human reviewer |
| Summarising reports and policies | Yes, then verify references | Fast index to long documents |
| Mood images for early conversations | Yes, labelled as such | Evocative, not accurate |
| Structural, fire or accessibility compliance | Draft only; qualified person verifies | Professional and legal responsibility |
| Dimensions, areas, quantities for construction | No, except checking your own arithmetic | Errors propagate into cost and safety |
| Choosing products and specifications | No; formatting and consistency checks only | Performance must be verified at source |
| Client personal data and unreleased site details | Only within your policy and contracts | Confidentiality and GDPR |
Professional bodies increasingly publish guidance on AI use; the Architects’ Council of Europe represents the profession at EU level and is a good starting point for the European context, and the EU’s own data protection pages set out the rules that apply to client data.
A practical setup for a small studio
- Create one project per job with the brief, the site facts and the client’s preferred tone.
- Create one “practice” project with approved bios, project descriptions, standard clauses and your house style.
- Agree a short internal rule: nothing from an assistant leaves the office without a named person reading it; no client personal data or unreleased site information goes in without checking the appointment terms.
- Start with updates and minutes for a month, then add proposals and statements.
On cost: a normal reply costs 1 point in Ask Mio, a long document draft 3, an image 20. The Chat plan at €5 a month plus VAT adds Research mode with web search, file uploads and memory; the Business plan at €29 gives a studio of up to five people 15,000 points, shared projects and API access. Ask Mio runs on our own servers and does not use your chats or files to train models. The live pricing page has the current figures.
Frequently Asked Questions
Can AI design a building?
No. An assistant can write, summarise, research and generate mood images, and specialised design software is advancing separately, but a general assistant does not produce a design that responds to a site, a brief, regulations and a budget. Use it for the documents around the design and keep the design with your own tools and judgement.
Is it safe to upload client documents and drawings?
Check your appointment terms and any confidentiality clauses first. Remove personal data that is not needed for the task. Choose a service whose data handling you can account for: Ask Mio stores chats and files on our own servers, does not train on them and lets you delete them at any time. Unreleased commercially sensitive site information deserves the same care as any other confidential material.
Can an assistant check building regulations for me?
It can summarise a regulation document you upload and point you to the relevant section, which speeds up reading. It cannot take responsibility for compliance, it can misread or paraphrase a clause, and it may not have the current edition. A qualified person verifies against the current text before anything is submitted or built.
Are AI-generated images acceptable in planning submissions?
Generally they should not be used as representations of the scheme, because they do not reflect your actual design, site or dimensions and can mislead officers and the public. Use them only for early mood conversations, label them clearly, and use verified drawings and renders of the real proposal in any formal submission.
Which tasks should a small practice start with?
Weekly client updates and meeting minutes: low risk, immediately useful, and they teach the team how to prompt with facts. Then fee proposals and planning statements, which reuse known structures. Leave specifications and anything involving compliance until the reviewing habit is firmly in place.
Which Ask Mio plan suits an architecture studio?
A sole practitioner can start on the free plan for text and move to the Chat plan for document uploads and Research mode. A studio of two to five people fits the Business plan, which includes all modes, shared projects for each job and a pooled allowance of 15,000 points a month. Prices are in EUR plus VAT, and the pricing page lists the details.
The Bottom Line
AI for architects is about the documents, not the design: briefs, proposals, planning statements, client updates, specifications checks, tender text and reading long reports. Give the assistant your facts, keep every project in its own context, verify every reference and let a qualified person sign anything that touches compliance. The time saved is real and it comes out of the unbillable hours. Start with updates and minutes on the free plan, and compare the Ask Mio plans when the studio wants uploads, research and shared projects.
