Business English Podcast · Meetings & Status Updates · Episode 27

Surfacing a Dependency Nobody Included in the Plan

The project plan is approved — but the key milestone depends on a vendor nobody accounted for. How to raise an overlooked dependency before it becomes a crisis.

C1 · Dialogue · 5 Min. · free

▶ Listen to the episode To the comprehension test +49 511 4739339

All episodesPodcast catalog →More gamesSimmonds English Games →

Editorially reviewed by James Simmonds – English teacher since 2004Published 13 September 2026

SceneIn the planning review Jonas spots a gap: the October migration assumes an interface specification from the vendor — and it appears in no plan. He has to surface the dependency without becoming the bearer of bad news.

0:00 / 5 Min.

Tip: listen to the episode twice before you start the test. · Worksheet (PDF)

✓ To the comprehension test

Jonas — Technical project lead, logistics ITRichard — Programme director

You may also like

Next episode: B1 · Explaining Why a Small Task Is Late · 3 Min.B1 · Asking a Colleague to Repeat an Action Point · 3 Min.B1 · Telling the Team What You Will Finish This Week · 3 Min.All podcast episodes →

Transcript

The full transcript opens after the comprehension test — so you train real listening instead of reading along.

German support

RichardRight, the migration plan looks solid to me. Development closes in September, migration runs in October, go-live on November the fourth. Unless anyone sees a problem, I'd like to sign off on this today.

JonasBefore you sign off, Richard — there's a dependency we haven't accounted for, and I'd rather raise it now than in October. The migration assumes we can map our data to the new customs interface. That mapping needs the interface specification from the vendor.„A dependency we haven't accounted for" – eine Abhängigkeit, die wir nicht eingeplant haben.

RichardAnd that specification is where, exactly? I don't remember seeing it in the plan at all.

JonasThat's precisely the point — it isn't in the plan. It sits with the vendor's product team in Rotterdam. According to their roadmap, we become the specification in mid-September, but nobody has actually —

RichardHold on — you become the specification? Jonas, in English you receive a document, or you get it. 'Become' means 'werden' — you'd be turning into a PDF, which I would pay to see. The German 'bekommen' catches everyone.„Bekommen" heißt „to get/receive" – „to become" heißt „werden".

JonasFair enough — we receive the specification in mid-September, according to their roadmap. But that date is a roadmap entry, not a commitment. Nobody on our side has confirmed it, and it isn't linked to our milestones.

RichardSo walk me through the impact. If Rotterdam delivers in mid-September, are we fine? And what happens if they slip by, say, four weeks?

JonasIf it lands in mid-September, we're fine — mapping takes three weeks, which still clears the October window. If they slip four weeks, the mapping pushes into the migration itself, and go-live moves into December. This specification is effectively on our critical path, and it's owned by a company that isn't in this room. The current plan simply doesn't account for their lead time at all.„On our critical path" – auf dem kritischen Pfad: Jede Verzögerung verschiebt das Ende.

RichardThat's the part I don't like — a single point of failure outside our control. What do you propose? I assume you didn't raise this without a plan.

JonasThree things. First, we make the dependency visible: it goes into the plan as a milestone with the vendor named as owner. Second, I'd ask you to escalate it commercially — a delivery date in the contract, not just on a roadmap. And third, we build a workaround: we can start the mapping against their draft specification and absorb the changes later. That cuts the lead time roughly in half.„Workaround" – Behelfslösung, um trotz des Hindernisses weiterarbeiten zu können.

RichardGood. I'll take the commercial escalation — I'm seeing their account director on Thursday anyway. You own the workaround and the milestone entry. And Jonas: this is exactly what a planning review is for. A dependency that surfaces in a meeting costs us a discussion. One that surfaces in October costs us the go-live.

JonasAgreed. I'll update the plan today and circulate the revised version by tomorrow morning — you'll receive it, not become it.

Key phrases

dependency

something your work cannot proceed without

The plan hides a dependency on an external vendor.

to account for

to include something in your plan or calculation

The schedule doesn't account for the vendor's lead time.

to sign off

to formally approve something

The director signed off on the migration plan.

critical path

the chain of tasks that determines the project end date

The interface specification is on the critical path.

single point of failure

one element whose failure stops everything

One vendor holding the specification is a single point of failure.

to escalate

to raise an issue to a higher level of authority

We escalated the delivery date to the account director.

workaround

a temporary solution that avoids a blocking problem

The workaround lets us start mapping against the draft specification.

lead time

the time between starting a process and its completion

Starting early cuts the lead time roughly in half.

Language notes

In this episode a project lead halts sign-off because a milestone depends on a vendor specification nobody put in the plan. You learn the C1 pattern for surfacing overlooked dependencies — name the gap, quantify the impact, offer a package of solutions — and why "we become the specification" is a classic German error.

Speak before sign-off — and arrive with a plan

Jonas picks the most uncomfortable but best moment: right before Richard signs off ("Before you sign off …"). Crucially, he brings not just the problem but a package of three: visibility (a milestone with a named owner), commercial escalation (a contract date instead of a roadmap entry) and a workaround (the draft specification). Richard's reaction confirms the rule: "I assume you didn't raise this without a plan." Reporting a dependency without a proposal delivers a problem; bringing both is leadership.

The "bekommen" trap: become vs. get/receive

"Bekommen" and "become" sound related but mean different things: "to become" is "werden" ("She became head of department"), never "to obtain". Documents, replies and deliveries are things you "get" or "receive": "We receive the specification in September." The error is stubborn precisely because the sentence stays grammatically correct — only the meaning tips into the absurd: "We become the specification" = "We turn into the specification."

Making dependencies visible: the language of the critical path

The episode delivers the vocabulary international project teams use for risk: "on the critical path" (any delay moves the end date), "single point of failure" (one weak point everything hangs on), "lead time" and "to account for". Important for German teams: in English project culture "to escalate" is neutral to positive — a normal governance step, not a breach of trust with the vendor.

Keep practising: Learn business English online — with real teachers from Simmonds, since 2004.

Frequently asked questions

What language level is this episode for?

Level C1 (CEFR). The dialogue uses advanced project management English (critical path, single point of failure, escalation language); the vocabulary list explains all eight key phrases bilingually.

How do I raise an overlooked dependency in English?

With the three-step pattern from the episode: name the gap ("There's a dependency we haven't accounted for"), quantify the impact ("If they slip four weeks, go-live moves to December") and offer a package of solutions (milestone, escalation, workaround).

Why is "we become the specification" wrong?

"To become" means "werden" (to turn into), not "bekommen" (to get). The sentence literally says "we turn into the specification". Correct: "we receive the specification" or "we get the specification" — one of the most stubborn German-English traps.

Where can I practise this project language live?

In the online business English courses from Simmonds Language Services (englisch-lehrer.com/online): live lessons with real teachers on Zoom, for companies and individuals across Germany — with a free consultation first, since 2004.

Is there a transcript to read along?

Yes, the full transcript with German support notes is on this page — listen first, then take the test, then read along.

Want to practise these phrases in a real conversation?

The podcast trains your ear — in our online lessons you practise the conversation yourself, with real teachers. For companies across Germany since 2004.

Online lessons with real teachers Book a free consultation

Call