Guide
Pull the full time record for the period, group it by deliverable, then write done, in progress, next and blockers, with hours against budget. Harvest wins if you also invoice from those hours; Toggl suits teams on timers; Timing suits Mac users who want an automatic billable record; Dayflow, free and open source, suits people who forget timers and want a readable daily timeline to draft from.
A good client status report answers three questions in under a minute of reading. What did my money buy this period? What happens next? Is anything at risk? Your tracked hours are the evidence for those answers. They are not the answers.
The report usually goes wrong late on a Friday afternoon. You open your timesheet, see “Client A - 11.5h” next to a few vague entries, and try to remember what those hours were. What comes out is either a raw dump of hours the client can’t interpret or a paragraph of reassurance with nothing behind it. Both get the same reply: “Can you tell me what’s actually done?”
This guide gives you a method that works with any time record, even a paper log. One of the options for collecting that record is Dayflow, which is our product. The tool details here come from each vendor’s own documentation as published on October 4, 2026, and Dayflow’s details come from version 2.2.0. That comparison of documentation is the whole method. We did not test these tools hands-on.
If you don’t track time yet, the tools fall into two groups. Timers record what you start and stop. Automatic trackers record in the background. Our comparison of Mac time trackers covers both, and automatic time tracking on a Mac explains how the background approach works.
Internal reports to your own team follow a different shape. For those, see how to write a weekly status report.
What to do. First pick the period. Weekly suits an active retainer. Every two weeks or at each milestone suits slower work. Then ask the client once what they want from the report, and write the answer down.
Most clients want three things:
Some want hours itemized. Others never look past the first line.
Illustration. Suppose you have a design retainer of 40 hours a month. Your contact is a marketing lead who forwards your report to her boss. What she needs is a top line she can paste as-is: “Landing page v2 shipped, pricing page in review, 26 of 40 hours used.” Knowing that shapes everything below it.
Mistake to avoid. Don’t write the report you would want to read, such as a detailed technical log, when the reader needs something to forward. If someone has to translate the report before passing it up the chain, it isn’t finished.
What to do. Open or export the full record for exactly the reporting period. Then scan it for the usual gaps: forgotten timers, meetings, calls and email.
What you get depends on how you track.
Timer apps. Harvest and Toggl (formerly Toggl Track) give you the entries you created (Toggl on a Mac compared).
Automatic trackers. Timing (Timing compared) and Memtime (Memtime compared) record apps, documents and websites in the background, so gaps are rarer.
Dayflow. Dayflow captures one frame of your screen every 10 seconds and has AI write the day as a timeline in plain sentences. You can export any date range as Markdown from Settings → Export. That export is close to a first draft of “what happened,” but it is not a set of billable entries.
By hand. Combine your calendar, sent mail, commit history and notes. It’s slow, but it works. The daily work log template makes next period easier.
Illustration. Your Toggl entries show 9 hours for the client from Tuesday to Thursday. Your calendar also shows a 90-minute workshop with them on Wednesday that never got a timer. Add it before you group anything.
Mistake to avoid. Don’t patch gaps from memory with round numbers. If you can’t find evidence for a block of time, mark it as an estimate or leave it out. Invented hours are the ones a client is most likely to question. If you often can’t reconstruct your week, remembering what you worked on covers ways to fix that habit.
What to do. Regroup every entry under the deliverables named in the scope.
Illustration. A month of entries for the design retainer might regroup like this:
| Deliverable | Hours | Status |
|---|---|---|
| Landing page v2 | 14.0 | Shipped |
| Pricing page | 8.5 | In client review |
| Analytics setup | 2.0 | Blocked on access |
| Calls and coordination | 3.5 | Ongoing |
Mistake to avoid. Don’t report by app or activity. “Figma 9h, Slack 4h” tells a client nothing about what they bought. If coordination is a large share of the month, raise it as a finding rather than hiding it inside a deliverable. The meeting cost calculator helps you put a number on it when you do.
What to do. Write four short blocks: Done, In progress, Next, and Needs your input.
Illustration.
Mistake to avoid. Don’t soften blockers or bury them at the bottom. “Analytics may be delayed” gets ignored. “Analytics slips to the 24th unless we get access by Tuesday” gets answered.
If you work from an automatic timeline such as a Dayflow export, don’t paste its sentences in as they are. A timeline describes what was on your screen, not what the client received. Use it to jog your memory and confirm dates. If you want an assistant to draft from the export, the Claude weekly report workflow shows one way to set it up.
What to do. Write one line of totals: hours this period, hours to date, the budget or estimate, and what remains. If a deliverable ran noticeably over or under, add one sentence on why and what you’ll do about it. For hourly clients, attach the itemized log or invoice detail separately rather than putting it in the body.
Illustration. “This month: 28 of 40 retainer hours used. The pricing page took 8.5 hours against an estimate of 5 because of the extra review round. We’ll still finish within the 40.”
Mistake to avoid. Don’t round one way in the report and another way on the invoice. The hours in your status report must match what you bill.
Whichever you use, apply the same rounding rule to both documents. If you keep going over estimate, the real hourly rate calculator shows what that does to your effective rate.
What to do.
Illustration. Your export for the week includes “reviewed Northwind contract in browser” inside a block you assigned to a different client. That line belongs elsewhere and must not appear. In the same export, the summary called an afternoon “pricing research” when it was a competitor teardown the client asked for. Fix the wording so it matches what you delivered.
Mistake to avoid. Don’t trust any automated summary without checking it. Dayflow’s own documentation says its AI summaries can miss or misinterpret work, and the same caution applies to any tool that summarizes for you. Also remember that pasting an export into a cloud assistant sends that data to the assistant. Strip other clients’ details before you paste, not after.
| Approach | Effort | What you get | Cost |
|---|---|---|---|
| Manual (calendar, notes, sent mail) | High, every period | A record only as complete as your memory and notes | $0 |
| Harvest (timer) | Low per entry, but you must start timers | Time entries, reports and invoices from tracked time | Free for 1 seat and 2 projects; Teams $9 seat/month billed annually or $11 billed monthly; 30-day trial |
| Toggl (timer) | Low per entry, but you must start timers | Time entries, billable rates on paid plans, team reports | Free for up to 3 users; Starter $9 per user/month billed annually or $12 billed monthly; 30-day trial |
| Timing (automatic, Mac) | Low capture, some time assigning activity to projects | Automatic app and document record, reports with rounding, AI activity summaries | No free tier; Professional $9 per month billed annually or $11 billed monthly; 30-day trial |
| Memtime (automatic) | Low capture, some time turning the timeline into entries | Automatic timeline stored on your device, custom reports | No free tier; Basic $14 per user/month billed annually, $18 billed quarterly, $12 billed 2-yearly; 14-day trial |
| Dayflow (automatic, Mac) | Low capture, review before sharing | A plain-language daily timeline, exportable as Markdown | $0, MIT licensed; optional Pro at $20 a month |
Since Dayflow is our product, weigh our description of it with that in mind.
The details of each processing mode are on local and cloud processing.
A client status report is a short, verifiable account of outcomes, with hours as supporting evidence. Pull the whole record, group it by deliverable, write done, in progress, next and blockers, then check every line before you send it.
The tool only changes how complete your record is when you start. Harvest and Toggl work if you reliably start timers, and Harvest is the clear choice if you also invoice. Timing and Memtime fill gaps automatically for billable work. Dayflow is a free way to get a readable account of each day on a Mac, which you can draft from as long as you check it first.
A one-line summary, what was finished, what is in progress, what comes next, anything blocked or waiting on the client's decision, and hours used against the budget or estimate. Write each item as an outcome the client can check, such as a link, a file or a decision. Itemized time entries belong in an appendix or on the invoice, not in the main body of the report.
Match the pace of the work. Weekly suits active retainers and projects with deadlines inside a month. Every two weeks or at each milestone suits slower engagements. Whatever you pick, send it on the same day every time. A predictable report builds more trust than a detailed but irregular one, and it stops the client from chasing you for updates.
Harvest covers the time and money side: tracked hours by project, team reporting, profitability reporting on Enterprise, and invoices built from tracked time. It lists no AI features, so the written account of what got done is yours to add. The free plan covers 1 seat and 2 projects, and Teams costs $9 per seat per month billed annually or $11 billed monthly.
No, and Harvest beats it there. Dayflow has no invoicing, payroll approvals or team reports. It writes your day into a readable timeline you can export as Markdown. If you need invoices built from tracked hours, with expense tracking and online payments, Harvest does that, including on its free plan for 1 seat and 2 projects. Some people use Dayflow to remember the work and Harvest to bill it.
Filter your Toggl entries to the client and the reporting period. Then regroup them under the deliverables in your scope instead of reporting entry by entry, and check your calendar for meetings you didn't time. Billable rates need a paid plan: Starter is $9 per user per month billed annually or $12 billed monthly. Toggl AI answers questions about workspace data, but check its answers before quoting them.
Yes, if you want an automatic record. Timing tracks apps, websites and documents on the Mac. It lists customizable reports with rounding, billing status tracking and AI activity summaries. It is Mac only and has no free tier. Professional costs $9 per month billed annually or $11 billed monthly, and the trial runs 30 days with no credit card required.
Memtime runs on Mac, Windows and Linux. It records time in programs, documents, emails, calls and browser tabs, and the vendor states that recorded activity stays on your device. Basic costs $14 per user per month billed annually, $18 billed quarterly or $12 billed 2-yearly, and there is no monthly option. Dayflow and Timing are Mac only, so of the tools covered here, Memtime is the Windows pick.
AI can produce a draft, but don't send the draft unedited. Timing's AI activity summaries or a Dayflow Markdown export pasted into an assistant give you a starting point. AI summaries can miss or misinterpret work. A cloud assistant also receives whatever you paste into it, so remove other clients' details first and check every claim against your own record.
Keep it short enough to read in a minute. That usually means a summary line, three to eight bullet points across done, in progress, next and blockers, and one line of hours against budget. If the client wants detail, attach the time log separately. Clients skim long reports, and the blocker you needed them to answer gets skimmed with everything else.
Only if the contract is hourly or the client asks. Retainer and fixed-price clients usually want progress and remaining budget, not a per-task breakdown. When a task ran well over its estimate, say so in one sentence with the reason, because the client will see it on the invoice anyway. Make sure any figure you quote uses the same rounding rule as your invoice.
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