Guide
Track one ordinary week. Write your guess first, then log a line every 30 minutes with a kitchen timer and paper, tally unplanned switches, and sort the lines on Friday. Paper wins if you want zero setup or work away from a screen. Dayflow, a free Mac app, wins if you keep forgetting to log, since it records your screen and writes the timeline for you.
It is late Thursday afternoon. You sat down in the morning with a clear list, and the list is mostly still there. You were not idle. You answered messages, joined two calls, and fixed a small problem that turned out not to be small. You opened a tab to check one fact and came back to your real work much later than you meant to.
When someone asks what you did today, the honest answer is a shrug and a few nouns. The day happened, and it was full, but you cannot account for it. That gap between feeling busy and knowing where the hours went is what this guide is about.
What follows is a one-week plan to find out where your time actually goes. Almost all of it uses paper, a kitchen timer, your calendar, and one other person. Near the end there is a short section on software that records the day for you. That software is Dayflow, which is our product and the publisher of this blog. Weigh that section with that in mind, and read the section after it, which covers when Dayflow is the wrong choice.
Memory keeps a highlight reel, not a recording. You remember the meeting that went badly and the task you finished. You do not remember the eleven small detours between them, because nothing about a detour asks to be remembered.
Small things do not feel like time. Replying to one message takes a minute. Checking one dashboard takes a minute. Each one is too short to register as a choice. Together they can take a large share of a day, and they leave almost no trace you can point to afterward.
Switching has a hidden cost. Many people find that getting back into a piece of work after an interruption takes longer than the interruption itself. You read the last paragraph again, reopen the files, and remember where you were. That re-entry time almost never gets counted, because it does not feel like a separate activity.
Reactive work leaves no artifact. A finished report is visible. An afternoon of answering questions, unblocking a colleague, and tidying a shared doc is real work, but at five o’clock it looks like nothing happened.
Calendars show the scheduled parts only. Your calendar tells you about the meetings. The blank spaces between them look like free time, but they are where most of the unaccounted hours live.
Most people’s sense of how long things take is rough. That is not a flaw in you. It is just how attention works when you are busy. It is also why the fix is to look rather than to try harder at remembering.
Start with a guess, before you track anything. This step is the one people skip, and it is the one that makes the rest of the week interesting.
What to do: On a sheet of paper, list the main kinds of work you do and write down roughly how many hours a week you think each takes. Do not look at your calendar. Write what you believe, then fold the paper and put it somewhere you will find it on Friday. If you want a quick warm-up first, the time estimation test is a short exercise that compares your sense of time with a clock. It is a curiosity, not a diagnostic.
Illustration: A product designer might write: design work 20 hours, meetings 8, feedback and reviews 5, email and chat 4, admin 3.
After a week: You will know this step worked if you feel a small jolt when you unfold the paper. Even a modest gap between the guess and the log tells you which parts of your week are invisible to you.
This is the core of the week. You need a notebook, a pen, and a kitchen timer or any timer that rings.
What to do: Set the timer for 30 minutes. When it rings, write one line about what you were doing just before it rang, then reset it. Keep the line short and honest: “Slack thread about launch date” is better than “communication.” If you missed a ring, write “missed” and move on. Do not reconstruct it from memory, because memory is the thing you are testing. A printable daily work log works well if you want ruled columns instead of a blank page.
Illustration: Part of one person’s Tuesday might read: “9:30 drafting proposal. 10:00 drafting proposal. 10:30 email, then back to proposal. 11:00 call ran over. 11:30 looking for the old contract. 12:00 still looking for the contract.”
After a week: It is working if you have most of five days covered and the lines are specific. If you have a full Monday and nothing after Tuesday, the interval is too short or the timer is too easy to ignore. Move it to 45 minutes, or put it somewhere you have to stand up to reach.
A log of tasks can make a choppy day look smooth. “10:00 to 12:00 writing” hides the fact that you got pulled away six times.
What to do: Next to your log, keep a running tally. Every time you switch to something you did not plan, such as a message, a question from someone nearby, or a sudden urge to check something, make one mark. You do not need to note what it was. Just mark it.
Illustration: Someone might find their Monday morning has two marks and their Wednesday afternoon has fourteen. The log for both says “writing,” but the tally shows they were very different blocks of time.
After a week: You should be able to name the time of day when your switches cluster, and probably what causes them. If the tally feels like too much bookkeeping, keep it for only two days. Even a partial count tends to show where the choppy hours are.
Your calendar is already a partial time log. Most people never read it backward.
What to do: Open last week’s calendar and go through it with a highlighter or a colored pen on a printout. Mark meetings in one color, the time right before and after meetings in another, and long open blocks in a third. Then ask a plain question about each open block: what actually happened there? If meetings are a big share of your week, the meeting cost calculator can put a rough number on a recurring one.
Illustration: A team lead might notice that a free hour between two calls almost never becomes focused work. It turns into prep for the second call and follow-up from the first.
After a week: Compare this calendar reading with your paper log. You will know it helped if you can point to at least one kind of block that looks open on the calendar but reliably gets eaten by something else.
Saying your day out loud is a surprisingly strong check on memory. It also makes the week easier to stick with, because someone is expecting you.
What to do: Find one person, such as a friend, a partner, or a colleague doing the same exercise, and agree to send each other two or three lines at the end of each workday: what took the most time, what you did not expect, and what got pushed. Write it before you look at your log, then check it against the log.
Illustration: A freelancer texts a friend: “Most of today was client revisions. Didn’t expect the invoicing mess. Pushed the website work again.” The log then shows the invoicing mess took longer than the revisions.
After a week: It is working if the gap between what you report and what you logged starts to shrink by Thursday. That means you are paying closer attention as the day goes, which is half of what this week is for.
Friday is when the week pays off. Set aside half an hour with your log, your tally, and the folded guess.
What to do: Read every line once without judging it. Then sort the lines into four to six buckets that fit what you actually did. Choose the buckets now, not at the start of the week, so the categories match reality instead of forcing reality into them. Count the lines in each bucket, multiply by your interval, and write the totals next to your guess. If you would rather plug in numbers than add them up by hand, the where does my week go calculator does the arithmetic. For a longer, more structured version of this review, there is a full guide on how to do a time audit on a Mac.
Illustration: A developer guessed four hours a week on code review and finds about twice that in the log, mostly in small pieces after lunch. That is the one thing to work on next week, not the five other small surprises.
After a week: The test is simple. Can you finish the sentence “Most of my week went to ___, and I thought it was ___”? If you can, the week did its job. Pick one change, try it for a week, and log again to see whether it moved.
A paper log has one weak spot: it only knows what you remembered to write. On busy days the timer rings during a call, you skip it, and the gap gets filled in from memory later, which is the exact thing you were trying to avoid. If you have ever ended a day asking where did my day go, that gap is usually why.
An automatic record removes the remembering. Dayflow runs on Macs with macOS 14 or later. It records your screen, keeps the recordings and a local timeline on your Mac, and has AI write the day into a readable timeline you can check against your Friday sort. You choose where analysis happens: Local AI through Ollama or LM Studio keeps screenshot analysis on-device, while your own cloud provider or Dayflow Pro processes selected screenshots off-device. The local and cloud processing page explains the difference. The app costs $0 and is MIT licensed, with an optional Pro plan at $20 a month. You can export a date range as Markdown from Settings, then Export. AI summaries can miss or misread work, so treat the timeline as a draft.
Other Mac time trackers take different approaches. These Dayflow details come from its own documentation for version 2.2.0, reviewed September 6, 2026. Dayflow publishes this blog, and the app is our product.
You are not on a Mac. Dayflow is Mac only and needs macOS 14 or later. On Windows, Linux, or an older Mac, the paper log above is the better tool, and it is free.
Much of your work happens away from the screen. Dayflow sees only what is on your Mac’s screen. Meetings in a room, calls on your phone, thinking on a walk, and time spent with people do not show up. If that is a big part of your day, paper wins.
You want the writing itself. For some people, stopping every 30 minutes to write a line is what builds awareness. An automatic record skips that step. If the habit is the point, use the notebook.
You want something to change your behavior. Dayflow is a record, not a coach, a blocker, or a treatment. It does not provide website blocking, and seeing your day does not by itself make the day different. If you want to stop visiting certain sites, a blocker is the right tool.
You need billing or team features. Dayflow does not provide invoices, payroll approvals, or team reports. If you track time to bill clients, a time tracker for Mac with invoicing built in will serve you better.
Screen recording feels wrong to you. That is a reasonable line to draw. The one-week paper method gets you most of the answer without recording anything.
Your time is not disappearing. It is going into small, reactive, unremembered pieces that memory is not built to keep. The way to see them is to look for one ordinary week: write your guess, log a line every 30 minutes, tally the switches, read your calendar backward, tell someone about your day, and sort it all on Friday.
Most people can do every part of that with a notebook and a timer. If you work on a Mac and keep forgetting to log, an automatic record like Dayflow can fill the gaps. Either way, the goal is the same. Finish the week able to say where your time went, then change one thing and look again.
Keep a simple log for one ordinary week. Write down what you expect your week to look like, then record one line about what you are doing at regular intervals, such as every 30 minutes. On Friday, group the lines into a few buckets and compare them with your guess. The gap between the two is usually where the useful answer is.
One full working week is a good start because it covers different kinds of days: heavy meeting days, quiet days, and the day something breaks. A single day is easy to dismiss as unusual. If your work runs in longer cycles, like a monthly deadline, track a second week later in the cycle and compare the two.
Yes. A notebook, a pen, and a kitchen timer are enough. Set the timer for 30 minutes, write one short line when it rings about what you were just doing, and reset it. Paper has no setup, works away from a computer, and makes you notice your day as it happens, which is part of the point.
Every 30 minutes is a workable default for most people. Every hour is easier to keep up but tends to blur several things into one line. Every 15 minutes gives more detail but can get tiring by Wednesday. Pick an interval you can sustain for five days, since a complete week at a coarse interval beats a detailed Monday and nothing after.
Many people find their days fill with small, reactive work: replies, quick questions, short fixes, and the time it takes to get back into a task after each one. None of it feels big enough to count, and most of it leaves nothing you can point to later. A week of logging usually shows how much of the day these pieces take.
Decide them after the week, not before. Read through your lines and sort them into four to six buckets that fit your actual work, such as focused work, meetings, messages, admin, and unplanned. Choosing categories first tends to force messy real activity into neat boxes and hides the very thing you were trying to see.
For some people, yes. If you use Windows, work mostly away from a screen, or want the act of writing to make you more aware of your day, a paper log is the better tool. Dayflow only runs on Macs with macOS 14 or later and only sees what is on your screen. It is most useful when you keep forgetting to log.
No. Dayflow does not provide invoices, payroll approvals, team reports, or website blocking. It is a record of what was on your screen, written up as a timeline. If you need to bill clients, a dedicated time tracker with invoicing is the better choice. If you want to stop visiting certain sites, use a blocker instead.
Recordings and the local timeline are stored on your Mac. With Local AI, screenshot analysis stays on-device through Ollama or LM Studio. If you choose your own cloud provider or Dayflow Pro, selected screenshots are processed off-device. Under the privacy policy, Dayflow Pro deletes screenshots after processing and may retain Activity Data for sync.
Change one thing. Look for the single biggest gap between your guess and what you logged, and run a small experiment against it for the next week, such as batching messages twice a day or protecting one morning block. Then log again and compare. Changing five things at once makes it hard to tell what helped.
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