Skip to content

Email follow-up for architects: when the client's sign-off goes quiet

On this page

To write a follow-up email that checks project status, put the project number and the thing you’re waiting on in the subject. Then say what you sent and when, what it’s holding up, and the one question you need answered by a date. Keep it short enough to answer from a phone. That’s the whole shape of good email follow-up for architects, and the rest of this page is the templates.

There are four follow-ups a small practice sends every week. Chasing a client’s approval. Recapping a meeting so the decisions stick. Checking where a contractor stands. Asking after a fee. Each one is below, ready to copy, with the contract clause that puts a date on it.

How to write a follow-up email that checks project status

A status check works when the reader can answer it in one line. Five parts get you there:

  • A subject that searches. Project number, project name, the item, and the date you need it. “24-117 Maple St: SD approval, needed Oct 9.”
  • What you sent and when. “We sent the schematic design set on September 21.”
  • What it’s holding up. “Design development starts once you’ve signed off, and our engineers are booked from the 12th.”
  • One question with an easy answer. “Can you reply ‘approved as drawn’, or tell me which sheets you want to talk through?”
  • A date. “If I have it by Friday, we keep the schedule.”

The easy answer is what saves the phone call. A client who has to write a paragraph puts it off. A client who can reply in three words often does it on the spot.

Keep the thread too. Reply in the email that carried the drawings, so the set and the chase sit together. The practice’s subject-line habits are covered in the practice inbox.

What your agreement says about a slow approval

A stalled approval feels like a favor you’re asking for. In most owner-architect agreements, it’s a date the client agreed to.

Many US practices sign the AIA’s B101-2017. The AIA’s own summary describes basic services in five phases, from schematic design through construction. Each design phase ends with a request for the owner’s approval. Section 3.2.7, for example:

The Architect shall submit the Schematic Design Documents to the Owner, and request the Owner’s approval.

The owner’s side of that is in section 5.3:

The Owner shall render decisions and approve the Architect’s submittals in a timely manner in order to avoid unreasonable delay in the orderly and sequential progress of the Architect’s services.

So a timely decision is the client’s job under the agreement. The schedule makes “timely” a number. Section 3.1.3 has the architect’s schedule allow time “for the Owner’s review,” and then says:

Once approved by the Owner, time limits established by the schedule shall not, except for reasonable cause, be exceeded by the Architect or Owner.

A slow decision can also cost money. Section 4.2.1 lists Additional Services that need the owner’s written go-ahead before you start. One of them is:

Services necessitated by decisions of the Owner not rendered in a timely manner or any other failure of performance on the part of the Owner or the Owner’s consultants or contractors

The same section asks you to notify the owner “with reasonable promptness.” That’s why the chase belongs in email. Each follow-up is a dated record of what you asked for and when.

These quotes come from a B101-2017 posted by the Medford School District in Oregon. Your own agreement may be edited, or written on your firm’s form. Read its schedule and its additional-services clause before you rely on either.

Chasing a client’s approval, in three emails

Here’s the Maple Street job. You sent the schematic design set to Ruth Okafor on Monday, September 21. She said she’d sign off by Friday, October 2. It’s now Monday, October 5, and nothing has arrived.

Names, dates and sheet numbers stand in for yours. Each one goes in the thread that carried the drawings. When to send each is a question of intervals, and how long to wait before following up covers it.

One. The morning after the date.

Subject: Re: 24-117 Maple St: SD set for approval, needed Oct 9

Hi Ruth,
Checking in on the schematic design set we sent on September 21.
If you’re happy with it, a reply saying “approved as drawn” is all we need. If something’s bothering you, tell me which sheet and I’ll answer it in writing.
Getting it by Friday keeps design development on its October 12 start.
Sam

Two. A week on, saying what it holds up.

Subject: Re: 24-117 Maple St: SD set for approval, needed Oct 9

Hi Ruth,
We’re still waiting on your sign-off for the schematic design set.
Our structural and mechanical engineers were booked to start on October 12. I’ve held their start for now.
If it would help, I can send a one-page list of the decisions the set makes, so you can approve them one by one. Or reply with the two or three points you want to change, and we’ll revise those first.
Sam

Three. The written notice.

Subject: 24-117 Maple St: SD approval and the schedule

Hi Ruth,
I want to put this in writing so we’re both looking at the same dates.
The schematic design approval was due on October 2 under our schedule. Every week it waits moves design development, and the permit submission after it, by about a week.
If the approval brings changes that mean redrawing work we’ve already done, that would be an additional service under our agreement. I’d send you a fee for it and wait for your written OK before starting.
Nothing needs to happen today. A reply with “approved” or your list of changes gets us moving again.
Sam

The third one is calm on purpose. It names the date, the effect, and the clause. It doesn’t threaten anything. A client who reads it knows what’s at stake and how to fix it in one reply.

If three emails haven’t moved it, the silence usually means something else. What to do when a client stops replying covers that turn.

A follow-up after a client meeting that records the decisions

Most stalled approvals start in a meeting. Everyone nodded. Nobody wrote it down. Two weeks later, nobody’s sure what was agreed.

Send the recap the same day, in a shape people can scan. Decisions first, then open items, then who owes what by when.

Subject: 24-117 Maple St: design meeting Oct 6, decisions and actions

Hi Ruth, Dev,
Thanks for this morning. Here’s what we agreed, so we’re all working from the same list.

Decided\

  1. Stair stays in the north bay, as shown on A-201 rev B.\
  2. Kitchen window widens to 6’-0”. We’ll revise A-301.\
  3. Fiber cement siding replaces wood on the east and west walls.

    Still open\
  4. Skylight over the stair. Ruth to decide by October 14.\
  5. Garage door style. We’ll send three options by October 9.

    Who owes what\
  • Sam: revised A-201 and A-301, October 9\
  • Dev: updated cost for the siding change, October 12\
  • Ruth: skylight decision, October 14

    If anything here doesn’t match your notes, reply by Friday and I’ll correct it.
    Sam

The last line does real work. It gives people a short window to correct the record while the meeting is fresh. After that, the list is the record.

Here’s the one place a common habit needs care. “If we don’t hear by Friday, we’ll treat this as approved” is fine for confirming notes. It isn’t a phase approval, and it isn’t the written authorization section 4.2.1 asks for before additional services. For those, get a reply that says yes.

The thread is also where the decision lives later. Finding the email where it was agreed covers how to search for it a year from now. A recap with numbered decisions is much easier to find than eleven replies that say “sounds good.”

The other approvals an architect waits on

The client isn’t the only one holding a decision. Each of these has its own clock, and the chase should point at it.

Waiting onFromWhat sets the clockWhat to ask for
Phase approvalClientYour agreement’s schedule, B101 sections 3.1.3 and 5.3“Approved as drawn,” or a list of changes
Change order signatureClientA201 section 7.2.1: owner, contractor and architect all signThe signed form, or the one term holding it up
Consultant reviewEngineerYour consultant agreement and the dates you gave themThe marked-up set, or the date it’ll come
Plan review commentsBuilding departmentThe jurisdiction’s posted review timesWhere it sits in the queue, and the reviewer’s name
Fee approval for added workClientB101 section 4.2.1: written authorizationA written OK on the fee you sent

Change orders deserve a note. A201-2017 section 7.2.1 calls a Change Order “a written instrument prepared by the Architect and signed by the Owner, Contractor, and Architect.” If the owner and contractor can’t agree on price or time, section 7.3.1 provides a Construction Change Directive instead. That one needs only the owner’s and architect’s signatures. So when a change order stalls, ask which term is stuck. The answer tells you which form to send.

For the building department, the follow-up goes to the reviewer named on your application, if there is one. Ask a question they can answer from their screen: is it assigned, and when are comments expected. B101 section 3.1.3 already has your schedule allow time for those approvals. If the review runs past it, tell your client in the same week.

The text of A201 above is from the copy posted by Tri-County Technical College in South Carolina.

A contractor status check that gets a straight answer

During construction, the contractor owes you a schedule. A201-2017 section 3.10.1 has the contractor submit one with “interim schedule milestone dates,” for the owner’s and architect’s information. It also says:

The schedule shall be revised at appropriate intervals as required by the conditions of the Work and Project.

That gives a status check its anchor. Ask about one milestone, by its date.

Subject: 24-117 Maple St: framing milestone Oct 23, status check

Hi Marco,
Two quick questions ahead of Thursday’s site meeting.\

  1. The schedule shows framing complete by October 23. Are you still on that date? If not, what’s the new one?\
  2. RFI 14 on the stair handrail went back to you on October 2. Is anything else you need from us holding up the stair?
    A one-line answer to each is plenty. I’ll bring anything bigger to Thursday.
    Sam

Two numbered questions get two numbered answers. A general “how are things going” gets a paragraph you have to read twice.

Status checks run the other way too. Contractors chase you. Section 9.4.1 gives the architect seven days after receiving a pay application to certify it or say why not. RFIs carry their own clock, and the RFI triage guide covers it.

Asking after a fee

B101 section 11.10.2.1 says payments are “due and payable upon presentation of the Architect’s invoice.” The form leaves a blank for how many days pass before interest starts. Your agreement fills it in.

The first chase can be short and kind. Most late fees are sitting in someone’s approval process.

Subject: Re: 24-117 Maple St: invoice 1142, SD phase, $18,400

Hi Ruth,
Invoice 1142 for the schematic design phase was sent on September 30, and it hasn’t come through yet.
Can you tell me if it’s with you or with someone else to approve? I’m glad to resend it to whoever pays.
Sam

Section 9.1 matters if it goes much further. It treats nonpayment as cause to suspend services, and it asks for “seven days’ written notice” before you do. That notice is a letter you’d want to send carefully, with your own agreement in front of you. The full sequence, from the first reminder to a write-off, is in the follow-up email for an unpaid invoice.

Keeping track of everything you’re waiting on

The emails above are the easy part. The hard part is remembering, on October 9, that Ruth’s approval was due.

Your sent folder sorts by the day you wrote. The due date isn’t in it anywhere. A practice with six live jobs might be waiting on twenty things at once. Some practices keep a list in a spreadsheet. Some flag the email. Both work on the days someone keeps them up.

Tracking what you’re owed covers what the list needs to hold. Following up without nagging covers how often to chase the same person.

How Point keeps the wait for you

Point is an email client that runs on your existing Gmail or Microsoft 365 mailbox. It keeps track of what you’re waiting on, so the chase starts on time without a list.

Here’s the Maple Street approval with Point in the inbox.

  • You say it once, as you send. On the thread with the SD set, you note that Ruth’s sign-off is due by October 2. Point turns that into a dated task, with one link back to the thread. It sits with the rest of your work.
  • The quiet thread comes back on the day. On October 2, if Ruth hasn’t replied, the thread returns to the top of your feed with a prompt on it. If she replied on the 1st, it stays put.
  • The chase is drafted from the thread. Ask Point for the follow-up and it writes one in your voice, with the dates and sheets from the thread. The draft waits for you. You change a line, or you send it. Why a drafted email waits for you covers that pause.
  • The approval lines up the next step. Tell Point once: when Ruth approves the SD set, give me a task to issue the set to the engineers. When her yes lands, Point prepares the task. Nothing is created yet. It waits for you. One click is your go. A watch that lines up the work shows how.
  • Settled elsewhere counts. If Ruth approved on the phone and you mentioned it in an email, Point can mark the task as looking done and show you why. It stays open until you agree.

Review is the default for each kind of action. Point prepares the work, and the work waits for you. You can raise a setting when you’re comfortable, so routine reminders might go out on their own. At the top of the dial, Point handles that kind of task without asking. A chase to a client usually stays on review. Setting how much your inbox does on its own walks through it.

The rest of the practice inbox is in Point for architecture practices and on the benefits page.

Common questions

How do you write an email to follow up the status?

Reply in the original thread so the context comes with it. Put the project number and the item in the subject. Say what you sent and when, what it’s holding up, and ask one question that can be answered in a line. End with the date you need it by. For an approval, offer an easy answer like “approved as drawn.”

How long should an architect wait before chasing an approval?

Start from the date in your schedule. Chase the morning after that date passes. If there’s no date, set one in your first email and chase the day after it. How long to wait before following up has the intervals in more detail.

Can ChatGPT write my emails?

It can draft one if you paste in the details. It doesn’t see your thread, so you’ll supply the dates, sheets and names yourself. Think about what you paste, too. OpenAI’s data use page says business plans aren’t used for training by default, and that individual users can opt out. Is an AI email client safe for client data? covers the questions to ask any tool before client drawings go near it.

What are the 5 C’s of email?

The usual list is clear, concise, complete, correct and courteous. For a follow-up, “complete” matters most. A chase that names the set, the date and the decision you need gets answered. One that says “any update?” starts another round.

Does an email reply count as a client’s approval?

Often, for design approvals, a clear written yes in email is what practices rely on. Check your agreement for how approvals and notices must be given. Make the reply unambiguous: ask for “approved as drawn” or a list of changes. “Looks good” leaves room for doubt later. Change orders are different. A201 calls for a signed form.

Should I call instead of emailing a third time?

A call can unstick it, and sometimes it’s the right move. Follow it with an email that records what was decided on the call. The decision needs to live somewhere you can find it later.

Is this page about email lists of architects?

No. This page is about the follow-ups your own practice sends. Buying architect contact lists for marketing is a different job with different rules, and the practice inbox points to them.

Ready for a calmer inbox?

Join the private beta

We're onboarding a few teams at a time. Leave your email, confirm it once, and we'll send an invitation the moment a place opens.

By joining you agree to our privacy policy.

Private beta

What you're joining

It runs on the mail you have

Point sits on top of Gmail or Outlook. Your address, your history and your contacts stay exactly as they are, so there is nothing to migrate.

You set how much Point does

Out of the box everything waits for your review, replies included. You hand over only what you trust, one kind of work at a time.

Join the private beta

We're onboarding a few teams at a time. Leave your email, confirm it once, and we'll send an invitation the moment a place opens.

By joining you agree to our privacy policy.