Email drafting for architects comes down to knowing what each email has to carry. Most practice email is easy to write. A few kinds carry contract weight, and those are the ones worth slowing down for. A scope change is a notice. An RFI reply is a written instruction. A contractor’s “quick question” can turn into a change in the work. Each one reads best when it’s short, calm and specific, whether you write it yourself or start from a draft.
Here’s the short version:
- Client updates lead with what changed and what you need from them, with a date.
- Scope and fee changes go out promptly, explain why and wait for a written yes.
- RFI replies answer in writing, point to the sheet and stay out of the contractor’s means and methods.
- A contractor’s quick question gets a quick answer, unless the answer costs money or time.
- AI drafts get checked for dates, figures and anything you’d be agreeing to.
Point drafts these replies for you, in your voice, under the thread they answer. On review, which is where drafting starts, each draft waits for you. The rest of this page shows each email written out, with the clause behind it.
Email drafting for architects starts with what each email carries
Every practice writes the same handful of emails week after week. They aren’t equal. Here’s where each one sits.
| To | What it must carry | What governs it in AIA documents | |
|---|---|---|---|
| Project update | Client | What moved, what’s next, what you need and by when | Your agreement’s schedule |
| Scope or fee change | Client | The change, why it’s extra, the fee, a request for written OK | B101 section 4.2.1 |
| Construction-phase extra | Client | What you’re doing beyond the limits, and why | B101 sections 4.2.2 and 4.2.3 |
| RFI reply | Contractor | The answer in writing, the sheet reference, any change flagged | A201 sections 4.2.14 and 3.2.4 |
| Minor change | Contractor | The change in writing, and that it costs no money or time | A201 section 7.4 |
| A quick question from site | Contractor | A clear answer, or a route to the right process | A201 sections 4.2.2 and 4.2.4 |
The quotes on this page come from two posted copies. B101-2017 is from a copy posted by the Medford School District in Oregon. A201-2017 is from a copy posted by Tri-County Technical College in South Carolina. Your own agreement may be edited, or on your firm’s form. Check its clauses before you rely on any of these.
Two jobs belong elsewhere. Chasing a client’s approval and recapping a meeting are in email follow-up for architects. Pulling one answer out of a thirty-reply RFI chain is in summarizing RFI threads.
A client update they can answer in one line
A client reads your update between other things. What they want is simple. Is it on track, and do they need to do anything?
So the update leads with the ask, if there is one. Then it says what moved. Then it says what’s next. Three short parts, in that order.
Subject: 24-117 Maple St: update, and one decision by Friday
Hi Dana,
One thing needs you this week. We need your choice of window frame color by Friday, October 9, so we can release the order. The two samples are on the table in our office, or I can bring them Thursday.
Since last week, the structural engineer has signed off on the stair. The permit set went to the city on Monday.
Next, we’ll answer the city’s first-round comments when they arrive. They usually take three to four weeks.
Thanks,
Sam
A few things make that work:
- The project number and the ask are in the subject. Dana knows before opening it that something’s due.
- The date has a reason. “So we can release the order” tells her what Friday is protecting.
- Each paragraph holds one thing. She can reply “Bronze” and be done.
- Nothing in it is a promise you can’t keep. “Usually three to four weeks” is honest about a timeline you don’t control.
When the client changes the brief
This is the email practices put off, and it’s the one that costs most to put off. The client asks for a bigger kitchen, a second floor or a different budget. You know it’s more work. The question is when to say so.
The AIA owner-architect agreement answers that. Section 4.2.1 of B101-2017 says:
Upon recognizing the need to perform the following Additional Services, the Architect shall notify the Owner with reasonable promptness and explain the facts and circumstances giving rise to the need. The Architect shall not proceed to provide the following Additional Services until the Architect receives the Owner’s written authorization
The first item on that list is a change in the client’s own instructions:
Services necessitated by a change in the Initial Information, previous instructions or approvals given by the Owner, or a material change in the Project including size, quality, complexity, the Owner’s schedule or budget for Cost of the Work, or procurement or delivery method
So the clause asks for three things. Tell them promptly. Say why. Wait for a written yes before you start. An email does all three, and it’s easiest to write the day the change comes up.
Subject: 24-117 Maple St: the second-floor addition, scope and fee
Hi Dana,
Thanks for the call this morning. Adding a primary suite over the garage is a real improvement, and we’d be glad to design it.
It’s outside the scope we agreed in May. It means reworking the schematic plans you approved on September 2, adding a structural review of the garage, and a new zoning check on height.
Our fee for that work is $14,500. It would add about four weeks to design development.
We’ll hold off on the addition until you reply to say go ahead. The rest of the design keeps moving in the meantime.
Sam
What each part does:
- It starts with the client’s idea, kindly. They asked for something they want. The email treats that as good news.
- It names what’s already approved. “The schematic plans you approved on September 2” is the fact that makes this extra.
- It gives the fee and the time together. Clients feel the schedule more than the fee.
- It says what you’re waiting for. “Reply to say go ahead” asks for the written authorization in plain words.
If the reply doesn’t come, chasing it is its own email. Email follow-up for architects has that one, including why “we’ll proceed unless we hear otherwise” won’t do here.
Extra work during construction
Construction brings a second kind of scope email. Here the clause works the other way around. B101-2017 section 4.2.2 has you do the work first, to avoid holding up the job, and tell the client. The client can then say stop:
The Owner shall compensate the Architect for the services provided prior to the Architect’s receipt of the Owner’s notice.
The services on that list are ones a contractor’s email often triggers:
- Reviewing a submittal out of sequence from the approved submittal schedule.
- Answering RFIs whose answer is already in the drawings, field conditions or earlier correspondence.
- Preparing change orders that need you to evaluate the contractor’s pricing or revise drawings.
- Evaluating a large number of claims as the initial decision maker.
- Evaluating a substitution and revising drawings to suit it.
Section 4.2.3 adds limits the parties fill in when they sign. These cover the number of reviews of each submittal and the number of site visits. When you reach a limit, the clause says to notify the owner.
The email that does this is short. It goes to the client when the work starts, not at invoice time.
Subject: 24-117 Maple St: substitution review for the storefront system
Hi Dana,
The contractor has proposed a different storefront system, to save lead time. We’re reviewing it now so the schedule doesn’t slip. It also means revising four elevation sheets if it’s accepted.
Under our agreement, evaluating a substitution is an additional service. We expect about 12 hours, billed at our hourly rates.
If you’d rather we didn’t review it, reply and we’ll stop and tell the contractor.
Sam
The same note works when you’ve used up the agreed site visits, or the third resubmittal of the same shop drawing arrives. It tells the client early, while there’s still a choice to make.
Replying to a contractor
A contractor’s email wants an answer they can build from. That’s what a good reply gives them. A few clauses in A201-2017 shape how it should read.
The RFI reply
A201-2017 section 4.2.14 sets the basic expectation:
The Architect’s response to such requests will be made in writing within any time limits agreed upon or otherwise with reasonable promptness.
A good RFI reply has four parts:
- The answer, in a sentence or two.
- The sheet, detail or spec section it comes from.
- Any drawing you’re issuing, named with its revision.
- A flag when it may change cost or time.
That last part matters because of section 3.2.4. A contractor who thinks your answer adds cost or time has to raise it as a claim. A reply that says so up front keeps that conversation in the open.
Subject: 24-117 Maple St: RFI 23, parapet flashing at grid C
Hi Luis,
Use the flashing shown in detail 7 on A-501. The termination bar runs continuous behind the coping, as drawn. The note on A-201 calling for a reglet is superseded. We’ll remove it in the next revision.
This is a clarification of the documents. We don’t expect it to change cost or time. If you see it differently, please tell us before you proceed.
Sam
When the answer is already on a sheet, it’s fine to say so politely. “This is shown in detail 7 on A-501” is a full answer. If it keeps happening, section 4.2.2.2 makes those replies an additional service, and that’s worth a word with the client.
What to keep out of a site reply
A201-2017 section 4.2.2 draws a line that matters in every contractor email:
The Architect will not have control over, charge of, or responsibility for the construction means, methods, techniques, sequences or procedures, or for the safety precautions and programs in connection with the Work, since these are solely the Contractor’s rights and responsibilities under the Contract Documents.
The same section says you won’t make “exhaustive or continuous on-site inspections.” Both lines are easy to blur in a friendly, fast reply. Some words to watch:
| Instead of | Try | Why |
|---|---|---|
| “Shore it from below and pour Thursday” | “The finished slab needs to meet the detail on S-301” | How and when to build it is the contractor’s call |
| “We inspected the framing” | “We observed the framing at our October 6 visit” | Your visits are general, not exhaustive |
| “Make sure the crew is safe up there” | Leave it out, or refer it to the contractor’s safety lead | Site safety is the contractor’s |
| “Approved” on a shop drawing | The review stamp and wording your agreement uses | The stamp carries defined meaning |
A small change, in writing
Sometimes the contractor asks to move an outlet or swap a matching trim. A201-2017 section 7.4 lets you order minor changes that don’t touch the contract sum or time:
The Architect’s order for minor changes shall be in writing.
An email can be that writing. Say what changes, say that it’s at no change in cost or time, and ask them to tell you before proceeding if they disagree. Section 7.4 has a useful edge here. A contractor who carries out the minor change without first saying it affects cost or time gives up any adjustment. So the line “tell us before you proceed” protects everyone.
Who’s on the email
Clients email contractors directly. It happens on every job. Section 4.2.4 asks the owner and contractor to include you:
The Owner and Contractor shall include the Architect in all communications that relate to or affect the Architect’s services or professional responsibilities.
The same section routes your consultants through you, and subcontractors and suppliers through the contractor. When a thread arrives without you on it, a kind reply brings it back. “Thanks for copying me. I’ll answer Luis on the detail, so the drawings stay in step.”
The one email that shouldn’t be an email
Most of this page treats email as perfectly good writing. There’s one exception worth knowing, because getting it wrong can cost a claim.
A201-2017 section 1.6.1 accepts notices by email only when the agreement sets out a method for it. Notices go by electronic transmission “if a method for electronic transmission is set forth in the Agreement.” Section 1.6.2 is stricter for claims:
Notice of Claims as provided in Section 15.1.3 shall be provided in writing and shall be deemed to have been duly served only if delivered to the designated representative of the party to whom the notice is addressed by certified or registered mail, or by courier providing proof of delivery.
So if a contractor emails what reads like a claim, reply calmly and acknowledge it. Then check your agreement for how notice has to be given, and talk to your attorney or insurer before anything goes out that might be read as a position. The email is where it starts. The notice that counts may need to go another way.
A professional voice when the email is hard
The hard emails in a practice tend to be the same few. A fee the client didn’t expect. A contractor who’s annoyed about a late answer. A mistake in your own drawings. The voice that works is the same in each.
- Lead with the fact. “The stair detail on A-502 has the wrong riser height” before any apology or context.
- Say what you’ll do and when. “A revised sheet comes to you tomorrow by noon.”
- Keep one ask per email. Two asks get one answer.
- Leave out the adjectives. “Unfortunately” and “as previously stated” add heat without adding facts.
- Match the length to the news. Bad news gets a short email and a phone call. Good news can run longer.
When the email is about your own error, write the facts and the fix, and keep it brief. Whether to say more, and how, is a question for your professional liability insurer. Most carriers have a claims line for exactly this.
Drafting with AI, and what to check
An AI draft handles the slow part, which is getting a first version on the screen. Your mailbox may already offer one. Copilot in Outlook can draft messages and suggest responses, according to Data Studios, a third-party guide. Purpose-built email clients do the same with more of your history behind each draft.
Whatever writes the draft, the check is the same. A draft goes wrong by adding something nobody put there. In a practice email, look for these before it goes:
- Dates. A delivery date, a response date or a meeting time you didn’t give it.
- Figures. A fee, a dimension, a lead time or an hour estimate.
- Sheet and revision numbers. “A-501 Rev C” when the current issue is Rev D.
- Commitments. “We’ll have it to you Friday,” or “that’s fine to proceed.”
- Approval words. “Approved,” “accepted” or “agreed” in reply to a contractor.
- Recipients. A client added to a contractor thread, or a consultant left off.
A draft that passes those six is usually fine to send with a light edit. A draft about money, a mistake or an unhappy client is better as a starting point you rewrite. Why a drafted email waits for you sets out how to sort drafts so the careful reading goes where it’s needed.
Client confidences matter here too. A practice inbox holds fee letters, site addresses and floor plans. Is an AI email client safe for client data? covers what to ask any vendor before you connect a mailbox.
How Point drafts the reply
You open Dana’s email about the second-floor addition, and the reply is already there. Point has drafted it under the thread, in your voice. It names the approved schematic plans and asks for a written go-ahead, because that’s how you write scope emails. A gray auto-drafted mark shows Point wrote it.
You change the fee line. The mark comes off, and the words are yours. You press send. The reply goes from your own Gmail or Microsoft 365 address and threads under Dana’s original, like any reply you wrote.
A few things sit behind that:
- Your voice comes from your own sent mail. Point learns how you open, how you sign off and how you phrase a fee. Getting AI replies that sound like you wrote them explains how.
- You can teach it a habit in one sentence. “Always cite the sheet number in RFI replies” is the kind of thing Point keeps. How Point learns your email habits shows the list you can read and edit.
- How far it goes is your setting. The dial is set per kind of action. Drafting starts on review, so each draft waits for you. You might raise it for a routine acknowledgment to a supplier. At the top of the dial, Point sends that kind of reply without asking. Client and contractor replies can stay on review for good. Setting how much your inbox does on its own walks through it.
- Everything shows in a log. You can reverse what Point did, except a sent email. Once it reaches someone else’s server, nobody can call it back.
Point for architecture practices shows the whole day. The benefits page lists what else Point does, and Point is the short version.
Common questions
What should an architect include in a scope change email?
Say what the client asked for, and why it’s outside the agreed scope. Name what’s already approved that the change affects. Give the fee and the effect on the schedule. Then ask for a written go-ahead before you start. AIA B101-2017 section 4.2.1 asks the architect to notify the owner promptly, explain the circumstances and wait for written authorization before providing those additional services.
Is an email reply to an RFI enough?
Often, yes. A201-2017 section 4.2.14 asks for RFI responses in writing, within any agreed time or with reasonable promptness. An email is writing. Many practices also log the RFI and answer on a form, and your contract may specify a protocol. Either way, give the answer, the sheet it comes from and a flag if it may change cost or time.
Can an architect approve a change by email?
A minor change, yes, if your contract follows A201-2017. Section 7.4 lets the architect order minor changes that don’t affect the contract sum or time, and asks for the order in writing. Anything that changes cost or time needs a change order, which the owner, contractor and architect all sign. An email can propose it, but it isn’t the change order itself.
Should I answer a contractor’s means-and-methods question?
Answer the part about the finished work, and leave how to build it with the contractor. A201-2017 section 4.2.2 says the architect has no control over or responsibility for construction means, methods, sequences or site safety. “The finished wall needs to meet detail 4 on A-510” is your answer. “Brace it this way” is theirs.
Is it okay to use AI to write emails to clients?
Yes, as long as you check it and it goes out as yours. Look for dates, figures, sheet numbers and commitments you didn’t supply. Keep client mail on review, so nothing leaves before you’ve read it. Check how the tool handles client data before you connect your mailbox.
How do I keep emails professional when a contractor is angry?
Lead with the fact, say what you’ll do and by when, and keep it short. Leave out “as previously stated.” If the email starts to read like a claim, acknowledge it calmly and check your agreement’s notice clause before taking a position. A201-2017 section 1.6.2 requires notice of claims by certified or registered mail or courier, not email.