Team coordination
Use ChatGPT to Turn a Vendor Email Thread into a Follow-Up Checklist
Cihan's view: Upload an approved email export, ask ChatGPT to separate quoted facts from inferred actions, and review the checklist against each message before assigning work.
What you will make
A follow-up checklist from a fictional vendor email thread. The checklist will show each request, the person named in the thread, any stated date, the message that supports it, and what still needs a decision.
This is a documentation-based guide. The messages and output are illustrative. OpenAI’s File Uploads FAQ says ChatGPT can search documents, extract specific sections, and analyse uploaded spreadsheets or other supported files. Availability and limits depend on the account.
Before you start
You need:
- ChatGPT on the web or a supported mobile app with file uploads available.
- Permission to use the export. Do not upload a real customer or vendor thread to an account your organisation has not approved.
- A text file containing the complete fictional thread below.
Create vendor-thread.txt:
From: Lena at Northstar Supplies
Date: 2026-10-06
Subject: October packaging order
We can hold the October price if we receive the final quantity by Friday, 9 October. Please confirm whether you need the standard cartons or the reinforced cartons.
From: Arda, Operations
Date: 2026-10-07
We need the reinforced cartons for the glass shipment. I will confirm the quantity after the warehouse count.
From: Lena at Northstar Supplies
Date: 2026-10-07
Thanks. We can reserve production space, but the reservation is not a confirmed order. Please send the quantity and delivery address. Our current estimate is delivery during the week of 19 October, subject to production capacity.
From: Arda, Operations
Date: 2026-10-08
The warehouse count is still open. Cihan, can you confirm the delivery address? Also, I am not sure whether the Friday deadline means the start or end of the day.
The file is fictional. It contains an unresolved quantity, an address request, a conditional delivery estimate, and an ambiguous deadline. Those details are deliberate.
Three steps
1. Upload the complete thread
Start a new chat and attach vendor-thread.txt . Paste this prompt:
You are preparing a follow-up checklist from the attached vendor email thread. Use only the attached file.
Return a table with these columns:
- item
- type: request, commitment, estimate, question, or decision
- named person or organisation
- stated date or timing
- exact supporting quote
- source message date
- status: supported, unresolved, or not stated
Rules:
- Preserve the wording of every date and condition.
- Do not turn an estimate into a commitment.
- Do not invent an owner when the message does not name one.
- Do not answer the deadline question yourself.
- If the thread asks for a delivery address, mark the address as not stated.
- Include the unresolved carton quantity.
- After the table, list decisions a person must make before replying.
2. Run a source check
Paste this follow-up:
Audit the checklist against every message in vendor-thread.txt.
For each row, return PASS only when the item, person, timing, condition, and quote match the source. Return CHECK when the row contains an inference, missing information, or an ambiguous date. List any source sentence that did not appear in the checklist. Do not rewrite the checklist yet.
Read the quoted messages yourself. The audit is a review aid, not proof that the extraction is correct.
3. Separate reply material from internal work
Use a final prompt only after reviewing the audit:
Using only rows marked PASS, draft two separate blocks:
1. Reply questions for Northstar Supplies. Ask only for the quantity, delivery address, and clarification of the Friday deadline.
2. Internal follow-up tasks. Include an owner only when the source names one. Keep the delivery week labelled as an estimate and keep the order unconfirmed.
Do not send the message. Do not add a price, address, quantity, or deadline that is not in the source.
Copy the draft into your normal approval process. ChatGPT should prepare the material. A person decides what to send and who owns the work.
Illustrative output
| Item | Type | Named person or organisation | Stated date or timing | Status |
|---|---|---|---|---|
| Final quantity | Request | Arda, Operations | By Friday, 9 October | Unresolved |
| Carton type | Decision | Arda, Operations | Reinforced cartons requested | Supported |
| Delivery address | Request | Cihan is asked to confirm | Not stated | Unresolved |
| Delivery timing | Estimate | Northstar Supplies | Week of 19 October, subject to production capacity | Supported |
| Order status | Decision | Northstar Supplies | Reservation is not a confirmed order | Supported |
| Friday deadline meaning | Question | Arda, Operations | Start or end of day is unclear | Unresolved |
This table is an editor-written illustration, not a ChatGPT result.
Acceptance checks
The workflow passes when:
- Every row has a quote that appears in the source file.
- The quantity and delivery address remain unresolved.
- The delivery week keeps its condition and remains an estimate.
- The reservation is not described as a confirmed order.
- No person receives an invented owner or deadline.
- The audit lists any source sentence that the table missed.
If something goes wrong
- ChatGPT assigns Cihan the quantity: ask it to show the source quote. The thread names Cihan for the address question only.
- The delivery week becomes a promise: add the phrase to the acceptance check and rerun the audit.
- The model answers the Friday question: delete the answer and keep the question unresolved for the vendor.
- A message is missing: upload the complete export again, including headers and dates, then compare the message count manually.
Limits and privacy
Use the minimum approved text and remove unrelated personal data. File upload limits, retention, and organisational controls vary by account. This workflow extracts follow-up material. It does not approve a purchase, determine responsibility, or send a vendor reply.
Evidence label
Documentation-based guide with fictional email text and an illustrative checklist. No ChatGPT execution, measured result, or vendor communication is claimed.
Next lesson
For a source-linked document workflow, read Use ChatGPT to extract contract renewal dates into a review table.