A project status report should help a named decision-maker understand what changed, what the project now forecasts, which evidence supports that view and what action is required. It should not be a diary of completed tasks.

This guide provides STATUS-8, a copyable one-page template, calculation rules and a worked example for projects that need a disciplined weekly or monthly review.

The copyable STATUS-8 template

Field What to record Test of usefulness
1. Decision summary Decision, approval or help required; owner; due date Can the reader act without another meeting?
2. Outcome and benefit Intended outcome, current measure, target and forecast Is project health linked to value rather than activity?
3. Scope and change Approved scope, proposed changes, acceptance effect Is every material change visible and authorized?
4. Milestones and forecast Baseline date, forecast date, variance, confidence Does the report show where the finish date is moving?
5. Cost and capacity Budget, actual/committed cost, estimate at completion, critical capacity Are financial and resource consequences explicit?
6. Risks and issues Trigger, probability/impact, owner, response and decision threshold Are future uncertainty and current problems separated?
7. Dependencies and quality External dependency, evidence date, acceptance or quality result Can hidden handoffs invalidate the forecast?
8. Next control point Next milestone, evidence due, owner and review date Is the next verification event unambiguous?

Keep each field short. Link to registers or evidence rather than pasting them into the report.

Start with the decision, not the colour

The first line should answer: What does the reader need to decide or unblock?

Examples include approving a scope trade-off, releasing contingency, accepting a residual risk, assigning scarce capacity or escalating a dependency. If no decision is required, state the most important forecast change and the evidence that will be reviewed next.

A useful status report can be green and still ask for a decision. Conversely, a red report without a specific action is often only an alarm.

Calculate schedule variance consistently

For a milestone, use:

Schedule variance (days) = current forecast date − approved baseline date

If the baseline launch is 30 September and the forecast is 10 October, variance is +10 calendar days. Preserve the baseline; do not quietly move it to make the report green.

Add a confidence statement:

  • High: critical dependencies are confirmed and recent evidence supports the forecast;
  • Medium: one material dependency or estimate remains open;
  • Low: critical evidence is missing, conflicting or older than the review threshold.

Confidence is not probability. It describes the quality of the forecast basis.

Calculate cost exposure without hiding commitments

Use three values:

  • Actual cost: recorded expenditure to date;
  • Committed cost: approved obligations not yet fully invoiced;
  • Estimate at completion (EAC): expected total cost if the current plan is completed.

Then calculate:

Forecast cost variance = EAC − approved budget

Suppose the budget is €240,000, actual cost is €145,000, open commitments are €62,000 and remaining work is estimated at €48,000. EAC is €255,000 and forecast variance is +€15,000, or +6.25%. Reporting only actual cost would falsely imply unused headroom.

Define RAG status with gates

Use colour only after the evidence fields are complete. A simple rule is:

Status Decision rule
Green Outcome, milestone and cost forecasts remain within approved tolerance; no critical unowned risk or dependency
Amber A tolerance may be exceeded without action, confidence is medium/low, or a material dependency lacks confirmation
Red An approved tolerance is breached, a critical outcome is at risk, or required authority/evidence is absent

Apply a critical gate: a project cannot be green when safety, legal, privacy, security, acceptance or mandatory-control evidence is unresolved beyond its decision threshold.

Do not average red and green dimensions into amber. The most consequential unresolved gate should drive the overall status.

Worked one-page example

Project: Customer onboarding redesign
Reporting date: 4 September 2026
Overall status: Amber
Decision required: Product owner to approve a two-week phased release by 7 September.

STATUS-8 field Example entry
Outcome Reduce median onboarding time from 4.8 days to 2.5 days; pilot forecast 2.9 days
Scope Core web flow unchanged; proposed deferral of two low-volume integrations
Milestone Baseline 30 Sep; forecast 10 Oct; +10 days; medium confidence
Cost Budget €240k; actual €145k; commitments €62k; EAC €255k; +€15k
Risks/issues Integration test environment unavailable; owner: Platform Lead; escalation threshold reached
Dependencies/quality Security test passed 3 Sep; data-retention acceptance pending; vendor environment due 6 Sep
Next control point Phased-release decision 7 Sep; integrated rehearsal 12 Sep

The report is amber because the forecast exceeds the date tolerance and one acceptance dependency is open. The decision line makes the remedy visible.

Separate risks, issues, assumptions and decisions

These four records answer different questions:

  • Risk: What uncertain event could affect objectives?
  • Issue: What problem exists now?
  • Assumption: What unverified condition does the plan depend on?
  • Decision: What authorized choice was made, by whom and why?

Blending them obscures action. A supplier delivery expected next week is an assumption until confirmed; a missed delivery is an issue; a possible future delay is a risk; accepting a phased launch is a decision.

For stakeholder prioritization, use the STAKE-8 mapping template. For post-launch value, the benefits realization plan provides baselines, owners and review dates.

Build the report from controlled sources

Every important number should name its source and evidence date. Typical sources include the approved charter, integrated plan, finance ledger, resource plan, risk register, quality results, acceptance record and decision log.

When an AI tool helps summarize project records, require source links, prohibit confidential data in unauthorized services and make a responsible person verify every conclusion. The report is an accountable management record, not generated prose.

A 20-minute reporting workflow

  1. Freeze the reporting date and approved baselines.
  2. Refresh milestone, cost, capacity and acceptance evidence.
  3. Recalculate variances and confidence.
  4. Check critical gates and tolerance breaches.
  5. Write the decision line before the narrative.
  6. Confirm owners and due dates with the people accountable.
  7. Remove task detail that does not change a forecast or decision.
  8. Archive the report and link it to the supporting registers.

Next step

Use STATUS-8 for one reporting cycle, then ask decision-makers which fields changed an action and which created noise. Improve the template without removing baseline, forecast, evidence, owner or decision traceability.

MTF Institute's Professional Certificate in Project Management includes applied work on charters, schedules, budgets, stakeholders, communication, risk, quality, change, procurement, metrics and portfolio decisions. The live page states the current curriculum, tuition and professional, non-degree credential status.

Sources