Skip to content

Email triage for architects: what's holding up the job comes first

On this page

The best way to triage email as an architect is to rank it by what’s holding up the job. Ask three things of every message. Which project is it on? What date does it carry? Who is waiting behind it? A contractor’s RFI with a crew standing by goes first, even if it arrived last. A client’s decision that gates the next phase goes next. A product launch from a manufacturer goes to the bottom, however nicely it’s written. That’s email triage for architects in one line. The job sets the order.

  • Project first. Every message belongs to a job. Read it as part of that job’s list.
  • Then the date. RFIs and submittals carry response times the contract sets. Those dates outrank everything without one.
  • Then who’s waiting. A contractor with a crew, a client with a board meeting and a consultant with a sheet to issue each carry a different cost if you wait.
  • Four groups, not forty folders. Holding up the job, has a date, needs you sometime, needs nothing.
  • Triage at set times. Two or three passes a day, so the drawing gets the rest of it.

This page is the priority order and how to run it. How the whole practice inbox works day to day, from the morning read to drawing attachments and the archive, is the practice inbox.

Email triage for architects starts with three questions

Sorting by sender or by arrival time feels natural. It fails in a practice because one job reaches you from six directions at once. The contractor, the engineer and the client can all write about the same stair on the same day.

So ask three questions, in this order.

  1. Which project? If you can’t tell from the subject line, that’s the first fix. A project number in every subject makes the rest of triage possible.
  2. What date does it carry? Some dates are written in the message. Others sit in the contract, the submittal schedule or the permit review letter.
  3. Who is waiting, and what are they waiting to do? A question with work stopped behind it is a different message from the same question asked early.

The third question is where sender role comes in. Here’s how each kind of sender usually lands.

SenderWhat makes it urgentWhat makes it importantUsual group
ContractorA crew or a pour waiting on your answerCost or time on the jobHolding up the job
ClientA decision date, a board or lender meetingScope, fee and the relationshipHas a date
Structural, MEP or civil consultantA sheet you can’t issue without their commentCoordination across the setHas a date
Building departmentA resubmittal deadline in the review letterThe permit itselfHas a date
Manufacturer or supplierA lead time that closes an order windowA substitution against the specNeeds you sometime
Your own teamSomeone blocked on a markupWork done twice if missedNeeds you sometime
Newsletters, webinars, product launchesRarelyRarelyNeeds nothing

The roles are a starting point. A supplier’s email saying a window has a 14-week lead time can jump to the top. A contractor’s “just checking in” can wait until the afternoon.

Why RFIs and submittals carry their own clock

Most of your dates aren’t in the email. They’re in the contract. On many US projects, the general conditions are the AIA’s A201. The AIA describes them as the document that sets “the rights, responsibilities, and relationships of the owner, contractor, and architect” (AIA Contract Documents).

A201-2017 gives the architect a response duty for RFIs. Section 4.2.14 reads:

The Architect will review and respond to requests for information about the Contract Documents. The Architect’s response to such requests will be made in writing within any time limits agreed upon or otherwise with reasonable promptness.

Submittals get a similar clock in section 4.2.7:

The Architect’s action will be taken in accordance with the submittal schedule approved by the Architect or, in the absence of an approved submittal schedule, with reasonable promptness while allowing sufficient time in the Architect’s professional judgment to permit adequate review.

The full form is sold by AIA Contract Documents. Public owners often post their copies, and the text above is from the A201-2017 posted by Tri-County Technical College in South Carolina.

So “within any time limits agreed upon” sends you to your own documents. Look in the owner-architect agreement, the specifications and the approved submittal schedule. If a project has a stated number of days, that number is the deadline triage should read. If it doesn’t, “reasonable promptness” is the standard, and a crew waiting on site is what makes promptness unreasonable fast.

That’s the case for putting the RFI number and reply date in the subject line. The AIA’s G716 summary says RFIs “should be numbered, logged and tracked.” The log lives in your project system. The subject line is how the inbox knows the date.

A priority order for a practice inbox

Four groups cover almost everything a small practice receives. Each one has a plain test.

GroupThe testWhat goes here
Holding up the jobSomeone can’t work until you answerA site question with a crew waiting, an RFI at or past its reply date, a submittal on the critical path, a safety issue
Has a dateIt carries a deadline, and the deadline isn’t todayA client decision due Friday, plan review comments with a resubmittal date, a consultant comment you need before an issue
Needs you sometimeIt needs your judgment, with no date pressingA fee question, a new project inquiry, a team question, a substitution request still early in its window
Needs nothing from youYou’re copied, or it’s information you’ll find again if you need itCC’d coordination, transmittal receipts, meeting accepts, newsletters, product launches

Two cautions keep this honest.

Dates move between groups. A client decision due Friday is “has a date” on Monday. By Thursday it’s holding up the job. So each pass re-reads the dates.

“Needs you sometime” is where important mail gets lost. A new project inquiry has no deadline and a large consequence. It sits below the urgent pile every day until the prospect goes elsewhere. Give this group a fixed slot, say the last pass on Tuesday and Thursday. Important versus urgent explains why this group loses every time without one.

A Tuesday morning, ranked

Here’s what that order looks like on one morning in a five-person practice. It’s 8:30, and 58 messages came in since yesterday afternoon. Ranked by the three questions, the top of the list reads like this.

  1. 24-117 Maple St library. The contractor’s superintendent asks where the stair stringer bears. Framing starts Thursday. Holding up the job.
  2. 24-117 Maple St library. RFI 14, handrail extension, has a reply date of tomorrow under the project’s agreed response time. Holding up the job by tomorrow.
  3. 25-032 Ortega house. The client asks to move the kitchen window. Your consultant’s lintel comment is due Friday. Has a date.
  4. 25-008 Elm Ave mixed-use. The city’s plan review letter gives a resubmittal date three weeks out. Has a date, and it goes on the calendar today.
  5. New inquiry. A school board asks whether you’d take a small renovation. Needs you sometime, and it gets Thursday’s slot.
  6. 24-117 Maple St library. Three emails between the engineer and the contractor, with you copied. Needs nothing from you yet.

The last 40 or so are supplier news, calendar accepts and receipts. They can wait until the afternoon, or forever.

Notice that Maple St holds three places, in three different groups. Sorting by project alone would bury the stair under the CC’d chatter. Sorting by sender alone would split the job three ways.

Running it by hand in Gmail or Outlook

You can run this order with the inbox you already have. It takes discipline more than software.

Make the subject line carry the job. Put the project number first, then the subject, then the date if there is one. “24-117 Maple St: RFI 14 handrail, reply by Oct 9” can be sorted, searched and ranked by anyone in the office. Ask your contractors and consultants to use the same format. Most will, because it helps them too.

Triage at set times. One well-known version is the 3-21-0 method. Ben Meer describes it as “3 email processing sessions daily, 21 minutes per session, 0 emails left,” and credits the author Kevin Kruse (Ben Meer). For a practice, the zero matters less than the rhythm. A pass at 8:30, one after lunch and one before you leave keeps site questions answered the same day.

Make one decision per message during the pass. Put it in a group. Don’t answer anything except what’s holding up the job. Replying as you go is how a 20-minute pass becomes an hour and a half.

Use the mailbox’s own grouping for the four groups. Gmail does this with labels. Outlook does it with categories and flags. How to build either is covered in our own guides: Gmail labels that work and Outlook folders, and rules that fill them.

Know what the mailbox can’t see. A rule can match a project number or a sender. It can’t read “framing starts Thursday” and know that makes the message urgent. That judgment stays with you on every pass. Both mailboxes also offer their own sense of what matters, in Outlook’s Focused Inbox and Gmail’s priority inbox. Those sort by sender and habit, which is the axis a practice needs least. Where Focused Inbox falls short and where Gmail’s priority inbox falls short go into each.

By hand, this works well up to a few dozen messages a day. Past a hundred, the deciding takes longer than the reading. How email triage works has the research on where hand triage breaks.

Triage with AI built into your mailbox

Microsoft and Google both now offer AI inside the mailbox. Microsoft’s support page describes a “Summary by Copilot” button at the top of a thread in Outlook (Microsoft Support). Google describes a “Summarize this email” button in Gmail, powered by Gemini (Google Workspace).

A summary helps once you’ve decided to open a thread. Triage is the decision before that. When you weigh any AI tool for a practice, ask three questions:

  • Does it know the project? Can it tell that three threads from three senders are one job?
  • Does it read the date? Can it see “reply by Oct 9” or “framing starts Thursday” and rank on it?
  • What can it do next, and who approves that? A ranked list is useful. A reply sent to a client without review may not be what you want.

What Copilot in Outlook can’t do covers Microsoft’s version in detail. An email assistant for architects covers choosing between software and a person.

How Point runs this triage for you

Point reads and ranks your mail as it lands, so the order above is waiting when you sit down. It weighs how important each message is and how urgent it is, together. The superintendent’s stair question leads your feed. The CC’d chatter sits below it.

Here’s what that looks like on a practice’s Tuesday.

  • The people who matter are marked once. Star the client and the contractor’s project manager on a live job. Their mail weighs more from then on. VIP mail that never gets buried covers who belongs on the list.
  • Every thread carries a one-line summary. You see that the engineer agreed the lintel before you open eleven replies. How to catch up on a long email chain shows how.
  • What can wait comes back when you choose. Set the school board inquiry aside until Thursday at 4:00. It returns to the top then.
  • Point watches for what you’re waiting on. Say it once: “When the revised calcs for 24-117 arrive, put the RFI 14 reply on my list.” When they land, Point prepares the task. Nothing is created yet. It waits for you, and one click is your go.
  • The ranking travels with your mail. On Gmail, Point’s groups show as labels on your account, so your phone and your desk agree.

Each kind of action has its own setting. Review is the default, so ranked mail, drafted replies and prepared tasks wait for you. You can raise a setting when you’re comfortable. At the top of the dial, Point handles that kind of task without asking. Setting how much your inbox does on its own walks through it.

The first read of the day is its own job. Everything today asks of you, in one read covers the briefing. Point is the short version, and the benefits page is the full list.

Common questions

What is the best way to triage emails?

Make one pass at a set time and make one decision per message. Sort each one into needs me now, needs me later or needs nothing, and answer only the first group during the pass. Rank on both importance and urgency, because a message can carry one without the other. In an architecture practice, read the project and the date first, and the sender’s role third.

What does the 3-21-0 email rule mean?

It’s a batching habit: three email sessions a day, 21 minutes each, aiming for zero messages left unsorted. Ben Meer describes it and credits the author Kevin Kruse. The useful part for a practice is the fixed sessions. They protect drawing time and still get site questions answered the same day.

What is the typical email format for an architect?

Put the project number and name first in the subject, then the topic, then any date. “24-117 Maple St: RFI 14 handrail, reply by Oct 9” is a good model. In the body, lead with the question or decision you need. Give the drawing or spec reference, the revision you’re working from and the date you need an answer. Close with your name, firm and phone number. Attach single sheets, and link full sets with a transmittal that says what’s in them.

What are the 5 C’s of email etiquette?

The usual list is clear, concise, complete, correct and courteous. For a practice, “complete” does the most work. An RFI reply that names the sheet, the detail and the revision gets acted on. One that says “see attached” starts another round of email.

Should the principal triage the practice inbox, or someone else?

Someone can triage for you if they know the projects and the contract dates. The awareness is harder to hand over than the replies. Many principals keep the first pass and hand off the answers. An email assistant for architects covers what to hand over and what to keep.

Is this about buying architect email lists?

No. This page is about the inbox your practice already runs. Lists of architects’ addresses for marketing are a different job with different rules, which the practice inbox points to.

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.