How to write a project status report from the current evidence
A status report gives stakeholders a clear view of progress, upcoming work and issues that need attention. It is useful when the source material is spread across a selected project view or a set of notes.
Start with the right material.
- What you provide
- a loaded project board or task table.
- The intended result
- Save completed work, work in progress and visible blockers with coverage stated.
How the workflow works.
Separate completed work from work in progress and planned work. Explain stated blockers and important changes, keeping the reporting period and the selection of tasks visible.
What to check in the result.
Check totals and status labels against the source. A report built from a partial view should not imply that the entire project was examined or that unreported work is complete.
Preview the Markdown to check headings, lists and links as well as the words. Keep source references with the document so a reviewer can trace important statements back to the material you supplied.
Learn from the worked example.
The downloadable Markdown example shows one possible organization of the result. Read it alongside the source example and notice which statements are recorded facts, proposed wording or questions still needing an answer.
The supplied example is illustrative. It is not a recorded run on your data.
Download the example ↓Use it with your own material.
- Open the source you want to work with and activate WebAct on that tab.
- Copy the task from the hero, add any required fields or preferences, and review the proposed actions.
- Compare the first result with your source. Ask for a specific correction or refinement where needed.