PMI-SP · Domain 5 of 5

PMI-SP Domain 5: Stakeholder Communications Management

A schedule only controls a project if the right people see it, trust it and act on it. This domain tests how schedulers build that trust and report bad news early.

Exam weight
14%
Official tasks
4
Estimated questions estimate
~24
Suggested study time estimate
15–25 hrs

About 12 min read Reviewed October 2026

Overview

Stakeholder Communications Management covers four tasks: developing and fostering relationships with project stakeholders in line with the communication management plan, generating and maintaining visibility of the project schedule, giving senior management and other stakeholders verbal and written schedule status including the impact of corrective actions, and communicating schedule issues that could affect delivery of scope or adherence to the schedule.

Candidates must understand how to tailor schedule information to an audience: a milestone summary and confidence level for executives, a look-ahead with near-critical work for activity owners, and logic-level detail for auditors. The domain runs through every phase, presenting the baseline built in Domain 2, the variances and forecasts from Domain 3, and the final reports issued in Domain 4.

How it's tested

Questions are situational and judgment-based. You choose the BEST way to report a forecast slip, the FIRST person to inform, or the most effective format for an audience. Calculations are rare. The right answer is usually timely, honest, routed through the communication management plan and tailored to the audience's decision needs.

  • Audience tailoring

    You pick the format and level of detail that suits an executive, a team lead or a customer, such as a milestone trend chart instead of a detailed network.

  • Early warning

    A newly found issue threatens a milestone between reporting cycles; you decide whether and how to communicate it before the next scheduled report.

  • Status with consequences

    You select the report that shows status together with impact, options and the effect of corrective actions, rather than raw variances alone.

Reasoning it through

An executive asks why the monthly schedule report is ignored. The report is a 40-page Gantt export. Reasoning: the content does not match the audience's decisions. Replace it with a one-page summary of key milestones, forecast versus baseline, confidence level, top schedule risks and decisions needed, agreed with the executive and recorded in the communication management plan.

Tasks 4

Official tasks from the PMI outline, in outline order.

5.1 Develop and foster relationships with project stakeholdersBuild working relationships consistent with the communication management plan.
What it means
You identify who needs schedule information, understand their interests and influence, and build relationships that make honest status and early warnings welcome rather than resisted.
What to understand
Relationships follow the communication management plan, which defines audiences, content, frequency, format and channels; trust is built by consistent, accurate reporting.
How it shows up
A functional manager disputes every schedule update; the best response is to meet, understand their concerns and agree how their input and reports will work.
Common confusion
Treating relationship building as informal networking separate from the communication management plan.
5.2 Generate and maintain visibility of project scheduleKeep the schedule visible to sustain stakeholder support.
What it means
Working with the project manager, you make the schedule accessible and understandable through dashboards, milestone charts, look-ahead schedules and reviews.
What to understand
Visibility means the right view for each audience, kept current; a schedule stored where only the scheduler can read it provides no control.
How it shows up
Team leads are surprised by upcoming critical activities; the answer is a regular look-ahead view that highlights near-term critical and near-critical work.
Common confusion
Equating visibility with sending everyone the full schedule file.
5.3 Provide senior management and other stakeholders with verbal and written schedule statusReport status and the impact of corrective actions.
What it means
You deliver status that shows progress against baseline, forecast dates, variances beyond threshold, and the expected effect of corrective actions, in written reports and verbal briefings.
What to understand
Executives need milestone forecasts, trends, confidence and decisions required; status should show what corrective actions are expected to recover, not only what slipped.
How it shows up
You are asked which content to include in an executive briefing; choose milestone trends, impact and options over activity-level detail.
Common confusion
Reporting variances without causes, impacts or the planned corrective action.
5.4 Communicate schedule issues that could impact delivery of project scope or adherence to scheduleRaise issues promptly to the right people.
What it means
When an issue threatens scope delivery or schedule dates, you analyze its impact and communicate it promptly through the agreed route, usually the project manager, with options.
What to understand
Timing matters: a critical issue should not wait for the next scheduled report, and the message should include impact on milestones and possible responses.
How it shows up
A supplier warns of a delay on a near-critical path two weeks before the monthly report; the best answer analyzes the impact and informs the PM now.
Common confusion
Either waiting for the routine report or bypassing the project manager to alert the customer directly.

High-yield concepts

The terms, rules and formulas this domain turns into questions most often.

  • Communication management plan

    The plan that defines who receives which project information, in what format, how often, through which channel, and who sends it.

    Remember
    Schedule reporting content, cadence and escalation routes should be consistent with it.
    Tested as
    The anchor for most Domain 5 answers about how to report.
    Trap
    Inventing a new reporting channel instead of using or updating the plan.

  • Stakeholder analysis

    Identifying stakeholders' interest, influence and information needs, for example with a power/interest grid.

    Remember
    High-influence stakeholders need tailored, regular schedule information and early warning of threats to their milestones.
    Tested as
    Drives tailoring choices in reporting questions.
    Trap
    Giving every stakeholder the same report.

  • Milestone trend chart

    A chart showing how forecast dates for key milestones have moved across reporting periods.

    Remember
    It shows direction and stability of forecasts at a glance, which suits executives.
    Tested as
    A preferred format for senior management status.
    Trap
    Choosing a detailed Gantt chart for an executive audience.

  • Look-ahead schedule

    A short-horizon view, often two to six weeks, of upcoming activities filtered for the people performing them.

    Remember
    It keeps activity owners focused on near-term critical and near-critical work.
    Tested as
    A common answer for schedule visibility at the team level.
    Trap
    Sending the whole schedule to field teams.

  • Schedule confidence level

    The probability of meeting a date from schedule risk analysis, for example P80.

    Remember
    Reporting a date with its confidence level helps executives make risk-aware decisions.
    Tested as
    Executive reporting and baseline consensus questions.
    Trap
    Presenting a single deterministic date as certain.

  • Escalation path

    The agreed route and thresholds for raising issues, usually from scheduler to project manager to sponsor or steering group.

    Remember
    Use the route; the scheduler normally informs the project manager, who engages sponsors and customers.
    Tested as
    Who-to-tell-first questions.
    Trap
    Bypassing the project manager to alert the customer.

  • Schedule narrative

    A short written explanation accompanying status that covers critical path changes, causes of variance and planned recovery.

    Remember
    Numbers without narrative leave stakeholders guessing about causes and actions.
    Tested as
    Content questions for written status reports.
    Trap
    Sending charts with no explanation of what changed and why.

  • Impact of corrective action

    The expected effect of a proposed or approved action on forecast dates, cost and risk.

    Remember
    The ECO asks for status that includes this, so reports should show expected recovery.
    Tested as
    Distinguishes complete status reports from incomplete ones.
    Trap
    Reporting the problem but not the expected outcome of the fix.

  • Push vs. pull communication

    Push sends information to recipients (reports, emails); pull lets them access it when needed (dashboards, portals); interactive allows discussion (meetings).

    Remember
    Urgent issues need interactive or push communication, not a passive dashboard update.
    Tested as
    Channel selection questions.
    Trap
    Relying on a dashboard to communicate an urgent critical issue.

Side by side

Concepts candidates mix up, compared on the point that decides the answer.

Executive report vs. team look-ahead vs. detailed schedule

ConceptMeaningKey differenceCommon trap
Executive status report Milestone forecasts, trends, confidence, risks and decisions needed Supports decisions, low detail Overloading it with activity-level data
Team look-ahead Near-term activities, logic and responsibilities for owners Supports execution over weeks Omitting near-critical work
Detailed schedule model Full network with logic, resources and float Supports analysis and audit Distributing it as the main status communication

Push vs. pull vs. interactive communication

ConceptMeaningKey differenceCommon trap
Push Sent to recipients, such as reports or emails Confirms delivery, not understanding Assuming a sent report was read and understood
Pull Recipients access it, such as dashboards Good for large audiences and reference data Using it for urgent issues
Interactive Two-way exchange, such as meetings or calls Best for complex or urgent issues needing decisions Skipping it when a critical issue needs immediate discussion

Exam traps

Each trap is an answer that looks right. Learn the clue that should change your mind.

  1. Wait for the report

    What candidates pick
    Include the new issue in next month's status report.
    Why it looks right
    It follows the reporting cadence in the communication plan.
    Why it's wrong
    Issues that threaten milestones or scope need prompt communication; the cadence covers routine status, not urgent issues.

    Clue to watch for The issue affects the critical or near-critical path and the next report is weeks away.

  2. Go straight to the customer

    What candidates pick
    Email the customer about the forecast slip immediately.
    Why it looks right
    It looks transparent and fast.
    Why it's wrong
    The scheduler normally reports through the project manager, who owns customer communication and can present options.

    Clue to watch for The question asks what the scheduler should do FIRST.

  3. More detail is better

    What candidates pick
    Give executives the full schedule so nothing is hidden.
    Why it looks right
    Complete information seems most transparent.
    Why it's wrong
    Executives need decision-ready summaries; excessive detail hides the message and the report gets ignored.

    Clue to watch for The audience is senior management or a steering committee.

  4. Bad news only

    What candidates pick
    Report the variance and its cause.
    Why it looks right
    Variance and cause seem to be the core of status.
    Why it's wrong
    The ECO expects status to include the impact of corrective actions, so stakeholders know the expected recovery and decisions needed.

    Clue to watch for An option mentions recovery effect or decision required alongside the variance.

  5. Dashboard as escalation

    What candidates pick
    Update the online dashboard to show the new red milestone.
    Why it looks right
    The dashboard is the agreed visibility tool.
    Why it's wrong
    Pull channels do not ensure urgent issues are seen; critical issues need direct, interactive communication.

    Clue to watch for The issue requires a decision soon.

Answer framework

Use this sequence when a question asks how to communicate schedule information or an emerging schedule issue.

  1. Analyze the issue in the schedule model first to quantify its effect on milestones, the critical and near-critical paths, and scope delivery.
  2. Identify the audience and their decision needs using stakeholder analysis and the communication management plan.
  3. Choose timing and channel: urgent threats get prompt interactive or push communication, while routine status follows the cadence agreed in the plan.
  4. Tailor the content to include status, impact, options and the expected effect of corrective actions, with confidence levels where relevant.
  5. Route the message through the agreed escalation path, usually the project manager, then record the outcome, decisions taken and any follow-up actions.

Practice question

A supplier tells the scheduler that a component on a near-critical path will arrive three weeks late. The path has five days of total float, and the monthly status report is due in three weeks. What should the scheduler do?

Want more like this? The PMI-SP practice test has questions for every domain.

Checklist

0 of 10

Tick each one you can do without notes. Your ticks stay in this browser.

Study strategy

Start with the communication management plan: list what it defines for schedule information, then map typical audiences to the content, format and cadence each needs. This gives you a default answer frame for most questions.

Next, practice tailoring. Take one status situation and write three versions: a one-page executive summary with milestone trends and decisions needed, a two-week look-ahead for team leads, and a detailed variance explanation for the project manager. Seeing the differences side by side makes exam options easier to separate.

The commonly underestimated area is timing. Drill scenarios where an issue appears between reporting cycles and decide whether it needs immediate communication, through whom, and through which channel. Pay attention to who the scheduler reports to first.

Afterwards, practice mixed situational sets that combine Domain 3 analysis with Domain 5 communication, because many exam items require both: compute or locate the impact, then choose the right way to tell the right person.

FAQ

How much of the PMI-SP exam is Stakeholder Communications Management?

PMI weights it at 14%. Applied to 170 items, that is about 24 questions as a planning estimate.

Are there calculations in this domain?

Rarely. You may need to read a variance or float value to judge urgency, but most items test audience, timing, channel and content choices.

Should the scheduler report directly to the customer?

Normally the scheduler reports schedule issues to the project manager, who owns customer communication, unless the communication management plan assigns that role differently.

What should an executive schedule report contain?

Key milestone forecasts against baseline, trends, confidence levels, top schedule risks, the effect of corrective actions and decisions needed, kept short.

When should an issue be raised outside the regular reporting cycle?

When it threatens milestones, the critical path or scope delivery and waiting would reduce the options available to recover.

How does this domain connect to the others?

It carries Domain 2's baseline to stakeholders for consensus, Domain 3's variances and forecasts to decision-makers, and Domain 4's final reports to the organization.

How long should I study this domain?

A planning estimate is 15 to 25 hours, mostly on situational practice rather than memorization.

Other Project Management certifications

Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.

Test your Domain 5 knowledge

You have covered stakeholder relationships, schedule visibility, executive status and timely issue escalation. Check whether you can pick the right audience, timing and channel in a scenario.

Take the PMI-SP practice test Check your PMI-SP readiness

Keep going