HKSM

A status report is a periodic summary of project progress, variances, risks, and upcoming work for stakeholders. It consolidates verified information to show performance against the plan and any needed decisions or support. It helps manage expectations and guide stakeholder engagement.

Key Points

• Time-bound snapshot showing facts, trends, and exceptions as of a specific status date.
• Compares actual performance to baselines and forecasts, highlighting impacts and actions.
• Tailored by audience and delivery method, such as dashboard, PDF, email, or briefing slides.
• Sources include PMIS, schedules, cost reports, risk and issue logs, and change records.
• Action-oriented, clearly stating decisions needed, escalations, and stakeholder requests.
• Serves as a key input to stakeholder communications and engagement activities.

Purpose

Provide transparent, consistent information to align stakeholders, build trust, and enable timely decisions. In Manage Stakeholder Engagement, it frames conversations, targets messages to interests and influence, and supports two-way feedback.

How to Create

• Confirm audience and information needs using the communications and stakeholder engagement plans.
• Collect current data on scope, schedule, cost, quality, milestones, deliverables, risks, issues, and changes.
• Analyze results: variances and trends, SPI and CPI, forecasts such as EAC, and milestone projections.
• Summarize exceptions and impacts on objectives, benefits, constraints, and dependencies.
• Highlight achievements, blockers, and explicit asks for decisions or support.
• Select a concise format with clear visuals, such as RAG status, charts, and bullet summaries.
• Validate with team leads, fix the status date, and obtain required reviews or approvals.
• Version, store in the PMIS, and prepare distribution aligned to the communication cadence.

How to Use

• Circulate as a pre-read to shape agendas for stakeholder meetings and steering sessions.
• Drive discussion on variances, risks, and issues, and capture decisions and follow-up actions.
• Tailor key messages per stakeholder needs to manage expectations and reduce resistance.
• Update related logs, trigger escalations, and initiate change requests when thresholds are breached.
• Record feedback to refine future reports and adjust the stakeholder engagement approach.
• Maintain traceability by referencing baselines and prior report trends.

Ownership & Update Cadence

• Owner: Project manager, with inputs from team leads, product owner, PMO, and control accounts.
• Reviewers: Sponsor and governance bodies for high-visibility or escalated items.
• Cadence: Weekly or per sprint for delivery teams, monthly for steering committees, and ad hoc for escalations.
• Channels: PMIS dashboards for real time, plus distributed summaries for formal checkpoints.
• Governance: Version control, status date clearly stated, distribution list managed, and repository archived.

Example

• Overall RAG: Amber due to supplier delay impacting Milestone M3 by two weeks.
• Schedule: SPI 0.92. M2 complete, M3 forecast 6/14 vs. baseline 5/31. Recovery plan pending approval.
• Cost: CPI 0.98. EAC within 2 percent of budget. Overtime capped.
• Scope: No approved changes this period. One new change request submitted for API scope clarification.
• Quality: Defect density trending down. UAT entry criteria on track.
• Risks: R-12 supplier capacity high exposure, mitigation to onboard backup vendor in progress.
• Issues: I-07 environment outage resolved; root cause under review.
• Decisions Needed: Approve backup vendor spend by Friday to protect M3, confirm revised comms to end users.
• Next Steps: Execute supplier mitigation, complete integration test cycle 2, update stakeholder briefing pack.

PMP Example Question

Several executives were surprised by a two-week slip raised in a meeting. To avoid surprises and drive timely decisions in future stakeholder engagements, what should the project manager do with the status report?

1. Tailor and distribute a concise, baseline-referenced status report before meetings, highlighting variances and decisions needed.
2. Extend the length of stakeholder meetings to discuss more details.
3. Update the risk register after each meeting without changing the reporting approach.
4. Ask team leads to send ad hoc emails when problems occur.

Correct Answer: A — Tailor and distribute a concise, baseline-referenced status report before meetings, highlighting variances and decisions needed.

Explanation: Proactive, tailored status reporting sets expectations and enables informed decisions during engagement. The other choices are reactive or insufficiently structured.