ChatGPT for project managers: client updates, decisions and meeting prep
A project update can be beautifully written and still confuse a request with an approval. Start with a small evidence pack and make that distinction visible before using the draft with a client.
The useful starting point: give ChatGPT dated notes, the relevant change request and the decision that followed. Ask for a short update with evidence attached to each claim. Keep missing owners and dates visible instead of letting the draft fill them in.
OpenAI's Projects documentation, checked 21 October 2026, describes keeping related chats, files and instructions together. That is a practical home for a recurring engagement. For setup and memory behavior, see the Project memory guide.
One fictional project pack
Cedar is an invented client implementing a new onboarding process. The following three records are the entire evidence for this example; no real client data or product-test transcript is involved.
| Source | Dated record |
|---|---|
| A · Meeting note, 16 October | Go-live target for the new onboarding process: 9 November. Client HR manager to nominate two acceptance testers. No agreement yet on adding the reporting dashboard. |
| B · Client email, 19 October | Please have the dashboard ready at go-live. If that puts the date at risk, show us the tradeoff before changing the plan. |
| C · Decision record, 20 October | Sponsor approved go-live without the dashboard. Two acceptance testers have been nominated. Client IT lead must confirm whether the data migration finishes in time for 9 November. |
There are two traps. The dashboard request was not the final decision, and the go-live date is still a target, not a commitment. A status report that misses either can set the wrong expectation.
Prompt for a client-ready draft, with an evidence layer
Using only sources A, B and C, draft a Cedar status update under 180 words. Separate confirmed decisions, assumptions and unanswered questions. For each factual statement, include the source letter and date. Do not turn a target into a commitment. End with the decision or confirmation needed next. Do not assign a traffic-light status unless the sources establish the criteria.
A correct reading of the pack: go-live excludes the dashboard under source C (20 October), even though source B (19 October) asked for it; the two acceptance testers are nominated under C; 9 November remains a target until the client IT lead confirms the data migration. The next useful question is whether the migration finishes in time for go-live under the agreed scope.
Treat that reading as your marking key when you check a draft. It was worked out by hand from the three records; it says nothing measured about how often ChatGPT gets this right. If the response invents a green status, ask it to identify the evidence for green. If it cannot, remove the label from the report.
Make a decision log that preserves changes
A decision log needs more than the latest sentence. It should retain the request, the decision, the person authorized to make it and the source that shows it. For the Cedar example, ask:
Build a decision log with these columns: issue, request, current decision, decision source, outstanding confirmation. Keep superseded requests visible as history, not as active commitments. Leave the decision-maker blank if the source does not name one.
The dashboard row should distinguish the client's 19 October request from the sponsor's 20 October decision. The go-live row should still show the IT lead's migration confirmation as outstanding. That gives the next meeting a purpose: resolve the open item rather than reopen the settled one.
When a new message arrives, keep its original date. Do not overwrite yesterday's decision with today's proposal and lose the sequence. A brief is easier to trust when you can reconstruct how the current position was reached.
Review the draft against five failure checks
- Scope: did a requested addition become an approved deliverable?
- Timing: did a target become a promise?
- Ownership: did the draft invent a person responsible for an open item?
- Freshness: did it use the later decision rather than the earlier request?
- Audience: did an internal assumption appear as a client-facing fact?
Resolve these before polishing the tone. Then remove the working source labels from the client-facing version if your format requires it, while keeping the checked evidence alongside your internal record.
For repeated reports, compare two versions using the same source pack. Change one instruction, such as how uncertain dates are handled, and see whether it fixes the actual defect. More elaborate prompts are not automatically more useful.
Prepare the conversation, not only the report
A program lead often has the report already. The difficult moment is switching from another engagement and remembering which question is still open here. Ask for a three-line preparation note: the latest decision, the unresolved item and the question that should open the call.
For Cedar, the opening question is whether the data migration supports 9 November now that the dashboard is out of go-live. The dashboard is background unless someone proposes changing the decision again. This keeps a status conversation from becoming a tour of every document.
Keep selected client context with Equerry
Equerry can sit alongside your project system as your personal assistant. Forward the correspondence you want remembered and save your own decision notes. Team status and formal approvals remain in the system your team uses.
| What you send | Forward the client's 19 October dashboard email to your Equerry address, and save your 16 October meeting note and the sponsor's 20 October decision as notes. |
|---|---|
| What you ask | “What did Cedar's sponsor decide about the dashboard, and what is still unconfirmed for the 9 November go-live?” |
| What you get back | An answer from the records you sent that keeps the dates apart: the sponsor's 20 October decision to go live without the dashboard, the 19 October request it settled, and the 9 November target still waiting on the IT lead's migration confirmation. Where it draws on one of your saved notes, that note's source chip shows the passage and opens the original. |
If the Cedar status call is on your calendar, a Meeting Prep Routine saved with calendar access runs 15 minutes before it and builds a brief from what you sent that mentions the meeting's title or a person on the invite, which is why it helps to write names, not only roles, into your Cedar notes. Equerry does not update the project board, synchronize the firm's systems or send the status report; the update stays yours to write and send.
Frequently asked questions
How can project managers use ChatGPT?
Useful starting points are a draft status update, a decision-log review and a list of questions for the next client meeting. Supply dated evidence and distinguish confirmed decisions from assumptions.
Can ChatGPT write a project status report?
It can help draft one from supplied material. Review the evidence behind every status, owner and date before sharing it. A confident summary does not establish that a change was approved.
Should each client engagement have its own Project?
That is a useful organizational choice when you need to keep engagement material together. Define the scope, avoid mixing similarly named clients and review the account's available memory and sharing settings.
Does Equerry replace a project-management system?
No. It helps you recover selected client context and prepare for meetings. It does not maintain the team's board, synchronize project status or send updates for you.
Last updated 2026-10-21.
All product names, logos, and brands are property of their respective owners. Equerry is not affiliated with, endorsed by, or sponsored by any other product mentioned; comparisons are provided for informational purposes.