How to prepare a status report with AI

Anchor status to the baseline and cutoff

Record the reporting cutoff, approved scope, baseline milestones, budget or capacity basis, and prior forecast. Then collect current delivery artifacts, decisions, issue logs, risk changes, and owner forecasts. A status statement without a dated baseline cannot show variance.

Build an evidence ledger:

| Status claim | Baseline | Current evidence | Confidence | Owner | |---|---|---|---|---| | Configuration complete | 12 Sep | Test record passed 11 Sep | High | Product lead | | Reviewer practice ready | 13 Sep | Draft exists; approval absent | Medium | Operations lead | | Pilot starts 16 Sep | 16 Sep | Access decision due 15 Sep | Low | Pilot owner | | Final decision 24 Sep | 24 Sep | Depends on pilot sample | Low | Sponsor |

The example is synthetic. It exposes that “on schedule” would conceal the unresolved access dependency.

UK project-management guidance describes regular highlight reports covering stage status, significant changes, issues, progress, and exceptions for oversight. The UK major-projects annual report also cautions that a delivery-confidence rating is a snapshot under current risks and issues, not a complete reflection of performance. These official sources support evidence-led reporting, not a rating for any Two Prune project.

Separate progress, forecast, and confidence

Progress describes completed, evidenced work. Forecast describes the current expected outcome or date. Confidence explains the strength and uncertainty of that forecast. Keep them separate.

For each milestone, show baseline date, current forecast, variance, cause, consequence, and recovery decision. A completed workshop is not progress toward a deliverable unless it produced and approved the required output. Ask AI to find updates that use vague completion language such as “mostly done” and request the underlying artifact.

A failure example reads: “Overall status is green. All workstreams are progressing, and the team expects to recover a minor delay.” It provides no evidence, hides the affected milestone, and leaves recovery unowned. Repair it: “Reviewer practice approval is two days late; pilot start remains 16 September only if the operations lead approves by 13 September and access clears by 15 September. Otherwise the forecast moves to 23 September.”

Make risks and decisions operational

Report only the risks and issues that matter to the current decision horizon. Include trigger, exposure, response, owner, and next review. Distinguish a risk that might occur from an issue that has occurred. Link both to milestones or outcomes.

List decisions separately with a clear owner and latest useful date. If the status report needs sponsor action, place that request near the top. Do not bury it in commentary.

Use AI to compare this period with the last report and flag unexplained changes in dates, ratings, owners, or scope. A changed status is acceptable; an untraceable change is not.

Reconcile and challenge optimism

Before release, ask workstream owners to confirm the evidence and forecast attributed to them. Recalculate dependency effects rather than copying local dates. Review whether recovery assumes overtime, unapproved scope changes, or capacity that is already allocated.

Verify that:

The final artifact is the concise status report plus evidence ledger, milestone variance table, risk and issue extract, decision log, and forecast assumptions. Preserve prior reports so leadership can see trend and forecast accuracy rather than only the latest narrative.

• the cutoff and baseline are explicit;
• completed work points to accepted artifacts;
• forecast dates include dependency effects;
• confidence reflects evidence strength;
• red, amber, or green labels match defined rules;
• risks and issues are distinguished;
• recovery actions have owners and dates;
• decisions identify authority and deadline; and
• changes from the prior report are explained.

Sources and claim map

The dates, project, roles, and status are synthetic. This method does not assert a delivery result, forecast accuracy, or project outcome.

• UK Government, Guidelines for Managing Projects: supports regular highlight reporting of stage status, progress, changes, issues, and exceptions.
• NISTA, Major Projects Annual Report 2025-26: supports the limited warning that delivery-confidence ratings are current snapshots rather than complete performance accounts.

Sources: [1] [2]