Communicate a delay without losing credibility.
Five real scripts client-facing project managers use to report delays. No blame. Clear next step. Calm authority.
No spam. Unsubscribe anytime.
What's in the pack
Five scripts. Three tone variants each (friendly, neutral, firm). Each one built on a single framework: Facts, Options, Recommendation, Next Step.
- When a missed dependency forces a schedule change and you need a recovery plan
- When a vendor misses a milestone and you have to update the client without blame
- When a design change creates a delay that wasn't your call
- When a delay requires a budget conversation alongside the schedule
- When the delay creates a scope trade-off and you need a decision from the client
Who this is for
Client-facing project managers who navigate senior stakeholders, high-stakes deadlines, and political nuance every week.
You speak English well. The challenge isn't vocabulary, it's tone. Push too soft and the message loses its meaning. Push too hard and you damage the relationship.
Built for PMs in engineering, infrastructure, consulting, construction, and tech delivery. Especially those who need to deliver hard updates with calm authority.
From me to you
I'm Amber. I'm an executive at a global engineering, science, and advisory firm, with over 15 years in project execution.
Across that career, I've watched non-native English speakers struggle to break into client-facing roles. The work is excellent. The technical thinking is sharp. But conversational English creates a confidence gap that costs them. They get misunderstood. They get passed over. Their careers move slower than they should.
This pack is a small way of giving back. I believe communication transcends borders, and the best projects happen when every voice on the team can be understood clearly.