Use ChatGPT to draft a weekly update from your notes

ChatGPT can turn checked project notes into a short weekly update with the decision at the top. You will give it a small source, specify the structure, then ask it to expose unsupported optimism before you use the draft.

Give it the facts before asking it to make them sound better. Otherwise, the most reassuring part of the update may be the part with the least evidence behind it.

What you'll make

an update of no more than 150 words that names the progress, the problem and the decision somebody needs to make.

What you'll need

a short set of checked notes and an approved ChatGPT account. Plain text is enough. No project-system connection, transcript or automation is needed; normal account limits apply.

Practise safely: the example is fictional. For real work, follow your organisation’s data policy and omit details it does not permit in the chosen account. Removing a customer’s name may not remove the confidential information.

1. Collect facts before adjectives

Write down what happened, what is blocked and what is still unknown. “Good progress” can wait until there is enough evidence to earn it.

Here are fictional notes for the week ending 9 October 2026:

New booking form: 8 of 10 planned checks passed.
The remaining 2 need a supplier test account.
Supplier said "probably Monday 12 October"; no confirmation.
Target launch: Friday 16 October.
Need the operations director to name an escalation owner by 9 October.
Launch impact cannot be confirmed until testing is complete.

Notice the difference between a target, an estimate and a confirmed date. Keep those words in the notes. They are doing useful work.

Eight successful checks out of ten also does not mean that the whole project is 80% complete. It means eight checks have passed. Those statements have different ambitions.

2. Ask for the update you would want to receive

Open ChatGPT in your approved account, start a new chat and paste this prompt with the notes. This is a manual paste; ChatGPT is not reading your project system:

Write a weekly update of no more than 150 words from these notes.
Use four headings: Completed, Still open, Risk, Decision needed.
Put the decision in the opening sentence as well.

Keep dates and numbers exact. Distinguish confirmed dates from
estimates and targets. Do not infer an overall completion percentage,
invent a status colour or make the project sound healthier than the
evidence supports. If an owner, deadline or fact is missing, flag it.
Use only these notes as the source.

[Paste the notes.]

This is a drafting request, rather than a request to investigate the project. A short, bounded input makes checking the result easier. If more context is needed, add it deliberately instead of attaching the entire week’s correspondence.

3. Check the sentence that sounds most reassuring

Read the draft once looking only for claims. Phrases such as “on track”, “minor delay” and “delivery expected Monday” deserve attention. The supplier only said “probably Monday”, which can become a firm commitment after passing through enough presentations.

Compare the draft with the notes:

If the source says…	Keep it as…	Do not turn it into…
8 of 10 checks passed	Eight checks passed; two are blocked	80% of the project complete
Probably Monday	An unconfirmed supplier estimate	Delivery confirmed for Monday
Target launch 16 October	A target with impact still unknown	Launch remains on track
Need an escalation owner	A decision still required	An escalation already in progress

OpenAI warns that ChatGPT can give incorrect or misleading answers. A smoother sentence is not evidence that the facts have improved.

4. Make the ask easy to answer

The reader should be able to see who must decide, what they must decide and by when. If one of those is missing, keep the gap visible.

Review this draft against my original notes. Make the decision request
explicit: who needs to decide, what they need to decide and by when.
Mark anything missing. Remove optimistic wording that is unsupported.
List any factual claim in the draft that the notes do not support.
Do not invent a workaround, owner or date.

Here is an illustrative worked update, written to show the intended structure. It is not a captured ChatGPT response:

Decision: Please name an escalation owner by 9 October so we can obtain the supplier test account.

Completed: Eight of ten planned checks on the new booking form have passed.

Still open: Two checks are blocked by the missing test account. The supplier suggested 12 October, but that date is unconfirmed.

Risk: The effect on the 16 October launch target is unknown until testing is complete.

Decision needed: The operations director needs to name the escalation owner by 9 October.

This leaves a small amount of repetition because the decision is the point of the update. You can trim the closing line if your recipient’s usual format makes the opening request sufficient.

5. Read it once as the recipient

Can you see what changed, what is blocked and what is being asked of you without opening another document? Check every number and date against the notes. Check that the supposed decision is within the recipient’s authority to make.

Then decide whether to send it. ChatGPT has drafted the update; it has not obtained the test account or escalated anything. Keep those actions separate.

If the draft is too long, remove background before removing uncertainty. “Unconfirmed” is often more useful than another sentence about the work everyone has been doing.

6. Keep the structure, replace the facts

Save the prompt beside an update you have checked. Next week, replace the factual notes and identify the new decision. Do not leave last week’s risk, dates or owner in place because they happen to fit the template.

Keep the source notes so a follow-up question does not require reconstructing the whole week. An update should be a shorter view of the evidence, not its replacement.

Keep this: A useful update makes the next decision easier, even when the news is inconvenient.

Account settings and limits

Use your approved workspace and check its access and retention settings. OpenAI’s data-control guidance distinguishes personal-account choices from managed workspaces. Those settings do not replace permission to use confidential project material.

Sources and status

Checked 4 October 2026 against OpenAI’s accuracy guidance and data controls. All project notes and the worked update are fictional or illustrative. We have not run a live model test or measured time saved.

If your source is a meeting rather than weekly notes, try turning meeting notes into agreed actions.