Catch Up on a Long Faculty or Sponsor Thread with Copilot in Outlook

What This Does

You are added to a thread with forty replies about a subaward, a budget change or a late biosketch. Copilot in Outlook scans the conversation and puts a summary at the top, so you can see where things stand before you read the whole chain.

The summary tells you where to look. The messages themselves tell you what was actually said.

Before You Start

• Your Outlook has Copilot, which needs an eligible Microsoft 365 subscription or Copilot license. Microsoft's page distinguishes new Outlook from classic Outlook and from Outlook for Mac, so the labels below differ by version. If you see no Copilot icon or summary box, ask your IT group about licensing. Pricing is on Microsoft's own pages.
• Check your institution's AI guidance first. A faculty or sponsor thread may hold unpublished research details, personnel matters or budget figures, and whether that content may go into an AI feature depends on that guidance. Use only a tool your institution approved for that kind of data. If the thread is too sensitive, read it by hand.
• You know what you need from the thread, such as decisions, promises, dates and open questions.

Steps

1. Find the AI feature

Select the conversation in your inbox. Microsoft's help page gives these labels:

• New Outlook: the Summary by Copilot box at the top of the thread.
• Classic Outlook: select Summarize at the top of the thread.
• Outlook for Mac: select Summarize in the Summary by Copilot box.
• iOS and Android: select the Copilot icon in the toolbar. The summary appears under the email.

Copilot scans the thread for key points and writes the summary. Microsoft's page says the summary may include numbered citations, and that selecting one takes you to the matching email in the thread. Use them.

2. Tell it what you need

Microsoft's page describes the summary as automatic and does not describe a place to type instructions into it. So use it to orient yourself, then build the four lists you actually need from the messages it points to:

1. What was decided.
2. What each person said they would do.
3. Every date mentioned, and what each one refers to.
4. Questions still open.

If your version of Outlook also shows a Copilot chat, you can ask for those four lists there. Treat that answer the same way: a map to the messages, never a replacement for them.

3. Review and use the result

Go to the original messages for anything touching dates, money or scope. A summary can compress "we may need to extend" into "an extension was agreed." Open each cited message and read the sentence.

Then write your own short note: decisions, promised actions with names or codes, dates, and open questions. Put it in your tracker or in a reply to the thread.

Do not forward the summary to a sponsor, a subrecipient or a faculty member as if it were a record of the conversation.

Real Example

Scenario: You inherit a thread about Subaward S-12 (invented), 38 messages between PI A, Person B in the department and the sponsor's grants officer, with the subrecipient copied in.

What you do: Select the thread and open Summary by Copilot.

What you get: A short summary saying the subaward paperwork was waiting on a signature, that Person B promised to send a revised scope statement, and that a date in the second week of November was mentioned. It includes numbered citations.

What you check: Open each citation. Suppose the November date turns out to be the subrecipient's hoped-for start, not an agreed one. The summary blurred the two, and you would have put the wrong date in your tracker. Write "start date proposed, not confirmed" and ask Person B to confirm.

Tips

• Open the citation for every date or promise before acting on it.
• Keep names out of anything you paste elsewhere. Use codes such as PI A and S-12.
• For threads about people (hiring, performance, personal circumstances), skip the feature altogether.

Tool interfaces change. If a button has moved, look for Copilot or a summary option near the top of the message list or the open thread.