A completed example
This fictional example shows the level of detail to aim for. It is not a customer's work history.
Monthly status report Project: Harbor billing migration Period: September 1 - September 30, 2026 Prepared by: Priya N., project lead Sent to: Finance ops leads, engineering manager Overall status: At risk Summary: Invoice generation now runs on the new system for internal accounts. Customer accounts move in October, two weeks later than planned, because the tax lookup service still fails on multi-region addresses. Completed this month - Moved internal test accounts to the new invoice engine (Sept 12) - Finished a parallel run comparing old and new August invoices, found 4 mismatches and fixed all of them - Wrote the rollback runbook and walked through it with the on-call team (Sept 24) In progress - Tax lookup fix for multi-region addresses, owner: Marco, about half done - Customer email templates for the new invoice format, owner: Lena, in review with support Not done or slipped - Customer account cutover, moved from Sept 29 to Oct 13 - Finance reporting dashboard, not started, paused until after cutover Risks and blockers - If the tax fix is not merged by Oct 6, the Oct 13 cutover moves again - Support has not confirmed staffing for cutover week Decisions needed - Approve the new cutover date of Oct 13 (Finance ops leads, by Oct 3) Plan for next month - Merge and test the tax lookup fix by Oct 6 - Cut over customer accounts on Oct 13 - Start the finance reporting dashboard
Make it yours
Your draft
The example is fictional. Edits stay in this page and disappear when you leave. Copy or download your work to keep it.
How to fill it in
- Fill in the sections below the summary first, then choose one overall status and write the two-sentence summary last.
- List completed work with dates, and keep slipped items in their own section with the old date and new date instead of deleting them.
- Give every in-progress item an owner and a rough state so readers know who to ask about it.
- Write each decision as a single approval or question that one named person can answer by a specific date.
- Before sending, check the plan for next month against the risks section so nothing that depends on an open blocker reads as certain.
Start from your actual work
On a Mac, Dayflow can help you remember the work behind the update. It drafts a timeline from screen activity. Export a date range as Markdown from Settings → Export. Review that record alongside your calendar and task tracker, then fill in the template above.
For a guided walkthrough, see exporting your work history or drafting a report with Claude Code. Check the assistant's draft before sending it.
Local AI keeps screenshot analysis on-device. Your own cloud provider or Dayflow Pro processes selected screenshots off-device. An assistant can receive the Dayflow data it retrieves in your conversation. Local storage does not make a cloud assistant conversation local. Read the data-flow guide before choosing a workflow.
Questions about this template
What should a monthly status report include?
Include an overall status, a short summary, work completed with dates, work in progress with owners, anything that slipped, risks and blockers, decisions you need from readers, and the plan for next month. Put the status and summary at the top so someone who reads only two lines still knows whether the project is on track.
How long should a monthly status report be?
Aim for one page that a reader can scan in a couple of minutes. Use short bullets rather than paragraphs and leave out routine tasks nobody needs to act on. If a topic needs more detail, such as a design decision or incident review, link to it separately instead of expanding the report.
How do I report a project that is behind schedule?
Say so in the overall status and the summary, not only further down. Give the original date, the new date and the reason for the delay. Then name what the new date depends on and any decision you need from readers. Readers handle bad news better when it arrives early with a plan.
What is the difference between a monthly and a weekly status report?
A weekly report tracks tasks and short-term blockers for the people doing the work. A monthly report steps back for managers and stakeholders, focusing on outcomes, schedule changes, risks and decisions. It is also not a performance review or a full project plan. It summarizes where things stand and what comes next.
Can I build a monthly status report from my tracked time?
Time records can help you remember what happened over the month. Dayflow drafts a timeline from your screen activity on a Mac, and you can export a date range as Markdown. You still have to check it, add offline work like meetings and calls, and turn activity into outcomes. A status report is also not an approved timesheet.
Use the right format for the next step
- Weekly status report for a concise progress update.
- Daily work log for a record you can come back to.
- Daily standup template for yesterday, today, and blockers.
Download Dayflow