Skip to content

Email to task for architects: turning site mail into a list you can work through

On this page

Architects turn emails into tasks by reading each message for the asks inside it and writing every ask down on its own. Each task gets a verb, the project number, one person who does it, a due date and the email it came from. One contractor email after a site meeting often holds four or five of these. The flag on that email holds none of them.

Below, a typical site email is worked through line by line. After it come the dates, the asks that belong to someone else, and the tools you already have. If you came here looking to buy a list of architects’ email addresses, that’s a different search, and your own inbox, not a list of architects explains the split.

Email to task for architects in five fields

A task you can act on in a week’s time has five parts. Leave one out and you end up opening the email again to rebuild it.

FieldWhat goes in itExample
ActionA verb and the specific thingConfirm which detail governs at the Stair 2 landing
ProjectNumber and short name23-041 Harbor Rd library
OwnerOne named personYou
DueA day, and why that dayThursday, so the fabricator has it Friday
SourceA link to the email it came fromThe contractor’s Tuesday recap

One word needs care in a practice. In this page, the owner of a task is the person who does it. Your contract uses owner for the client, so a column called owner on a shared list can mislead a new hire. Some practices label it “who” for exactly that reason.

The source link earns its place later. A task is a summary of an email, and summaries lose detail. The link puts the contractor’s own words one click away when the task says “confirm detail” and you’ve forgotten which one.

One site email worked through

Here’s the kind of message that lands on a Tuesday afternoon. It’s a recap from the contractor’s project manager after a site meeting.

Subject: Harbor Rd: site meeting recap

Thanks for coming out today. What we need from your side:

  1. Stair 2 handrail at the landing doesn’t match the structural drawings. Which governs? Our fabricator needs it by Friday to hold the steel order.
  2. The client wants to see the tile samples on site, not just the board. Can Maria bring them Thursday?
  3. RFI 14 (roof drain at grid C) is still open. Has your MEP engineer looked at it?
  4. We’re pouring the slab on the 22nd. The inspector’s booked.
  5. Revised door hardware schedule attached, rev C.

Five numbered points. Here’s what they turn into.

From pointTaskOwnerDue
1Confirm with the structural engineer which handrail detail governs, then answer the contractorYouThursday
2Bring tile samples to siteMariaThursday
3Answer RFI 14 on the roof drain at grid CYouThe RFI’s agreed response date
5Review door hardware schedule rev C and return itYouPer the submittal schedule

Point 4 isn’t a task for you. It’s a date. Put it on the calendar, and if you plan to be there for the pour, that’s a site visit to book.

Point 3 holds two things. Answering the RFI is yours. The MEP engineer’s comment is something you’re owed. Write the task as the answer you’ll send, and keep the engineer’s part as a separate wait. Tracking what you’re owed a reply on covers that half.

Point 5 came with an attachment. The task is to review it. Filing rev C so nobody works from rev B is its own job, and the drawings page covers that one.

Look at what a flag would have kept. One marker on one email called “Harbor Rd: site meeting recap”. Four pieces of work for two people, with three different due dates, sitting behind it.

Where the due date comes from

Some dates are in the email. “By Friday” is easy, as long as you count back to the day you need to act. The fabricator needs it Friday, so your answer goes Thursday.

Other dates live in your documents. RFI and submittal response times are set by your contract and your approved submittal schedule. Why RFIs and submittals carry their own clock quotes the AIA A201 clauses that set them. When a contractor’s email doesn’t say when, the contract usually does.

The rest you choose. “Can you take a look at the revised elevations?” has no date in it at all. Pick one while the email is open. A task with “soon” on it sits on the list and never moves up.

One owner for each ask

A task with two names on it has nobody’s name on it. Each person thinks the other one has it. In a small practice that’s the most common way a site ask goes quiet.

So every ask gets one person. Three kinds of ask come in, and each needs a different home:

  • Yours. It goes on your list.
  • A colleague’s. Hand it to them by name, with the email attached. Maria needs to know it’s Thursday and that the client asked.
  • Someone outside the practice. That’s a wait, not a task. The consultant’s comment, the client’s decision and the contractor’s revised schedule are all things you’re owed. Chasing a client’s approval has the emails for when they go quiet.

The 3 email rule and the site thread that needs a call

People asking how to manage project email often meet the three email rule. MediaPost credits it to Phil Simon, author of Message Not Received:

after three messages, it’s time to talk.

It means a thread that hasn’t settled in three emails gets a phone call instead of a fourth.

It fits site work well. A handrail clash bounced between contractor, engineer and you can run to fifteen replies. A ten-minute call settles it. Then send one short email that records what you agreed, so the decision sits in the project record. The task comes from that recap, not from the fifteen replies before it. If the thread is already long, the RFI thread summary page shows how to read it as decisions and open items.

Running it by hand in Gmail or Outlook

Most practices start here. Each approach turns an email into something, and each one breaks at a different point.

Flag it and review the flags. Mark LePage of EntreArchitect describes the classic version: anything over two minutes goes to your task manager. It works when one email holds one ask. A site recap holds five, and the flag covers all five as one.

Gmail’s Tasks panel. You can drag an email into Tasks to make a task from it. That’s one task per email. You split the five asks by hand.

Outlook’s flag and Microsoft To Do. A flagged email shows up in To Do as a task. Microsoft’s support page is clear about what that task is called:

the task’s name will be the subject of the flagged message and will include a preview of the email’s text in its detail view.

So the Harbor Rd recap becomes one task named “Harbor Rd: site meeting recap”. The same page says flags from shared mailboxes don’t sync. If your practice runs a projects@ address, that mail stays out of the list.

An automation. Tools like Zapier can create a task when you flag an email. On Zapier’s free plan, its Outlook to To Do workflow checks every 15 minutes. It still starts from your flag, so it still turns one email into one task.

All four share the same gap. You do the reading, and you split the asks. On a quiet day that’s fine. On the day of three site meetings, it’s the step that gets skipped.

Your project software keeps its job through all of this. The AIA’s G716 summary says RFIs “should be numbered, logged and tracked through a document management logging system.” If RFI 14 belongs in that log, log it there. The task in your list is the reminder that the answer is yours and when it’s due.

What Point does with a site email

Point is an email client, so it reads your mail as it lands. When the Harbor Rd recap arrives, Point lifts out each ask as its own task. The handrail, the RFI and the hardware schedule each get a date, and each one opens on the contractor’s own words. Nothing is typed in. Email task management, without writing it down explains how Point finds the ask and the date.

Your tasks are yours. Point doesn’t assign tasks to other people, so the tile samples go to Maria the way you’d tell her anyway. Team messages sit in the same feed as client mail. “Tile samples to site Thursday, the client asked” sits right beside the recap it’s about.

The engineer’s comment on RFI 14 is held as something you’re owed. It comes back when it’s worth chasing.

When you’ve done your part, Point notices. You reply to the contractor about the handrail, and Point marks that task as looking done. It shows you why, and it waits for you to agree.

If you know a reply is coming, you can line up the next step. “When the MEP engineer answers on RFI 14, make a task to respond to the contractor.” When the answer lands, Point prepares the task. When a watch lines up the work shows how that reads.

How far Point goes is your call, and tasks get their own setting apart from drafts. On a new account, a task Point finds waits for your review. At the top of the dial, Point creates it without asking. The dial sets out the three positions. Everything else Point handles is on the benefits page, and Point for architects shows it across a practice.

Common questions

How do architects turn emails into tasks?

Read each email for the asks inside it and write each ask as its own task. Each one needs a verb, the project number, one person who does it, a day it’s due, and the email it came from. A site recap with five points usually becomes three or four tasks, one calendar date and one thing you’re waiting on.

What is the 3 email rule?

It’s the idea that if a thread hasn’t settled in three emails, you pick up the phone. MediaPost credits it to Phil Simon, author of Message Not Received. For a practice, the useful half is what comes after the call: a short email recording what you agreed, so the decision is in writing.

Should an RFI be a task or go in the project log?

Both, for different reasons. The log is the project’s record, and the AIA’s guidance is that RFIs are numbered, logged and tracked. The task is your reminder that the answer is yours and when it’s due.

What if the ask is for someone else in the practice?

Give it to one person by name, with the email attached and the date stated. Point keeps each person’s tasks personal, so the handoff happens in a team message beside the thread.

What’s the difference between a task and something I’m waiting on?

A task is work you do. A wait is work someone else owes you, like a consultant’s comment or a client’s sign-off. Keep them on separate lists, because you act on them differently. You do a task. You chase a wait.

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.