# 英语中级 · 第 1 周 Day 5｜模拟会议六问答

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

**今天学什么**
前四天你一直在准备材料：会议词、时态、八句进展。今天把它们扔进一个真实的压力场景——没人给你稿子，六个问题连着问，你要在 15 秒内开口。六个问题覆盖了项目会议里八成的追问：进度、延迟、资源、风险、下一步、需要什么。练完这一遍，下次开会你至少不会在「So where are we?」之后沉默五秒。

## 一、今日任务

| 环节 | 时长 | 具体动作 | 产出 |
| --- | --- | --- | --- |
| 1. 写问题卡 | 8 min | 把六个问题各写一张卡，正面英文问题，背面只写两个关键词 | 6 张问题卡 |
| 2. 关键词准备 | 10 min | 每题写 2 个关键词，不写整句；数字和时间尽量具体 | 12 个关键词 |
| 3. 逐题自问自答 | 12 min | 抽卡，看问题 3 秒内开口，每题说 2—3 句，说完立刻下一张 | 6 段短回答 |
| 4. 连成 90 秒 | 15 min | 六题连做，中间不暂停，录 3 次，留最后一版 | 90 秒录音 |
| 5. 回听标记 | 10 min | 听最后一版，标出停顿超过 2 秒的地方和时态错误 | 标记稿 |

六个问题不是随便挑的，它们对应会议里四个真实功能：汇报（进度）、解释（延迟）、预判（风险）、请求（资源与支持）。把这四类答顺了，临时被问到别的细节，也能挂到其中一类上，不至于慌。录音时建议站着说，气息更稳，也更容易进入「在开会」的状态。

自问自答的关键是「不许写稿」。先看问题卡背面的两个关键词，把它们当成唯一的路标，剩下的句子现场拼。写了稿就会背，背出来的是书面语，一紧张全忘。只写关键词，逼自己现场组句，这才是开会时真正发生的事。

## 二、核心词汇与搭配

| 词（音标） | 词性 | 释义 | 高频搭配 | 例句与翻译 |
| --- | --- | --- | --- | --- |
| status /ˈsteɪtəs/（≈斯泰特斯·轻） | n. | 状态、进展 | give a status update；status report | Let me give a quick status update. 我先简单说一下进展。 |
| at risk /ət rɪsk/ | 短语 | 有风险 | at risk of slipping；put sth at risk | The June date is at risk. 六月的节点有风险。 |
| capacity /kəˈpæsəti/（≈克派瑟提） | n. | 产能、人力 | spare capacity；at full capacity | We don't have the capacity this month. 这个月我们没有人力。 |
| bandwidth /ˈbændwɪdθ/（≈班德威德思） | n. | 精力、可用时间（口语） | have the bandwidth to do sth | I don't have the bandwidth for another project. 我没有精力再接一个项目。 |
| dependency /dɪˈpendənsi/（≈迪佩恩德恩西） | n. | 依赖项 | a hard dependency；remove a dependency | The vendor is a hard dependency for us. 供应商是我们的硬依赖。 |
| mitigation /ˌmɪtɪˈɡeɪʃn/（≈米提诶希恩） | n. | 缓解措施 | a mitigation plan；mitigation steps | What's our mitigation plan? 我们的缓解方案是什么？ |
| contingency /kənˈtɪndʒənsi/（≈克恩提恩哲恩西） | n. | 应急方案 | a contingency plan；as a contingency | We have a contingency plan for the delay. 延迟我们有应急方案。 |
| slip /slɪp/（≈斯利普·短） | v. | 滑期、推迟 | slip by a week；the date has slipped | The launch has slipped by two weeks. 上线滑期两周。 |
| on hold /ɒn həʊld/ | 短语 | 暂停 | put sth on hold | Hiring is on hold until June. 招聘暂停到六月。 |
| come up /kʌm ʌp/ | 短语动词 | 出现（问题） | sth came up；come up with | A new issue came up this morning. 今早出了个新问题。 |

记这组词的时候顺手记一个搭配场景：status update 用在开场，at risk 用在预警，capacity 和 bandwidth 用在要人，dependency 和 contingency 用在谈风险，slip 用在报偏差，on hold 用在说暂停，come up 用在说突发。一个词对一个场景，说的时候不用想。

这组词里最容易用错的是 bandwidth 和 capacity。capacity 偏「人力、产能」，讲团队规模用；bandwidth 偏「某人有没有精力」，讲个人时间用。跟老板说 I don't have the bandwidth 比说 I'm busy 专业得多，但别对客户说，听起来像推脱。

## 三、语篇点：回答先给结论

会议回答和写作文不一样，听的人没有耐心等你铺垫。四步结构：结论、原因、影响、请求。

1. **第一句必须是结论。** 好、不好、按期、滑期，先给判断。On track. / We're two weeks behind. / The date is at risk.
2. **第二句给原因，一句就够。** because testing took longer than we expected。不要从三月讲起。
3. **第三句说影响。** 影响的是日期、预算还是客户：That puts the June launch at risk.
4. **第四句说你要什么。** 要人、要时间、要决定：I need one more tester for two weeks.
5. **没准备好就明说，并给时间点。** I don't have the numbers yet; I'll send them by four. 这比编一个数字安全。

为什么结论要放第一句？因为会议是多人场合，每个人只分给你十几秒注意力。你说到第三句才给出「落后十天」，前面两句已经被人脑补成「还行」。反过来，先给「落后十天」，听的人会自动竖起耳朵听原因，后面的话反而更容易被记住。这个顺序和你写邮件正好相反：邮件可以先铺垫，口头不行。

**正误对比**

| 绕的回答 | 结论先行 | 差在哪 |
| --- | --- | --- |
| Well, we started in July and then there were some issues with the vendor and the team was quite busy, so… | We're about ten days behind. The vendor was late with the data. | 前一句要听 20 秒才知道好坏 |
| Maybe it's fine, I think, probably. | It's on track. | 模糊词堆在一起等于没回答 |
| We need more people because the workload is high and everyone is tired. | I need one more tester for two weeks. | 请求要具体到人、到时长 |

**常见错误**

- 用 might、maybe、probably 遮住判断，听的人反而更担心。
- 只讲过程不讲结果：说了三分钟做了什么，没说现在到哪。
- 把「需要什么」答成抱怨：大家太累了。要换成具体的资源和时长。

每题控制在 15 秒左右，是个很实用的自我约束。15 秒大约能说三句、四十个词，刚好装下结论、原因、请求。超过 20 秒，听的人开始走神；低于 8 秒，信息不够，别人还得追问。练的时候可以用手机计时，六个问题连下来正好 90 秒，这就是今天录音的标准长度。

## 四、句型与范例

| 问题 | 开场句 | 补充句 |
| --- | --- | --- |
| 进度 | We're on track for… | We've finished… and we're now… |
| 延迟 | We're about… behind. | The delay comes from… |
| 资源 | We're at full capacity. | We'd need… to stay on schedule. |
| 风险 | The main risk is… | If that happens, we'll… |
| 下一步 | Next, we'll… | That should take about… |
| 需要什么 | I need… by… | Can you confirm by Thursday? |

**90 秒示范（六问连答）**

> — Where are we with the launch?
> — We're about ten days behind, but still inside the quarter. Testing took longer than we planned.
> — Why the delay?
> — The vendor sent the data late, and we had to redo one round. We've already fixed the process with them.
> — Do you have enough people?
> — Not really. We're at full capacity until the end of the month.
> — What's the biggest risk?
> — The payment module. If it fails again, the launch slips into July. We have a contingency plan: we ship without it and add it in August.
> — What's next?
> — We'll finish testing by the 20th and do a final review on the 22nd.
> — What do you need from me?
> — One more tester for two weeks, and a decision on the payment module by Friday.

注意六段里几乎没有 I think，也没有 maybe。不是因为这些词不能用，而是回答自己的项目时，模糊词会让对方怀疑你掌握不掌握情况。真要保留不确定，就把不确定放在具体位置上：I'm not sure about the exact date, but it's the week of the 20th。

六段回答平均 15 秒，每段都是「结论—原因—影响—请求」的简化版。你练的时候可以先照着念一遍，再抽掉文字只看问题卡。

## 五、练习

做改写题时先问自己：这句话最想让人记住哪个信息？把它提到第一句，其余全部降级成一句原因或一句影响。六题都这么处理，你会发现原来三句话的信息，一句话就能说清。

**A 词汇（8 题）**

1. 填空：The launch is ______ risk because of the payment module.
2. 填空：Hiring is ______ hold until we know the budget.
3. 用 capacity 翻译：这个月我们人手已经满了。
4. 用 slip 翻译：上线滑期两周。
5. 改错：I don't have bandwidth for another project.（缺什么）
6. 选词（mitigation / contingency）：What's our ______ plan if the vendor fails again?
7. 选词（dependency / status）：The vendor is a hard ______ for the June date.
8. 用 come up 写一句：今早出了个新问题，我们正在处理。

**B 改写：把绕的回答改成结论先行（6 题）**

9. Well, we had a meeting and discussed a lot, and I think maybe we are more or less OK.
10. The team is working very hard and everyone is quite tired, so we may need some help.
11. We started testing in August and there were several problems, so now we are still testing.
12. I'm not sure about the numbers, I need to check with finance.
13. If the vendor is late again, things will be difficult, but we will try our best.
14. We will do the review next week and then decide.

**C 输出（2 题）**

15. 口头：六问连答，录 90 秒，不写稿，留最后一版。
16. 书面：把录音写成 100—120 词的会议回答稿，保留结论先行的结构，用出至少 5 个今日词。

## 六、参考答案

1. at。at risk 是固定搭配，表示有风险。
2. on。on hold 表示暂停。
3. We're at full capacity this month. at full capacity 比 we are busy 具体。
4. The launch has slipped by two weeks. slip by + 时长。
5. 改为 I don't have the bandwidth for another project. bandwidth 前面要加 the。
6. contingency。contingency plan 是应急方案，mitigation 是缓解措施，这里问「万一失败怎么办」，用前者。
7. dependency。hard dependency 指绕不开的依赖。
8. A new issue came up this morning, and we're looking into it. come up 是不及物用法。
9. We're on track. 或 We're slightly behind but inside the quarter. 先给判断，再决定要不要解释。
10. We need one more person for two weeks. 把「大家累」换成具体请求。
11. We're still testing, about two weeks behind. 一句说清状态和偏差。
12. I don't have the numbers yet; I'll confirm with finance and send them by four. 承认不知道，但给出时间点。
13. The July date is at risk. We have a contingency plan: we ship the core features first. 先给风险等级，再给方案。
14. We'll review next week and decide by Friday. 给出两个时间点，别用 then。

**15 评分**：90 秒内说完六问，每问不超过 20 秒，时态错误 ≤ 2 处，六问都有明确结论。
**16 参考**：We're about ten days behind, but still inside the quarter. Testing took longer because the vendor sent the data late, and we had to redo one round. We're at full capacity until the end of the month, so I need one more tester for two weeks. The main risk is the payment module; if it fails again, the launch slips into July, and we have a contingency plan to ship without it. Next, we'll finish testing by the 20th and review on the 22nd. 结构完整，五个词用出。

录音回听时按三个层次听：第一遍只听有没有结论，第二遍只听时态，第三遍只听停顿。三个层次分开听，问题才定位得准；一边听一边什么都想抓，最后只记得「说得不太好」这种没用的结论。

## 七、今日输出与自查

| 检查项 | 门槛 | 存档 |
| --- | --- | --- |
| 问题卡 | 6 张，正面英文，背面 2 个关键词 | 纸质卡 |
| 录音 | 90 秒，六问齐全，不写稿 | Day05_六问答.m4a |
| 时态 | 错误 ≤ 2 处 | 回听标记 |
| 结构 | 每问第一句是结论 | 逐题打勾 |
| 今日词 | 口头用出 ≥ 5 个 | 记录清单 |

把最后一版录音存好，不要覆盖。Day 7 录完纪要朗读后，把两段放在一起听，你会发现自己这周真正的变化不在词汇量，而在敢不敢在第一句就给判断。这个变化比多背十个词值钱。

## 八、明日预告

Day 6 复盘：重做 20 题，默写 8 个词，把正确率记下来。今天录音里标出的时态错误，明天要在错题本里找到对应类型——同一个错犯两次，说明你的判断顺序还没固定。