What a governance Status Report must do
Preserve delegated authority through evidence.
The Project Board approves the Business Case and delegates delivery within defined tolerances. The Status Report is the Project Manager's evidence that the delegation remains safe. It confirms whether the forecast remains inside those limits and escalates when it will not.
Authority
Does delivery remain inside the authority delegated to the Project Manager?Forecast
Where will time, cost, scope, risk and benefits finish?Tolerance
How much management margin remains before exception?Trajectory
Is control improving, stable or deteriorating?Escalation
What must the Project Board decide, enable or accept?Report where the project is expected to finish, how much tolerance remains and which assumptions support that view. Current activity and spend do not prove future control.
Do not duplicate plans, registers or task lists. Extract the evidence that changes Board assurance, delegated authority or the need for a decision.
Copyable Project Governance Status Report template
Start with the approved control position.
Copy this structure into Word or your organisation's approved reporting format. Confirm the current baselines and tolerances before assigning any status. Replace every prompt with verified evidence and remove drafting guidance before submission.
Document details
[Insert approved project name]
[Insert start and end dates]
[Insert evidence cut-off date]
[Insert approved stage]
[Insert name and role]
[Insert name and role]
[Insert review date]
[Insert controlled reference]
[Green, amber or red against the agreed thresholds]
[Improving, stable or deteriorating]
[High, medium or low]
[Within tolerance or forecast breach]
Status rules used for this report
| Status | Control meaning | Minimum response |
|---|---|---|
| Green | Forecast remains within delegated tolerance and no material Board intervention is required. | Continue delivery and monitor early-warning triggers. |
| Amber | Margin is tightening, confidence is weakening or a decision may be required before the next report. | Apply recovery action, increase monitoring and expose the decision deadline. |
| Red | A tolerance breach is forecast or immediate Board authority, direction or intervention is required. | Escalate with options, recommendation, consequences and decision request. |
1. Executive snapshot
State the complete control position in one minute.
Write this section last. It should tell the Board whether the project remains viable, whether delegated tolerance is safe and what has changed since the previous reporting cycle.
[State the overall health, forecast tolerance position and viability. Explain the principal movement since the previous report.]
[State which tolerance has the least remaining management margin and whether it is tightening.]
[Explain why confidence is high, medium or low and identify any weak evidence or uncertain assumption.]
[State the risk, issue or dependency most capable of changing the forecast.]
[State the recovery or preventive action, owner, deadline and expected effect.]
[State the decision, support or direction required, or confirm that none is required.]
Executive snapshot scrutiny questions
- Can a Board member understand the control position in under one minute?
- Does the statement confirm whether the project remains within delegated tolerance?
- Are overall RAG, trend and delivery confidence supported by the narrative?
- Is movement since the previous report explained?
- Is the most material exposure visible rather than buried later?
- Does the statement distinguish current performance from forecast outcome?
2. Forecast against tolerances
Show the remaining margin before exception.
Compare the approved baseline, current forecast and delegated tolerance explicitly. Do not limit the analysis to time and cost where scope, quality, benefits or risk could invalidate the Business Case.
| Control dimension | Approved baseline | Current forecast | Tolerance range | Remaining tolerance margin | Trend and confidence | Status and response |
|---|---|---|---|---|---|---|
| Time | [Approved position] | [Forecast position] | [Delegated limit] | [Margin remaining] | [Direction and evidence confidence] | [RAG, action, owner and date] |
| Cost | [Approved position] | [Forecast position] | [Delegated limit] | [Margin remaining] | [Direction and evidence confidence] | [RAG, action, owner and date] |
| Scope | [Approved position] | [Forecast position] | [Delegated limit] | [Margin remaining] | [Direction and evidence confidence] | [RAG, action, owner and date] |
| Quality | [Approved position] | [Forecast position] | [Delegated limit] | [Margin remaining] | [Direction and evidence confidence] | [RAG, action, owner and date] |
| Benefits | [Approved position] | [Forecast position] | [Delegated limit] | [Margin remaining] | [Direction and evidence confidence] | [RAG, action, owner and date] |
| Risk | [Approved position] | [Forecast position] | [Delegated limit] | [Margin remaining] | [Direction and evidence confidence] | [RAG, action, owner and date] |
| Resource capacity | [Approved position] | [Forecast position] | [Delegated limit] | [Margin remaining] | [Direction and evidence confidence] | [RAG, action, owner and date] |
[Explain what moved since the previous report, the cause and whether the change is temporary or structural.]
[State contingency used this period, contingency remaining and whether the rate of use is sustainable.]
[Confirm whether the assumptions supporting viability and expected benefits remain valid.]
[State the expected impact of current recovery action and when the forecast will be reassessed.]
Forecast and tolerance scrutiny questions
- Are the baselines and tolerances the latest versions approved by the Project Board?
- Is current forecast shown separately from actual performance to date?
- Is remaining tolerance margin visible for every controlled dimension?
- Are tightening margins explained before they become breaches?
- Are scope, quality, benefits and risk treated as controls, not footnotes?
- Is contingency consumption linked to the underlying drivers and recovery action?
3. Milestone position
Expose trajectory through decision-relevant dates.
Include stage boundaries, approvals, product acceptances, procurement events, transition points and other dates that materially affect control. Routine tasks belong in the plan.
| ID | Milestone | Owner | Baseline date | Forecast or actual date | Variance | Trend | Significance, recovery or decision |
|---|---|---|---|---|---|---|---|
| [M1] | [Board-relevant milestone] | [Name] | [Date] | [Date] | [Days or weeks] | [Improving, stable or deteriorating] | [Governance impact and current response] |
| [M2] | [Board-relevant milestone] | [Name] | [Date] | [Date] | [Days or weeks] | [Improving, stable or deteriorating] | [Governance impact and current response] |
| [M3] | [Board-relevant milestone] | [Name] | [Date] | [Date] | [Days or weeks] | [Improving, stable or deteriorating] | [Governance impact and current response] |
Milestone position scrutiny questions
- Are only milestones that matter to Board control included?
- Is each baseline date compared with a current forecast or actual date?
- Does every adverse variance explain its governance significance?
- Is the recovery action owned, dated and reflected in the forecast?
- Are critical dependencies and approval dates visible?
- Would gradual schedule erosion be visible before time tolerance is breached?
4. Risk and material issue position
Report exposure that could change control.
Do not reproduce the Risk Register or Issue Log. Elevate only items capable of affecting viability, tolerance, delivery confidence or the need for Board action.
Overall risk exposure
[Increasing, stable or reducing, with a short explanation]
[State whether current exposure threatens a tolerance, assumption or Board decision date]
Material risks
| ID | Risk and impact | Residual exposure | Trend | Owner | Response and due date | Escalation likelihood |
|---|---|---|---|---|---|---|
| [Risk ID] | [Cause, uncertain event and consequence] | [Rating after response] | [Direction] | [Name] | [Action and date] | [Assessment and trigger] |
Material issues
| ID | Issue and impact | Forecast effect | Owner | Resolution plan and date | Board attention required |
|---|---|---|---|---|---|
| [Issue ID] | [Current event and consequence] | [Effect on tolerance or confidence] | [Name] | [Action and date] | [Decision, direction, acceptance or none] |
Risk and material issues scrutiny questions
- Are risks kept separate from issues that have already happened?
- Are only exposures capable of changing viability, tolerance or confidence elevated?
- Does every item have a named owner and current response?
- Is residual exposure shown after the planned response?
- Is the likelihood of Board escalation explicit?
- Are newly emerging threats surfaced before a complete answer is available?
5. Financial position
Show forecast completion, not spend alone.
The Board needs assurance that financial control remains deliberate. Actual expenditure can be below plan while the expected final cost is already deteriorating.
| Approved budget | Actual to date | Forecast to complete | Forecast at completion | Remaining contingency | Forecast variance | Status and trend |
|---|---|---|---|---|---|---|
| [Value] | [Value] | [Value] | [Value] | [Value] | [Value and percentage] | [RAG and direction] |
[Explain the principal causes of current and forecast variance.]
[Explain contingency used, remaining exposure and whether consumption is proportionate to work remaining.]
[State the expected effect of unresolved risks, issues, changes, claims or commitments.]
[State action, owner, review date and expected forecast effect.]
Financial position scrutiny questions
- Do approved budget, actual cost and forecast at completion reconcile?
- Is remaining contingency shown separately from unspent budget?
- Are the causes of forecast variance explained?
- Is the rate of contingency consumption proportionate to the stage remaining?
- Are pending changes and risk allowances reflected in the forecast?
- Would an unfavourable trend be visible while cost remains technically within tolerance?
6. Decisions and support required
Make escalation impossible to misread.
A concern is not a decision request. State the authority, direction, acceptance or support required, the recommendation and the latest date on which the Board can act without changing the forecast.
| ID | Decision or support required | Recommendation and rationale | Impact if not approved | Decision owner | Required by |
|---|---|---|---|---|---|
| [D01] | [State the exact approval, direction or support] | [Recommended response and reason] | [Effect of delay, refusal or no action] | [Role or Board] | [Date] |
No Project Board decision or additional support is required at this reporting point.
Decisions and support scrutiny questions
- Is every request written as a decision, authority or support requirement?
- Does each request include a clear recommendation?
- Are the consequences of delay or refusal stated?
- Is the latest decision date explicit?
- Is the accountable decision maker identifiable?
- If no decision is required, does the report say so directly?
7. Forward look
Close with judgement about the next control period.
Do not finish with a task list. State how the project is expected to evolve, which assumptions matter and what would cause confidence or tolerance exposure to change.
[State the delivery outcome, approval or transition event that will determine the next control position.]
[Identify external decisions, suppliers, resources or sequencing constraints and their latest safe dates.]
[State which risks or issues are expected to increase, stabilise or reduce and why.]
[State whether delivery confidence is expected to improve, remain stable or deteriorate.]
[State the evidence or event that would require reassessment or escalation before the next report.]
[Insert the review date, evidence required and accountable owner.]
Forward look scrutiny questions
- Does the forward look describe trajectory rather than list routine tasks?
- Are the next period's decisive events and dependencies visible?
- Does it state how risk exposure is expected to move?
- Does it state whether delivery confidence is expected to change?
- Are early-warning triggers defined for assumptions that could fail?
- Can the next report test whether this forecast judgement was sound?
Final quality check
Test whether the report proves control.
Final Project Governance Status Report quality check
- Can the control position be understood in under one minute?
- Is the report anchored to forecast rather than activity?
- Are current baselines and delegated tolerances explicit?
- Is remaining tolerance margin visible?
- Are RAG status, trend and confidence supported by evidence?
- Does the Executive Snapshot explain movement since the previous report?
- Are scope, quality, benefits and risk controlled alongside time and cost?
- Do milestones expose trajectory and decision deadlines?
- Are full plans and registers kept outside the report?
- Are only material risks and issues elevated?
- Does every material exposure have an owner and response?
- Does the financial section show forecast at completion?
- Is contingency consumption explained?
- Is every Board request explicit, recommended and time-bound?
- Does the Forward Look describe expected movement and early warnings?
- Would the report expose deterioration before tolerance is breached?
If any answer is no, the report is not ready for Project Board scrutiny.
Want the editable Word version?
Use the preformatted governance Status Report.
The page above gives you the complete reporting structure and strengthened scrutiny tests. The editable nine-page Word resource adds the practitioner explanation of delegated authority, what Project Boards actually look for, a compact two-to-three-page report layout and ready-to-complete tables with removable drafting prompts.
The resource unlocks shortly after the trial period.
Explore Prepare2Lead membershipIncluded with paid Prepare2Lead membership, from $97 a month.Important note
This working template supports Board-level governance reporting. It does not replace the baselines, tolerances, reporting frequency, assurance requirements or decision authorities approved for your project.
Never use artificial intelligence to invent progress, forecasts, tolerance margins, costs, risks, issues, confidence or Board decisions. It can help organise verified evidence, but accountability remains with the Project Manager and Project Board.