Guide
Record one normal week, sort the time into four to six categories, and compare the totals with what you planned. Apple Screen Time is enough if app totals answer your question. Dayflow (free, our product) writes a readable timeline of what you actually worked on. Timing or Toggl is the better choice if the audit needs to end in billable hours.
A time audit answers one question: where your hours actually went, compared with where you think they went. You record a normal week, sort it into a few buckets and look at the gap. A useful audit ends with one or two concrete changes, such as moving email to the afternoon or dropping a standing meeting.
Audits usually go wrong in one of three ways. Some people log from memory at the end of the day and write down what they meant to do. Others start a timer, forget it for three hours and stop trusting the data. The third group collects a week of app totals, sees a large number next to their browser and has no idea what that number means.
This guide works with pen and paper. Software makes the recording step easier, and we cover the Mac options for that step. Dayflow is our product, so weigh what we say about it with that in mind. The tool details below are a comparison of each vendor’s own documentation as checked on October 4, 2026, and nothing more.
Write one sentence that the audit has to answer. The question decides everything else: the categories, the tool and how much detail you need.
Good questions are narrow. “How much of my week is meetings?” works. “Am I productive?” does not, because no recording can answer it.
Illustration: A product designer suspects that review cycles are eating her week. Her question is “How many hours a week go to design reviews and the revisions that follow them, compared with new design work?” That question tells her she needs to separate two kinds of design time, and that app totals alone will not be enough, because both kinds happen in the same app.
Mistake to avoid: Starting to record before you have a question. You end up with a week of data and no way to decide which numbers matter.
Choose four to six categories, and write down the share of the week you expect each one to take. Those guesses are half the value of the audit. The gap between the guess and the total is what tells you something.
Base the categories on your question, not on your apps. A useful default set:
Add one category for the thing your question is about, and drop any that do not matter to it.
Illustration: A freelance developer guesses 60% coding, 15% client calls, 15% email and Slack and 10% admin. He adds “unpaid fixes” as a fifth category, because his real question is how much time goes to bugs he cannot bill for.
Mistake to avoid: Using too many categories. With twelve buckets, the daily sorting becomes a chore and the weekly totals become hard to read.
You can record by hand, with a timer, or with an automatic recorder. Here are the Mac options for this step. For a wider roundup of Mac time trackers, see our list of the best time tracker for Mac apps.
Paper or a spreadsheet. Every hour or so, write down what you did. It costs nothing and works on any Mac. The weakness is that you will miss stretches, and memory fills the gaps with intentions.
Apple Screen Time (Screen Time vs Dayflow). This is built into macOS and free. Once you turn on App & Website Activity, it reports which apps and websites you used and for how long, how many notifications you got and how often you used your devices, in daily or weekly views. “Share across devices” adds usage from other devices signed in to the same Apple Account. It records nothing until you turn it on, so turn it on before the audit week. Reports stay at the app and website level. Apple’s guide does not describe projects, billing or exports.
Toggl (formerly Toggl Track) (Toggl for Mac). Toggl is built around manual and real-time timers, timesheets and calendar integrations. The vendor also lists automated background tracking and a timeline in the desktop app. The free plan covers up to 3 users and includes timers, focus mode and calendar integrations. Data lives in Toggl’s cloud and syncs across web, desktop and mobile. Timers give you clean, labeled entries if you remember to start and stop them.
RescueTime (RescueTime alternative). RescueTime runs in the background and tracks time in apps and websites automatically. The vendor states it does not collect keystrokes, form input, screenshots or webpage content. Data goes to RescueTime’s cloud to generate reports. The Focus (Solo) plan is $7 a month billed annually ($84) or $9 billed monthly. Paid plans have a 14-day trial, which covers a one-week audit. A free Lite plan exists, but its limits are not described on the pricing page.
Timing (Timing alternative). Timing is Mac only and records time across apps, websites and documents, down to specific URLs and Mail threads. The vendor states that tracked times stay on your Mac unless you opt into sync. It lists AI activity summaries on all plans. There is no free tier. The Professional plan is $9 a month billed annually or $11 billed monthly, and there is a 30-day trial with no credit card required.
Dayflow. Dayflow records the screen at one frame every 10 seconds and has AI write the day into a readable timeline. Full screen recordings and the timeline are stored on your Mac. You choose where the analysis runs: Local AI through Ollama or LM Studio keeps screenshot analysis on-device, or selected screenshots go to your own cloud provider or to Dayflow Pro. The app is $0 and MIT licensed, and Pro is $20 a month. It answers the question app totals cannot: what you were actually doing in that browser. AI summaries can miss or misread work, so check the timeline before you trust the totals. See how automatic time tracking works on a Mac for more on the approach.
How to choose:
Illustration: The designer from Step 1 needs to split review work from new work, and both happen in the same design app and the same browser tabs. App totals would merge them, so she picks a tool that records what was on screen rather than which app was open.
Mistake to avoid: Installing a tool on the first morning of the audit week. You will spend that day configuring it, and the first day’s data will be patchy. Set the tool up a few days early.
Let the recording run for five working days without changing how you work. At the end of each day, write two lines: what you planned to do, and what actually happened. Our daily work log template has a simple layout for this.
The note matters even with an automatic tool. Software can tell you that you spent the afternoon in a spreadsheet. Only you know that the spreadsheet was an unplanned fire drill for a client.
Illustration: On Wednesday, the developer’s note reads: “Planned: finish the checkout refactor. Actual: a production bug ate the afternoon, refactor half done.” On Friday, that note explains a block of unpaid fixes that would otherwise look like ordinary coding.
Mistake to avoid: Cleaning up the week because you know it is being measured. If you skip the news sites on Monday because the recorder is running, the audit measures a week you don’t have. Work the way you normally do.
At the end of the week, assign each block of time to a category and add up the hours. Put three columns side by side: category, guessed share, actual share.
How you get the raw data depends on the tool:
Then read the gaps. The useful findings are the categories where actual and guessed differ the most, and the daily notes that explain why.
Illustration: The designer guessed 30% of her week went to reviews and revisions. Her totals put it at roughly half, and her daily notes show that most of the revision time came after a single recurring review meeting. That is something she can act on.
Mistake to avoid: Treating every minute of browser or chat time as waste. Some of it is research, and some of it is the job. Sort by what the time was for, not by which app it happened in.
If you share the results with a manager or client, the weekly status report template is a reasonable format.
Pick the single biggest gap and make one change aimed at it. Then run a shorter audit, three to five days, a month later and compare.
One change at a time is the point. If you move meetings, block mornings and turn off notifications in the same week, you can’t tell which change helped. Our piece on running a deep work review goes into the follow-up audit in more detail.
Illustration: The designer asks for the recurring review to move to Thursday and for feedback to be batched into one document. A month later, she runs a three-day audit to see whether the revision category shrank.
Mistake to avoid: Making a long list of changes and abandoning it by the second week. A single change that sticks beats five that don’t.
| Approach | Effort | What you get | Cost |
|---|---|---|---|
| Manual (paper or spreadsheet) | High: an entry every hour, plus totaling | Your own labels, with gaps wherever you forgot | $0 |
| Toggl (timer-based) | Medium: start and stop a timer for each task | Clean labeled entries, if you remember the timer | Free plan up to 3 users; Starter $9 per user per month billed annually or $12 billed monthly |
| Apple Screen Time | Very low: turn it on | Daily and weekly app and website totals, no projects | Free, built into macOS |
| RescueTime (automatic) | Low: install and categorize | Background app and website tracking, cloud reports | Focus $7 a month billed annually ($84) or $9 billed monthly; free Lite plan |
| Timing (automatic) | Low: install and assign to projects | App, website and document time on the Mac, stored locally unless you sync | Professional $9 a month billed annually or $11 billed monthly; 30-day trial |
| Dayflow | Low: install and pick a processing mode | An AI-written timeline of what was on screen, exportable as Markdown | $0 (MIT); optional Pro $20 a month; your own provider’s charges if you use one |
Dayflow is our product. This table compares vendor documentation, and each vendor’s own pages are the place to check current details.
Dayflow is built to show you what you did. It is the wrong tool for several audit outcomes:
A time audit is a one-week experiment: write the question, guess the split, record honestly, total, change one thing and check again. The method works on paper. Tools only change how much effort the recording takes and how much detail you get back.
If app totals answer your question, Apple Screen Time is free and already installed. If you need billable hours at the end, Timing or Toggl is the better choice. If the hard part is remembering what you were actually doing inside the browser, the editor and the chat window, Dayflow will write that timeline for you at no cost. More on that use case is in see where your time goes on a Mac.
One normal working week is the usual minimum. A single day is too easy to explain away, and a week captures the meetings, admin and recurring work that repeat. Pick a week without travel, a launch or time off. If your work runs in two-week cycles, record two weeks so both halves of the cycle appear in the totals.
Yes, if your question is about apps and websites. Screen Time is free, built into macOS, and shows daily or weekly usage once App & Website Activity is turned on. Apple's guide does not describe projects or exports, so you will copy the totals into a spreadsheet by hand. It cannot tell you which client or task the time in a browser went to.
Yes. If the audit shows that distraction is the problem and you want software to stop it, RescueTime is the better fit. It lists distraction blocking, focus sessions, goals and alerts. Dayflow has no website blocking. Dayflow can show what the distraction looked like across the day, but it will not prevent the next one. RescueTime's Focus plan is $7 a month billed annually or $9 billed monthly.
Use four to six categories based on the question you want answered, not on the apps you use. A common set is focused work, meetings, communication, admin and breaks. Add one category for the work you care about most, such as writing or client delivery. Too many categories make the totals hard to read and the daily sorting tedious.
Full screen recordings and the timeline stay on your Mac. Where analysis happens depends on the mode you choose. With Local AI through Ollama or LM Studio, screenshot analysis stays on-device. With your own provider or Dayflow Pro, selected screenshots are processed off-device. Under the privacy policy, Pro deletes screenshots after processing and may retain activity data for sync.
Yes. A paper log or spreadsheet costs nothing. Apple Screen Time is free and built in. Toggl has a free plan for up to 3 users with timers. Dayflow is $0 and MIT licensed, with an optional Pro plan at $20 a month. If you use your own cloud AI provider with Dayflow, that provider's charges apply.
Use Timing or Toggl. Timing is Mac only and lists billing status tracking, customizable reports with rounding, and a GrandTotal invoicing integration, depending on the plan. Toggl lists billable rates and team reports on paid plans. Dayflow does not create invoices or billable timesheets, so for a client-billing audit either of those is the stronger pick.
Often it does, at least for the first day or two. That is one reason to run the audit for a full week and to prefer a method that needs little attention, such as automatic recording. Timers are the most likely to distort the result, because starting and stopping them reminds you that you are being measured.
No. Dayflow requires macOS 14 or later. On an older Mac you can still run a time audit with a paper log, a spreadsheet or Apple Screen Time. For other apps, check the system requirements on each vendor's site before you start the audit week, so the week doesn't begin with an install problem.
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