An email assistant for architects takes the inbox work that isn’t architecture. It sorts the overnight mail by project and puts the RFI that’s due first. It reads the long consultant thread and tells you what was decided. It chases the engineer, books the site visit and drafts the routine replies. What it leaves with you is anything that changes the drawing, the fee or the client’s mind. That split holds whether the assistant is a person or software. If your practice has no PA, the inbox work is already being done. You’re the one doing it, at 9:40 at night.
- Hand over: the morning sort, thread summaries, filing, chasing, scheduling and first drafts of routine replies.
- Keep: RFI answers on substance, submittal decisions, scope and fee, and any instruction to site.
- Choose on fit: pick the one that suits how your practice already works. The criteria are below.
What an email assistant does for an architect
Picture a seven-person practice with four live jobs. Mail comes from clients, the structural engineer, the MEP consultant, two contractors, a planning officer and a dozen suppliers. Nobody’s job is to read it first. Here’s what an assistant takes off that pile, in the order the day asks for it.
| When | The job | What it looks like in a practice |
|---|---|---|
| Before you sit down | Sort overnight mail by what needs you | The contractor’s RFI with a Friday response date goes above the newsletter and the product rep. |
| First coffee | A short read of the day | What each project needs from you today, and the site meeting at 2:00. |
| Mid-morning | Turn long threads into decisions | Thirty messages on the stair detail become: what was agreed, what’s open, who owes what. |
| As mail lands | Catch the dates | “Comments by the 14th” becomes a dated item, tied to the thread it came from. |
| After lunch | Chase what you’re owed | The engineer’s markups were promised Tuesday. A polite nudge goes Thursday. |
| Whenever | Book the site visit | Three parties, one time, without six emails about it. |
| End of day | Draft the routine replies | “Received, we’ll review and respond by Wednesday” is ready for you to check. |
| Weeks later | Find the decision again | The email where the client agreed to the cheaper cladding, found by what you remember of it. |
Each of these is its own skill, and each has its own guide on this site. The table is what they add up to for a practice. Email management for architects: the practice inbox covers how a practice runs one inbox across all its jobs, if you want the method before the help.
The jobs to hand over and the jobs to keep
The test is simple. If a reply could change what gets built, what it costs or when it’s done, it stays with an architect. Everything around it can go.
The RFI shows why. The contractor needs an answer, and the answer is design work. AIA’s form for it carries a warning worth knowing:
“Neither the request nor the response received provides authorization for work that increases the cost or time of the project.” From the AIA Contract Documents summary of G716-2004
That keeps cost and time out of the RFI itself. But a careless reply can still read like an instruction on site, so the substance of the answer is yours. The acknowledgment, the log entry, the response date and the chase all belong to the assistant.
| Task | Hand over? | Why |
|---|---|---|
| Sorting mail by project and urgency | Yes | It’s reading, not deciding. |
| Summarizing consultant and contractor threads | Yes | You still read the summary, and the thread is one click away. |
| Acknowledging receipt of an RFI or submittal | Yes | It sets a date and buys you the time to answer well. |
| Answering an RFI on substance | No | It’s design intent, and site will act on it. |
| Reviewing a submittal or shop drawing | No | That’s professional judgment with your name on it. |
| Chasing a consultant for comments | Yes | The words are routine. The timing is the hard part. |
| Booking site visits and client meetings | Yes | It’s pure coordination. |
| Filing drawings and attachments to the project | Yes, then check | The version that matters needs to be the one on record. |
| Fee, scope or change-order correspondence | No | Every word can end up in a dispute. |
| Telling a client about a delay or a problem | Draft only | An assistant can start it. You should send it. |
| Instructions to the contractor on site | No | That’s direction, and it has consequences. |
What a person brings and what software brings
A human assistant, in-house or a virtual assistant, brings judgment you can talk to. A good one picks up the phone to the planning office. They notice the client sounds upset and walk the email over to you. They can run the parts of the practice that have nothing to do with email: invoicing, timesheets, ordering samples.
Software brings coverage. It reads every message the minute it lands, including the ones at 11 at night. It doesn’t need a month to learn who the structural engineer is. It’s there the week your PA would have been on vacation.
Cost is where most practices start. The US Bureau of Labor Statistics puts the median annual wage for secretaries and administrative assistants at $48,310 in May 2025. That’s before payroll taxes and benefits. Virtual assistants are paid by the hour or on a monthly retainer, and rates vary too widely to quote one fairly. If you bring a VA on as a contractor, the IRS test for who counts as an employee still applies:
“The keys are to look at the entire relationship and consider the extent of the right to direct and control the worker.”
So a VA who works set hours on your inbox, to your instructions, may be closer to an employee than the contract says. Your accountant can tell you where that line falls for you.
Many small practices end up with both. Software does the reading and sorting. A part-time person handles the calls, the billing and the judgment that needs a voice. Point vs hiring an assistant works through that choice in full, including which to do first.
How to choose an email assistant for a practice
Most comparisons of email assistants are written for sales teams. A practice needs different things, because its mail is built around drawings, consultants and dates. Ask these of any assistant, human or AI.
| Criterion | What to ask | Why it matters in a practice |
|---|---|---|
| Works on the mail you have | Does it keep your address, history and folders? | Ten years of project mail is your record. Moving it costs more than the tool. |
| Reads by project | Can it tell the Elm Street job from the Main Street job? | Ten messages about one job are one situation. |
| Copes with drawing sets | Does it handle large PDFs and links to shared folders? | The revision that changes the work is often the attachment three messages down. |
| Finds old decisions | Can you search by what you remember, not exact words? | Disputes turn on an email from two years ago. |
| Catches dates | Does “by the 14th” become something you’ll see on the 13th? | RFI and submittal dates are buried in prose. |
| Sets its own limits | Can you decide, per kind of task, how much it does alone? | You might let it book visits freely but never reply to a client. |
| Shows its work | Is there a record of everything it did, and can you reverse it? | You need to know what went out in the practice’s name. |
| Keeps confidences | Who else can read the mail, and what’s in writing about it? | Client briefs, fees and planning strategy all sit in the inbox. |
| Fits your project software | Does it sit alongside Newforma, Procore or your filing system? | The inbox is where mail arrives. The project system is where it’s kept. |
No single tool wins every row. A VA wins on calls and judgment. Software wins on coverage and recall. The rows you weigh most tell you which you need.
Client confidences in someone else’s hands
Any assistant reads mail your clients sent in confidence. The AIA’s Code of Ethics and Professional Conduct speaks to that directly:
“Members shall not knowingly disclose information that would adversely affect their client or that they have been asked to maintain in confidence, except as otherwise allowed or required by this Code or applicable law.” AIA Code of Ethics, Rule 3.401
The duty stays with you, whoever does the reading. The commentary to the same rule adds that “the law does not recognize an architect-client privilege.” So you choose the assistant on how well they protect the mail, because no privilege does it for you.
For a person, that means a written confidentiality agreement and access to only the mailboxes they need. For software, it means knowing what the vendor can read, and whether your mail is used for training. Is an AI email client safe for client data? lists the questions to put to any vendor before you connect anything.
Which AI email platform is best for a practice?
There isn’t one answer, and the honest version depends on where your mail lives.
If your practice is on Microsoft 365, Copilot is already in Outlook. Microsoft documents a thread summary in Outlook, and in 2025 Microsoft announced it for users without the paid Copilot license (Office 365 for IT Pros, on MC1124564). A March 2026 answer on Microsoft Q&A describes the unlicensed version as mostly limited to the open email or thread. That’s useful on one long thread at a time. It doesn’t read the whole inbox by project or tell you what’s due across four jobs. Gmail practices have Gemini in a similar place.
The difference to look for is between help with the email in front of you and help with the whole inbox. A practice without a PA needs the second. Point compared with Outlook and Point compared with Gmail set the built-in tools side by side with Point. What is an AI email client? explains the category itself.
A Tuesday with Point in the inbox
Overnight, the contractor sent an RFI about the stair stringer. The engineer replied to the client about the beam. A supplier sent three price lists. Point has already read all of it.
Your morning briefing is waiting when you sit down. The RFI is at the top with its Friday date. The beam thread is one line: the engineer agrees to the deeper section, and the client hasn’t confirmed. The price lists are below the fold, where they belong. Everything today asks of you, in one read shows how the briefing is put together.
You open the RFI. Point has drafted the acknowledgment in your voice, with a response date. It waits for you. You change one line and send it. The answer about the stringer is yours to write, and the RFI sits on your list until you do. Email task management, without writing it down covers how a request becomes a dated item.
The drawings the engineer attached are gathered with every other file, each one tied to the thread that carried it. You ask which revision of the beam detail the client last saw, and Point finds it. Ask a question, get the answer out of the attachment shows that on a real document.
The site visit needs the contractor, the engineer and the client. Point runs the back-and-forth and puts it on everyone’s calendar. A meeting scheduler, without the email chain has the detail. The MEP consultant’s comments were due yesterday, so the nudge is lined up too. Tracking what you’re owed a reply on explains when Point brings that back.
How much of this happens on its own is your setting, one kind of task at a time. Out of the box, drafts wait for your review. You might let scheduling run by itself and keep every client reply on review. Turn a task all the way up and Point handles it without asking. Everything Point does is in a log you can reverse from, except a sent email, which nobody can call back. Setting how much your inbox does on its own walks through it.
Point connects to the practice’s own Gmail or Microsoft 365 account. Your address stays the same, and there’s nothing to migrate. Point for architecture practices shows a practice’s day end to end. The benefits page has the full list, and Point is the short version.
Common questions
What can an email assistant do for an architect?
It can sort mail by project and urgency, summarize long consultant and contractor threads, pull out RFI and submittal dates, chase overdue comments, book site visits and draft routine replies. It shouldn’t answer RFIs on substance, review submittals, or handle fee and scope letters. Those stay with an architect because site and the client act on them.
Which AI email platform is the best?
The best one for a practice is the one that reads the whole inbox by project, works on the mail you already have, and lets you limit what it does alone. Built-in tools like Copilot in Outlook help with one thread at a time. A dedicated AI email client works across the whole inbox. Weigh the criteria table above against how your practice runs.
What is the best AI for architecture?
That depends on the job. Design and visualization tools are a different category, and they don’t touch your inbox. For the correspondence around a project, the useful AI is the kind that reads your email by project, summarizes threads into decisions and tracks dates. What is an AI email client? explains what that category covers.
Should a small practice hire a PA or use an AI email assistant?
If the pain is reading, sorting, chasing and scheduling, software covers most of it for far less than a salary. If you need someone on the phone, running invoicing or walking problems over to your desk, hire a person. Many practices do both. Point vs hiring an assistant compares them in full.
Can an email assistant answer RFIs for me?
It can acknowledge the RFI, log its date, draft a holding reply and remind you before it’s due. The answer itself is design intent, so it should come from an architect. Point drafts it if you ask, and the draft waits for your review by default.
Is it safe to let an assistant read client email?
It can be, if you choose with care. AIA Rule 3.401 keeps the duty of confidence with you, whoever reads the mail. For a person, that means a written agreement and limited access. For software, ask what the vendor can read and whether it trains on your mail. Is an AI email client safe for client data? has the questions.
Does an email assistant replace project management software?
No. Newforma, Procore and similar tools keep the formal record of RFIs, submittals and transmittals. An email assistant handles the mail that arrives around them, and helps you get what matters into that record.