Week 11 — Articles, register and escalation¶

This week

Grammar: Advanced articles and the zero article with abstract nouns · Vocabulary: Register: formal vs informal, and switching · Idioms & phrasal verbs: Escalation phrasal verbs: flag up, push back, loop in · Speaking: Clarity on calls and video: pacing, signposting · Writing: Escalation emails · Soft skill: Saying no without burning bridges

Day 1 — Grammar: Advanced articles and the zero article with abstract nouns¶

⏱ 30 min · Mon Week 1 covered the basics of a/the/zero. This week is the hard part: abstract nouns and fixed phrases, where fluent speakers still slip.

Rule in 60 seconds¶

1. Generic abstract and uncountable nouns take no article. Reliability matters more than speed, Security is a shared responsibility, Latency is critical for users, Trust takes years to build. Generic plural nouns also take zero: Engineers dislike meetings.

2. Add the when the noun is specified or unique. A specifying phrase (of ..., a relative clause, a limiting adjective) makes the noun definite:

**The** reliability **of our platform** is our priority.
**The** trust **we built with the carriers** took years.
**The** latency **in the checkout flow** doubled.

3. Use a/an with abstract nouns when they are qualified as one instance or kind: a deep understanding of the domain, a growing need for automation, a lack of trust, a high degree of uncertainty, a reasonable expectation. Without the qualifier, they are zero: We need understanding, There is need for automation is unusual.

4. Fixed phrases (learn as chunks).

Zero article	With `the`
in production, in development, in practice, in theory	in the cloud, in the meantime, in the end
at scale, at risk, at work, at speed	on the whole, on the other hand
on time, in time, in advance, in detail	at the moment, at the same time
by email, by phone, by hand, by design	the internet (also `the web`), the market, the board
under pressure, in charge, on call	in the loop (idiom), out of the office

5. Unique or shared reference takes the: the CTO, the board, the customer (the one we discussed), the data (specific data set). Generic: data (Data drives decisions).

6. Product and proper names: zero for most (Kubernetes, Kafka, Terraform), but the before a generic noun after the name (the Kubernetes API, the Jira ticket). Countries: zero (Germany), except the Netherlands, the UK, the US.

The errors fluent speakers make:

Over-inserting the for generic ideas: The latency is critical for the users (generic; should be Latency is critical for users).
in the production (wrong: in production, unless the production environment).
Adding a to uncountable nouns: a documentation, an information. Use some documentation, a piece of information.
Dropping the article before a qualified abstract noun: We have great need for automation should be a great need for (though great need is also found in formal writing).
by the email: means of communication needs zero (by email).

Exercise¶

Correct each sentence or fill the gap (10). Write - for zero article.

The latency is critical for the users.
We need a documentation for the API.
___ reliability matters more than ___ speed in this domain.
The service is running in the production.
She has ___ deep understanding of the payment domain. (a / the / -)
We contacted them by ___ email. (the / an / -)
___ trust is hard to rebuild. (Trust / The trust) Use for generic meaning.
___ trust that we built with the carriers took years. (Trust / The trust)
Our workloads run in ___ cloud and must perform well ___ scale. (fill each)
The success of the project depends on a support from leadership.

Answers and explanations

Latency is critical for users. Both nouns are generic.
We need **documentation** for the API (uncountable). A piece of documentation is possible but rarely needed.
- and -: Reliability matters more than speed. Generic abstract nouns.
The service is running **in production**. Fixed phrase.
a: a deep understanding of..., qualified abstract noun.
-: by email, means of communication.
Trust: generic idea.
The trust: it is specified by that we built with the carriers.
in **the** cloud and at scale (zero). Both fixed chunks.
...depends on **support** from leadership. Uncountable, no a; leadership here is generic.

Use it¶

Write three sentences about your work using: one generic abstract noun with zero article (Reliability...), one specified abstract noun with the ... of (the reliability of the billing service), one fixed phrase (in production, at scale, on call). Then read them aloud and listen for the where it does not belong.

Day 2 — Vocabulary: Register: formal vs informal, and switching¶

⏱ 30 min · Tue Register is the level of formality. In global enterprises you move between Slack, a design review and a board paper in one day.

Word	Part of speech	Meaning	Example
ascertain	verb	To find out something with certainty; formal for `find out` or `check`.	We need to ascertain whether the data was encrypted at rest before we notify the regulator.
notwithstanding	preposition	Despite; formal, used in contracts and formal reports; can go before or after its noun.	Notwithstanding the vendor's delay, the go-live date remains 14 March.
expedite	verb	To make a process happen faster; formal for `speed up`.	Could you expedite the security review, as the launch date is fixed?
reiterate	verb	To say again, for emphasis or clarity.	I want to reiterate that no customer data was exposed.
forthright	adjective	Direct and honest in speech; more formal than `candid`, often used to describe someone who states an opinion plainly.	The VP was forthright about which two features would slip.

Collocations and word family¶

ascertain: ascertain the facts / cause / extent / whether; noun ascertainment is rare; use determine in similar formal contexts. Not used with people (ascertain John).
notwithstanding: notwithstanding the above / this / any objections / anything in section 4; also postposed: objections notwithstanding. Do not use in casual writing.
expedite: expedite a request / delivery / approval / process; noun expedition (a journey) is a different word; adjective expeditious (formal).
reiterate: reiterate a point / commitment / concern / that; noun reiteration; repeat is the neutral choice.
forthright: a forthright answer / manner / assessment; adverb forthrightly (rare, prefer in a forthright way); do not confuse with forthcoming (willing to give information, or about to happen).

Register ladder: find out (informal) < check < establish < ascertain / determine (formal). Speed up < accelerate < expedite. Start < commence. Help < assist. Use commence, ascertain, aforementioned only when a document requires legal or highly formal tone; overuse makes writing stilted.

Exercise¶

Fill each gap (8). Review words: contentious, leverage, negligible.

Please ______ the cause of the failure before we brief the customer.
______ the delay, we still expect to meet the deadline.
Could you ______ the approval, since the vendor's quote expires on Friday?
I would like to ______ that the deadline has not changed.
Give me your ______ opinion: is the team ready? (more formal than candid)
Which register is Let's find out what went wrong: informal or formal? Rewrite formally.
Ownership of the shared queue is a ______ topic between the two teams.
The impact on latency is ______, so we can proceed.

Answers and explanations

ascertain (find out with certainty), or determine.
Notwithstanding: despite, formal.
expedite: speed up.
reiterate: say again.
forthright: direct and honest, a formal register choice.
Informal. Formal: We need to ascertain what went wrong. / We must establish the cause.
contentious (review, Week 8).
negligible (review, Week 9). Leverage (review, Week 10) is not a fit here: it needs an object.

Use it¶

Pick one Slack-style sentence you wrote today and rewrite it in a formal register (for a board paper). Then rewrite a stiff email sentence in a friendly register. Say both aloud. The goal is speed in switching, not loving the formal version.

Day 3 — Speaking: Clarity on calls and video: pacing, signposting¶

⏱ 30 min · Wed Audio compresses on calls: delays, echoes and accents make speech harder to parse, so slow down and structure more.

Prompt (60-90 seconds): In a distributed team meeting, give a status update on one project. Start with the headline, use spoken signposts, check that people can hear you, and end with what you need.

Structure: Headline, Signpost, Body, Check, Ask

Headline (10 s): The headline is: we are on track for 14 March, with one risk.
Signpost: I'll cover three things: progress, the risk, and what I need from you.
Body: short sentences; number each point aloud (First..., Second..., Third...).
Check: Can everyone hear me OK? / Any questions so far? / Let me pause there.
Ask: What I need from this group is a decision on the vendor by Friday.

Pacing on calls: aim for about 130-150 words per minute (a normal conversational pace is faster), pause 1-2 seconds after key numbers and after each signpost, and repeat critical figures (fourteen, one-four, March).

Pronunciation micro-drill: can vs can't and linking

can is weak in statements: /kən/ (We can meet the date). can't is strong: US /kænt/ with clear /æ/ and a stop, UK /kɑːnt/. On a bad line, weak can and strong can't are easily confused. Fix: stress the meaningful word and lengthen can't: We CAN'T meet the date. Better, when it matters: We are not able to... or We will not meet the date.
Linking (consonant to vowel): say check it out as check_it_out, turn it off as turn_it_off, an apple as a-napple, as soon as possible as a-ssoon-a-spossible. Practice with: pick up all issues, look at it again, roll it out on Monday, a lot of it.
Chunking: group words in thought groups of 3-6 words: The headline is / we are on track / for the fourteenth of March. Pause between groups.

Self-check

I stated the headline first.
I used at least three signposts (First, Second, Finally, Let me turn to).
I paused after key numbers and after signposts.
My can't was clearly different from can.
I checked audience understanding at least once.

Day 4 — Idioms & phrasal verbs: Escalation phrasal verbs: flag up, push back, loop in¶

⏱ 30 min · Thu

Expression	Meaning	Example
flag up	Bring attention to a problem or issue; `flag up` is more UK, and `flag` alone (`flag a risk`) is common in US and UK. Neutral.	Please flag up any blockers in the stand-up so we can help.
push back (noun: pushback)	Resist or object to a request or plan; can be constructive. Neutral in business.	The security team pushed back on the timeline, and they were right.
loop in	Include someone in a conversation or email chain; informal to neutral; opposite `leave out of the loop`.	Can you loop in legal before we send the contract?
bubble up	Rise to the attention of senior people, or move upward through an organization; informal.	Concerns about the migration were starting to bubble up to the leadership team.
weigh in	Contribute an opinion to a discussion, often a decision; informal to neutral.	The CTO weighed in on the architecture choice after the review.

Grammar: loop in is separable (loop legal in / loop in legal), push back is intransitive with on (push back on the estimate), flag up is separable (flag it up), weigh in is intransitive with on (weigh in on the decision), bubble up is intransitive (it bubbled up). Pronouns go in the middle: loop them in.

Exercise¶

Choose or complete (8).

Rewrite: Please tell the team about any blockers. (using flag up)
Can you ______ the compliance team on this email? (loop in / push back)
Correct: We need to loop in her before the meeting.
A colleague says I will push back on that estimate. What are they going to do?
Rewrite plainly: Concerns are bubbling up to the executive team.
Complete: Product wanted to ______ on the architecture decision, though they are not part of the review. (weigh in / loop in)
Which is more assertive: push back or flag?
Fix: I will push it back on them.

Answers and explanations

Please **flag up** any blockers. (US: flag any blockers.)
loop in.
We need to **loop her in** before the meeting. A pronoun object must go between verb and particle (a noun can go either side: loop in legal).
They will object to or challenge the estimate; often constructive, so they may propose a better number.
Senior leaders are beginning to hear about the concerns.
weigh in: give an opinion.
push back: it resists or challenges; flag simply draws attention.
I will **push back on** them (or push back on that). Push back takes on plus the thing pushed against; it does not take it.

When NOT to use them

Push back can sound confrontational in cultures where direct disagreement is uncommon; raise a concern is safer in first-time contact. Loop in and bubble up are corporate-internal jargon and can confuse non-native readers; in formal escalation to executives or customers, write include and escalate. Do not use flag up in a US audience unless you are comfortable with a UK feel; flag is fine.

Day 5 — Writing: Escalation emails¶

⏱ 30 min · Fri

Bad draft:

Hi Tom, this is the third time I am asking about the API access for our vendor integration and honestly it is unacceptable. Your team keeps ignoring my tickets and this is putting our whole project at risk. I have cc'd your boss because someone needs to do something. Please fix this immediately.

Task: Rewrite as a firm but professional escalation email to a peer team's manager, 110-150 words. Constraints: neutral subject line; state facts and dates; state business impact with a number; make one clear request with a deadline; no blame words; register formal-neutral (use one of expedite, ascertain, reiterate).

Model answer and what changed

Subject: Request to expedite API access for vendor integration (needed by 12 Oct)

Hi Tom,

I am writing to follow up on ticket INT-4412, submitted on 22 September, and two subsequent reminders on 29 September and 3 October. We have not yet received a response. I understand your team is handling a heavy queue.

The access is needed to keep the vendor integration on schedule. Without it by 12 October, the go-live date of 1 November is at risk, which affects roughly 40 customers. Could your team expedite the request, or let me know by Wednesday if there is a blocker we can help ascertain?

I have copied Sara, as the request is now close to a critical-path date. Please tell me if you would like to talk it through.

Thanks, Rahul

Subject line contains the ask and the date so the manager can triage without opening.
Facts and dates replace emotion: ticket number, three dates, no unacceptable.
Impact is quantified (roughly 40 customers, go-live date).
Acknowledges the other side (heavy queue), which keeps the door open.
One request and one deadline, with an alternative if there is a blocker.
The cc is explained, not used as a threat.
Register: formal-neutral, with expedite and ascertain used naturally; no idioms.

Day 6 — Speaking record: Clarity on calls and video: pacing, signposting¶

⏱ 30 min · Sat

Record a 2-minute talk: Record yourself on a video call (or audio only) giving a 2-minute project update to a distributed team, as if some listeners have a poor connection. Use the structure Headline, Signpost, Body, Check, Ask. Use at least two escalation phrasal verbs from Day 4 (flag up, push back, loop in, weigh in) and one formal word from Day 2. Speak at 130-150 words per minute.

Rubric (score 1-4)

Criterion	1	2	3	4
Clarity	Hard to follow on a poor line	Key points buried	Clear; a few phrases lost	Every key point audible and clear
Structure	No signposting	Signposts sparse	Headline and signposts present	Headline, signposts, check and ask all present
Fluency	Rushed or halting	Uneven pace	Mostly steady pace	Steady 130-150 wpm with deliberate pauses
Grammar accuracy	Errors block meaning	Frequent article errors	Few errors; articles mostly right	Articles and passive/active correct
Vocabulary range	Repetitive	Basic terms	Register-appropriate words	Precise, natural register switching
Pronunciation	`can/can't` unclear	Some linking issues	Clear; occasional slips	Clear `can't`, linking and chunking

Shadowing task: Choose a recorded conference talk or online meeting demo (for example, a talk from a developer conference) where the speaker signposts clearly. Shadow the first 90 seconds three times, matching pace and pauses. Write down their signposting phrases.

Log your score: total out of 24 in docs/log/, plus your measured words per minute (transcribe 100 words and time them).

Day 7 — Soft skills + weekly review: Saying no without burning bridges¶

⏱ 30 min · Sun

Scenario. Your head of sales, Jorge, has a strategic customer who wants a custom reporting feature in two weeks. Building it would derail the platform migration you promised finance for this quarter. Jorge says: "This customer is worth 8 million a year. I need a yes." You cannot say yes, and you value the relationship.

Task: Script your 150-word reply, keeping the relationship intact.

Model response and techniques

Jorge, I understand what is at stake, and I want to help win this customer. The honest answer is that I cannot deliver a custom report in two weeks without putting the migration at risk, and the migration is what protects the revenue of every existing customer, including this one. So the answer to the two-week version is no. Here is what I can do. I can give you a manual, weekly export in five days that covers about 80 percent of what they want, and I can scope the full feature for the start of next quarter with a committed date. Could you check with the customer whether the export would meet their immediate need? If they need the full feature sooner, let us raise it together with finance, who set the migration priority, so the trade-off is a shared decision.

Techniques used

Acknowledge the stake and the goal before saying no.
Clear, early no to the specific request (the answer to the two-week version is no), not to the person, and without hedging.
Reason tied to a shared interest (protecting revenue).
Alternatives with dates and scope (export in five days, full feature next quarter).
Ask for information (what does the customer need) to invite collaboration.
Escalate the trade-off, not the conflict (raise it together with finance).

Weekly recap (20 items)¶

Article: ___ reliability matters more than speed. (generic)
Article: ___ reliability of our platform is our priority.
Correct: We need a documentation.
Correct: in the production.
Fixed phrase: ___ scale and in ___ cloud.
Correct: by the email.
When does a qualified abstract noun take a? Give an example.
Formal synonym of find out.
Formal equivalent of despite.
Formal word for speed up.
What does reiterate mean?
Difference between forthright and blunt.
Meaning of push back and its preposition.
loop in meaning; correct: loop in her.
Which word is more UK: flag up or flag?
weigh in meaning.
can vs can't: what is the trick on a bad line?
Three linking examples.
Target speaking pace on calls?
Three parts of the no model response.

Answers and explanations

Zero: Reliability matters more than speed.
The: specified by of our platform.
We need documentation. (uncountable)
in production.
at scale, in the cloud.
by email.
When it names one instance or kind: a deep understanding of, a lack of trust.
ascertain (or determine).
notwithstanding.
expedite.
To say again for emphasis.
Forthright is direct and honest, and reads as a formal, positive trait; blunt is harsher and less considerate of the listener.
To resist or object; push back on.
Include someone in a conversation; loop her in.
flag up.
To contribute an opinion to a discussion.
Stress and lengthen can't, or rephrase (we are not able to).
check_it_out, turn_it_off, an_apple.
About 130-150 words per minute.
Acknowledge the goal, give a clear no to the request, offer alternatives (plus reason and a shared decision).

Self-score

I use zero article with generic abstract nouns and the when specified.
I know the fixed phrases: in production, at scale, in the cloud, by email.
I can switch register for the same message.
I signposted on a call and my can't was clear.
I can write a firm escalation email without blame words.
I can say no and still offer a path forward.

Error log: write down your top 3 recurring mistakes this week (for example, the with generic nouns, a documentation, in the production) and one correct model sentence for each.