In many Chinese workplaces the weekly report is how a manager sees your work, and often how they remember it at review time. The common failures are a list of activities with no results, risks hidden until they are problems, and a plan with no dates. This skill turns rough notes into a report that shows outcomes, raises risks early, and asks for help clearly.
Write the output in Simplified Chinese unless the person asks for English or Traditional Chinese.
What This Skill Produces
- The report (weekly report or monthly report) in the five-part structure below
- A one-line summary for WeChat, DingTalk or Feishu, where the report is often shared
- A risk flag at the top if something needs the manager's decision this week
Required Inputs
Ask for these if not provided:
- This week's notes: what was done, in any form
- The goals or OKR / KPI the work serves, if the team uses them
- Last week's plan, so progress can be compared
- The reader: direct manager, skip-level, or a cross-team group
- The team's template, if one exists; follow it over this structure
Framework
- Done this week (done this week): outcomes, not activities. "Completed the payment page redesign and launch, conversion rate increased from 3.1% to 3.6%" rather than "worked on the payment page". Link each item to a goal.
- Key numbers (key numbers): the two to four metrics the manager tracks, with last week's figure for comparison.
- Issues and risks (issues and risks): each with impact, the proposed solution, and the decision needed. Raise it now, not next week.
- Next week's plan (next week): each item with an owner and a date. Mark carry-overs from last week honestly.
- Support needed (support needed): specific asks, with who and by when.
Style:
- Short lines, numbered items, numbers wherever the person has them.
- Lead with the most important item, not the first thing done.
- Use plain business Chinese. Avoid filler such as "continuing to advance" without a result or a date.
Output Format
Weekly Report: [Name]｜[Date Range]
⚠️ Decision needed(if any): [one sentence]
1. Completed this week
- [Result] (corresponding goal: [Goal])
2. Key data | Metric | This week | Last week | Change |
3. Issues and risks | Issue | Impact | Proposed solution | Who needs to decide |
4. Next week's plan | Item | Owner | Completion time | Remarks (carried over / new) |
5. Support needed
- [Specific request, from whom, by when]
One-sentence version(for group chat): [...]
End every output with a short Assumptions and gaps block: two to four bullets naming what was assumed because the input did not say, and what missing information would most change this output. If nothing was assumed and nothing was missing, say so in one line instead.
Quality Checks
- Every item completed this week states a result, and a number where the person gave one
- Every risk has an impact, a proposal and a named decision-maker
- Every next week's plan item has an owner and a date
- Carry-overs from last week are marked as carried over
- No number appears that the person did not provide
Anti-Patterns
- A running account (a diary of activities). Managers read results.
- Hiding a slipping item until it is late. A risk raised early is a plan; raised late, it is a surprise.
- Vague plans. "Advancing Project A" with no date commits to nothing.
- Inflating numbers to look busy. Weekly figures are easy to check.
Example Trigger Phrases
- "Help me organize these notes into a weekly report."
- "Write a monthly report for my boss, highlighting the data."
- "My work this week is a bit messy, help me write a weekly report; there's a risk I need to raise next week."
- "Write my weekly report in Chinese for my manager."