Skip to content

Email thread summaries for architects: an RFI chain in one paragraph

On this page

Architects can summarize a long email thread by reducing it to three short lists: what was decided and by whom, what’s still open, and who owes what by when. Then add one line for anything that touches cost or time, because that’s where an RFI thread stops being a question and starts being a change. Read the last message first, find the original question, and write those lists in your own words. On a project thread, that paragraph is the version you act on and file.

  • Decided. Each decision names the person who made it and the message it’s in.
  • Open. Each question still unanswered, in one line.
  • Who owes what. A name, an item and a date. “Structural to confirm” isn’t enough. “Priya owes the reinforcement detail by Wednesday” is.
  • Cost or time. If anyone has said “this adds,” the thread needs a change process, not another reply.

This page is about the threads your practice already runs with contractors and consultants. How the whole practice inbox works, from the morning read to drawings and the archive, is in the practice inbox.

What an email thread summary for architects holds

A thread on a live job can run to thirty replies from five firms. You don’t need the story. You need where it landed, so the summary has a fixed shape. Use the same shape every time and you’ll read your own summaries in seconds.

LineWhat goes in itExample
SubjectProject number, RFI or submittal number, a few words2417 · RFI 014 · beam vs. duct at C/4
DecidedThe decision, who made it, which messageStructural accepts two 8-inch web penetrations with reinforcement (Priya, Tue)
OpenEach question without an answerDoes the client accept the added cost?
Who owes whatName, item, dateYou: written RFI response by Wed. Client: yes or no on cost
Cost or timeAnything priced, delayed or “extra”Contractor says $3,800 and two days
SourceThe attachment or sketch the decision rests onSK-S-07, attached to Priya’s Tuesday reply

The last line matters more than it looks. On a project thread, the answer is often in a marked-up PDF, not in the email text. A summary that says “see sketch” without naming the sketch sends you back into the thread.

How email threads form, and why one RFI ends up in three

An email thread is the set of replies your mail client groups together. You create one by replying to a message, and every reply or reply-all keeps adding to it. You start a new one by writing a fresh message or changing the subject line.

Both big mail clients group on the subject line. Google’s Gmail Help sets out when a thread splits:

A conversation breaks off into a new conversation when the subject line changes, or the conversation gets to more than 100 emails.

Microsoft’s Outlook support page defines it the same way: “A conversation includes all messages in the same thread with the same subject line.”

That rule is simple, and a project chain breaks it constantly. Here’s how one RFI turns into several threads:

  • You forward it to a consultant. The “Fwd:” starts a side thread the contractor never sees.
  • Someone replies to one person. A reply instead of a reply-all forks the chain into two copies with different endings.
  • Somebody edits the subject. “RFI 014” becomes “RFI 014, revised duct,” and your client now shows two threads.
  • A new person joins late. They get the history as quoted text underneath, not as messages of their own.

So the thread in front of you is your copy of the conversation, not the whole of it. A decision can sit in a side thread with the engineer, or in quoted text from a message you were never sent. How to catch up on a long email chain goes into quoted history and late arrivals in detail.

The habit that keeps an RFI in one place is cheap. Put the project and RFI number at the start of the subject, and ask everyone to reply-all on the original. A subject format for the whole practice is in email triage for architects.

A long RFI thread, in a paragraph

Here’s a real-shaped example. Job 2417 is a three-story mixed-use building. Ridgeline Builders’ project manager, Dana, finds a supply duct that won’t fit under a steel beam above the retail ceiling. Over two days the chain picks up a structural engineer, a mechanical engineer and the client.

WhenFromWhat they said
Mon 7:40Dana (contractor)RFI 014: can the beam at C/4 drop 2 inches so the 10×16 duct fits? Photo attached
Mon 9:15YouForward to Priya (structural) and Tom (mechanical) in a separate thread
Mon 2:30PriyaThe beam can’t drop. Web penetrations up to 8 inches are fine with reinforcement. Sketch SK-S-07 attached
Mon 4:05TomThe 10×16 could become two 8-inch round ducts
Tue 8:10Dana, reply-all on the originalFraming crew is there Thursday. Need an answer by Wednesday
Tue 9:00Marcus (client), added by DanaDoes this lower the retail ceiling?
Tue 11:20Tom, in the side threadTwo 8-inch rounds work. Minor rebalancing only
Tue 1:45You, to Marcus onlyNo, the ceiling stays as drawn
Tue 3:30DanaReinforcement and two round ducts add $3,800 and two days

Nine messages, three threads, five people. Here’s the paragraph:

2417 · RFI 014 · beam vs. duct at C/4. Structural won’t lower the beam but accepts two 8-inch web penetrations with reinforcement per SK-S-07 (Priya, Mon). Mechanical accepts two 8-inch round ducts in place of the 10×16 (Tom, Tue, side thread). The retail ceiling stays as drawn (you to Marcus, Tue). Open: Ridgeline prices the fix at $3,800 and two days, and Marcus hasn’t answered. You owe the written RFI response by Wednesday. Marcus owes a yes or no on cost. Framing starts Thursday.

Notice what the paragraph does that the thread can’t. It pulls Tom’s answer out of the side thread Dana never saw. It records the ceiling answer you sent to Marcus alone. And it puts the $3,800 in plain sight, which is the one line that changes what happens next.

When “agreed” in a thread is a decision

This is the place a summary can mislead you, so it’s worth a minute. Everyone in the chain above “agreed” to the fix. On most projects that still doesn’t make it a change to the contract.

If you’re on AIA general conditions, A201-2017 separates an answer from a change. Section 4.2.14 sets the architect’s side of an RFI:

The Architect’s response to such requests will be made in writing within any time limits agreed upon or otherwise with reasonable promptness.

That response is yours to give. A change to cost or time needs more people. Section 7.2.1 defines the instrument:

A Change Order is a written instrument prepared by the Architect and signed by the Owner, Contractor, and Architect stating their agreement upon all of the following: .1 The change in the Work; .2 The amount of the adjustment, if any, in the Contract Sum; and .3 The extent of the adjustment, if any, in the Contract Time.

So three signatures, on a written instrument. A reply-all saying “works for us” isn’t that. Here’s how the common thread phrases map onto A201-2017:

What the thread saysWhat it is under A201-2017Who has to sign
“Here’s our answer to RFI 014”RFI response, section 4.2.14You, in writing
“Go ahead, no cost or time impact”Minor change in the Work, section 7.4You, in writing
“Agreed, with the extra cost and days”Change Order, section 7.2.1Owner, contractor and you
“Proceed while we settle the price”Construction Change Directive, section 7.3.1Owner and you
“This adds cost” from the contractorPossible Claim, section 3.2.4Goes through Article 15

AIA’s own summary of the G716-2004 RFI form says the same from the RFI side:

Neither the request nor the response received provides authorization for work that increases the cost or time of the project.

The contractor’s “this adds cost” line deserves its own flag. Section 3.2.4 sends that belief into the claims process. Section 15.1.3.1 gives claims a 21-day window from the event or from when the claimant first recognizes it. And section 1.6.2 says a claim notice is only served by certified or registered mail, or by courier with proof of delivery. Ordinary contract notices can go by email only if your agreement sets out a method for it, under section 1.6.1. So the email isn’t the notice. It’s the early warning that one may follow.

Two caveats. Many owners modify A201, so check your own agreement before relying on these section numbers. And this is how the form reads, not legal advice on a dispute. What a good summary does is make the “Cost or time” line impossible to miss, so the item leaves email and goes into your change process while it’s still small.

Summarizing a thread by hand

You can do this well in about ten minutes with nothing but your mail client. It works best on the threads that will matter later.

  1. Gather the pieces. Search the project and RFI number across your mailbox. Pull in the side threads and the forwards, not just the thread on screen.
  2. Read the last message first. It tells you where things stand now. Then read the first, which tells you what the question was.
  3. List who’s in it and what each represents. “Tom” means nothing in a year. “Tom, mechanical engineer, Hartwell MEP” does.
  4. Mark every change of position. The contractor who said “can’t” on Monday and “can” on Wednesday matters more than either message alone.
  5. Write the paragraph in the fixed shape. Decided, open, who owes what, cost or time, source.
  6. Send it back to the thread. Reply-all with the summary at the top and “please correct anything I have wrong by Wednesday.” Silence isn’t agreement under the contract, but it does surface mistakes early.
  7. File it with the project. Paste the paragraph into your RFI log next to the formal response.

Step six is the one most practices skip, and it saves the most. It sets one written account everyone has seen. A year from now, that message is what you’ll search for. Finding it again is covered in the practice inbox.

The step that takes longest by hand is the first one. Gathering three threads from five people is tedious when the subject lines don’t match.

How AI summaries handle a contractor and consultant chain

Microsoft and Google both summarize a thread from inside the mailbox. Microsoft’s support page says a Copilot summary in Outlook “will appear at the top of the email and may also include numbered citations” that take you to the message it came from. Google describes a “Summarize this email” button at the top of a thread in Gemini in Gmail (both checked October 4, 2026). The citations are worth a lot on project mail, because you can check a decision against the sender’s own words.

On a multi-party construction chain, AI summaries do well and strain in predictable places.

They do well at the reading. Thirty replies with long signatures and quoted history are tedious for a person and quick for software. The “who said what” in a single thread usually comes out right.

They strain where the thread is incomplete. A summary of the thread in front of you can only see that thread. Tom’s answer in the side thread and your note to Marcus alone won’t appear unless the tool looks across threads. One Microsoft Q&A answer from March 2026, a community reply rather than formal documentation, says Copilot Chat without the paid add-on is “mostly limited to the currently open email or thread.”

They strain on superseded answers. “Can’t drop the beam” on Monday and “two penetrations work” on Tuesday can both end up in a summary as if both were current. This is the error to watch for, because it looks plausible.

They strain on roles. Software sees names and email domains. It doesn’t know that Hartwell is your mechanical engineer or that Marcus is the owner. A decision attributed to “Tom” is fine today and opaque next spring.

They strain on the attachment. When the answer is a sketch, a summary that reads only the email text reports “Priya sent a sketch,” not what the sketch says.

They don’t know your contract. No general-purpose summary will flag that a priced fix needs a change order. You add that line yourself, or you tell your tool to.

So when you weigh any AI summary for practice mail, ask four things:

  • Can it see across threads that share a project or RFI number?
  • Does it say which message each decision came from?
  • Does it lead with the current position, not the history?
  • Can you tell it once how your project summaries should be shaped?

Microsoft’s version is covered in more detail in what Copilot in Outlook can’t do. Choosing between software and a person for this work is in an email assistant for architects.

How Point keeps the paragraph current

Point is an email client that runs on your existing Gmail or Microsoft 365 mailbox. Every thread is summarized by the time you look at it, so RFI 014 reads in a line before you open nine replies. The full thread is one click away when you want the detail.

Here’s what that looks like on the job above:

  • The pieces come together. The sketch, the site meeting and the task that came out of RFI 014 open together with the thread. SK-S-07 stays tied to Priya’s reply.
  • You say the shape once. Tell Point that project summaries should lead with what’s agreed, what’s open and who owes what. Point holds onto that instruction, and you can see it and edit it later. How a summary learns from your edits explains how.
  • Your Wednesday deadline becomes a task. When a message asks something of you, it lands on your list with the date and the thread attached. Email task management, without writing it down covers it.
  • Marcus’s answer on cost comes back to you. Point tracks what you’ve handed off, and you hear about it when it’s worth chasing. Tracking what you are owed a reply on has the rest.
  • The answer in the sketch is one question away. Ask what SK-S-07 says about reinforcement. You get the answer and a link to the spot in the PDF it came from. Ask a question, get the answer out of the attachment shows it.

Point can draft your reply-all summary, too. By default it waits for you. Review is where every kind of action starts, and you can raise the setting one action type at a time. At the top of the dial, Point handles that kind of action without asking. Setting how much your inbox does on its own walks through it. The change order itself stays in your project process, signed by the people the contract names.

RFI 014 reaches the top of your morning through a daily email briefing for architects. For the wider picture, see Point for architecture practices and the benefits page.

Common questions

How do you create an email thread?

You create a thread by replying to a message. Each reply or reply-all adds to the same thread, as long as the subject line stays the same. Gmail and Outlook both group messages by subject, so editing the subject or writing a fresh message starts a new thread. Gmail also splits a thread once it passes 100 emails.

How can architects summarize long email threads?

Reduce the thread to what was decided and by whom, what’s still open, and who owes what by when. Add a line for anything that changes cost or time, and name the drawing or sketch each decision rests on. Read the last message first, gather the side threads, and send the summary back to everyone so mistakes surface early.

Can I trust an AI summary of an RFI thread?

Trust it for the reading and check it for the one claim you’d be embarrassed to get wrong, usually a dimension, a price or a date. Open the message the decision came from and read the sender’s own words. The common error isn’t an invented fact. It’s an old answer reported as current.

Does an email in the thread count as written notice under the contract?

It depends on your agreement. Under AIA A201-2017, ordinary notices can go by electronic transmission only if the agreement sets out a method for it. Notice of a claim has to go by certified or registered mail, or by courier with proof of delivery. Check your own contract, because many owners modify A201.

What if one thread covers two RFIs?

Split them. Reply on a new subject line with the second RFI number, and say in the old thread where the new one lives. One RFI per thread keeps the summary, the log and the search all pointing at the same record.

Should the summary go in the RFI log or the email?

Both. The email puts one account in front of everyone and invites corrections. The log is the record the AIA form expects to be numbered and tracked. Your project software holds the log, and email is where the question first arrives.

I searched for architect email lists. Is this the right page?

Probably not. This page covers summarizing the project threads already in your inbox. Buying contact lists to market to architects is governed by commercial email law, and the practice inbox points to the rules for that.

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.