# Work Summary Template (English Edition)

> **Companion tutorial**: B5 "Your First Work Summary, Written with AI"
> **Audience**: Office beginners who go blank the moment they need to write a summary
> **Core structure**: 5-section (Achievements / Shortcomings / Reflection / Next-Period Focus / Resource Needs) + Opening paragraph

---

## 1. How to Use This Template

1. **Make a copy** of this `.md` file and rename it to `[YourName]_[Period].md` (e.g., `WorkSummary_LiZhang_2026Q3.md`).
2. Open it in VS Code / Typora / Obsidian / any Markdown editor (you can also paste it into Word / WPS Writer).
3. **Replace every `[placeholder]` with your real content.** AI can draft each section for you, but **data, names, numbers, and project names must come from you** — AI doesn't know what you actually did.
4. After replacing, apply the heading styles (Word / WPS "Heading 1 / Heading 2 / Heading 3") using the **Heading-Level Mapping** below — one click generates a table of contents.

---

## 2. Heading-Level Mapping (Word / WPS Writer)

| Level | In this template | Word style | Used for | Length guidance |
|-------|------------------|------------|----------|-----------------|
| H1 | `# Work Summary — [Name] [Period]` | Heading 1 | The single big title | 1 line |
| H2 | `## 1. Opening` `## 2. Achievements` … | Heading 2 | Each main section | 5 of them |
| H3 | `### Key Initiative A` | Heading 3 | Sub-items under Achievements | As needed |
| Body | Plain paragraphs | Normal | Body paragraphs | — |

> 💡 **Tip**: Once styles are applied, click **References → Table of Contents → Automatic Table 1** in Word / WPS and a TOC appears in 1 second.

---

## 3. Template Body (copy into your own file)

```markdown
# Work Summary — [Your Name] [Period, e.g., Q3 2026]

> Role: [Your role, e.g., Marketing Operations Specialist]
> Period: [Start date — End date]
> Date written: [Date]
> Use case: [Weekly / Monthly / Project / Quarterly / Yearly summary]

---

## 1. Opening (1 paragraph, set the scene)

[In 1–2 sentences, state the period, role, and overall tone. For example:

"This quarter, under the team's guidance, I focused on three areas: official-account operations, offline events, and WeChat-group building. Average reads grew steadily, offline events produced first-time on-site conversions, and we built 8 WeChat groups from scratch. Overall, the quarter's results met our targets."]

---

## 2. Achievements (key numbers + bullet structure)

### 2.1 [Key Initiative / Module A]

- Headline (one sentence): [e.g., "Average reads per post grew 87.5% QoQ"]
- Specific numbers: [e.g., "Published 24 posts; average reads went from 800 to 1,500"]
- Key actions: [e.g., "Shifted content angle from product-led to user-story-led"]

### 2.2 [Key Initiative / Module B]

- Headline: [e.g., "Offline events generated first-time on-site conversions"]
- Specific numbers: [e.g., "2 events, 120 attendees, 30 on-site leads"]
- Key actions: [e.g., "Invited industry KOLs and added a prize-draw interaction"]

### 2.3 [Key Initiative / Module C]

- Headline: [e.g., "Built 8 WeChat groups from zero"]
- Specific numbers: [e.g., "~600 total members; ~75 per group"]
- Key actions: [e.g., "Unified group rules, weekly fixed topics, rotating host"]
- To improve: [e.g., "Daily engagement is average; interaction rate is low"]

---

## 3. Shortcomings (be honest, pick 1–3)

1. **[Shortcoming 1: time management / planning / communication / technical skill]**
   - What it looked like: [e.g., "Frequent firefighting; monthly plan disrupted 3+ times"]
   - Impact: [e.g., "Two event materials were delivered late"]

2. **[Shortcoming 2]**
   - What it looked like: […]
   - Impact: […]

3. **[Shortcoming 3]**
   - What it looked like: […]
   - Impact: […]

---

## 4. Reflection (the "why" behind the shortcomings)

- **[Reflection on Shortcoming 1]** — [e.g., "I never blocked core working hours; instant messages constantly interrupted me. Next quarter I will reserve a 2-hour no-interruption block."]
- **[Reflection on Shortcoming 2]** — […]
- **[Reflection on Shortcoming 3]** — […]

---

## 5. Next-Period Focus (no more than 5 items)

1. **[Goal 1]** — concrete action + measurable indicator
   - Action: [e.g., "Standardize 4 event SOPs"]
   - Measure: [e.g., "Next event needs 30% less manpower, conversion rate ≥ this time"]

2. **[Goal 2]** — action + measure
   - Action: […]
   - Measure: […]

3. **[Goal 3]** — action + measure
   - Action: […]
   - Measure: […]

---

## 6. Resource Needs (what you need from your boss)

- **People** — [e.g., "1 community-operations intern to handle daily topics and user Q&A"]
- **Budget** — [e.g., "¥15,000 / quarter for offline event materials"]
- **Training / Tools** — [e.g., "Attend a data-analysis class in September"]
- **Cross-team** — [e.g., "Sales to share last quarter's customer-profile data"]

---

## Appendix: Applying Word / WPS heading styles in 4 steps

1. Select `# Work Summary — …` → apply **Heading 1**.
2. Select `## 1. Opening` `## 2. Achievements` … `## 6. Resource Needs` → apply **Heading 2**.
3. `### 2.1` `### 2.2` … → apply **Heading 3**.
4. **References → Table of Contents → Automatic Table 1** for an instant TOC.
```

---

## 4. Field Reference (placeholder explanations)

| Placeholder | Type | Example | Notes |
|-------------|------|---------|-------|
| `[Your Name]` | text | Li Zhang | Author |
| `[Period, e.g., Q3 2026]` | text | Aug–Oct 2026 | Time range |
| `[Your role, …]` | text | Marketing Ops Specialist | Job title |
| `[Key Initiative / Module A]` | text | Official-Account Ops | 3–5 parallel modules |
| `[Specific numbers]` | number | 24 posts | **Must be real** |
| `[Shortcoming 1: …]` | text | Time management | Pick 1–3 weaknesses |
| `[Goal 1] + Action + Measure` | text | — | Structured style for next-period focus |
| `[People / Budget / Training / Cross-team]` | text | 1 intern | 4 categories of resource needs |

> ⚠️ **AI-generated numbers must always be verified against this table.** Let AI draft, but never let AI make up numbers — that's the one rule you cannot break.

---

## 5. Five Scenario Prompts (copy directly into AI)

### Scenario 1 — Weekly summary (every Friday)

```
Based on the bullets below, please write a weekly summary (~300 words).
Tone: formal but natural, no empty bureaucratic clichés.
Structure: four blocks — Completed this week, Not completed (rolls over to next week),
Plan for next week, Items needing help.
Keep the numbers in the bullets exactly as given; do not fabricate or alter them.

This week's bullets:
1. …
2. …
3. …
```

### Scenario 2 — Monthly summary (end of month)

```
Based on the bullets below, please write a monthly summary (~600 words).
Tone: formal but natural, no "under the leadership of…" clichés.
Structure: five blocks — Overview, Key results this month, Issues & improvements,
Next month's focus, Resource/support needs.
Keep the numbers exactly as given; do not fabricate them.

This month's bullets:
1. …
2. …
3. …
4. …
```

### Scenario 3 — Project summary (after a project ends)

```
Based on the bullets below, please write a project retrospective for "[Project Name]"
(~1,200 words). Tone: professional but readable, no grandiose clichés.
Structure: six blocks — Background, Goal achievement, Key results, Process issues &
retrospective, Reusable lessons, Next-step actions.
Keep the numbers exactly as given; do not fabricate them.

Project bullets:
1. Background: …
2. Goal achievement: …
3. Key results: …
4. Process issues: …
5. Reusable lessons: …
6. Next steps: …
```

### Scenario 4 — Quarterly summary (end of quarter)

```
Based on the bullets below, please write my personal work summary for
[Q3 2026] (~800 words). Tone: formal but natural, no "fully completed" clichés.
Structure must include five sections — Opening, Work Recap, Key Achievements,
Shortcomings & Improvements, Next Steps.
Keep the numbers exactly as given; do not fabricate them.

My bullets:
1. …
2. …
3. …
4. …
5. …
```

### Scenario 5 — Yearly summary (end of year)

```
Based on the bullets below, please write my personal year-end summary for [2026]
(~1,500 words). Tone: formal but natural, no "remarkable results" empty phrases.
Structure must include seven blocks — Year overview, Core results (with numbers),
Major project retrospective, Capability growth, Existing shortcomings & reflection,
Next-year direction, Resources & support needed.
Keep the numbers exactly as given; do not fabricate them.

My bullets:
1. Core results this year: …
2. Major projects: …
3. Capability growth: …
4. Shortcomings: …
5. Next-year direction: …
6. Resource needs: …
```

---

## 6. AI Rewrite Prompt (polish the first draft)

After AI's first version comes back, run this "drop clichés + quantify + bullet structure" triplet:

```
Please do three things to the summary above:
1) Quantify achievements wherever possible — use numbers, avoid vague phrases like
   "significantly improved";
2) Rewrite the "Key Achievements" section as bullets, each starting with a
   one-sentence conclusion followed by one specific explanation;
3) Remove clichés such as "under the leader's care," "fully completed," and
   "remarkable results" — keep it natural and like a real person wrote it.

Keep the total around [X] words — trim if too long, add a transition if too short.
```

> Reminder: **replace `[X]` with your target word count** (800 / 1200 / 1500 depending on the scenario). AI will not extend short drafts on its own but will trim long ones.

---

## 7. FAQ After Applying Styles

- **Q: What are the heading styles called in WPS Writer?**
  A: Same as Word — "Heading 1 / Heading 2 / Heading 3". Found in the **Home** tab's Styles pane.
- **Q: My automatic Table of Contents is missing some H2s.**
  A: Check whether the line really has the **Heading 2** style (not just bold-formatted text). Manual bolding only changes the look; it isn't a "heading".
- **Q: Should I add a logo / company letterhead?**
  A: If your company has a template, use it; otherwise use this template and remove the `>` blockquote lines.
- **Q: The AI draft reads like "translated bureaucratic Chinese." What now?**
  A: Send this instruction: "Rewrite all sentences in a more conversational, human voice; don't use bureaucratic tone." If it still doesn't read like you, manually rewrite the awkward sentences in your own voice.

---

*This template works with WPS Writer and Microsoft Word 2016+. AI tool: WPS AI or ERNIE Bot (either is fine). In every scenario, **numbers come from your own bullets; AI never invents your data**.*