A good prompt for an architecture practice or engineering firm has five parts: the role the AI should take, the context of the task, an example of the result you want (a real document from the practice, with personal data removed), clear rules (the most important: don’t make anything up, and mark anything missing as [OUTSTANDING]) and the output format. With those five pieces, any business AI assistant produces useful drafts; without them, it produces generic text you have to redo.

Here are fifteen prompts ready to copy, grouped by task: site documentation, design and specifications, regulations and authority comments, tenders, quantities and communication. Copy them, adapt them to your practice and save them so the whole team uses the same ones.

Before you start: three rules

  1. Use a business account and don’t upload personal data that isn’t needed. If in doubt, see our guide on ChatGPT and data protection.
  2. Always give an example. Paste a real, anonymised document from the practice below the prompt. It’s what improves the result most.
  3. Check everything it produces. AI drafts; the professional checks and signs. Measurements, dates and regulatory references, one by one.

Site documentation

1. Site visit report from notes

You write the site visit reports for our practice. Using the notes, voice transcript and photos I give you, write the report following exactly the structure and tone of the example report. Don’t make up any data: if something needed is missing, write [OUTSTANDING]. Copy measurements, references and names exactly. Separate progress, issues, instructions (each with owner and deadline) and next steps. At the end, list your questions about the notes.

We explain the full method in site visit reports with AI.

2. Progress summary for the client

Using the site visit reports I give you, write a one-page summary for the client on the state of the works: progress, open issues, pending decisions that depend on them and upcoming milestones. Clear language, no unnecessary jargon. Don’t add anything that isn’t in the reports. Next to each point, note which report it comes from.

3. Close-out checklist

I’m giving you our practice’s index for the final project file and the list of files we have in this project’s folder. Compare them and return a table with three columns: required document, present or missing, and notes. Don’t assume a document exists if it isn’t on the list.

More on close-out in completion certificates and handover files.

Design and specifications

4. Adapting a previous specification to a new project

I’m giving you the design statement from one of the practice’s previous projects and the data for the new project. Write the statement for the new project with the same structure and style. Use only the data I give you; where the previous statement has a fact that doesn’t apply to the new project and you don’t have it, write [OUTSTANDING]. At the end, list the sections you had to leave incomplete.

5. Checking a specification for consistency

Check this specification against the project data table I’m giving you (areas, heights, materials, number of units). In a table, flag every figure in the specification that doesn’t match the data table, quoting the exact sentence and the correct value. Don’t correct the text; only flag.

6. Finishes schedule for the client

Using this technical finishes specification, write a version for the buyer or client: same content, clear language, organised room by room, with no brands or references that aren’t in the original. Don’t exaggerate or add sales language. How to use these three prompts without carrying errors from one project to the next: specifications and design statements with AI.

Regulations and authority comments

7. Splitting authority comments into points

I’m giving you comments from the planning authority on a project. Split them into numbered items. For each, give in a table: the exact wording, the regulation or clause it cites (if any), and whether it looks documentary, a matter of justification, or a design change. Don’t interpret what the text doesn’t say.

8. Draft response to authority comments

Using the table of items and the answers I give you for each point, write the response in the format of the example response. Each point must say where it’s resolved in the project (document and page) according to what I tell you. If I haven’t given an answer for a point, write [OUTSTANDING].

9. Checklist from a regulation clause

I’m giving you the exact text of a regulation clause. Turn it into a checklist for reviewing a project: one line per requirement, with the exact clause reference. Use only the text I give you, not your memory of the regulation. If something is ambiguous, mark it “for the professional to interpret”.

Always paste the official text of the regulation: AI models quote from memory and sometimes mix versions. And the checklist helps you review; it doesn’t decide whether the project complies.

Tenders and competitions

10. One-page tender summary

Using these tender documents, prepare a one-page summary: scope, budget, submission deadline, contract period, award criteria with their weighting, required experience, guarantees, penalties and documents to submit. Give the page each fact comes from. If something isn’t stated, write “not stated”.

11. Required documents matrix

From these tender documents, make a table of every document to be submitted, ordered by envelope or file, with the required form (signed, original, self-declaration…) and the page where it’s requested. Don’t leave out any document, even if it seems obvious.

Quantities and costs

12. Checking a quantities spreadsheet

Check this quantities spreadsheet and flag in a table: items whose units don’t fit their description, items that look duplicated, quantities far out of line with the rest, and items with no code. Don’t change any value; only flag and explain why.

13. Explaining budget versus actual cost

I’m giving you the contract budget and the actual cost by work package. Calculate each package’s variance in euros and as a percentage, sort them from largest to smallest and write a short paragraph for management on the three most important. Show the calculations so I can check them.

Communication

14. A clear reply to a client

A client is asking what I paste below. Write a short, friendly, clear reply that explains the technical issue without jargon and says what we’ll do and when. Use the tone of the example email. Don’t promise deadlines or costs I haven’t given you.

15. Minutes of a project meeting

Using the transcript of this meeting, write minutes with: attendees, topics discussed, decisions, and a table of actions with owner and deadline. If a decision has no clear owner or deadline, mark it [OUTSTANDING]. Don’t include opinions that didn’t lead to a decision unless I ask.

Getting the most out of them

  • Save them as fixed instructions in your assistant (projects, GPTs, Gems or agents, depending on the tool), with the example document included.
  • Test them on three real cases before using them daily, and adjust the prompt where it fails.
  • Use the same ones across the team. Results then look alike and are quicker to check.
  • Measure time before and after on the tasks that repeat most.

If a task repeats every week, the next step is to automate it so nobody has to copy and paste. We explain how in how to use AI in an architecture practice.

What not to ask it

  • To decide whether a project complies with regulations. It can help you review; the decision is yours.
  • Structural or building services calculations. There’s dedicated, verifiable software for that.
  • Measurements read off a drawing. Models still misread many drawings; take measurements from the source.
  • To sign or certify anything.

Frequently asked questions

Which tool works best with these prompts?

They work with any current business assistant: ChatGPT, Claude, Gemini or Copilot. The example and the rules make more difference than the tool.

Why so much [OUTSTANDING]?

Because it forces the AI to show what it doesn’t know instead of filling it in with something that sounds right. It’s the rule that prevents the most mistakes.

Can I upload drawings as PDFs?

Yes, for text tasks such as finding which document deals with a point. Don’t rely on measurements or areas the AI reads from a drawing: always check them against the source.

Should I write the prompts in English?

Preferably in the language of the document you want. If the result must be in another language, say so explicitly in the prompt.