How to Write a Weekly Work Report with ChatGPT

The everyday problem

Friday arrives and your accomplishments are scattered across notes and task lists. Writing a report from memory can turn activity into vague claims. Begin with evidence: what changed, who needs to know, and which decisions are still open.

Which tool to use, and why

Use ChatGPT to structure and rewrite notes you are allowed to share. Replace client names and sensitive figures with placeholders. The assistant is helpful for organization and tone; it should not be the source of your performance metrics.

Step by step

Collect dated notes from your own task tracker. Mark each item as done, in progress, blocked, or planned.
Attach an outcome only when you have evidence. “Draft reviewed” is different from “project completed.”
Provide your manager’s preferred format and a word limit. Ask for missing information to stay visibly missing.
Compare every claim in the report with your notes. Check quantities, owners, dates, and whether a plan became a promise.
Edit the final report in your own voice. Keep a short source note so next week’s report can follow up on unresolved work.

A prompt you can copy

Replace every bracketed placeholder with your own non-sensitive information before you use this prompt.

Turn these notes into a weekly work report of 180–220 words. Use headings: Completed, In Progress, Blockers, Next Week. For each completed item, state the supplied result. Preserve all dates and numbers exactly. Do not invent impact, percentages, owners, or deadlines. Mark missing details as “not confirmed.” Notes: [paste approved notes].

A worked example

Illustrative example: this input and output were written to explain the workflow. They are not a live product test, a user testimonial, or a promise of identical output.

Example input

Week ending October 16. Drafted onboarding checklist; manager reviewed it. Two support cases still open, waiting for product guidance. Next week: revise checklist after feedback. No response date from product.

Example output

Completed: drafted the onboarding checklist and received manager review. In Progress: two support cases remain open. Blocker: product guidance is pending; response date not confirmed. Next Week: revise the checklist using the manager’s feedback. This shortened excerpt shows the structure, not the full requested word count.

Check the result

The report must not say the onboarding process is finished or that support cases were resolved. If you did not measure time saved, remove any claim about productivity gains.

Common mistakes to avoid

Confusing hours spent with a completed result. Name the deliverable or decision.
Allowing AI to invent impact metrics to make a report sound impressive.
Including confidential customer information without approval.

Frequently asked questions

What if I have very little progress to report?

Report the current state honestly, identify the blocker, and name the next decision needed. Do not pad the update with invented achievements.

Can I reuse the same prompt weekly?

Yes. Keep the format, replace all source notes, and carry forward unresolved blockers explicitly.

Keep learning

Official documentation and availability

Product interfaces, plans, limits, and optional features can change. Check the current documentation for your own account. This guide’s original prompt and worked example do not depend on a particular model version.