English for Project Managers: Status Reports, Escalations, and Sprint Language

Project managers in IT use a specific set of English phrases, reports, and communication patterns that differ from both general management communication and pure developer communication. You are constantly translating: between technical teams and business stakeholders, between urgency and diplomacy, between what you know and what you need to say when you don’t know yet.

This guide covers the vocabulary, templates, and phrases for the core communication tasks of an IT project manager.

Part 1: Status Report Language

The weekly status report is the most universal project manager communication task. It needs to be concise, honest about risks, and actionable for whoever reads it.

Status report structure

## Project Status: [Project Name] — Week of [Date]

**Overall Status:** 🟢 On Track / 🟡 At Risk / 🔴 Off Track

**Summary:** 
One-paragraph summary of the week's progress and current state.

**Accomplishments This Week:**
- [Completed milestone or task]
- [Completed milestone or task]

**Planned for Next Week:**
- [Upcoming milestone or task]
- [Upcoming milestone or task]

**Risks and Issues:**
| Risk/Issue | Impact | Status | Owner | Action |
|------------|--------|--------|-------|--------|
| [Description] | [High/Med/Low] | [Open/Mitigated] | [Name] | [Next step] |

**Decisions Needed:**
- [Decision that needs to be made, by whom, by when]

**Budget Status:** On track / [X]% over/under
**Timeline Status:** On track / [X] days ahead/behind

Status language by color

Green (on track):

“The project is progressing as planned.”
“All milestones are on track for the agreed delivery dates.”
“Sprint 12 completed on schedule with all committed stories delivered.”

Yellow (at risk):

“The project is at risk due to [specific reason]. Without intervention by [date], this will impact [timeline/budget/scope].”
“We are currently [X] days behind schedule on [component]. We are developing a recovery plan and expect to share it by [date].”
“A dependency on [external team/vendor] is creating uncertainty. We are escalating to [person] to resolve by [date].”

Red (off track):

“The project is currently off track. The primary cause is [reason]. We are working on [recovery action] and will provide a revised timeline by [date].”
“We need to have a conversation about [scope/timeline/resources]. I would like to schedule 30 minutes with [stakeholders] this week.”

The golden rule of status reporting

Never hide a yellow. If something is at risk, say so, and say what the recovery plan is. A problem raised early can be solved. A problem raised at delivery cannot.

Part 2: Sprint Ceremony Language

Sprint planning

Opening the planning session:

“Welcome to Sprint [N] planning. We have [N] story points of capacity this sprint based on [N] team members and [N] days. The sprint goal [proposed by product owner] is: [goal]. Does this feel achievable?”

Estimating stories:

“This story seems straightforward — are we all aligned on [3 points]?” “I’m seeing some disagreement in our estimates. Can the people who said [5] and [13] walk us through their thinking?” “Let’s break this down — it might be too large for one sprint.”

Identifying dependencies:

“This story has a dependency on [team/system/approval] — is that dependency resolved before we start?” “Are there any stories in this sprint that can’t begin until something else is done?”

Daily standup facilitation

The facilitator’s job is time-boxing, not checking in on each person:

“Let’s keep to the format: what did you finish, what’s next, any blockers.”
“Take that offline — let’s continue and sync after standup.”
“Who can help [name] with that blocker today?”
“Anything else for the standup, or should we wrap up?”

Sprint review

“This is the sprint review for Sprint [N]. The sprint goal was [goal]. Let me hand over to the team to demonstrate what was completed.”

After demos:

“Thank you for the demo. Does the product owner accept this story as meeting the acceptance criteria?” “What feedback does the stakeholder group have? We’ll capture it as backlog items if it’s out of scope for this sprint.”

Sprint retrospective

Opening:

“This is a safe space. We’re looking for honest feedback about our process — not attributing blame to individuals.”

Structured format (Start / Stop / Continue):

“What should we start doing?” “What should we stop doing?” “What is working well that we should continue?”

Closing:

“Let’s agree on [1-2] action items from this retro, with an owner and a due date, and review them at the start of next sprint.”

Part 3: Escalation Language

Escalation is raising an issue to a higher level of authority because it cannot be resolved at the current level. The language of escalation must be:

Factual (not emotional)
Clear about what decision or action is needed
Specific about the urgency and impact

Escalation to your manager

Email format:

Subject: Escalation: [Issue Title] — Decision Needed by [Date]

Hi [Name],

I need to escalate an issue with [Project Name] that requires a decision 
from your level.

**The issue:** [One sentence description]

**Why it's being escalated:** [Explain what blocks it from being resolved 
at the team level]

**Impact if not resolved by [date]:** [Specific consequence]

**The decision/action needed:** [Clear, specific ask]

**Options:**
1. [Option A] — [Pros/Cons, cost/time]
2. [Option B] — [Pros/Cons, cost/time]

**My recommendation:** [Your recommendation if applicable]

I'm available for a call [suggest times] if a discussion would be helpful 
before making the call.

[Your name]

Escalation phrases in conversations

“I need to escalate this because it’s outside my authority to approve.”
“We’ve been trying to resolve this at the team level for [time period] without progress. I need your help to unblock it.”
“I want to flag this proactively — it’s not a crisis today, but it will be if we don’t address it by [date].”
“This is a risk that I’m not comfortable holding at this level. I think you should be aware of it.”

Dealing with a difficult escalation conversation

When delivering bad news up the chain, use this structure:

State the problem clearly
State the impact
State what you’ve already tried
State what you need

Example:

“We have a significant problem with the [feature] delivery. The external vendor has confirmed they’ll miss the agreed deadline by 3 weeks, which puts our Q2 launch at risk. I’ve already explored alternatives — there are two we’ve checked: [A] and [B]. I need your help to make a call today on which direction to take.”

Part 4: Stakeholder Communication

Managing expectations

“I want to set expectations about what’s achievable in this sprint.”
“Before we commit to this deadline, I’d like to walk through the risks.”
“I want to be transparent about where we stand: [honest status].”
“I want to make sure we’re aligned on the scope before we proceed.”

Pushing back on scope creep

“That’s a great idea. To include it in this sprint, we’d need to remove something of equivalent size. Which of the current stories is the lower priority?”
“We can add that — but it would push the delivery date by approximately [X] days. Would the business prefer to add it now and shift the date, or defer it to the next sprint?”
“Adding this would increase scope by roughly [X] story points. I’d suggest looking at this as a Sprint N+1 commitment unless the priority warrants moving something else out.”

Delivering bad news to stakeholders

Structure: Situation → Client Impact → Root Cause → What You’re Doing → What You Need

“I need to update you on [project]. We’ve encountered [situation], which means [impact on stakeholder]. The root cause is [explanation]. We’re addressing it by [actions]. To get back on track, we need [decision/support/resources] by [date].”

Part 5: Common IT PM Vocabulary

Term	Meaning
capacity	How much work a team can handle in a given sprint/period
velocity	The average story points a team delivers per sprint (historical)
scope creep	Unplanned additions to project scope without corresponding adjustment to time or resources
critical path	The sequence of tasks where any delay directly delays the project end date
milestone	A significant checkpoint or deliverable in the project timeline
dependency	A task or resource that must be in place before another task can start
blocker	Something preventing progress — needs immediate resolution
impediment	Scrum term for a blocker raised in standup
RAID log	Risks, Assumptions, Issues, Dependencies — a tracking document
stakeholder	Anyone with an interest in or impact from the project
sponsor	The senior person accountable for the project’s success, provides funding/authority
RACI	Responsible, Accountable, Consulted, Informed — a responsibility matrix
WBS	Work Breakdown Structure — a hierarchical decomposition of deliverables
change request	Formal document requesting a change to scope, timeline, or budget

Quick Reference: Useful PM Phrases

Situation	Phrase
Opening a meeting	”Let’s get started. The goal for today’s meeting is [X]. We have [N] minutes.”
Keeping meetings on track	”That’s an important topic — let’s capture it in the parking lot and come back to it if time allows.”
Closing a meeting	”To summarise: we agreed to [X]. [Name] will [action] by [date]. I’ll send a summary with the action items.”
Reporting status	”We are [on track / at risk / off track] because [reason].”
Escalating	”I need to escalate this — it requires a decision at your level.”
Managing scope	”To include that, we’d need to adjust [timeline / scope / resources].”
Delivering bad news	”I need to give you an honest update: [situation, impact, plan].”