Guide
Keep a running record during the week, turn it into outcomes, and put anything that needs your manager's decision first. A free daily log works for most people. Toggl suits teams that already run timers and shared reports. Timing suits Mac users who want automatic, billing-ready records. ActivityWatch is a free cross-platform activity log. Dayflow writes a readable Mac timeline you can export as Markdown.
You want your manager to read your update in about two minutes and come away knowing three things: what moved, what happens next, and where they need to step in. Most status updates miss that. They get written from memory at the end of the week, so they become a list of activities (“worked on onboarding”, “synced with design”) with the one blocker that needed attention buried halfway down.
This guide fixes both halves of the problem: keeping an accurate record of your work, and turning that record into something your manager can act on. The method works with a notes file and your calendar. Tools only help with the record-keeping step. We cover four of them, including Dayflow, which is our product. Competitor details come from each vendor’s own pages as checked on October 4, 2026. Dayflow details come from its 2.2.0 release.
Ask directly. One short conversation saves months of updates written for the wrong reader. Three questions cover it:
The third question matters most. A manager who forwards your update to their own boss needs project-level outcomes. A manager who uses it to unblock you needs the blockers first and fast.
Illustration: You ask, and your manager says they skim updates on Monday morning before their leadership meeting, mainly to see which launches are at risk. That tells you to send on Friday, lead with risk to dates, and keep everything else to one line.
Mistake to avoid: copying the format a previous manager liked. Different managers read for different things, and an update tuned for the wrong reader gets skimmed and ignored.
Capture as you go. Reconstructing a week on Friday afternoon leaves out the unplanned work, the interruptions and the small fixes, which is often the work that explains why the planned work slipped.
Pick one capture method and make it a habit:
If you want a wider view of the options, our roundup of the best time tracker for Mac picks covers more of them.
One caution for any tracker that records screen or app activity on a work machine: check your employer’s policy first, and decide where the data is processed. Dayflow can analyze screenshots locally, through your own AI provider, or through Dayflow Pro. Our page on local and cloud processing explains what leaves your Mac in each mode.
Illustration: On Wednesday you spend most of the afternoon helping support debug a customer issue. It was never on your plan. Your daily note, or your tracker’s timeline, shows it. Without the record, Friday’s update says the dashboard work “is progressing” and hides the reason it slipped.
Mistake to avoid: collecting so much detail that writing the update means wading through it. You need enough to jog memory and back up claims, not a minute-by-minute log.
Your record is a list of things you did. Your manager wants to know what changed because you did them. Go through the week’s record and, for each item that matters, ask “so what?” until you reach something observable: shipped, decided, unblocked, learned, reduced.
Group small items under the outcome they served. Five separate bug fixes become one line about the release they cleared.
Illustration:
| Activity (from your record) | Outcome (for the update) |
|---|---|
| Three meetings with legal about data retention | Retention policy approved; we can start the export feature |
| Refactored the billing module | Billing changes now take hours instead of days; unblocks Q1 pricing work |
| Wrote tests, fixed four bugs | Release 4.2 cleared QA, ships Tuesday |
Mistake to avoid: keeping effort words like “worked on”, “looked into” or “continued”. They tell your manager you were busy, not where things stand. If something has no outcome yet, say what state it is in: “drafted, waiting on review” is more useful than “worked on the draft”.
Anything that needs your manager to do something. That means decisions you need from them, blockers they can remove, and risks to a date or commitment they care about. Put this section first, even when it is empty. Writing “Needs from you: none” tells them they can relax.
Each item should carry three parts: the fact, the impact, and the specific ask with a deadline.
Illustration: “Needs from you: The vendor contract is still unsigned. Without it, the integration slips from the 14th to at least the 21st. Can you escalate with procurement by Tuesday?”
If you want a rough sense of what a stalled decision costs, the meeting cost calculator can put a number on the extra syncs it creates, which is sometimes the nudge that gets a decision made.
Mistake to avoid: softening a real risk to keep the update positive. A risk flagged early reads as judgment. The same risk surfaced the week of the deadline reads as a surprise, and managers remember surprises.
The same one, every time. A fixed structure means your manager learns where to look and you spend less time deciding what to write. A format that works for most roles:
Keep each item to one line and link to the ticket, doc or pull request for detail. The weekly status report template has this structure ready to copy. For a deeper look at the weekly version specifically, see our guide on how to write a weekly status report.
Illustration:
Needs from you: Decision on whether the export ships with CSV only or CSV and JSON. JSON adds about a week. Need an answer by Wednesday. Done: Release 4.2 cleared QA, ships Tuesday. Retention policy approved by legal. Next: Start export feature. Finish onboarding copy review. Notes: Out Friday afternoon.
If you write the draft with AI from an exported record, the Claude weekly report workflow shows one way to do it. Read every line before sending. AI summaries can miss or misinterpret work, and your name is on the update.
Mistake to avoid: padding “Next” with everything on your list. Put down what you expect to finish. If half of it carries over every week, your manager stops believing the section.
Send at the same time each cycle, in the channel your manager picked. Consistency is a large part of what makes an update useful: your manager can plan around it, and gaps stand out.
Keep every update you send in one place, such as a single running doc or a folder. Over a quarter, that file becomes the raw material for a performance review, a promotion case or a project retrospective. You will not remember March in June without it.
If your team prefers daily async updates over a weekly note, the same structure works at a smaller scale. Our post on automatic standup updates covers the daily version.
Illustration: Your update goes out every Friday by 4 p.m. as a reply in the same Slack thread, so your manager can scroll up and see the last month at a glance. A copy goes into a doc titled “Status updates 2026”.
Mistake to avoid: skipping a week because “nothing happened”. Send the short version: no blockers, what is in progress, what is next. A missed update makes your manager wonder; a short one reassures them.
| Approach | Effort | What you get | Cost |
|---|---|---|---|
| Manual daily note | A minute or two a day; easy to skip on busy days | Whatever you remembered to write down | $0 |
| Toggl (timer-based) | Start and stop timers, or fill in a timesheet | Time per project and task you labeled; billable rates and team reports on paid plans | Free plan for up to 3 users; Starter $9 per user per month billed annually or $12 billed monthly; Premium $16 billed annually or $24 billed monthly |
| Timing (automatic) | Set up projects once, then review | Automatic record of apps, websites and documents on the Mac; AI activity summaries | Professional $9 per month billed annually or $11 billed monthly; no free tier; 30-day trial, no credit card required |
| ActivityWatch (automatic) | Install, add browser extensions | Active app, window titles, URLs with extension, away-from-keyboard time; no AI summaries listed | Free, MPL-2.0 open source |
| Dayflow | Install, choose local or cloud AI processing | A written timeline of your day from a screenshot every 10 seconds; Markdown export | $0, MIT licensed; optional Pro plan at $20 a month |
Disclosure again: Dayflow is our product. It helps with step 2, remembering what you did. It does not write the outcomes, choose your blockers or decide what your manager needs to hear. Those steps are yours whichever tool you use.
Dayflow is a personal memory tool for one person on a Mac. It is the wrong choice in several common cases:
If none of those apply and your problem is simply “I can’t remember what I did”, that is the job Dayflow is built for. For more on that specific problem, see how to remember what you worked on.
A good status update is mostly decided before you start writing. Know what your manager uses it for, keep a record during the week, and the writing becomes a short exercise in turning activity into outcomes and putting the asks first.
For the record-keeping, a daily note costs nothing and works if you keep the habit. Toggl fits teams that already live in timers and shared reports. Timing fits Mac users who bill by the hour and want an automatic record. ActivityWatch is a free, cross-platform activity log. Dayflow fits a single Mac user who wants their day written out for them and exported as text. Whichever you choose, the update itself follows the same structure: needs from you, done, next, notes. Send it on time, every time.
Four parts, in this order: anything that needs your manager's decision or help, what got done this period stated as outcomes, what you plan to do next, and any risks to dates or scope. Leave out routine activity that changed nothing. If a section is empty, write "none" rather than deleting it, so your manager knows you checked.
Short enough to read in about two minutes. For a weekly update that usually means a handful of bullets per section, each one a single line with a link to the ticket, document or pull request for detail. If you need more than a few sentences to explain a problem, flag it in the update and ask for a short call instead.
Whatever cadence your manager asks for, and if they have not said, ask. Weekly is the most common default. Daily written updates make sense for fast-moving projects or async teams that skip standups. Pick a fixed day and time and stick to it, because a predictable update builds more trust than a polished but irregular one.
Record it as you go instead of reconstructing it on Friday. A two-line note at the end of each day is enough. Your calendar, ticket history and commits fill in gaps. If you forget to write notes, an automatic tracker such as Timing, ActivityWatch or Dayflow keeps a record in the background that you can review before writing.
Only if your manager or client asks for them, or if time spent is the point, for example an estimate that is running long or meetings crowding out project work. Most managers care about outcomes and blockers, not minutes. When you do report time, use rough figures from a tracker rather than guesses, and say what the time bought.
AI is useful for turning a raw record into a first draft, but read every line before you send it. Summaries can miss work, mislabel it or overstate it, and your manager will hold you to what the update says. Check your company's policy before pasting work details into any cloud AI tool.
Toggl is the better fit than Dayflow here. It offers billable rates and team reports, with timesheet approvals and profitability reports on the Premium plan, and runs on web, Mac, Windows and mobile. Dayflow has no team reports, invoicing or payroll approvals, so it only helps an individual remember their own day.
Yes. ActivityWatch is free and MPL-2.0 licensed, records the active app, window title and away-from-keyboard time, and stores data on your device, but lists no AI summaries. Dayflow is free and MIT licensed, needs macOS 14 or later, and has AI write your day into a readable timeline. Its optional Pro plan is $20 a month.
State the facts, the impact and the specific thing you need. For example: the API spec is still unapproved, the integration slips past Thursday without it, and you need a decision by Tuesday on which version to build against. A clear ask with a deadline reads as ownership, not complaint.
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