A report outline you can reuse.
Set the project name, reporting start and end dates, report date and author at the top. State the evidence cutoff so readers know how current the report is.
An editable Word document with report sections, tables and fields ready to complete. No signup required.
Download Word template ↓- Executive summary
Explain the period's main change, overall delivery position and most important decision in a short paragraph.
- Status and delivery outlook
State the overall red, amber or green assessment and explain the evidence. Distinguish the approved baseline from any revised forecast.
- Progress this period
Record completed outcomes and material changes within the reporting window. Separate work completed from work still in progress.
- Milestones and next-period priorities
Show planned and forecast dates, material variance and the next deliverables. Include owners for the priorities.
- Risks and issues
Summarize significant current issues and future risks, including impact, owner, response and escalation needs. Reference the supporting logs.
- Actions and decisions required
List the deliverable, responsible person and due date for each action. For decisions, name the decision-maker and explain the consequence of delay.
A completed example.
Fictional project: Customer Portal Refresh · Reporting period: 1–31 October 2026 · Evidence cutoff: 31 October 2026
Monthly status report
Customer Portal Refresh
Overall status: Amber. Acceptance testing began during October. A supplier file delay put testing two days behind the original plan; one day was recovered. At the reporting cutoff, the final cycle was incomplete. The forecast launch date remains unconfirmed pending test completion.
Progress and milestones
The first test cycle completed and the second cycle started. The approved testing finish was 30 October. The team forecasts completion on 2 November, subject to resolution of remaining defects.
Current issue · I-01
The final test cycle is incomplete at month-end. Maya, the test lead, owns the recovery plan. The delivery effect must be reassessed after final results are available.
Future risk · R-01
If high-priority defects remain after the final cycle, the launch may need to move. Jordan, the project manager, will confirm the release criteria with the operations lead.
Next action · A-01
Maya will confirm final test results and the forecast completion date by 2 November. Status at cutoff: Open.
Decision required
The sponsor must confirm by 3 November whether to retain or move the launch window, using the final test results. A later decision may reduce the time available to notify users.
Use the example as a writing pattern. Its dates, names and status assessments are illustrative, rather than records from a customer project.
Before you share the report.
- Check that every completion claim is supported by an update or record.
- Keep unresolved issues visible even if they were first recorded before this period.
- Confirm owners, due dates and the difference between baseline and forecast dates.
- Explain the reason for a status rating instead of showing a color alone.
- Make sure the status report and attached logs describe the same delivery position.
If your organization has a required report format or status rules, adapt this outline to those requirements.
Use the outline with Project Controls Assistant.
Record your updates, review proposed control records and compile a report for the relevant period. Review the status report and supporting logs before exporting to Word or PDF. Custom date ranges depend on your plan.