Published by JMB Project Management Co. LLC
A project status report should help its sponsor decide whether intervention is needed. Start with the delivery position and the decisions ahead. Detailed activity lists can sit behind that account, where they support it.
Ask whether the report answers a practical question: can the project still achieve its agreed scope, date and budget on the assumptions currently being used? If the answer is uncertain, describe what needs to be established.
Explain what changed
Show changes since the previous report. A delayed milestone matters because of its effect on the remaining plan. Identify the affected dependency, revised forecast and proposed response.
Consider an illustrative system implementation awaiting interface specifications. Recording that a workshop took place provides little insight into delivery. A useful update explains whether the specification was agreed, when development can begin and what happens if approval is delayed again.
Separate facts from forecasts
Label completed work as completed only when the relevant evidence or acceptance is available. Explain the basis for future dates and any assumptions that could change them.
A percentage-complete estimate should be accompanied by a definition. If half the tasks are complete but the unresolved work includes the largest integration dependency, the percentage alone may give a misleading impression.
Bring decisions into view
For each sponsor decision, state the issue, available options, recommended action and latest useful decision date. Explain the consequence of postponement.
Approval requests should identify who has authority to decide. If a matter belongs with another committee or budget owner, show the route rather than leaving it as an open action.
Make the risk discussion useful
Describe the most significant risks in terms of their potential effect, current response and owner. A long unchanged register can obscure the matters affecting delivery now.
Distinguish a risk from a problem that has already occurred. An unresolved supplier delay needs an action and forecast adjustment; it should not remain described as a possible future occurrence.
PMI’s discussion of project sponsorship examines the sponsor’s responsibilities and organizational role. JMB recommends designing the report around those decisions and responsibilities, while keeping the supporting detail available to the delivery team.
End with accountable next steps
Record who will do what before the next review. Include actions by the sponsor as well as the project team, and carry unresolved decisions forward visibly.
To assess your current report, ask whether a sponsor could identify the leading delivery concern and required action without attending a separate briefing. If not, revise the summary before adding more pages.
JMB supports project governance and management reporting for organizations seeking a clearer view of delivery.