# 英语中级 · 第 3 周 Day 5｜百词状态更新的写法

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

**今天学什么**

今天的产出是本周两件成品之一：100 词协作状态更新，含 3 项进展、1 个阻塞、1 个明确请求，并且至少 3 个定语从句不出错。难点不是写满 100 词，而是在 100 词里把「做了什么、卡在哪、要你帮什么」说清楚，还让人愿意读完。今天用一个固定骨架解决结构，用「一句一信息」解决长度，最后用定语从句把背景压进句子里，避免写成流水账。

## 一、今日任务

| 环节 | 时长 | 具体动作 | 产出 |
| --- | --- | --- | --- |
| 拆骨架 | 8 min | 读第三节五段结构，把本周三件真实进展写成关键词，不写句子 | 5 行关键词 |
| 写主干 | 20 min | 先写 5 句主干（主谓宾齐全），不管从句 | 5 句主干 |
| 加从句 | 12 min | 在 3 处补定语从句，标出先行词与关系词 | 初稿 |
| 压缩 | 10 min | 删形容词与重复信息，把字数压到 95—110 词 | 100 词初稿 |
| 朗读校对 | 10 min | 朗读一遍，改掉读不顺的地方，检查请求是否有时间点 | 朗读版 |

合计 60 分钟。先写主干再加从句，顺序不要反：先想从句，句子一定会头重脚轻。

动笔前先定一件事：这份更新发给谁。发给上级就突出风险与请求，发给协作方就突出交付时间，收件人不同，第一句就不同。

## 二、核心词汇与搭配

| 词 | 音标 | 词性 | 释义 | 高频搭配 | 例句 |
| --- | --- | --- | --- | --- | --- |
| progress | /ˈprəʊɡres/（≈普罗格雷斯） | n. | 进展 | make progress；progress on sth | We've made good progress on the data mapping. 数据映射进展不错。 |
| on track | /ɒn træk/ | phr. | 按计划进行 | stay on track；on track for Friday | The launch is still on track for Friday. 发布仍按计划在周五进行。 |
| slip | /slɪp/（≈斯利普·短） | v. | （时间）往后滑 | the date slipped by a week | The testing date has slipped by three days. 测试日期往后滑了三天。 |
| risk | /rɪsk/（≈里斯克·短） | n. | 风险 | at risk；a real risk of sth | The launch date is now at risk. 发布日期现在有风险。 |
| priority | /praɪˈɒrəti/（≈普赖奥若提） | n. | 优先级 | top priority；set priorities | Fixing the login bug is our top priority. 修复登录问题是我们的最高优先级。 |
| request | /rɪˈkwest/（≈里克韦斯特） | n. | 请求 | a request for sth；at sb's request | This is a request for two more testers. 这里请求再增加两名测试人员。 |
| ETA | /ˌiː tiː ˈeɪ/ | n. | 预计完成时间 | what's the ETA?；ETA Friday | What's the ETA on the API key? 接口密钥预计什么时候到位？ |
| next step | /nekst step/ | n. | 下一步 | the next step is to… | The next step is to run the final test. 下一步是跑最终测试。 |

状态更新里最值钱的两个词是 blocker 和 ETA：一个说明卡在哪，一个说明什么时候能好。评审的人通常只扫这两处，其余都是背景。

## 三、语篇点：五段骨架与从句密度

**五段骨架（100 词刚好装下）**

1. **开场一句**：a quick update on + 项目名。不超过 12 词。
2. **进展三句**：每句一项，动词用过去时或现在完成时，结尾带一个可验证的结果（日期、数量、百分比）。
3. **阻塞一句**：说清「什么挡住了什么」，不要只写「有困难」。
4. **请求一句**：要什么 + 谁来做 + 什么时候。
5. **收尾半句（可选）**：下一步或 thanks。

**四条规则**

1. **一句一信息**。一句话里塞两件事，读者只会记住后一件。
2. **主干先出**。先写「谁做了什么、结果如何」，从句只用来补背景。写完主干再想从句，句子自然短。
3. **从句密度控制在 3—5 个**。全篇 100 词，3 个从句已经能提供足够背景；每句都带从句，读起来像合同。
4. **阻塞和请求必须可执行**。阻塞要写影响（which puts the launch at risk），请求要写时间（by Thursday）。

写之前先想清楚读者是谁。如果是你的直属上级，他最想知道「有没有风险、要不要他出手」，进展可以压缩；如果是跨部门协作方，他关心「你这边的产出什么时候能给到我」，时间点要写足。同一份 100 词更新，换个读者，重心就要移。这一点想明白，句子自然知道该先写哪句。

**定语从句在这里的三个用途**

| 用途 | 例子 | 说明 |
| --- | --- | --- |
| 定义对象 | the dashboard **that the team built last quarter** | 团队可能有好几个面板，需要限定 |
| 补充背景 | the API key, **which IT promised on Monday**, is still missing | 不限定，只是提醒对方承诺过 |
| 评价影响 | the date has slipped by three days, **which puts Friday at risk** | which 指代整句，一句话收住后果 |

**正误对比**

| 问题写法 | 改后 | 差别 |
| --- | --- | --- |
| Testing delay, need key. | Testing is delayed because we are still waiting for the API key. | 名词堆不是句子，读者要猜关系 |
| Please help with the budget. | Could you approve the extra budget by Thursday? | 请求要有动作、对象、时间 |
| The report that I sent that Tom wrote which covers Q3 is late. | The Q3 report, which Tom wrote, is late. | 三个从句套在一起，主干被埋掉 |

**三个常见错误**

- **把进展写成过程**。We had a meeting and discussed and then we decided… 不是进展，进展是「决定了什么、完成了什么」。
- **阻塞没有影响**。只说 The API key is missing，读者不知道急不急；补一句 which is blocking the final test。
- **请求没有时间点**。Could you help? 等于没提；by Thursday 才是请求。

还有一类不明显的错误：把「没做完」写成「正在做」。We are working on it 连续出现三次，读者会认为你在拖。换成具体进度数字，哪怕只是 11 of 14，也比「还在做」可信。

## 四、句型与范例

1. Here's a quick update on the migration project.
   这里简单汇报一下迁移项目的进展。
2. We finished the data mapping on Tuesday, **which was two days ahead of schedule**.
   我们周二完成了数据映射，比计划早了两天。
3. The dashboard **that the team built last quarter** is now in testing.
   上个季度团队做的那个看板现在进入测试了。
4. We've fixed eleven of the fourteen bugs **that were reported last week**.
   上周报告的十四个问题我们已经修好十一个。
5. The main blocker is the API key, **which IT promised on Monday**.
   主要阻塞项是接口密钥，IT 周一承诺过。
6. Without it we cannot run the final test, **which puts Friday at risk**.
   没有它我们就跑不了最终测试，这让周五的进度有风险。
7. Could you ask IT to issue the key by Thursday?
   你能让 IT 在周四前把密钥发出来吗？
8. The next step is to run the final test **as soon as the key arrives**.
   下一步是密钥一到就跑最终测试。

第 8 句不是从句，但它是收尾最好用的一句：把「下一步」和「条件」绑在一起，读者立刻知道该盯什么。

## 五、练习

**A 词汇（8 题）**

1. 翻译：数据映射进展不错。
2. 填空：The launch is still ______ track for Friday.
3. 翻译：测试日期往后滑了三天。
4. 选词（risk / priority）：Fixing the login bug is our top ______.
5. 翻译：接口密钥预计什么时候到位？
6. 填空：This is a ______ for two more testers.
7. 翻译：下一步是跑最终测试。
8. 改错：The date slipped for three days.

**B 语篇与改写（6 题）**

1. 把名词堆改成完整句：Testing delay, no key, need help.
2. 给请求补上对象和时间：Please approve the budget.
3. 合并成一句，用 which 指代整句：The key arrived late. This delayed the test by two days.
4. 把两个短句合成含定语从句的一句：We fixed eleven bugs. They were reported last week.
5. 判断下面哪句适合做阻塞句，说明理由：a. The API key is missing. b. The API key is missing, which is blocking the final test and puts Friday at risk.
6. 删到 100 词以内（原句 138 词，只保留必要信息）：先数信息点，再决定删哪句。原段落：I just wanted to give you a quick update on where we are with the migration project at the moment. We have been working on the data mapping for the last two weeks and I am happy to say that we finished it on Tuesday, which was actually two days ahead of the schedule that we agreed. The dashboard that the team built last quarter is now in testing and we have fixed eleven of the fourteen bugs. The main blocker right now is the API key and we are still waiting for IT. Could you please ask IT to issue the key by Thursday?

**C 输出（2 题）**

1. 写作：100 词状态更新（95—110 词），3 项进展 + 1 个阻塞 + 1 个请求，含 ≥ 3 个定语从句。这是本周成品之一，文件名见第七节。
2. 口头：朗读初稿 60 秒，录音；再脱稿说一遍同样的内容，允许简化。

## 六、参考答案

**A 组**

1. We've made good progress on the data mapping. progress 不可数，用 make progress。
2. on。on track 是固定搭配，介词不能换。
3. The testing date has slipped by three days. slip by 表示滑了多久。
4. priority。top priority 指最高优先级，risk 与句意不合。
5. What's the ETA on the API key? ETA 前用 on 接对象。
6. request。a request for sth 是固定搭配。
7. The next step is to run the final test. next step 后接不定式。
8. The date slipped by three days. 幅度用 by，不用 for。

**B 组**

1. Testing is delayed because we still don't have the API key, and we need your help. 名词堆补成主谓结构。
2. Could you approve the extra budget by Thursday? 动作、对象、时间三样齐全。
3. The key arrived late, which delayed the test by two days. which 指代前面整句，前面必须有逗号。
4. We fixed eleven of the bugs that were reported last week. 先行词是 bugs，从句缺主语，用 that 或 which。
5. b。a 只说了状态，没说影响；b 把「挡住什么、威胁什么」都写出来，读者才知道要不要现在处理。
6. 参考（96 词）：Here's a quick update on the migration project. We finished the data mapping on Tuesday, which was two days ahead of schedule. The dashboard that the team built last quarter is now in testing, and we've fixed eleven of the fourteen bugs. The main blocker is the API key, which IT promised on Monday. Without it we can't run the final test, which puts Friday at risk. Could you ask IT to issue the key by Thursday? Thanks. 删掉的是寒暄（I just wanted to…）、重复的时间状语（for the last two weeks）和解释性从句（that we agreed）。

**C 组参考范文（104 词）**

Hi all, a quick update on the migration project. First, we finished the data mapping on Tuesday, which was two days ahead of schedule. Second, the dashboard that the team built last quarter is now in testing, and eleven of the fourteen bugs are fixed. Third, HR has signed off the training plan. The main blocker is the API key, which IT promised on Monday. Without it we cannot run the final test, which puts Friday at risk. Could you ask IT to issue the key by Thursday? Thanks.

数一遍：3 个进展、1 个阻塞、1 个请求、4 个从句（which 两处、that 一处、which 指代整句一处），104 词。第二项进展用了并列，是因为它和第一项同属「测试准备」，合并不影响信息量。

## 七、今日输出与自查

| 检查项 | 达标线 | 怎么查 |
| --- | --- | --- |
| 字数 | 95—110 词 | 编辑器字数统计 |
| 结构 | 3 进展 + 1 阻塞 + 1 请求 | 逐项打勾 |
| 从句 | ≥ 3 个，无关系词与逗号错误 | 标出先行词 |
| 请求 | 有动作、对象、时间 | 找出 by + 时间 |
| 朗读 | 60 秒内读完，不磕巴 | 录音回听 |

产出文件：`Day05_状态更新初稿.md`（95—110 词）与 `Day05_朗读.mp3`。今天只交初稿，不追求终稿；Day 7 会在此基础上改成定稿，所以把改不动的地方标出来，别硬憋。

初稿里如果有一句你读了三遍还不顺，问题多半在信息顺序，不在语法。把它拆成两句，再决定哪一句可以删——100 词的容量只够放读者必须知道的事。

## 八、明日预告

Day 6 复盘：合并句改错、词表默写、听录音标停顿，三件事各占 20 分钟。复盘日不产出新东西，只把前三天的错处逐个消掉，所以今天写错的句子先别扔。今天的初稿先放着，明天不动它——复盘日只处理「已经学过的」，不产生新内容。记得把 Day 2 的 20 句和 Day 4 的录音都找出来。