Keep stakeholders informed with a weekly project status report covering progress, milestones, budget, risks, and decisions. Preview the three-page example, copy it into your workspace, or generate an update from your own project notes.
Customize your documentComplete example · 3 pages
A fictional weekly update for Northstar Services as it moves 20 sales users from spreadsheets to a shared CRM. The dark teal three-page example shows completed work, a USD 24,000 budget, an overdue data file, and a pending resource decision. Its 60% progress figure means 18 of 30 tasks are complete, not that 60% of the effort is finished.
Generate a document from your brief, or copy the example into your workspace.
Generate in ML Clever Copy to my workspaceYour generated document will reflect your brief and sources. The preview shows a completed example.
Name the project, reporting period, author, and intended reader. Summarize the overall status and explain what needs attention. In the example, the CRM rollout is at risk because an overdue customer data file could delay testing and go-live, even though several tasks are complete.
State what finished during the reporting period and show how you measure progress. The example records approved field mapping, a validated data sample, and completed pipeline configuration. Its 18 of 30 completed tasks equal 60% by task count; tasks may require different amounts of effort.
Keep original due dates visible alongside actual completion dates or revised targets. Explain how a delay affects later work. The example's data file was due October 8 and has a revised target of October 13. Testing is due October 16, and the October 30 go-live target remains at risk until data delivery and testing are resolved.
Separate the approved budget, actual spend, and forecast total cost. The sample shows USD 24,000 approved, USD 10,800 spent, and USD 23,500 forecast at completion, leaving a forecast budget balance of USD 500. The difference between budget and spend to date is not the final expected saving.
Identify the problem, likely impact, responsible owner, and response. An overdue file is an existing issue; possible duplicate records are a risk to check before migration. The example also flags unconfirmed training attendance so readiness work stays visible alongside technical delivery.
Make each requested decision clear, with an approver and deadline. Follow it with actions, owners, and dates. In the example, sponsor approval for two working days of internal analyst support is still pending. The next actions cover the resource decision, data delivery, testing, training attendance, and the next weekly update.
Start with a clear structure, then tailor the evidence and recommendation to the people in the room.
Collect this period's notes, milestone changes, budget figures, and open decisions. Replace the prompt placeholders with your details and attach any supporting files in Docs mode. Include the previous report only when you can distinguish its information from the latest update.
Choose Generate in ML Clever to draft an update from your brief, or Copy to my workspace to adapt the completed CRM rollout example. Replace its fictional company, names, dates, progress, and budget with your project's details. Adjust the theme and structure to suit your audience.
Verify the headline status against the milestones and risks, recalculate progress and budget figures, and confirm action owners, deadlines, and approval status. Set the correct reporting period and review every page before sharing. For the next update, supply fresh notes and identify completed, changed, and still-open items.
Include the project name, reporting period, overall status, completed work, progress measures, milestone dates, budget where relevant, risks, blockers, decisions required, and next actions with owners and deadlines. The executive summary should explain the most important change or decision without requiring the reader to study every table.
Start with the latest project facts and explain the overall status. Summarize what finished this week, compare milestones with their original dates, identify blockers and decisions, and list the next actions. Reconcile the summary with the detailed dates and figures before sharing. The prompt on this page follows that structure.
Yes. Change the reporting period and summarize progress across the month while keeping the same core sections. Use monthly figures where available and preserve original milestone dates. If you combine weekly updates, remove duplicate achievements and check that resolved issues are not still presented as open.
Explain what your percentage measures. The example divides 18 completed tasks by 30 planned tasks to get 60% task completion. That does not establish 60% of the effort or cost is complete. If you use weighted tasks or effort estimates, state the method and use consistent inputs each reporting period.
Use the shortest report that gives stakeholders enough information to act. This example uses three pages for the executive snapshot, milestone schedule, and risks with next actions. A smaller project may need one page; a complex project may need supporting detail beyond the main update.
You can preview all three pages and use the outline and prompt here before signing up. To edit a document, generate a report from your own brief or copy the example into your ML Clever workspace. You can change the text, structure, and theme. PDF export is available on eligible plans.
