Guide

What Is a Status Report? The Complete Guide (2026)

Updated October 2026 · by Jerry Liu, Dayflow's founder

A status report is a short, regular update that tells stakeholders what moved, what is next, what is at risk and what you need. The hard part is remembering the week. Toggl wins when the report must come from team timesheets, Timing when you bill clients on a Mac, ActivityWatch when you want free local data, and Dayflow when you want an AI-written timeline to draft from.

A status report is a short, regular written update that tells the people who depend on your work where it stands: what got done, what comes next, what is at risk, and what you need from them. It is written for a reader who has to make a decision, not as a record of how busy you were.

Most people get it wrong by writing it backwards. They open the calendar late on Friday, list everything they touched, and send a wall of activity that buries the one blocker their manager needed to see. The fix is less about writing skill and more about having an accurate picture of the week before you start, then putting the reader’s questions first.

Disclosure: Dayflow, one of the tools listed near the end of this guide, is our product. Details about other tools come from a comparison of each vendor’s own documentation as checked on October 4, 2026.

The short version

What is a status report, exactly?

A status report is a recurring snapshot of a piece of work at a point in time. It can cover a project, a team, a client engagement or your own role. The common thread is that someone else needs to know where things stand without asking you directly.

A complete status report has six parts:

  1. The period. “Week of October 5” or “Sprint 14.” Readers need to know what window they are looking at.
  2. Overall status. A one-word or one-color summary such as on track, at risk or off track, plus one sentence saying why.
  3. Progress. What was finished or meaningfully advanced since the last report, written as results.
  4. Plans. What you will do before the next report, ideally with dates.
  5. Problems. Risks, blockers and dependencies on other people.
  6. Asks. Decisions, approvals or help you need, and from whom.

The audience shapes the tone. A report to your direct manager can be informal and detailed. A report to a client should avoid internal jargon and focus on deliverables. A report to executives should fit in the preview pane of an email.

What a status report is not: a diary, a defense of your time, or a list of every task. If a line would not change what the reader thinks or does, it probably does not belong.

Status report vs standup, timesheet and progress report

Four documents get mixed up constantly because they all describe recent work. They answer different questions for different readers.

DocumentMain question it answersTypical readerTypical cadenceUnit
Status reportAre we on track, and what do you need?Manager, client, stakeholdersWeeklyOutcomes and risks
Standup updateWhat did I do, what am I doing, what is in my way?Immediate teamDailyTasks
TimesheetWhere did the hours go?Finance, client billing, payrollDaily or weeklyHours per project
Progress reportWhat did this phase achieve against the plan?Sponsors, leadershipPer milestoneDeliverables

The practical difference: a standup is about coordination inside a team, a timesheet is about accounting, a progress report is a look back, and a status report is about steering. You can build a status report out of a week of standups or a timesheet, but you have to translate tasks and hours into outcomes and risks on the way. Our guide to automatic standup updates covers the daily version in more detail.

How does a status report actually get read?

Understanding how readers use a status report explains most of the advice about writing one.

It gets skimmed. Your manager may receive several reports on the same afternoon. They read the top, scan the headings, and dig in only where something looks wrong. That is why the overall status and asks go first.

It gets forwarded. A good line in your report may end up pasted into your manager’s report to their manager. Write lines that make sense out of context: name the project, the deliverable and the date instead of saying “the thing we discussed.”

It becomes a record. Over months, a stack of status reports is the clearest history of what a project went through and what you contributed. This is useful at review time, and it is why consistency matters. If the format changes every week, nobody can compare.

It sets expectations. Every “next week” item is a small promise. If you list ten next steps and finish four, the report trains readers to discount your plans. List fewer, and hit them.

The PPP method: how to write a status report in five steps

PPP stands for Progress, Plans, Problems. It is a widely used structure for status updates because it maps directly to what readers want to know. Adding a red, amber or green status line on top (often called RAG status) gives skimmers a one-glance summary. Here is how to put it together.

  1. Gather the raw week before writing. Open your calendar, your task tracker, your sent messages, your merged pull requests or shared files, and any notes you kept. If you kept a short daily log, start there. A work journal or an app that records your activity, such as an automatic time tracker, removes most of the guesswork. Do not write anything yet. You are building an inventory.

  2. Decide the overall status. Look at your goals and dates, not your effort. Green means the current plan will land on time and in scope. Amber means a risk exists that could change that. Red means it will slip without intervention. Write one sentence explaining the color. If you hesitate between two colors, pick the worse one and explain.

  3. Write progress as outcomes. Go through the inventory and keep only items that changed the state of the work. Rewrite each as a result: shipped, approved, decided, unblocked, measured. Merge small related tasks into one line. Three to five lines is usually enough.

  4. Write plans as commitments. List what will be true by the next report. Attach dates where you can. Keep the list short enough that you expect to finish all of it.

  5. Write problems as asks. For each risk or blocker, say what it is, what it affects, and what you need, from whom, by when. “Waiting on design” is a complaint. “Need final icon set from design by Wednesday to keep the October 20 launch” is an ask someone can act on.

Then reorder: overall status first, asks second, then progress, plans and remaining problems. Our weekly status report template follows this order, and the companion guide on how to write a weekly status report walks through each section with more examples.

What does a good status report look like?

The following is a made-up example to illustrate the method. The person, project and details are invented.

Priya is a product designer working on a checkout redesign. Her first draft, written from memory on Friday afternoon, looked like this:

This week I had the design review on Monday, worked on the checkout screens, met with engineering twice, did some research on payment methods, responded to feedback from legal, updated the Figma file, and started thinking about the mobile version. Next week I’ll keep going on mobile and finish the remaining screens. Still waiting on a few things.

Everything in it is true, and almost none of it helps the reader. There is no status, no outcome, and “waiting on a few things” hides the one item that matters.

After running through the PPP steps, she sent this:

Checkout redesign, week of October 5

Status: Amber. Desktop design is on track. Mobile is at risk for the October 20 handoff because the payment provider’s updated button guidelines have not arrived.

Ask: Marco, can you escalate the guidelines request with the payment provider’s account contact by Tuesday?

Progress

  • Desktop checkout screens approved in Monday’s design review.
  • Legal signed off on the new terms checkbox wording.
  • Engineering confirmed the address form can reuse the existing component, which removes one screen from scope.

Next week

  • Hand off final desktop specs to engineering by Wednesday.
  • Draft mobile layouts for the three highest-traffic screens.

Risks

  • Mobile handoff slips by about a week if payment guidelines arrive after October 14.

The second version is not much longer, but a reader knows within two lines whether to worry and what to do. Notice what was dropped: the number of meetings, the vague research, the “started thinking.” Notice what was added: dates, names and a reason for the color.

How often should you send a status report?

Weekly is the usual default for ongoing work. It is frequent enough to catch problems while they are still cheap and spaced out enough that each report shows real movement.

Other cadences fit other situations:

Whatever you choose, send it on the same day each period. A predictable report gets read. An irregular one gets lost, and readers start pinging you directly instead, which defeats the purpose.

Common status report mistakes

Listing activity instead of outcomes. Meetings attended and hours spent describe effort. Readers want to know what changed. If you catch yourself writing “worked on,” ask what is now different because of that work.

Burying the bad news. Putting a slipping date in the fifth paragraph does not make it less real. It just means the reader finds out later, with less time to help. Bad news goes at the top with an ask attached.

Staying green until it turns red. A report that is green for six weeks and then suddenly red damages trust. Amber exists for the uncertain middle. Use it early.

Vague asks. “Need help with the API” gives the reader nothing to do. Name the person, the decision and the date.

Writing from memory on Friday. Memory favors the last day or two and the most stressful moments. Tuesday’s quiet win often disappears entirely. Keeping a short daily work log or a passive record of your week fixes this more reliably than trying harder to remember. If the week regularly feels like it vanished, the where does my week go calculator is a quick way to see the rough split.

Changing the format every week. Readers compare reports over time. Keep the sections and order fixed so differences stand out.

Over-explaining. Background, context and long rationale belong in a linked document. The report should point to it, not contain it.

Tools that help with status reports

No app writes a good status report on its own, because the judgment calls are yours: which color, which risk matters, what to ask for. What tools can do is handle step 1 of the method, giving you an accurate record of the week so you are not reconstructing it from memory. For a broader comparison, see our roundup of Mac time trackers. Four tools are relevant here.

Timing records time automatically across apps, websites and documents on the Mac, down to specific URLs and Mail threads, and lists AI activity summaries and customizable reports on its plans (Timing compared with Dayflow). ActivityWatch is free and open source under MPL-2.0, records the active app and window title, and keeps all data on your own device (ActivityWatch compared with Dayflow). Toggl (formerly Toggl Track) is built around timers, timesheets and calendar integrations, with team reports and Toggl AI for natural-language questions about workspace data (Toggl on the Mac).

ToolWhat it does for thisPrice
TimingAutomatic record of apps, websites and documents on the Mac, AI activity summaries, customizable reportsProfessional $9 per month billed annually, or $11 per month billed monthly; Expert $11 per month billed annually, or $14 per month billed monthly; Connect $16 per user per month billed annually, or $20 per user per month billed monthly. No free tier, 30-day trial with no credit card
ActivityWatchLocal record of active apps and window titles, plus tab titles and URLs with browser extensions and coding activity with editor plugins; no AI summaries listedFree
TogglTimers, timesheets, calendar integrations, team reports; Toggl AI answers questions about workspace dataFree plan for up to 3 users; Starter $9 per user per month billed annually, or $12 per user per month billed monthly; Premium $16 per user per month billed annually, or $24 per user per month billed monthly; Enterprise, contact vendor
DayflowRecords the screen at one frame every 10 seconds and has AI write the day into a readable timeline; exports a date range as Markdown$0, MIT licensed; optional Pro plan at $20 a month

As noted at the top, Dayflow is our product. It fits when your problem is recall: you want a written timeline of what you actually did to draft a weekly report from, and you can export a date range as Markdown from Settings → Export and hand it to an assistant, as in our Claude weekly report workflow. It does not fit when the report has to come out of a shared team system, because Dayflow has no team reports, invoicing, payroll approvals or website blocking, and it runs only on macOS 14 or later.

A few more specifics. Full screen recordings and the local timeline are stored on your Mac. Screenshot analysis can run on-device with a local model through Ollama or LM Studio, or you can send selected screenshots to your own cloud provider or to Dayflow Pro; the trade-offs are laid out on our local and cloud processing page. AI summaries can miss or misinterpret work, so check every line before it goes into a report someone else will read.

Where Dayflow is the wrong choice

The bottom line

A status report is a steering tool, not a diary. Lead with the overall status and your asks, write progress as outcomes, keep plans short enough to finish, and turn every problem into a specific request. The PPP structure with a red, amber or green line on top covers almost every situation.

Most bad reports come from bad recall, not bad writing. Build an inventory of the week before you draft, whether from a daily log, your calendar or an app that records your activity, and the report mostly writes itself. To start, copy the weekly status report template and use the same format every week.

Frequently asked questions

What should be included in a status report?

A status report needs five parts: the period it covers, an overall status such as on track, at risk or off track, the progress made against goals, the plan for the next period, and any blockers or decisions you need from the reader. Put the overall status and the biggest ask at the top so a skimming reader sees them first. Everything else is supporting detail.

How long should a weekly status report be?

Short enough to fit on one screen without scrolling. A weekly status report is read by busy people who often skim the first lines and stop. If yours runs long, cut activity that did not change the outcome, merge small items into one line, and move background detail into a linked document. Length signals effort, but readers want clarity, not effort.

What is the difference between a status report and a progress report?

A status report is a recurring snapshot, usually weekly, that covers where things stand right now and what needs attention. A progress report is usually tied to a milestone or the end of a phase and looks back at what was achieved against the original plan. Status reports are about steering. Progress reports are about accounting for a stretch of work that has finished.

What does RAG status mean in a status report?

RAG stands for red, amber and green. Green means the work is on track for its date and scope. Amber means there is a risk that needs watching or a decision soon. Red means the date, scope or budget will slip without intervention. The color is a summary for skimmers, so it should always come with one sentence explaining why it is that color.

How do I remember what I did this week for my status report?

Gather sources before you write: your calendar, closed tickets, merged pull requests, sent messages and any notes you kept. A short daily log written at the end of each day makes Friday much easier. An app that records your activity automatically, such as Timing, ActivityWatch or Dayflow on a Mac, can fill the gaps memory leaves behind.

Can AI write my weekly status report for me?

AI can draft one from a record of your week, and tools such as Timing and Dayflow list AI-generated activity summaries. What AI cannot do well is the judgment: choosing the status color, deciding which risk matters, and phrasing the ask. AI summaries can also miss or misread work, so treat any draft as raw material and check every line before you send it.

Is Dayflow or Toggl better for team status reports?

Toggl is the better choice for team status reports. It has team reports, billable rates and, on its Premium plan, timesheet approvals and profitability reports, and it runs on the web, Mac, Windows and mobile. Dayflow has no team reports and is Mac only. Dayflow helps an individual remember their own week, but it is not a shared reporting system for a team.

Should a status report include hours worked?

Only if the reader needs hours to make a decision, for example a client paying by the hour or a manager tracking a fixed budget. For most internal status reports, hours add noise and invite the wrong conversation about effort instead of outcomes. If you do include them, report them per project or deliverable, not as a daily total.

How often should you send a status report?

Weekly is the usual default for ongoing projects because it is frequent enough to catch problems early and rare enough to show real movement. Send daily updates during incidents, launches or tight deadlines. Executives and clients often prefer biweekly or monthly summaries. Pick a fixed day and stick to it, because a predictable cadence matters more than the exact interval.

Is there a free weekly status report template?

Yes. Dayflow publishes a free weekly status report template on its templates page, built around an overall status line, progress, next steps and blockers. You can copy it into a doc, email or chat message. Any template works as long as it puts the overall status and your asks at the top, keeps each item to one line, and stays the same from week to week.

See where your day actually went

Dayflow is $0 and open source. Full recordings stay on your Mac, with local AI available for on-device analysis.

Download for MacOS macOS 14+ · MIT licensed · no account required