Write Weekly Reports with ChatGPT: Give a Template + Give Data, Draft in 10 Minutes

Why Use It for Weekly Reports

A weekly report is essentially "re-telling what you did this week in the way your boss wants to read it". ChatGPT is good at this: categorizing information, polishing, adding structure. But it's bad at inventing numbers—so the correct posture is you give the facts, it handles the expression.

No need to think from scratch "what on earth did I do this week"—paste chat logs, to-dos, and emails and get a framework;
Unify wording and tone, avoiding style drift every issue;
A draft in 10 minutes, tweak a couple of sentences and send—saving the most annoying "hard to start".

Three-Step Drafting Method

Gather material (5 min)

Pile up this week's real records: what's done, what's in progress, snags, key data (revenue / user count / time spent, etc.). No need to organize—the more raw the better. Leave missing data blank, don't let AI fill it.

Apply the template to give instructions (1 min)

Use the prompt below, pasting your material after "[MY MATERIALS]". The template sets the structure, so AI won't ramble.

Verify data, adjust tone (4 min)

Numbers, names, and project names in AI's output must be verified by you. Then adjust the tone to your team's habit, and it's ready to send.

Prompt You Can Copy Directly

Send the whole block below to ChatGPT, replacing the bracketed content:

You are a rigorous weekly-report assistant. Based on [MY MATERIALS], help me write a work weekly report, with these requirements: 1. Use only the facts I provide, never fabricate data, names, project names, or results; 2. Structure into four sections: Completed this week / In progress / Risks and snags / Next-week plan; 3. Each item in the format "action + result/impact", 1~2 lines; 4. Concise, formal, not exaggerated; if a section lacks material, write "None" rather than filling it in. [MY MATERIALS] (paste this week's scattered records here) [TEAM HABIT NOTES, OPTIONAL] (e.g.: boss cares about progress numbers / prefers casual tone / use first person)

A Real Example

The material you provided:

This week migrated the login interface to the new gateway, integration passed, stress test QPS from 800 to 1500. Wednesday helped operations write a batch export script. Thursday server alerted once in the middle of the night, restarted and recovered, root cause not yet found. Next week need to review the plan with the client.

The weekly report AI produced (excerpt):

Completed this week: Migrated the login interface to the new gateway and completed integration; stress-test QPS raised from 800 to 1500; delivered a batch-export script to operations, reducing manual export time.
Risks and snags: One service alert occurred Thursday night, recovered after restart; root cause pending, added to next-week follow-up.
Next-week plan: Review the plan with the client; locate and fix the Thursday alert's root cause.

Note: in the example, "stress-test QPS 800→1500", "Wednesday script", "Thursday alert" are all facts you provided. AI only categorized and polished, adding no numbers—that's the safe way to use it.

Three Pitfalls to Avoid

Don't let it fabricate numbers: anything like "up 30%" or "saved 5 hours" must be filled in by you. Write "do not fabricate" into the prompt and double-check.
Redact sensitive info first: client names, internal codenames, unpublished data—mask or replace with placeholders before pasting to AI.
It's only a draft: especially for reports to your boss, read it through before finalizing to ensure the wording matches your team.

Back to the homepage for more tutorials, or browse office productivity tools to find a handy AI.

← Back to Tutorials