Email management for architects comes down to one habit. Read the inbox by project. Every message belongs to a job, and every job has a short list of things waiting on somebody. The client owes a decision. The engineer owes a comment. The contractor is waiting on an answer to an RFI. Your inbox holds all of that, sorted by the minute each person pressed send. Managing email across several projects means turning it back into one list per job, every morning, and keeping the record you’ll need later.
- Read by project. Ten messages about one job are one situation. One message each from ten jobs are ten.
- Surface what’s owed first. RFIs, submittals, site issues and client decisions each carry a date. They go first.
- Read long threads as decisions. A five-party chain matters for what it settled and who still owes what.
- Treat drawings as the record. The attachment is a copy. The set in the project folder is the drawing.
- Keep the archive. A decision made by email years ago is one you may have to find again.
The rest of this guide takes each of those in turn, with what Point does at each step.
Your own inbox, not a list of architects
Search this subject and half the results sell lists of architects’ email addresses. This page is about the other thing. It’s about the inbox your practice already has, and the projects, clients, contractors and consultants that write to it.
If you did come here to buy a list for marketing, know that a different set of rules governs that job. The FTC’s CAN-SPAM compliance guide covers commercial email, and it’s explicit about one point:
The law makes no exception for business-to-business email.
So an email to another firm still counts. The rest of this page is about running the practice.
Who writes to a practice
A small practice hears from more kinds of people than most businesses its size. Each of them writes for a different reason, and each carries a different cost if it waits.
| Who | What arrives | What it usually needs from you | What waiting costs |
|---|---|---|---|
| Client | Questions, changes of mind, approvals | A decision, or a fee conversation | A stalled design phase |
| Contractor | RFIs, submittals, site photos, schedule updates | An answer by a stated date | A crew standing still |
| Consultants | Structural, MEP and civil comments, revised sheets | Coordination, then a reply | Drawings issued out of step |
| Building department | Plan review comments, permit status | A response set by a deadline | A review cycle lost |
| Manufacturers and suppliers | Product data, lead times, substitutions | A check against the spec | A wrong product on site |
| Your own team | Questions, markups, who’s covering what | A quick answer | Work done twice |
The same project shows up in every row. That’s why sorting by sender doesn’t help much. A contractor’s message about the Maple Street library and a consultant’s message about it are one job, and they need reading together.
How email management for architects starts each morning
The most useful ten minutes in a practice day is the first read. It answers one question per project. What moved overnight, and what’s due from us?
Here’s what a good morning read surfaces, in this order:
- Anything from site that’s blocking work. A question with a crew waiting behind it beats everything else.
- RFI responses due today or tomorrow. Each one carries the reply date the contractor asked for.
- Submittals in review. What came in, what’s due back, and what’s still with a consultant.
- Client decisions you’re waiting on. And the date that decision starts to slip the schedule.
- Consultant comments owed to you. Especially anything another sheet depends on.
- Plan review comments and permit dates. These come rarely, and they matter when they do.
- Today’s meetings. The site visit at 9:40, and the client call at 2:00.
Everything else can wait for a quieter hour. Newsletters, product launches and webinar invitations are real mail. They just don’t need you before lunch.
Point does this reading for you. Overnight mail is already ranked when you sit down, and a short briefing gathers what needs you today. You choose when it arrives. The briefing is yours to keep or switch off. Everything today asks of you, in one read shows how the briefing is built. How email triage works covers how Point weighs one message against another.
Reading long threads as decisions
A thread on a live project often runs between the client, two consultants, the contractor and you. By the thirtieth reply, nobody remembers where it landed. What you need from it is short:
- What was decided, and by whom.
- What’s still open.
- Who owes what, and by when.
Picture a thread about a changed window head on a mixed-use job. The contractor asks a question. The structural engineer suggests a lintel change. The client asks whether it affects the budget. The supplier says the new size has a six-week lead time. Read as a summary, it’s two lines. The engineer’s lintel is agreed in principle. The client still owes a yes on cost, and the contractor needs it by Friday.
Point gives every thread a plain summary before you open it, so a long chain reads in a line. How to catch up on a long email chain covers how that works and where it helps.
There’s one thing in these threads worth watching for yourself. RFIs drift. A question about a detail becomes, three replies later, an agreement to change it. The AIA’s standard RFI form, G716-2004, is clear about where that line sits:
Neither the request nor the response received provides authorization for work that increases the cost or time of the project.
So when a thread starts to change cost or time, it needs to leave the email and go through your change process. A summary that lists “agreed” items makes that drift easier to spot. The same AIA summary also says RFIs “should be numbered, logged and tracked.” The log lives in your project system. The email is where the question first arrives.
Drawings and the version in play
Drawings make a practice’s email heavier than most. A PDF set, a DWG for a consultant and a model file for coordination can each run past what a mail server will carry.
| Mailbox | Size limit, as the provider documents it |
|---|---|
| Personal Gmail | 25 MB. Larger attachments are swapped for a Google Drive link (Gmail Help) |
| Google Workspace | Set by your administrator |
| Microsoft 365 | 35 MB to send and 36 MB to receive by default. Administrators can set anywhere from 1 MB to 150 MB (Microsoft) |
The receiving side matters as much as yours. A consultant on a 35 MB limit won’t receive the 60 MB set you were allowed to send.
That’s why most practices settle on a simple rule. Send a link for the full set, and attach only what someone needs to read on their phone. A single sheet, a sketch or a marked-up detail goes as an attachment. A full issue goes as a link to the project folder, with a transmittal that says what’s in it.
The AIA’s G810-2001 transmittal letter puts that purpose plainly:
AIA Document G810-2001 allows for the orderly flow of information between parties involved in the design and construction phase of a project.
Whether you use the AIA form or your own, a transmittal in the email body does three jobs. It says what was sent, which revision it is, and why. That’s the line someone searches for a year from now.
Version confusion is the expensive failure. Somebody prices or builds from Revision C after Revision D went out. A few habits keep it rare:
- Put the revision and date in the filename, as well as the title block.
- Say what changed in the email body, in a sentence.
- File the attachment to the project record the day it arrives. The copy in the inbox is a convenience.
- Reply to the latest issue, so the thread carries the current version at the bottom.
Point gathers attachments into one list as they arrive. Each one stays tied to the thread that carried it, so the version somebody actually sent is the one you find. You can also ask a question of a PDF, and the answer comes back with a link to where it was read. Ask a question, get the answer out of the attachment shows that on a real document.
Finding a decision years later
Architecture keeps its email longer than most trades. A question about a detail can come back during construction, at closeout or long after. The answer is usually an email. Somebody agreed to something, on a date, in writing.
Finding it starts with how you write today:
- Put the project number in every subject line. “24-117 Maple St: stair handrail RFI 14” can be found by anyone in the office.
- Name the RFI or submittal number when you reply to one.
- Keep the archive. Filing a thread away is fine. Deleting project mail rarely is. How long to keep it is a question for your insurer or attorney.
Then there’s the search itself. Most mailboxes match the exact words. That works when you remember them. It fails when you remember “the email where the engineer said the beam was fine” and the email says “W-section confirmed adequate.”
Point searches by meaning, so you can look for what you remember about a message. It searches mail, tasks, calendar and files from one box. Find an email when you can’t remember the words has the detail.
The dates hidden in project mail
Much of a project’s email is a date in disguise. “Can you get back to us by Thursday” is a task. “We’ll send revised calcs next week” is something you’re owed. “Can we meet on site?” is a scheduling job across four calendars.
Point handles each of these where it lands:
- A request becomes a dated task. When a message asks something of you, it goes on your list with the date and the thread attached. Email task management, without writing it down covers how.
- What you’re owed comes back. Point tracks what you’ve handed off, and the consultant’s comment resurfaces when it’s worth chasing. Tracking what you are owed a reply on has the rest.
- Site visits get booked. Point finds a time everyone can make and runs the back-and-forth itself. A meeting scheduler, without the email chain shows it.
- Replies come back drafted. A routine answer to site arrives written the way you write. Getting AI replies that sound like you wrote them explains how Point learns that.
How much Point does on its own
Every one of those jobs sits on a dial, and you set it for each kind of task. Review is the default. Point prepares the work, and the work waits for you. One tap approves it.
You can raise a setting when you’re comfortable. A routine acknowledgment to a supplier might run on its own. A reply to the client might stay on review for good. At the top of the dial, Point handles that kind of task without asking. That’s the reason to raise it.
Everything Point does shows in a log, and you can reverse what Point did from there. A sent email is the one exception. Once it reaches someone else’s server, nobody can call it back. Setting how much your inbox does on its own walks through the settings.
If you run a second business alongside the practice, each one stays sealed off from the other. Keeping one business isolated from another explains where that line runs.
Where your project software fits
Most practices already run drawing and project tools. Revit, a document control system or a contractor’s platform each hold their part of the job. They’re good at what they hold.
Email is what arrives around them. The client’s question, the consultant’s revised sheet and the contractor’s “quick one” still come to your inbox. Point works on that mail. It reads your existing Gmail or Microsoft 365 mailbox, so your address and years of project history stay where they are. Your drawings stay in the systems that manage them.
Point for architecture practices shows all of this on a practice’s day. The full list of what Point does is on the benefits page, and Point is the short version.
Common questions
How should architects manage email across multiple projects?
Read it by project. Put the project number in every subject line, so mail sorts and searches by job. Each morning, look for what’s owed on each project: RFI replies, submittals, site issues and client decisions. Read long threads for what they decided and who still owes what. File drawings to the project record and keep the archive. Point does the first read for you and ranks overnight mail before you sit down.
Should every project have its own email folder?
Folders help when someone files into them every day. Most small practices find they fall behind within a month. A project number in every subject line does more for less effort, because search and sorting can use it whether or not anyone filed. Keep folders for the record, and let the subject line do the daily work.
Should RFIs and submittals go through email at all?
They often start there, whatever system you use. A contractor writes a question before anyone opens a form. What matters is that the question gets a number, goes into your log and gets a dated reply. The AIA’s G716 summary says RFIs “should be numbered, logged and tracked,” and that holds wherever the first message arrives.
Should I attach drawings or send a link?
Attach what someone needs to read on a phone, like a single sheet or a marked-up detail. Send a link for full sets and model files. The receiving mailbox may have a lower limit than yours, and a link keeps one current copy in one place. Either way, say the revision and what changed in the email itself.
Is it safe to connect a practice inbox to an AI email client?
It’s a fair question when the inbox holds client drawings and fee letters. The answer depends on what the tool can read, what it can do next and who can see the result. Is an AI email client safe for client data? works through it, with the questions to ask any vendor before you connect anything.
Is this the same as project management software for architects?
No. Project and document tools hold the drawings, logs and schedule. Email is how the questions and decisions reach you. A practice usually wants both. Point covers the inbox side and leaves your project tools as they are.