AI for AEC
Three technical-office tasks AI can draft today, and what to check
AI tools can write a clean paragraph in seconds. For a technical office, the useful question is narrower: which recurring tasks produce a draft that an engineer can check faster than they could write it? This article picks three, shows a safe way to run each, and lists what must still be checked by a person.
The rule behind all three is simple. The tool drafts; the engineer is responsible. Generative systems sometimes present false content with confidence. The US National Institute of Standards and Technology (NIST) names this "confabulation" in its Generative AI Profile and describes it as the production of confidently stated but erroneous or false content.[1] It notes that the risk is greater when users believe the content because of its confident tone, and that confabulations can include invented logic or citations.[1] In engineering terms, a plausible clause number that does not exist is the typical failure.
Task 1: Meeting minutes and action registers
What AI can draft. Give it your own notes or a transcript of a coordination or progress meeting. Ask for a structured output: decisions, actions with owner and due date, open questions, and items deferred. The first draft saves the half hour of tidying that follows most meetings.
How to run it safely.
- Use your notes or a recording that participants know about, and check company policy on recording.
- Ask for a fixed table format so every meeting looks the same.
- Tell the tool to leave a field blank where the source does not say, instead of guessing.
What the engineer must check.
| Check | Why |
|---|---|
| Every action has the right owner | Tools may assign an action to the person who spoke last. |
| Dates match what was said | A "by next Thursday" must be turned into a calendar date by a person who knows the meeting date. |
| Decisions are decisions | Discussion can be summarised as agreement when it was not. |
| Numbers, drawing numbers and clause numbers are as spoken | Transcription errors are common with figures and codes. |
| Nothing commercially sensitive is in the circulated version | Remove instructions or admissions that should not be in the minutes. |
Review the draft within a day, while attendees remember the meeting. Circulate it as a normal minute under your name.
Task 2: First-draft correspondence and RFIs
What AI can draft. A request for information, a transmittal cover note, a reply to a clarification or a letter that records facts. Give it the facts: the drawing numbers, the issue, the dates, the contract reference you want cited, and the tone. Ask it to write a short, neutral draft.
How to run it safely.
- Provide the facts and the clause numbers yourself. Do not ask the tool to find the clause.
- Ask for a draft in plain English, with the subject, background, the question and the response date in separate lines.
- For Arabic letters, ask for formal Modern Standard Arabic, then have a native reader check the result.
What the engineer must check.
- Every fact and reference. Drawing numbers, revisions, dates and clause numbers come from your file, not the tool.
- Contractual effect. A letter may be a notice with time consequences, or it may waive a position. If a letter could affect a claim, have the contract manager read it. For time-limited notices, see our article on FIDIC 2017 Sub-Clause 20.2.
- Tone. Check that it neither concedes nor accuses more than you intend.
- Who it is addressed to. Confirm the recipient and the copy list.
Task 3: Specification-to-checklist and submittal register
What AI can draft. A specification section is dense. Ask the tool to extract each requirement into a table: requirement, source clause, submittal needed, test or inspection, and who verifies. The same extraction can start a submittal register, a material approval checklist or an inspection and test plan outline.
How to run it safely.
- Provide the specification text itself. Do not ask the tool to describe what a standard requires from memory.
- Ask for the clause number or heading next to every requirement, so each line can be traced.
- Process one section at a time. Long, mixed inputs make omissions more likely.
- Ask the tool to list requirements it was unsure about, and review that list first.
What the engineer must check.
| Check | Why |
|---|---|
| Completeness | Compare the table against the section. Missing a clause is easier than inventing one, and harder to notice. |
| Fidelity | Read the quoted requirement against the original wording. Paraphrase can change "shall" into "should". |
| References to standards | Confirm every standard and edition that appears is the one named in the specification. |
| Conflicts | The tool may not notice that a drawing note and a specification clause disagree. |
| Status | Mark what is a draft, who reviewed it, and when. |
A working method for any AI-drafted document
- Use your own source material. Paste the facts, the notes or the text. A draft built on your documents is much easier to check than one built on the tool's memory.
- Ask for a structure that is easy to review. Tables with a source column beat flowing paragraphs.
- Do not accept references you did not supply. If a clause number, standard or statistic appears that you did not provide, treat it as unverified until you find it in the primary source.
- Review before it leaves the building. Name the reviewer on the document record.
- Keep a note of what the tool did. If a dispute arises later, you can show how the document was prepared and who approved it.
- Mind confidentiality. Check what your employer and client contracts allow you to put into a third-party tool. If they are silent, ask.
What not to delegate
Some tasks carry professional responsibility and should not rest on an unchecked draft: structural or MEP calculations, certification of work, notices with contractual consequences, safety approvals, and anything that you would sign or stamp. AI can help you organise the inputs. The decision and the signature stay with the engineer.
Where to start
Pick one task, such as the minutes. Run it for four weeks on real meetings, with the review step in place, and count the corrections you make. Expand only if the corrections are few and consistent. If you want to set this up for your technical office, tell us which task takes most of your week and we will propose a small, checked workflow.