How to Write a Weekly Report: 3 Templates and Examples

Friday at 4 p.m., staring blankly at an empty document while glued to your desk—this is the reality for many people when writing their weekly report.

Recalling the week's work, you realize you really were busy for five days, but when it comes to putting it on paper, it either turns into a "running-account diary": did A on Monday, did B on Tuesday; or it becomes a "pile of adjectives": actively promoted, deeply optimized, continuously followed up—a whole lot written, but after reading it, no information is left behind.

The real purpose of a weekly report is not to prove "I did work," but to answer three key questions: what was advanced this week, what problems were encountered, and how do we plan to proceed next week. A good weekly report structure is built around these three questions.

This article provides 3 directly usable weekly report template structures, covering different roles and reporting scenarios. Each comes with a complete example and a pitfall-avoidance guide—ready to use as-is.

---

I. Results-Oriented Template (Suitable for Most Roles)

Applicable scenarios: Roles such as operations, marketing, sales, design, and administration that value "output" rather than "process."

Core concept: Leaders typically spend only 30 seconds to 1 minute reading a weekly report. This template puts "conclusions first"—the information you most want your supervisor to see goes at the very front, with details afterward.

Template structure:

[Weekly Report] Name | Role | Date range (e.g., 10.21-10.25)

▎I. Core outputs this week (3-5 items, each stating the result in one sentence)
1. [Project/Task name]: What was completed, what result/data change it brought
2. ...
(Principle: Each item must include a verb + output. Don't say "did," say "accomplished")

▎II. Key data (if the role has data metrics)
- Metric A: This week's value → week-over-week change
- Metric B: This week's value → week-over-week change

▎III. Problems encountered & solutions
1. Brief problem description → My analysis → Solutions taken/recommended → Who needs to support?
2. ...

▎IV. Key plans for next week (3-5 items, marked with priority)
- [P0] Task name + expected output + what the completion marker is
- [P1] Task name + expected output
- ...

▎V. Items requiring coordination (omit if none)
- Items requiring cooperation from XX department/XX person + expected completion time

Example reference (using a new media operations role as an example):

[Weekly Report] Zhang San | New Media Operations | 10.21-10.25

▎I. Core outputs this week
1. Published the 2nd installment of the official account "Brand Refresh" series: 23,000 reads, up 40% from the previous installment
2. Completed the Xiaohongshu account setup from 0 to 1: completed positioning plan + 3 note reserves + first post published (128 likes)
3. Collected 324 user research questionnaires: produced a draft research report and distilled 5 key insights
4. Assisted the marketing department in completing 3 rounds of revisions to Double 11 campaign copy, now finalized

▎II. Key data
- Official account followers: net increase of +780 this week, +15% week-over-week
- Xiaohongshu: first note received 128 interactions, above the industry average (about 80)
- Research questionnaires: 324/500 target, 65% progress

▎III. Problems encountered & solutions
1. The first Xiaohongshu post's traffic performance was mediocre → Analysis showed the posting time was too late (8 p.m.); plan to adjust the next post to 12 noon as a test
2. The spread of research questionnaires slowed down → Coordinated with the sales team to forward in customer groups; target expected to be met by Sunday

▎IV. Key plans for next week
- [P0] Write + publish the 3rd official account post (push before Thursday)
- [P0] Produce the first draft of Double 11 campaign warm-up copy (deliver before Tuesday)
- [P1] Publish the 2nd Xiaohongshu note (test the new posting time)
- [P1] Wrap up research questionnaires + produce the final report (before Wednesday)

▎V. Items requiring coordination
- Need the design team to cooperate on the cover for the 2nd Xiaohongshu note, provided before Tuesday

Pitfall tip: The "core outputs" in Part I are the soul of the entire weekly report. After writing each item, ask yourself: "After reading this item, can the other person know what I accomplished?" If they can only know that you "did" something, rewrite it.

---

II. Process Review Template (Suitable for Project/Product & R&D Roles)

Applicable scenarios: Roles centered on "project advancement" work, such as product managers, project managers, R&D leads, and design leads.

Core concept: Supervisors and collaborators care more about whether project progress has deviated, where it is stuck, and how to proceed next. This template focuses on "visualizing the progress bar" and "front-loading risk warnings."

Template structure:

[Weekly Report] Name | Role/Project | Date range

▎I. Overall project status (red/yellow/green markers)
- 🟢 Project A: On track, currently at XX stage
- 🟡 Project B: At risk, risk point XXX (see Part III for details)
- 🔴 Project C: Delayed/blocked, reason XXX

▎II. Key items completed this week
1. [Requirement/Feature/Design]: Advanced from "pending confirmation" to "review passed"
2. ...
(Mark each item's initial status → current status; seeing "movement" is more intuitive than seeing "completed")

▎III. Risks and issues
| Risk description | Scope of impact | Severity | Solution | Expected resolution time | Who needs to assist? |
|:---|:---|:---|:---|:---|:---|
| XX | Affects XX | High | XX | Before Friday | XX |

▎IV. Next week's plan (by priority)
- [P0] XX item → Completion marker: XX document delivered/XX review passed
- [P1] XX item → ...

▎V. Insights/lessons this week (optional)
- What pitfalls were encountered? What experience was summarized? Where in the knowledge base was it updated?

Example reference (using a product manager role as an example):

[Weekly Report] Li Si | Product Manager (E-commerce App product detail page redesign) | 10.21-10.25

▎I. Overall project status
- 🟢 Product detail page redesign: Now in the UI design stage, first draft on track for delivery next Monday
- 🟡 Recommendation algorithm tracking plan: Depends on the data team's schedule, currently scheduled for next Wednesday, may affect integration testing
- 🔴 Review feature iteration: Due to misalignment on merchant-side APIs, requirement review postponed to next Monday

▎II. Key items completed this week
1. Detail page interaction prototype V3 → V4 (review passed): Added a "size recommendation" module, simplified the add-to-cart path
2. Tracking requirements document: First draft completed → Aligned with the data team, schedule pending confirmation
3. Review feature PRD: First draft completed → Awaiting alignment on merchant-side API definitions before initiating review

▎III. Risks and issues
| Risk description | Scope of impact | Severity | Solution | Expected time | Assistance needed |
|:---|:---|:---|:---|:---|:---|
| Data team's schedule is late | Recommendation tracking integration testing | Medium | Prioritize front-end tracking that doesn't depend on the data team | Before next Wednesday | R&D lead to coordinate resources |

▎IV. Next week's plan
- [P0] Detail page UI first draft review (Monday)
- [P0] Review feature PRD review (Monday, merchant-side colleagues already coordinated to participate)
- [P1] Competitor research: Latest changes to Taobao/JD product detail pages (document before Wednesday)

▎V. Lessons this week
- In interaction reviews, "preparing competitor screenshot comparisons in advance" can significantly reduce back-and-forth communication costs; updated to the team's review checklist

---

III. Project Advancement Template (Suitable for Interns/Newcomers/Multi-Task Parallel Workers)

Applicable scenarios: Stages where work tasks are diverse with no unified main line, and you need to let your mentor/supervisor quickly understand what you are busy with.

Core concept: The mistake newcomers most easily make is "writing only about busyness, not about growth." This template adds a "Learning and Reflection" section beyond basic task reporting, letting supervisors see your growth curve.

Template structure:

[Weekly Report] Name | Role | Date range

▎I. This week's task list (annotated with status tags)
- ✅ Completed: XX (one-sentence output)
- 🔄 In progress: XX (current progress percentage/stage)
- ⏸️ Paused/blocked: XX (reason)

▎II. Time distribution (optional, helps mentors understand your time allocation)
- XX type of work accounts for 40%
- XX type of work accounts for 30%
- XX type of work accounts for 30%

▎III. Learning and reflection (the part newcomers should write most)
1. What did I learn this week? (Skills/processes/awareness)
2. What do I want to try/improve next week?
3. What confusions do I need to discuss with my mentor?

▎IV. Next week's plan
- Item 1 + expected output
- Item 2 + expected output

Example reference (using an operations intern role as an example):

[Weekly Report] Wang Wu | Content Operations Intern | 10.21-10.25

▎I. This week's task list
- ✅ Completed optimization of the official account scheduling template: Added an "estimated reads" column to facilitate later topic evaluation
- ✅ Completed content breakdown of 5 competitor accounts, produced a comparative analysis table
- 🔄 Independently wrote the 1st official account post: First draft completed, awaiting mentor feedback (80% progress)
- ⏸️ User comment interaction SOP organization: Postponed to next week due to this week's post scheduling adjustment

▎II. Time distribution
- Competitor breakdown and learning: 40%
- Post writing: 35%
- Tool and template optimization: 25%

▎III. Learning and reflection
1. Learned: The "suspense" of a title is far more important than "complete information"—after comparing the gap between my own titles and viral titles, this realization was especially profound
2. Want to try: Add an "interactive poll" module to next week's post to see if it can boost comment volume
3. Confusion: When unsure about topic direction, should I prioritize trending topics or evergreen content? Want to align on the judgment logic with my mentor next week

▎IV. Next week's plan
- [Monday] Complete the final draft of the first post
- [Before Wednesday] Complete the topic + outline for the second post
- [Before Friday] Complete the user comment interaction SOP organization

---

Guide to Choosing Among the Three Templates

---

4 General Pitfall-Avoidance Guides for Writing Weekly Reports