The weekly project update

A draft says testing is complete. The source says otherwise. Here’s the review I’d do before sending this update to a sponsor.

Illustrative example · Fictional data · By Harold Vazquez

The rehearsal still needs approval.

A project manager is preparing a weekly update for a fictional warehouse-system rollout. The sponsor needs to know whether testing is on track and whether the rehearsal date should change.

I would ask AI to group the source notes by progress, risk, and decision needed before drafting. I would then decide the project status myself. Two unresolved tests don’t tell a model enough about the wider project to make that call.

Source notes

P1: Training workstream note

Training materials approved. No open training-content decision.

P2: Integration test log

8 of 10 priority interfaces passed. Two require retesting after the vendor patch. Patch success is not yet confirmed.

P3: Project manager decision log

Request sponsor approval by Friday for a two-business-day rehearsal shift. If the patch fails, bring the readiness decision to the next steering meeting. Integration lead owns the contingency plan.

The draft needs a closer look

This sample draft was written to demonstrate the errors. It is not a recorded model response.

The project is green: testing is complete and training is approved. The rehearsal will move by two days.

What I would change

  • Reject green status: P2 still has two unresolved tests. Amber is the reviewer's assessment, not a status supplied by AI.
  • Preserve decision ownership: P3 requests approval; it does not record an approved schedule change.
  • Name the contingency: The patch and steering decision are material dependencies, not background detail.

The revised project update

Status: Amber, based on unresolved integration testing. Training materials are approved. [P1] [P2]

Evidence: 8 of 10 priority interfaces passed. Two await retesting after the vendor patch. [P2]

Decision requested: Approve a two-business-day rehearsal shift by Friday. This change is not yet approved. [P3]

Contingency: If the patch fails, bring the readiness decision to the next steering meeting. The integration lead owns the contingency plan. [P3]