How to Write a Project Status Report With AI
The update is scattered across a meeting note, three messages, and a task list. One item says “done.” Another says the same item is still waiting for approval.
Give AI dated source notes and require it to separate completed work from planned work. Use a fixed report structure, and reject any owner, deadline, percentage, or overall status that is not supported by the notes.
The aim is not a longer report. It is a report that lets someone understand the project in two minutes without being misled.
Use five parts
A practical status report needs:
- Overall status: on track, at risk, off track, or not yet assessed.
- Completed: work finished during the reporting period.
- Next: work planned for the next period.
- Blockers and risks: what is stopping progress or may cause trouble.
- Decisions needed: who needs to decide what, and by when.
Add owners and dates only when your source notes support them.
Atlassian's current project-status template likewise emphasizes progress, issues, risks, and information stakeholders need. Microsoft gives “status, milestones, risks, and decisions needed” as an example outline for a project update in Copilot for Word.
Clean the notes before asking for prose
Do not paste every project channel into a chatbot.
Make a short source list like this:
Reporting period: October 6–10
– Oct 6 — Draft homepage copy sent to review. Owner: Mia.
– Oct 7 — Review requested two wording changes. No new due date stated.
– Oct 8 — Analytics setup completed and checked by Sam.
– Oct 9 — Launch date moved from Oct 14 to Oct 17.
– Oct 10 — Payment-page test blocked; test account owner not stated.
– Undated note — “Project is 80% complete.” Source and calculation not stated.
Use labels instead of confidential client, employee, product, or system names. Remove credentials, private links, internal financials, personal data, and unreleased strategy unless you are using an approved workplace tool.
Keep dates. They help the AI tell an old plan from a newer update.
Copy this prompt
Turn the dated notes below into a short project status report.
Use these sections:
– Overall status
– Completed this period
– Next period
– Blockers and risks
– Decisions needed
Rules:
– Use only the notes provided.
– Do not turn “planned,” “in review,” or “waiting for approval” into “completed.”
– Do not invent owners, dates, percentages, reasons, or decisions.
– If notes conflict, show the conflict under
Needs confirmation.– If overall status is not supported, write
Not yet assessed.– Keep the report under 250 words.
– After the report, provide a fact-check table linking each statement to its source note date.
SOURCE NOTES:
[paste the cleaned notes]
The fact-check table is for you, not necessarily for the final reader. It makes unsupported claims easier to spot.
Decide the overall status yourself
Red, yellow, and green labels look objective, but the thresholds vary between teams.
Do not let AI decide that a project is “on track” because most tasks sound positive. A single unresolved security review, legal approval, payment failure, or missing dependency may matter more than ten completed minor tasks.
Use your team's rules. If no rules exist, write a plain sentence:
The planned launch moved to October 17. Analytics is complete, but payment testing remains blocked while ownership is assigned.
That tells the reader more than a green dot.
Look for tense errors
The most dangerous status-report mistake is often one verb.
- Completed: finished and verified.
- In progress: started but not finished.
- In review: work exists but is awaiting approval.
- Planned: intended but not started.
- Blocked: cannot proceed until something changes.
- At risk: still moving, but a known issue may affect scope, time, cost, or quality.
Compare every sentence with the source note. Watch for AI changing “should,” “will,” or “expected” into “did.”
Also check owners. If the notes say “someone from finance,” the final report should not assign the task to a named person.
Match the detail to the reader
Once the facts are correct, AI can adapt the same verified report.
For a manager:
Keep the update to 150 words. Put changed dates, blocked work, and decisions needed first.
For a client:
Use plain language. Include confirmed progress, the effect of the changed date, and any decision needed from the client. Do not expose internal discussion.
For the working team:
Keep owners, dependencies, and next actions. Use bullets instead of a narrative paragraph.
Do not generate three versions before the source report is correct. Otherwise, the same invented fact spreads into every audience version.
Check the report in two minutes
Before sending it, answer these questions:
- Does every “completed” item have evidence?
- Are moved deadlines shown as moved—not quietly replaced?
- Are blockers paired with a real owner or marked unassigned?
- Is every percentage supported by a calculation?
- Does “at risk” or “on track” follow a human decision?
- Is the reporting period visible?
- Can the reader see what they need to decide?
- Did confidential information stay out?
Then save the final report in the project's normal system. The AI chat should not become the only place where project status exists.
What happened in H5W's project-status test
H5W tested the prompt with fictional notes containing two launch dates, two contract states, an unsupported “about 80% complete” estimate, an expired test account, and no named owner for the blocker.
ChatGPT kept the overall status as NOT YET ASSESSED. It placed both launch dates and both contract states under NEEDS CONFIRMATION, described the 80% figure as unverified, and did not invent a blocker owner. Those are the behaviors a useful first draft should have.
One phrase still needed cleanup: the notes said Marketing needed the date “by Friday,” and the report repeated that relative deadline. Replace words such as today, tomorrow, and Friday with an actual date before sending the update. Relative dates age badly and can mean different things to different readers.
Short is useful when it is precise
A status report is not a diary of everything the team did. It is a current picture of what changed, what comes next, and what needs attention.
Use AI to compress the notes. Keep the project system, the dated evidence, and the final judgment as the source of truth.
For source cleanup, begin with How to Turn Messy Notes Into a Weekly Plan With AI. After a meeting, use How to Turn Meeting Notes Into a Follow-Up Email With AI. For the final message, see How to Write a Professional Email With AI.
Sources and verification
Information last verified: October 13, 2026.
- Atlassian: Project Status Report template
- Atlassian: End of Week Status Report template
- Microsoft Support: Welcome to Copilot in Word
- OpenAI: Data Usage for Consumer Services FAQ
- Google: Gemini Apps Privacy Hub
Free printable resource
AI Business Writing Brief Pack
Use the practical version while you work. It is a selectable-text U.S. Letter PDF with no email gate.
Public H5W PDF with selectable text and permanent source links.
Keep going
Choose your next step
Return to Work for the full collection, or continue with a closely related guide.
