1. Put the updates in time order.
This fictional project is preparing a customer portal release. The reporting period is 1–31 October 2026. Keep the date and source of each update so later changes can be interpreted in context.
- 5 October · Testing starts
Acceptance testing began today. The supplier's remaining test files are expected on 9 October.
- 16 October · A delay becomes visible
The supplier files arrived late. Testing is now two days behind the original plan. Maya will confirm a recovery plan by 20 October.
- 23 October · Partial recovery
Weekend testing recovered one day. The final test cycle is still in progress and is one day behind the original plan. No final test results are available.
No later update is available at the reporting cutoff. That gap is itself something to check before issuing the report.
2. Review the supporting records.
Extract the conditions and commitments without adding facts that the updates do not contain.
| Record | What the evidence supports | What still needs confirmation |
|---|---|---|
| Issue | Testing fell two days behind; one day was recovered by 23 October. | The current forecast and whether the final cycle has completed. |
| Action | Maya was to confirm the recovery plan by 20 October. | Whether the plan was delivered. Later progress does not prove this action closed. |
| Possible risk | Remaining testing may affect delivery if the schedule has no contingency. | The release date, available contingency and actual delivery exposure. Treat this as a candidate for review. |
A late update can leave an action apparently overdue without showing its actual outcome. Confirm it with the owner rather than automatically marking it complete.
3. Explain the change across the period.
Example status report
Testing progressed, with a delay still unresolved.
Acceptance testing started in October. Late supplier files put testing two days behind the original plan. Weekend testing recovered one day, leaving the final cycle one day behind as of the latest update on 23 October.
Final test results and the current completion forecast have not been confirmed at the reporting cutoff. Maya's recovery-plan action also needs an outcome update. The effect on the release date remains unconfirmed until the remaining test work and available schedule contingency are assessed.
Next step: Obtain the final test position and recovery-plan outcome from Maya, then update the delivery forecast and any decision needed from the sponsor.
This status report preserves the chronology, the partial improvement and the uncertainty. It does not claim that the launch is on track or that the recovery-plan action was completed.
4. Check the report against the logs.
- Use the selected period for progress claims and make the latest evidence date visible.
- Include relevant unresolved issues and risks even when they began in an earlier period.
- Check each completion claim against an update or confirmed record.
- Confirm owners, dates and decisions; distinguish missing information from a negative outcome.
- Remove unsupported certainty from the executive summary and status rating.
Use the monthly report template to organize the status report, milestones and decision requests.
5. Use the same review rhythm in the app.
In Project Controls Assistant, record the updates, review the proposed findings, maintain the approved logs and compile the reporting period. Edit the final report before exporting it. The review step is where you confirm the facts and fill gaps the updates cannot answer.