Project Communication: What to Report, to Whom, and When
Most project managers know, in the abstract, that communication is critical. Stakeholders who are kept informed make better decisions, provide timely support when it is needed, and are less likely to be surprised by problems that turn into escalations. Most project managers also know, in practice, that project communication is frequently done poorly: too much information sent to people who do not need it, not enough sent to people who do, formats that are designed for the person creating them rather than the person receiving them, and no systematic feedback loop to find out whether the communication is actually landing.
The Stakeholder Communication Matrix
The foundation of good project communication is a stakeholder communication matrix: a structured document that maps each significant stakeholder group to the information they need, the format they prefer, the frequency they require, and the person responsible for delivering it. The matrix is not complex to build, but it requires the project manager to think through communication from the receiver's perspective rather than the sender's.
The key questions for each stakeholder group are: What decisions will they need to make, and what information do they need to make those decisions well? What level of detail serves them — and what level will cause them to disengage? How often do they need updates for their own planning and oversight purposes? Who in the project team has the relationship and credibility to deliver communication to them effectively? And how will you know if what you are sending is actually useful?
Status Reports vs. Forecast Reports
Status reports are backward-looking: they document what has been accomplished, what milestones have been met, what was planned but not completed, and what variances from the plan exist. Status reports are important for accountability and for maintaining a record of project progress. They are less useful for decision-making because they describe a situation that has already occurred.
Forecast reports are forward-looking: they describe where the project is headed given current trajectory, what risks are likely to materialise, what decisions need to be made and by when, and what options exist to course-correct. Forecast reports are the primary tool for driving project governance decisions — but many project teams never produce them, because the habit is to report on what has happened rather than what is likely to happen.
Project sponsors and executives almost always prefer forecast reporting. They have limited time, limited context, and a primary interest in whether the project will deliver what they are expecting. A status report that shows everything is on track tells them less than a forecast report that shows two risks with high likelihood of impacting the delivery date and three options for managing them.
Executive Dashboards vs. Team-Level Reporting
Effective executive dashboards present a small number of key indicators — usually schedule, budget, scope, and a risk or issue flag — in a format that allows rapid pattern recognition. RAG (Red / Amber / Green) status indicators, trend lines, and a brief narrative summary of the most important current development are more useful to an executive audience than the task completion tables and milestone lists that team-level reporting requires.
How to Communicate Bad News
The communication of bad news is one of the areas where project managers most frequently underperform. The temptation is to delay reporting bad news in the hope that the situation will improve, or to bury it in a report dense enough that it may not be noticed. Both approaches are worse than the alternative.
The principle for communicating bad news is simple: early, clear, and accompanied by options. Sponsors and senior stakeholders can almost always help with a problem if they know about it early enough. They cannot help with a problem they discover only when it has become a crisis. The project manager who surfaces bad news early, frames it honestly, and presents two or three options for response builds significantly more credibility than the one who allows problems to accumulate silently.
When Stakeholders Are Not Reading Your Reports
If stakeholders are consistently not reading project reports, the report is the problem, not the stakeholders. The most common causes are: reports that are too long, reports that require too much context to interpret, reports that do not clearly surface the one or two things the recipient needs to act on, and reports that arrive too frequently or at the wrong time in the stakeholder's own work rhythm.
The diagnostic is simple: ask. A brief conversation with key stakeholders about what they actually find useful — and what they skip — will surface more actionable feedback than any amount of speculation about why engagement is low. Most stakeholders will give honest feedback if asked directly and will appreciate a project manager who is trying to make their communication more useful rather than just more comprehensive.
XNM Consulting works with project teams and programme offices to build communication frameworks, improve stakeholder engagement, and develop the reporting discipline that effective project governance requires. Learn more about our program and project delivery services.