Week 20 — Checkpoint: advanced structures, the 10-minute talk, Q&A under pressure

This week

Grammar: mixed advanced structures · Vocabulary: review and 100-word check (plus five new words: multifaceted, pivotal, enshrine, harmonize, underpin) · Idioms & phrasal verbs: idiom review round (five new: read the room, go back to the drawing board, play devil's advocate, cut to the chase, the price of admission) · Speaking: a 10-minute technical talk · Writing: blog post final edit · Soft skill: Q&A under pressure

Checkpoint comm-5. On Day 7, record your second 100-word score (compare with Week 16), your Saturday rubric total, and whether your top-3 error-log items have decreased since Week 16. Any category that has not improved in four weeks is your focus for Weeks 21-23.

Day 1 — Grammar: mixed advanced structures

⏱ 30 min · Mon

Rule in 60 seconds

Seven advanced structures that mark C1-C2 writing and speech. Learn the pattern, then the trap.

Structure	Pattern	Example
Cleft (it-cleft)	It was + focus + that/who ...	"It was the stale cache that caused the outage."
Wh-cleft	What + clause + is/was + focus	"What we need is a clear owner."
Negative inversion	Negative adverbial + auxiliary + subject	"Rarely do we see such clean data." "Only after the postmortem did we understand the cause." "Hardly had the deploy finished when the alerts fired."
Subjunctive after recommend/insist/suggest/essential	that + subject + base verb (no -s, no will)	"I recommend that we postpone the release." "It is essential that she approve it."
Mixed conditional	If + past perfect, would + base verb (past cause, present result)	"If we had added an index, the queries wouldn't be slow now."
Inverted conditional (formal)	Should / Were / Had + subject ...	"Should the vendor miss the deadline, we will invoke the penalty clause." "Had we known, we would have escalated."
Prepositional relative	preposition + whom / whose + noun	"The team on whose approval we depend is in Singapore."

Traps: - Hardly/scarcely ... when, no sooner ... than: not "hardly ... than". - After a negative or only + adverbial, the auxiliary comes before the subject (did we understand); forgetting it is the most common error. - Recommend that we will/should: British English accepts should ("I recommend that we should postpone"); American English and formal writing prefer the bare subjunctive. Never will and never -s ("that she approves" is common in speech but non-standard in formal registers). - Mixed conditionals: mix only when the times differ; do not use them when both are past.

The error fluent speakers make: applying inversion in the wrong place ("Only we realized after..."), or using cleft sentences everywhere: one per paragraph is emphasis, three is a tic.

Exercise

1. Rewrite as an it-cleft emphasizing the cause: "The stale cache caused the outage."
2. Correct: "Only after the postmortem we understood the cause."
3. Correct: "Hardly had the deploy finished than the alerts fired."
4. Correct: "I recommend that we will postpone the release."
5. Combine into one mixed conditional: "We did not add an index. The queries are slow now."
6. Correct: "The team whose approval we depend is in Singapore."
7. Rewrite as a wh-cleft: "We need a clear owner."
8. Choose: "Rarely (we see / do we see) such clean data."
9. Combine with a participle clause and passive: "The API was designed for internal use. It was later exposed to partners. It now lacks rate limits."
10. Rewrite formally with inversion: "If the vendor should miss the deadline, we will invoke the penalty clause."

Answers and explanations

1. "It was the stale cache that caused the outage."
2. "Only after the postmortem did we understand the cause." Inversion after only + adverbial.
3. "...when the alerts fired." The pattern is hardly ... when (or no sooner ... than).
4. "I recommend that we postpone the release." Subjunctive: base form after recommend; should postpone is acceptable in British English.
5. "If we had added an index, the queries wouldn't be slow now." Past condition, present result.
6. "The team on whose approval we depend..." (or "whose approval we depend on"). The preposition must accompany the relative pronoun in the formal version.
7. "What we need is a clear owner."
8. do we see. Negative adverb rarely triggers inversion.
9. "Designed for internal use and later exposed to partners, the API now lacks rate limits."
10. "Should the vendor miss the deadline, we will invoke the penalty clause."

Use it

Write three sentences about your project: one it-cleft, one with Only after ... did, one inverted conditional (Should ...). Read them aloud; check each has correct word order.

Day 2 — Vocabulary: review and 100-word check

⏱ 30 min · Tue

Part A: five new words

Word	Part of speech	Meaning	Example
multifaceted	adjective	Having many different sides or aspects; complex, not reducible to one factor	"The outage was multifaceted: a config error, a missed alert and an on-call gap all played a part."
pivotal	adjective	Of central importance; a turning point on which outcomes depend	"The pilot was pivotal in winning executive support."
enshrine	verb	To formally set down and protect a rule, right or principle, often in a document or policy	"We enshrined the on-call handover in the team's runbook."
harmonize	verb	To make different things consistent or compatible with each other	"Finance could not harmonize the invoice with the usage report."
underpin	verb	To support or form the basis of something	"A shared event schema underpins every integration on the platform."

Collocations: a multifaceted problem / issue / challenge; a pivotal role / moment / decision / figure; enshrine a right / principle / rule (in law / in policy); harmonize A with B / harmonize standards / harmonize data; underpin a strategy / an argument / the economy / a system. Word family: facet / multifaceted; pivot / pivotal; enshrine / enshrined; harmonize / harmonization; underpinning (noun). Pronunciation: mul-ti-FASS-et-ed, PIV-uh-tl, en-SHRINE, HAR-mo-nize, un-der-PIN.

Part B: the 100-word check, round 2

This is a new set of 100 words. Score each: 2 = can use it accurately in a sentence, 1 = recognize it, 0 = do not know it. Maximum 200.

• Block 1 (evidence): empirical, anecdotal, plausible, robust, rigorous, validate, verify, benchmark, heuristic, proxy, threshold, variance, deviation, fluctuate, plateau, spike, decline, surge, statistically significant, causation.
• Block 2 (organization): delegate, empower, foster, cultivate, streamline, consolidate, restructure, onboard, retain, attrition, succession, ownership, governance, compliance, oversight, transparency, cross-functional, silo, bandwidth, capacity.
• Block 3 (argument): cogent, resonate, rebut, premise, sway, refute, contend, assert, imply, infer, presume, speculate, hypothesize, counterargument, objection, rhetoric, credibility, legitimacy, conviction, dissent.
• Block 4 (delivery and nuance): expedite, ostensibly, tenable, salient, tacit, considerably, notably, arguably, inherently, markedly, candor, tactful, reservation, bottleneck, resilience, redundancy, iterate, refine, prototype, regression.
• Block 5 (precision): multifaceted, pivotal, enshrine, harmonize, underpin, ambivalent, contentious, pragmatic, unequivocal, tentative, provisional, conclusive, negligible, substantial, disproportionate, incremental, exponential, sporadic, persistent, exhaustive.

Scoring guide

Score	Interpretation	Action
170-200	Strong active C1 range	Maintain by using words in real writing; shift to register and collocation
130-169	Solid; some passive	Convert all 1-score words into sentences this week
90-129	Wide passive, narrow active	Use each 1-score word aloud three times; log in your weak-word list
below 90	Core gaps	Study 5 words per day; prioritize words scored 0

Compare with your Week 16 score: any increase of 10 or more is real progress; if it has not moved, your method (not effort) needs changing, so use each word in a written sentence about your own work rather than rereading definitions. Add all 0- and 1-score words to your weak-word list (used in Week 23).

Exercise

Cloze. Word bank: multifaceted, pivotal, enshrine, harmonize, underpin, cogent, premise, arguably.

1. A ______ problem like this one needs input from security, ops and finance, not just engineering.
2. The security review was ______ to the go-live decision: without it, legal would not sign.
3. We should ______ the incident-response steps in a runbook before the next on-call rotation.
4. Please ______ the two dashboards; the counts differ by 4 percent.
5. Three assumptions ______ the forecast; if any fails, the estimate collapses.
6. The proposal has a shaky ______: that demand will double each year.
7. It is ______ the most important architectural decision we have made.
8. Her ______ summary won the support of both camps.

Answers and explanations

1. multifaceted: with several distinct aspects, not reducible to one cause. 2. pivotal: decisive turning point. 3. enshrine: formally set down and protect. 4. harmonize: make consistent. 5. underpin: form the basis of. 6. premise (week 19): an assumption. 7. arguably (week 17): a contestable claim. 8. cogent (week 19): clear and convincing.

Use it

Say three sentences about your organization using pivotal, enshrine and multifaceted. Add any word you missed in the check to your weak-word list.

Day 3 — Speaking: a 10-minute technical talk

⏱ 30 min · Wed

Prompt. Plan a 10-minute talk on a technical topic you know well (for example, "Designing idempotent event consumers"). Today: build the outline in 10 minutes and deliver the first two minutes (hook and roadmap) aloud in 20 minutes. Saturday you will record a compressed version.

Structure and time budget

Segment	Time	Purpose
Hook	0:45	A failure, a number or a question
Roadmap	0:45	"I'll cover three things: what broke, what we built, what we'd change"
Section 1	2:30	Problem and constraints
Section 2	3:00	Solution and one trade-off (with a diagram)
Section 3	1:30	Results and lessons
Summary + call to action	1:00	Restate three points; one thing to try
Buffer	0:30	Pauses and transitions

Use signposts: "That brings me to...", "The second thing is...", "To summarize...". Use an it-cleft or a wh-cleft once for emphasis ("What surprised us was...").

Pronunciation micro-drill: technical vocabulary stress

Word	Stress	Note
ar-chi-TEC-ture	AR-ki-tek-cher	First syllable
pa-RAM-e-ter	pa-RAM-e-ter	Second syllable
AL-go-rith-um	AL-guh-ridh-um	First syllable
in-fra-STRUC-ture	IN-fra-struk-cher	First syllable
ITER-ate	IT-er-ate	Verb: -ate said as /eɪt/
ku-ber-NET-eez	koo-ber-NET-eez	Kubernetes
cache	cash (one syllable)	Not "cash-ay"
queue	kyoo	Same sound as the letter Q

Say each, then in a sentence: "The cache holds the parameter until the queue drains."

Self-check - [ ] The hook was not "Today I'll talk about...". - [ ] The roadmap named three things clearly. - [ ] I used two signposts and one cleft. - [ ] Technical words were stressed correctly (pa-RAM-e-ter, AR-chi-tec-ture). - [ ] The first two minutes ran to time without rushing.

Day 4 — Idioms & phrasal verbs: idiom review round

⏱ 30 min · Thu

Expression	Meaning	Example
read the room	To sense the mood of a group and adjust your behavior accordingly. Informal but common in business.	"I was about to ask for budget, then I read the room and waited."
go back to the drawing board	To start again after a plan has failed. Informal; neutral in tone, slightly self-deprecating.	"The load test failed, so it's back to the drawing board."
play devil's advocate	To argue an opposing view deliberately, to test an idea. Neutral; say it aloud so people know your intent.	"Let me play devil's advocate: what if the vendor never delivers?"
cut to the chase	To get to the main point without preamble. Informal; can sound abrupt.	"To cut to the chase: we need two more engineers or a later date."
the price of admission	The minimum thing you must accept or provide to be allowed to compete or participate. Neutral to informal, US and UK.	"Multi-region failover is the price of admission for this customer."

Exercise (8 items)

1. Fill in: "The executives look tense; let's ______ before we mention the cost."
2. Fill in: "The prototype failed; we're going ______."
3. Fill in: "I'll ______: does anyone believe this schedule is realistic?"
4. Fill in: "Encryption at rest is ______ for enterprise customers."
5. Choose the best: "We're short on time, so let me ______." (cut to the chase / read the room)
6. Review (week 16): "The decision is unavoidable, so we might as well ______." (bite the bullet / cut corners)
7. Review (week 19): "The pilot data ______ the skeptics." (won over / went back to the drawing board)
8. Rewrite more idiomatically: "Let me argue the opposite position to test the plan."

Answers and explanations

1. read the room. 2. back to the drawing board. 3. play devil's advocate. 4. the price of admission. 5. cut to the chase: get to the point. 6. bite the bullet (week 16). 7. won over (week 19). 8. "Let me play devil's advocate."

When NOT to use them: cut to the chase can sound dismissive if said to someone giving context; use it about your own preamble ("let me cut to the chase"), not to ask others to hurry. The price of admission can sound flippant about a serious requirement; explain it plainly for international audiences unfamiliar with the phrase. Play devil's advocate should be announced, otherwise colleagues may think you are opposing them.

Day 5 — Writing: blog post final edit

⏱ 30 min · Fri

Draft to edit (a section from a blog post):

It is important to note that the implementation of the new caching layer was carried out by our team over the course of a period of three weeks. The decision was made by the team to make use of Redis, due to the fact that it has the ability to provide very fast reads. There were several issues that were encountered during the migration, and the team was of the opinion that a rollback would be necessary. It should be noted that the rollback was performed successfully and the results that were obtained were very good.

Task. Do a final edit: cut at least 40 percent of the words, replace passive and nominalized phrases with strong active verbs, remove filler ("it is important to note"), and keep one participle clause and one contrast for rhythm. Keep the meaning. Then list the edits you made in five bullets.

Model answer

We built the new caching layer in three weeks. We chose Redis because it reads faster than the alternatives. Hitting several issues during the migration, we rolled back once, then relaunched successfully. Reads now average 3 ms, not 40.

(Word count: about 45, from about 100, a 55 percent cut. If you kept the numbers vague, add real ones; the model invents "3 ms, not 40" as an example.)

What changed and why: - Filler removed: "It is important to note that" and "It should be noted that" carry no information. - Nominalizations became verbs: "the implementation was carried out" became "we built"; "made use of" became "chose"; "has the ability to provide" became "reads faster". - Passive became active with "we", which shortens and clarifies responsibility. - "Due to the fact that" became "because"; "over the course of a period of three weeks" became "in three weeks". - One participle clause ("Hitting several issues...") and one contrast ("3 ms, not 40") give rhythm and a concrete payoff instead of "very good".

Day 6 — Speaking record: the talk, compressed

⏱ 30 min · Sat

Record a 2-minute talk. Deliver the compressed version of your 10-minute talk: hook, roadmap, the single most important lesson with a trade-off, and the takeaway. If you have time, also record the full 10 minutes and score it on another day.

Structure: hook (15 s) - roadmap (15 s) - core section with one diagram described aloud (60 s) - summary (15 s) - call to action (15 s). Use one cleft, one negative inversion and two of this week's words.

Scoring rubric (1 to 4)

Criterion	1	2	3	4
Clarity	Message unclear	Point emerges late	Clear main point	Point is unmistakable and memorable
Structure	No visible order	Some order, jumps	Clear sequence	Signposted, on time
Fluency	Frequent stops/fillers	Occasional long pauses	Mostly smooth	Smooth with deliberate pauses
Grammar accuracy	Errors block meaning	Frequent errors	Few errors	Advanced structures used correctly
Vocabulary range	Repeats basic words	Some C1 words	Good range	Precise, varied, natural
Pronunciation	Hard to follow	Stress errors distract	Generally clear	Technical terms and rhythm strong

Shadowing task. Shadow two minutes of a strong technical conference talk (for example, a QCon, GOTO or Strange Loop recording on YouTube) or a TED talk on technology. Watch the speaker's opening and copy the pace of the first 30 seconds.

Log your score: total out of 24 and compare with your Week 16 pitch and Week 14 negotiation recordings. Note which criterion has improved most.

Day 7 — Soft skills + weekly review: Q&A under pressure

⏱ 30 min · Sun

Scenario. After your technical talk, two questions arrive from the front row. (1) A director asks sharply: "Isn't this just reinventing Kafka? Why should we trust a homegrown solution?" (2) An engineer asks about the memory footprint at 100,000 partitions, which you have not measured.

Task. Script your answer to both questions in about 150 words in total.

Model response

"[Pause, then paraphrase.] So the question is whether we're duplicating Kafka and taking on unnecessary risk. It's a fair concern. There is overlap, and we did evaluate Kafka. What ruled it out was the operational cost for our team size, and our requirement for per-tenant ordering, which needed custom partitioning. We mitigated the homegrown risk by limiting the scope to one use case and open-sourcing the tests. Does that answer the trust question?

[Second question.] Good question, and I don't have that number. We've tested up to 10,000 partitions, where memory grew linearly, roughly 2 MB per thousand. Extrapolating suggests around 200 MB at 100,000, but I'd want to verify it before you rely on that. I'll run the test this week and share the result; if you leave your email with me, I'll send it."

Techniques used: (1) A pause and paraphrase gives thinking time and checks understanding. (2) The premise is corrected politely ("there is overlap, and we did evaluate") without saying "you're wrong". (3) Reasons before reassurance. (4) A check question closes the loop. (5) For the unknown: honest "I don't have that number", what you do know, a labeled extrapolation, and a dated follow-up, never a guess presented as fact. (6) Facts and numbers, no defensiveness.

Weekly recap (20 items)

1. Form an it-cleft: "The cache caused the outage."
2. What happens after "Only after..."?
3. Correct: "Hardly had he left than..."
4. Subjunctive: "I recommend that she ___ (approve)."
5. Mixed conditional pattern?
6. Formal inversion of "If the vendor should miss...".
7. Which relative form: "the team ___ approval we need"?
8. Define multifaceted.
9. What does pivotal mean?
10. What does enshrine mean?
11. Meaning and preposition pattern of harmonize?
12. Give a collocation of underpin.
13. Stress in pa-RAM-e-ter?
14. Pronounce cache.
15. "Read the room" means...?
16. "Back to the drawing board" means...?
17. "The price of admission" means...?
18. Why announce "devil's advocate"?
19. When you do not know an answer in Q&A, what four things should you do?
20. Why paraphrase a hostile question before answering?

Answers

1. "It was the cache that caused the outage." 2. Inversion: "did we understand". 3. "...when". 4. approve (bare form). 5. If + past perfect, would + base form. 6. "Should the vendor miss the deadline, ..." 7. whose. 8. Having several distinct aspects. 9. Central and decisive. 10. To formally set down and protect a rule or principle. 11. Make consistent; harmonize A with B. 12. underpin a strategy / an argument. 13. Second syllable. 14. "cash". 15. Sense the mood and adapt. 16. Start over after a failure. 17. The minimum thing you must accept to be allowed to compete. 18. So colleagues know you are testing, not opposing. 19. Say you do not know, share what you do know, label any estimate, promise a dated follow-up. 20. It buys thinking time, confirms understanding and de-escalates.

Self-score (comm-5 checkpoint) - [ ] I can use cleft, inversion, subjunctive and inverted conditional structures accurately. - [ ] My second 100-word score is recorded and compared with Week 16. - [ ] I outlined and delivered a talk with a time budget. - [ ] I can edit for concision without losing meaning (cut 40 percent). - [ ] I can handle a hostile question and an unknown answer calmly.

Error log. Write down your top 3 recurring mistakes and compare them with Week 16's list: which have gone, which persist? Carry the persisting ones into Weeks 21-23, when the pace rises to timed, interview-grade practice.