A project update is a small piece of writing with an outsized job. It tells people whether to relax, whether to help, or whether to start worrying. Yet most updates are written in a hurry, padded with activity rather than progress, and read by nobody beyond the subject line. The result is that stakeholders ask for meetings to find out what the update should have told them, and the project manager spends more time explaining than managing.
This guide shows how to use AI to write better project updates, faster, without losing honesty. You will learn what a good update contains, how to feed an assistant the right raw material, how to draft for different audiences, how to report bad news clearly, how to keep status colours meaningful, and how to check what the assistant produces before anyone reads it. Templates are included throughout so you can adapt them to your own projects.
Key takeaways
- A good update answers four questions: where are we, what changed, what is at risk, and what do you need from the reader.
- AI is best used to turn your factual notes into clear prose. It should not decide the status, and it should never invent progress.
- Write different versions for different audiences. An executive sponsor, a delivery team and a client need different levels of detail.
- Report bad news early and plainly. An assistant can help with tone, but the facts and the decision to escalate are yours.
- Check every claim, date and number in a draft against your source notes before sending.
What a project update is for
The purpose of an update is to reduce uncertainty for the reader. It is not a diary of your activity, and it is not a way to show how busy you have been. A reader wants to know whether the project is on track, what has changed since last time and whether they need to do anything.
Consider the readers you actually have. A sponsor wants to know if the outcome is still achievable and whether they need to unblock something. A team member wants to know what is coming and who is doing what. A client wants reassurance and clarity, and does not want to wade through internal detail.
The four questions
- Where are we? A clear overall status in one sentence.
- What changed? The most important progress and any shifts since the last update.
- What is at risk? Issues, blockers and uncertain items, with their likely impact.
- What do you need from me? Decisions, approvals or help, with dates.
If an update does not answer all four, it is incomplete. The rest of this guide is about answering them efficiently.
A structure that works every time
Consistency makes updates easier to write and easier to read. When readers know where to look, they absorb the content faster and spot changes. Use the same headings every week.
| Section | Content | Typical length |
|---|---|---|
| Summary | Status and the single most important message | One or two sentences |
| Progress | What was completed since the last update | Three to five bullets |
| Next | What is planned before the next update | Three to five bullets |
| Risks and issues | What could or does threaten the plan, with owner | Short list |
| Decisions needed | What you need and by when | Short list |
| Dates | Upcoming milestones and any changes | Small table |
Put the summary first. Many readers will only read that, so make sure it is complete enough to stand alone. A summary such as Green overall, with one risk on supplier delivery that needs a decision by Thursday gives a reader everything they need in a line.
Keep it short
Aim for something a person can read in two minutes. If detail is needed, link to a longer document, but do not bury the message beneath it. Long updates are not more transparent, only harder to read.
Gather the raw material first
An assistant writes well from good notes and badly from vague ones. Before you open any tool, assemble the facts. This step is the real work of the update, and it is what makes the output trustworthy.
What to collect
- Completed tasks or milestones since the last update, in your own words.
- Changes to dates, scope or budget, with the reason.
- Open risks and issues, with owners and next steps.
- Decisions that are waiting on someone.
- Anything the reader has asked about previously.
Keep a running log
The easiest way to produce a good update is to log progress as it happens. A few lines at the end of each day, in a simple document, give you everything you need on update day. Without a log, you rely on memory, which favours the recent and the dramatic over the important.
If you also take notes in meetings, the guide to taking better meeting notes with AI can help you turn those conversations into usable items for your log.
Drafting with an assistant
Once you have your notes, give them to the assistant with clear instructions. The better your prompt, the less editing you will do. The general principles are covered in how to write better prompts: state the role, the audience, the structure, the length and the rules.
A reusable drafting prompt
- Role: You are helping a project manager write a weekly update.
- Audience: An executive sponsor who has two minutes.
- Input: My notes follow. Use only these facts.
- Structure: Summary, progress, next, risks, decisions needed.
- Rules: Do not add information that is not in my notes. Do not use hype or filler. If something is unclear, ask me a question instead of guessing.
- Length: No more than 200 words.
The instruction to ask a question rather than guess makes the interaction more useful. It turns the assistant into an editor who flags gaps, not a ghostwriter who smooths them over.
Edit for your voice
Assistants tend to produce a generic corporate tone. Read the draft aloud and change anything you would not say. Replace abstractions with specifics, such as the supplier confirmed delivery on the twelfth instead of positive progress was made on procurement.
Writing for different audiences
The same facts should be framed differently for different readers. One strong habit is to keep a single set of notes and ask the assistant for several versions, then check each carefully.
| Audience | What they care about | Style |
|---|---|---|
| Executive sponsor | Outcome, risks, decisions | Brief, direct, no jargon |
| Delivery team | Tasks, dependencies, dates | Detailed, practical |
| Client | Progress against promises, next steps | Clear, calm, confident but honest |
| Wider stakeholders | Impact on them and timing | Plain and short |
Be careful with anything shared outside your organisation. A client version should leave out internal discussion, staffing details and opinions about individuals. An assistant will not know what is sensitive unless you tell it, so state the exclusions in your prompt and read the result with that in mind.
One source of truth
Do not let different versions contradict each other. Write the facts once, then adapt the framing. If your sponsor update says the date has slipped and your client update says it is on track, you have a larger problem than wording.
Updating for long projects
On a project that runs for many months, updates can become repetitive. Readers start to skim, and the one important change gets lost. Vary the emphasis by adding a short line at the top that begins with what is new this week. If nothing important has changed, say so plainly and keep the update to a few lines. An assistant can help you compare this week with last week and point out what actually differs, which is a useful way to decide what deserves space.
Tracking commitments
Keep a short list of promises you have made to stakeholders, such as dates and deliverables. At each update, ask the assistant to compare the list with your notes and flag any commitment that your notes suggest is now at risk. You still decide what to do about it, but the comparison catches items you might otherwise forget.
Make status colours mean something
Many teams use a traffic light system: green, amber, red. It is a useful shorthand but only if the colours have agreed meanings. Without definitions, green becomes a polite way of saying nothing has gone wrong yet, and red appears only when it is too late.
| Status | Suggested meaning | Typical action |
|---|---|---|
| Green | On track, no help needed | Continue |
| Amber | At risk, plan in place but could slip | Watch closely, share the plan |
| Red | Off track or blocked, help needed | Escalate with a specific request |
Agree the definitions with your sponsor and write them at the top of the template. Then decide status from the facts yourself, not from the assistant. A model may describe a delayed project in a reassuring tone because that is how much business writing sounds. Make sure the language matches the colour.
Watch for the soft words
Phrases such as progressing well, on target in the main and some minor delays can hide real problems. Ask the assistant to replace them with specifics, and ask yourself whether a reader could act on the sentence.
Reporting bad news well
Bad news does not improve with age. The earlier a problem is raised, the more options remain. A clear, calm update gives people the chance to help.
A structure for bad news
- State the problem in one sentence, without cushioning.
- Say what the impact is on time, cost, scope or quality.
- Explain what you know and what you do not know yet.
- Describe what you are doing about it.
- Say what you need from the reader, and by when.
An assistant can help with tone, turning a defensive draft into a direct and respectful one. Give it your facts and ask for a version that is plain, professional and free of blame. Then check that the facts still say what they should. Softening can accidentally change meaning, for example turning a firm delay into a possible delay.
Never let the assistant hide the problem
If the draft buries the issue in the third paragraph or wraps it in positive language, rewrite it. The risk, the impact and the request belong near the top. Transparency is a form of respect, and your credibility depends on it.
Check before you send
A polished draft is not a correct one. Before sending, compare the update with your notes and check every item that matters.
- Every date matches your source.
- Every number, such as budget or percentage complete, is one you provided.
- Nothing is claimed as done that is still in progress.
- Names and roles are correct.
- The status colour matches the facts and the definitions.
- Nothing confidential has slipped into an external version.
Language models are known to add plausible detail that was never in the input. This is covered in more depth in the guide to how to check AI output for mistakes. A good habit is to ask the assistant to list every claim in the draft that is not directly supported by your notes. Anything on that list should be removed or confirmed.
Read it as the recipient
Finally, read the update as if you were the sponsor opening it between meetings. Would you know the status within ten seconds? Would you know what you need to do? If not, revise.
Protect sensitive project information
Project notes can contain commercial terms, client names, staffing issues and unannounced plans. When you paste them into an online tool, you are sharing them.
- Follow your organisation rules about approved tools.
- Remove client names, prices and personal details when the task does not need them.
- Keep updates about individuals, such as performance concerns, out of any AI tool.
- Be careful with contracts and legal matters. This is general information, not legal advice.
The guide on protecting company data when using AI tools sets out the questions to ask before you share anything.
If a project is particularly sensitive, write that update by hand. The time saved by a tool is rarely worth a confidentiality breach.
A template you can copy
Keep a plain version of the update as a reusable starting point. Write the date and project name, then a status line with the colour and one sentence of explanation. Follow with the progress list, the plan for the coming week, the top three risks with owners, and the decisions needed with deadlines. Add a short dates table at the bottom for milestones. Having this skeleton ready means you or an assistant only need to fill in facts, which makes the drafting step quick and the results consistent from week to week.
Build a sustainable update routine
The best update process is light and regular. Set a time each week, keep the log current, draft with an assistant, check, edit and send. The whole thing should take twenty to thirty minutes for a typical project.
Weekly routine
| Step | Time | Notes |
|---|---|---|
| Review the log and collect facts | 5 minutes | Include any changes to dates or scope |
| Draft with the assistant | 5 minutes | Use your saved prompt |
| Edit and fact check | 10 minutes | Compare against your notes |
| Send and log decisions | 5 minutes | Note who must respond |
Ask for feedback occasionally. A one line question to your sponsor, such as is this the right level of detail, can save months of misdirected effort. Improve the template over time and keep prompts in a shared document so that the whole team writes consistently.
Frequently asked questions
Can AI write my project updates for me?
It can draft them from your notes, but you provide the facts and decide the status. Always check the draft before sending.
How long should a project update be?
Short enough to read in two minutes. Put the status and any decision needed at the top and link to detail if required.
How do I stop AI making progress sound better than it is?
Tell it to use only your facts, to avoid soft language and to flag anything unsupported. Then compare the draft with your notes.
Should I use one update or several versions?
Use one set of facts and adapt the framing for each audience. Check that the versions never contradict each other.
What should I do when the news is bad?
State the problem plainly, explain the impact, say what you know and do not know, describe your response and make a clear request.
Is it safe to paste project notes into an AI tool?
Only if your organisation allows it, and only after removing sensitive details. For highly confidential matters, write the update yourself.
Conclusion
A strong project update is honest, structured and short. Use your own notes as the source, ask an assistant to turn them into clear prose and keep the judgement about status, risk and escalation firmly in your own hands. Different audiences need different framing, but the facts must stay consistent.
To improve your drafts, practise how to write better prompts, learn how to check AI output for mistakes, and feed your updates from good meeting records using how to take better meeting notes with AI.
