# 英语中级 · 第 4 周 Day 4｜写出汇报稿的主题句

> 系列：语种学习 / 英语 / 中级 · 每日学习｜AI生成｜2026-10-27｜codebuddy

**今天学什么**

今天把昨天的结构图变成文字：250 词，四段，每段第一句必须是主题句。主题句的作用是让听众在十秒内知道这一段要干什么，所以它只表态、不展开；展开是后面两三句的事。写完这一稿，周五就有东西可练，不用现场编。今天不追求句子漂亮，追求的是「每段只说一件事，每件事都有一句能立住的开头」。写完先别改语法，先数主题句。

## 一、今日任务

| 环节 | 时长 | 具体动作 | 产出 |
| --- | --- | --- | --- |
| 复习 | 8 min | 打开昨天结构图，把四段各段的关键词念一遍；回看昨天改写的 3 个弱句 | 4 个关键词 |
| 列提纲 | 10 min | 只写四个主题句，不写别的；每句后面标上打算用的数字或事实 | 4 句主题句 |
| 写初稿 | 25 min | 按 40 / 120 / 60 / 30 词的比例填内容，卡住就跳过，先写完再回头 | 250 词初稿 |
| 自查改写 | 12 min | 检查每段第一句是不是主题句、段内有没有第二件事、被动与从句够不够 | 修改稿 |
| 朗读 | 5 min | 出声读一遍，标出读不顺的地方，改短句 | 朗读标记稿 |

## 二、核心词汇与搭配

这批词分两类：progress、remain、roll out 用来写进展，contingency、flag、behind schedule 用来写风险。写稿时不要每个都塞进去，挑 6 个用得顺的，剩下的留给听力识别。

| 词 | 音标 | 词性 | 释义 | 高频搭配 | 例句与翻译 |
| --- | --- | --- | --- | --- | --- |
| progress | /ˈprəʊɡres/（≈普罗格雷斯） | n. | 进展 | make good progress | We've made good progress on testing. 我们在测试上进展不错。 |
| roll out | /rəʊl aʊt/ | phr. | 推出；推广 | roll out the new version | The new version will be rolled out in June. 新版本将在六月推出。 |
| remain | /rɪˈmeɪn/（≈里梅恩·短） | v. | 仍然是；剩下 | two issues remain | Two issues remain before the launch. 上线前还有两个问题。 |
| ahead of schedule | /əˈhed əv ˈʃedjuːl/ | phr. | 提前 | two days ahead of schedule | We're two days ahead of schedule. 我们比计划提前两天。 |
| behind schedule | /bɪˈhaɪnd ˈʃedjuːl/ | phr. | 落后于计划 | fall behind schedule | Testing is two weeks behind schedule. 测试比计划落后两周。 |
| contingency | /kənˈtɪndʒənsi/（≈克恩提恩哲恩西） | n. | 应急方案 | a contingency plan | We have a contingency plan for the vendor delay. 针对供应商延期我们有应急方案。 |
| scope | /skəʊp/（≈斯科普） | n. | 范围 | within / out of scope | The extra report is out of scope. 额外的报告不在范围内。 |
| flag | /flæɡ/（≈夫莱格） | v. | 提出、标记（问题） | flag a risk | I'd like to flag one risk early. 我想提前提出一个风险。 |
| realistic | /ˌriːəˈlɪstɪk/（≈里厄利斯提克） | adj. | 现实的 | a realistic timeline | We need a realistic timeline for June. 我们需要一个现实的六月时间表。 |

## 三、语法/语篇/语音点

**主题句：一段只讲一件事，第一句就交代清楚**

1. **主题句放段首，一句话，不超过 15 词**。它回答「这段在讲什么」，不回答「为什么」和「怎么做」。
2. **主题句必须能被后面两三句证明**。写完回头检查：后面的句子是不是都在支撑它？有一条跑题，就删或另起一段。
3. **一段只做一件事**。进展和风险混在一段，听众会以为风险已经解决了。
4. **主题句里带状态或数字**。Three of the five milestones have been reached 比 Progress is good 有用，因为听众能判断规模。
5. **段内顺序固定：主题句 → 事实 → 落点**。落点是一句「所以呢」，把事实和听众关心的事连起来。

写稿和写文章不一样。文章可以铺垫，汇报不行：听众没有回看的机会，一句话没跟上，后面就全丢。所以汇报稿的句子要短，主句在前，从句在后，数字放在句尾——英文听数字本来就吃力，放句尾反而更容易被记住。一段里出现两个以上专有名词时，第二次就换成 it 或 the module，别重复全称。

正误对比：

| 环节 | 弱 | 强 | 问题在哪 |
| --- | --- | --- | --- |
| 进展 | Progress is good. | Three of the five milestones have been reached. | 前者是评价，后者是事实 |
| 风险 | There are some risks. | The main risk is a two-week delay in testing. | 前者没说是哪个风险、多大 |
| 请求 | We need your support. | I need a decision on the extra budget by Thursday. | 前者没说要什么、什么时候 |

三个常见错误：

- **把背景细节当主题句**。In July we started the project with a small team 是细节，不是主题句；主题句应该是 We're six weeks into the project and on track for June。
- **一段塞两件事**。The design is done and testing is delayed 一句话里有完成和延期两件事，听众不知道这段要强调哪个。
- **主题句和段内容对不上**。开头写 The main risk is the budget，后面却讲排期，听众会觉得你不清楚问题在哪。

## 四、句型与范例

先给四段的主题句模板，再给段内支撑句。模板里的空格换成你的项目即可。这 10 句不必全用，每段挑一句主题句、一句支撑句，稿子就有了骨架；剩下的篇幅用你自己项目的数字填。

**背景（约 40 词）**

1. We're now in week six of the portal project, and today I'll cover progress, one risk, and one request. 门户项目现在进入第六周，今天我要讲进展、一个风险和一个请求。
2. The project started in July and is planned to go live in June. 项目七月启动，计划六月上线。

**进展（约 120 词，2—3 点）**

3. Three of the five milestones have been reached. 五个里程碑已完成三个。
4. The design was approved by the client in early September. 设计在九月初获得客户批准。
5. Two offices are already using the portal, and the third will go live next week. 两个办公室已在使用门户，第三个下周上线。

**风险（约 60 词，风险 + 影响 + 应对）**

6. The main risk is that the payment module is two weeks behind. 主要风险是支付模块落后两周。
7. The delay was caused by a missing API key from the vendor. 延期是由供应商未提供接口密钥造成的。
8. If the key doesn't arrive by Friday, the June release will slip by two weeks. 如果密钥周五前不到位，六月发布将推迟两周。
9. To mitigate this, we've prepared a fallback version without the module. 为降低影响，我们准备了一个不含该模块的备用版本。

**请求（约 30 词）**

10. What I need from you is a decision on the extra budget for the fallback version. 我需要你方就备用版本的追加预算做出决定。

## 五、练习

**A 词汇与翻译（8 题）** 做之前先把八个词读出声，读到不卡再动笔；这八个词周五开口时都要用，认得但读不出等于没学。

1. 五个里程碑我们完成了三个。（milestone，用被动）
2. 测试比计划落后两周。（behind schedule）
3. 新版本将在六月推出。（roll out，用被动）
4. 上线前还剩两个问题。（remain）
5. 我们为供应商延期准备了应急方案。（contingency）
6. 这份额外报告不在项目范围内。（out of scope）
7. 我想提前提出一个风险。（flag）
8. 我们需要一个现实的六月时间表。（realistic）

**B 主题句改写（6 题）** 改写的判断标准只有一条：把改完的句子单独拿出来，别人能不能猜到这一段大概讲什么。猜得到就算过关，猜不到就说明还是太虚。

1. Progress is good. → 改成带数字的主题句（假设五个里程碑完成三个）。
2. There are some risks in the project. → 改成具体的风险主题句。
3. We need your support. → 改成有对象、有时间的请求。
4. In July we started the project with a small team. → 改成背景段的主题句。
5. The design is done and testing is delayed. → 拆成两句，各管一段。
6. The main risk is the budget. 后面接的是排期内容。→ 改主题句，使其与内容一致。

**C 输出（1 题）**

写 250 词汇报稿：四段，每段第一句是主题句；进展 2—3 点；风险 1 点 + 应对；请求 1 个。被动 ≥ 3 处，名词性从句 ≥ 3 处。文件名 Day04_draft.md。先写中文提纲再翻成英文，能省一半时间；直接写英文容易在形容词上打转。

## 六、参考答案

**A**

1. Three of the five milestones have been reached.
2. Testing is two weeks behind schedule.
3. The new version will be rolled out in June.
4. Two issues remain before the launch.
5. We have a contingency plan for the vendor delay.
6. This extra report is out of scope.
7. I'd like to flag one risk early.
8. We need a realistic timeline for June.

错题点：第 3 题 roll out 的过去分词是 rolled out，别写 roll outed；第 7 题 flag 后面直接跟宾语，不加 about。

**B**

1. Three of the five milestones have been reached.
2. The main risk is a two-week delay in testing.
3. I need your approval of the extra budget by Thursday.
4. We're six weeks into the project and on track for June.
5. The design is complete.（进展段）／Testing is two weeks behind schedule.（风险段）
6. The main risk is that testing will slip by two weeks.

**C 参考范文（约 245 词）** 注意范文的第一句同时交代了项目、周数和路线图，这是口头汇报最省时间的开场方式，写稿时可以照此改写。

> **We're now in week six of the customer portal project, and today I'll cover progress, one risk, and one request.** The portal replaces three separate login pages, and the first release is planned for June.
>
> **Three of the five milestones have been reached.** The design was approved by the client in early September, and the new login flow has been tested with 120 users. Two offices are already using the portal, and the third will go live next week. The team is now working on the payment module, which is the last major piece before the release.
>
> **The main risk is that the payment module is two weeks behind.** The delay was caused by a missing API key from the vendor. If the key does not arrive by Friday, the June release will slip by two weeks, and the training sessions planned for May will need to move. To mitigate this, we have asked IT for a temporary key and prepared a fallback version that works without the module. Both options keep the June date, but the fallback needs one extra week of testing.
>
> **What I need from you is a decision on the extra budget for the fallback version.** It is about 8,000 yuan, mainly for one more week of testing. Could you approve it by Thursday? That would let us start on Monday and still deliver in June.

评析：四段主题句都能独立成立，后面的句子全部在支撑它；被动 4 处（was approved / has been tested / was caused / is planned），名词性从句 3 处（what I need / that the payment module is behind / that would let us）。

这段范文有意用了两个「代价句」：the June release will slip by two weeks 和 the fallback needs one extra week of testing。汇报里把代价说清楚，比反复保证「没问题」更容易拿到支持，因为听众判断的是风险，不是态度。

## 七、今日输出与自查

写完先别急着改语法，按顺序做三件事：数主题句、数段落里的「第二件事」、数被动和从句。三样都过，再处理冠词和介词这些小错。顺序反了，容易在细节上耗掉半小时，结构问题却还在。

| 检查项 | 标准 | 打勾 |
| --- | --- | --- |
| 稿件 | 文件名 Day04_draft.md，230—260 词 |  |
| 主题句 | 4 段各有 1 句，均在段首，不超过 15 词 |  |
| 结构 | 进展 2—3 点，风险 1 点 + 应对，请求 1 个 |  |
| 语法 | 被动 ≥ 3 处，名词性从句 ≥ 3 处，无形式错误 |  |
| 朗读 | 全文朗读 1 遍，标出 3 处读不顺的句子并改短 |  |
| 数字 | 稿内数字单独列一行，确认单位、时间、口径一致 |  |

## 八、明日预告

Day 5 把稿子练三遍，第三遍计时录音，必须压进 2 分钟。今天写超 260 词的话，明天要删；所以今晚先读一遍，把读起来别扭的长句改短，明天才有时间练节奏。另外把稿子里的数字单独抄一行——数字是汇报里最容易说错、也最容易被追问的部分，明天要专门练。