How to Stop Losing Track of Time While Working on a Mac

Move timekeeping out of your head. Use a visible timer for each work block, write a one-line checkpoint when the block ends, and keep a passive record to compare against. Apple Screen Time is the free, built-in starting point. Timing wins for billable hours with local data, RescueTime for distraction blocking, Rize for Windows users, and Dayflow for a readable AI-written timeline at $0.

You sit down at 9:30 to answer two emails. The next time you look up it’s 11:15, the emails are half done and you have a pull request open that you don’t remember starting. You want to notice time passing while you work, and at the end of the day you want an accurate record of where it went.

Most people try willpower first: “I’ll check the clock more often.” That rarely works, because you lose track of time exactly when you aren’t thinking about the clock. The method below takes the job out of your head. Something outside you keeps time, and something outside you keeps the record.

Disclosure: Dayflow is our product. It’s one way to handle the record-keeping step, and every step here works without it. The tool details come from a comparison of vendor documentation as published on October 4, 2026.

If the problem feels bigger than a busy schedule, our guide to losing track of time with ADHD covers that angle. Neither guide makes medical claims.

The short version

1. Measure how far your sense of time drifts from the clock.
2. Turn on a passive record of your Mac use before you change anything.
3. Work in timed blocks with a timer you can see.
4. Write a one-line checkpoint when a block ends or you switch tasks.
5. Close each day by comparing your notes with the record.
6. Once a week, find the biggest gap and change one thing.

What you need before you start

• Your Mac and a visible timer. A phone on a stand, a menu bar timer or a kitchen timer on the desk all work. Whatever you use has to stay visible and can’t end up behind a window.
• One place for short notes. A plain text file is enough to start with.
• A passive recorder. The free option is Apple Screen Time, which is built into macOS. Step 2 covers the alternatives, and we wrote up how it differs from our app in Screen Time vs Dayflow.
• Ten minutes at the end of each workday. Put it on your calendar, or it won’t happen.

Step 1: How far off is your sense of time?

What to do: Before you start each of three tasks tomorrow, write down how long you think it will take. Note the start time. When you finish, note the end time. Compare.

For a quicker version, the time estimation test is a short exercise that compares your sense of time with a clock. It’s not a diagnostic. It just shows whether you tend to guess long or short.

Illustration: Say you estimate “reply to the client thread: 15 minutes,” “update the deck: 30 minutes” and “fix the login bug: 1 hour.” The clock shows 40 minutes, 35 minutes and 2.5 hours. That tells you something specific. Estimates for small communication tasks and debugging run long, while design work is close. Now you know where to put your checkpoints.

Mistake to avoid: Estimating after the fact. “That probably took about an hour” is the same faulty sense of time you are trying to measure. Write the estimate down before you start, or the exercise tells you nothing.

Step 2: How do you record your time without doing extra work?

What to do: Turn on something that records your Mac use passively. Do this before you change any habits, so you get a fair baseline.

The free starting point is Apple Screen Time. Open System Settings, go to Screen Time and turn on App & Website Activity. It records nothing until you do. After that it shows which apps and websites you used and for how long, how many notifications you received and how often you used your devices, in daily or weekly views. With “Share across devices” on, it also includes time from other devices signed in to the same Apple Account.

Screen Time’s limit is detail. It reports at the app and website level, and Apple’s documentation doesn’t describe projects, billing or exports. “4 hours in Safari” doesn’t tell you which client, or whether that was research or drifting.

If you want more detail, an automatic time tracker for Mac fills the gap, and that roundup compares the options in depth. Here are the main ones, according to each vendor’s documentation:

• Timing is Mac only. It records apps, websites and documents automatically, down to specific URLs and Mail threads. The vendor says tracked times are stored locally and never leave your Mac unless you opt into sync. It has no free tier but offers a 30-day trial with no credit card required. See Timing vs Dayflow.
• Rize runs on Mac and Windows. It tracks apps and websites automatically, uses AI to categorize and tag them, and can connect Google Calendar to capture meeting time. Data is hosted on Amazon Web Services. It has no free tier and offers a 7-day trial. See Rize vs Dayflow.
• RescueTime runs in the background and tracks apps and websites. The vendor states it doesn’t collect keystrokes, form input, screenshots or webpage content. Activity data is sent to RescueTime to generate reports. Paid plans come with a 14-day trial. See RescueTime vs Dayflow.
• Dayflow takes a different approach. It records the screen at one frame every 10 seconds, and AI writes the day into a readable timeline. Recordings and the timeline are stored on your Mac. With local AI through Ollama or LM Studio, screenshot analysis stays on-device. If you choose your own cloud provider or Dayflow Pro, selected screenshots are processed off-device. The local and cloud processing page explains the trade-offs.

Illustration: After three days, Screen Time might show Slack as your top app. That number alone doesn’t help you. A tracker with document or URL detail could show that most of the Slack time came in short visits during your planned writing block. That gives you something you can act on.

Mistake to avoid: Switching tools every few days. Pick one recorder, leave it running for a full week and judge it only after that. A recorder you keep swapping produces no baseline at all.

Step 3: How do you make time visible while you work?

What to do: Break the day into blocks with a defined length and a defined task, and run a timer you can see for each one. Start with 45 to 60 minutes, which is long enough for real work and short enough that drifting off course can’t eat a whole morning. Put the block on your calendar with the task in the title.

If distraction is what ends your focus, add a blocking layer. RescueTime lists focus sessions, distraction blocking, goals and alerts. Screen Time offers downtime schedules, time allowances for app categories and blocking of content and features, at no cost.

Illustration: Your 10:00 calendar block reads “Draft Q4 proposal, sections 1-2.” A timer on a phone stand next to the monitor counts down 50 minutes. At 10:35 you catch yourself in a browser tab about keyboard switches. The visible countdown says 15 minutes left, which is enough of a cue to close the tab.

Mistake to avoid: A timer you can’t see. A countdown hidden behind three windows only tells you time passed after it’s over. Blocks that are too long, such as three hours, cause the same problem, because drifting halfway through still costs you an hour before the timer catches it.

Step 4: What should you do when a block ends or you switch tasks?

What to do: Write one line, every time. Use the format “Done: X. Next: Y.” Do it when the timer goes off, when a meeting ends, when you close a pull request and whenever you notice you’ve switched tasks without deciding to.

A transition is when time usually gets lost. You finish one thing, open your email “for a second,” and the next task never really starts. A one-line checkpoint makes you decide what comes next, so it doesn’t happen by default.

Illustration:

• 10:50 Done: proposal sections 1-2 drafted. Next: 10 min break, then reply to Maya.
• 11:15 Done: replied to Maya. Next: login bug, 60 min block.
• 12:40 Noticed I was in the analytics dashboard for 20 min. Next: back to the login bug.

The third line matters most. It records a drift and also ends it.

Mistake to avoid: Turning the checkpoint into a planning session. If the line takes more than a minute to write, you’ve created a new way to lose time. Keep it to one line and avoid rewriting your to-do list.

Step 5: How do you close the day so you know where the time went?

What to do: At the end of the day, open your checkpoint lines next to your passive record. Fill in the daily work log template with what you got done, where the record and your notes disagree, and the first block for tomorrow. Ten minutes is enough.

How you fill in the gaps depends on your recorder. With Screen Time, you match app totals to your notes and estimate the rest. With Timing or Rize, you review time that’s already categorized. With Dayflow, you read the AI-written timeline of the day, correct anything it got wrong and export a date range as Markdown from Settings → Export if you want to keep it with your notes. AI summaries can miss or misinterpret work, so check the timeline before relying on it or sharing it. If your end-of-day problem is remembering what you did, see how to remember what you worked on.

Illustration: Your notes say the login bug took 60 minutes. The record shows you returned to it at 3:10 and stayed until 4:30, which you never logged. That bug ended up taking about two and a half hours, the same pattern you saw with debugging in Step 1. Write it down so tomorrow’s estimate accounts for it.

Mistake to avoid: Logging what you meant to do instead of what happened. The log is useful only when it disagrees with your plan. If every day matches the plan exactly, you’re writing the plan down again.

Step 6: How do you use a week of records to change something?

What to do: Once a week, read your five daily logs and find the single biggest gap between your plan and what happened. Change one thing about how you plan the next week. The where does my week go calculator helps you sketch hours by category. For a deeper version of this review, follow how to do a time audit on a Mac.

Illustration: Friday’s review shows debugging ran over every day, and none of the overrun was in your notes. The change is to schedule debugging as 90-minute blocks with a checkpoint at 45 minutes, and to leave the rest of the week alone.

Mistake to avoid: Changing five things at once. If you shorten blocks, add a blocker, switch trackers and move your meetings in the same week, you won’t know which change helped. Change one thing per week.

Doing it by hand vs with a tool

Approach	Effort	What you get	Cost
Manual (kitchen timer + paper or text log)	High. You write every entry	Only what you remember to note	$0
Apple Screen Time	Low. Turn it on once	App and website totals, daily or weekly; downtime and app limits	Free, built into macOS
RescueTime (focus sessions + tracking)	Low to medium	Background app and website tracking, focus sessions, distraction blocking, goals	Focus: $7/month billed annually ($84) or $9/month billed monthly. A free Lite plan exists, but its limits are not described on the vendor’s pricing page
Timing	Low	Apps, websites and documents tracked automatically, billing-oriented reports, stored locally unless you sync	Professional: $9 per month billed annually or $11 per month billed monthly
Rize	Low	AI-categorized app and website time, calendar meetings, cloud-hosted data, Mac and Windows	Basic: $9.99/mo billed annually or $12.99/month billed monthly
Dayflow	Low	A readable AI-written timeline from one screen frame every 10 seconds, stored on your Mac, Markdown export	$0, MIT licensed; optional Pro at $20 a month

To repeat the disclosure: Dayflow is ours. The table summarizes what each vendor documents, not how any tool performed on a particular Mac. Higher plans exist for Rize, RescueTime and Timing, and the vendor pages list what each one adds.

Common mistakes

• Starting with a tool instead of a habit. A tracker records the drift but doesn’t interrupt it. The timer and the checkpoint do that work.
• Judging the record too early. Day one always looks bad. Wait for a week of data before you change anything.
• Treating every gap as a failure. A 40-minute detour that solved a problem was work, even if it wasn’t planned. Log it honestly and move on.
• Hiding the timer. If you can’t see it without switching windows, it won’t help when your attention has drifted.
• Skipping the end-of-day close. Without the daily log, the record just fills up and nobody reads it.
• Picking a cloud tool without checking where data goes. Rize and RescueTime process data in the cloud. Timing keeps tracked time on your Mac unless you opt into sync. Dayflow stores recordings on your Mac, though its cloud analysis modes send selected screenshots off-device. If that matters for client work, check before you install, and read time tracking without surveillance.

Where Dayflow is the wrong pick

Dayflow handles one part of this method: a readable record of your day. It’s the wrong choice in several situations:

• You bill clients by the hour. Dayflow has no invoicing or payroll approvals. Timing documents billing status tracking, report rounding and GrandTotal invoicing integration, depending on plan. Pick Timing.
• You want to be stopped while drifting. Dayflow has no website blocking. RescueTime lists distraction blocking and focus sessions. Screen Time offers downtime and app limits for free.
• You work on Windows too. Dayflow runs only on macOS 14 or later. Rize supports Mac and Windows.
• You manage a team. Dayflow has no team reports. Rize, RescueTime and Timing all have team plans.
• You’re on an older macOS version or don’t want screen frames recorded at all. Screen Time is built in and records app and website use, not screenshots. RescueTime says it doesn’t collect screenshots.
• App totals are enough for you. If “how long was I in Slack” answers your question, Screen Time is already on your Mac and costs nothing.

The bottom line

You stop losing track of time by moving timekeeping out of your head. Measure your drift once. Turn on a passive record. Work in blocks with a visible timer. Write a one-line checkpoint at every transition. Close each day with a short log, and change one thing a week.

For the recorder, start with Apple Screen Time because it’s free and already installed. Move to Timing if you bill by the hour and want local data, RescueTime if you want blocking, or Rize if you also work on Windows. Choose Dayflow if you want a written, readable timeline of your day for $0, with the option to keep the analysis on your Mac.

Frequently asked questions

Why do I lose track of time when I'm focused on work?

Focused work pulls your attention away from the clock, and the clock is the only thing that would remind you time is passing. That is normal, not a character flaw. The practical fix is to stop relying on noticing. Use a timer you can see, set a planned stopping point for each block, and keep a record you can check later. Then outside cues do the noticing for you.

Is Apple Screen Time enough to track work time on a Mac?

For a first look, often yes. Screen Time is free and built into macOS. Once App & Website Activity is on, it shows which apps and websites you used and for how long, in daily or weekly views. It reports at the app and website level, though. Apple's documentation does not describe projects, billing or exports, so it cannot tell you which task or client the time went to.

What is the best free way to stop losing track of time on a Mac?

Combine free pieces. Use a visible timer for work blocks, a text file or a daily log template for checkpoints, and Apple Screen Time for app totals. If you want a written timeline instead of app totals, Dayflow is free and MIT licensed, runs on macOS 14 or later, and can keep screenshot analysis on your Mac with local AI through Ollama or LM Studio.

How often should I check the time while working?

Skip the scheduled glances. Set a block length before you start, such as 45 or 60 minutes, and let a visible timer end the block. When it ends, write one line about what you finished and what comes next. Add a checkpoint whenever you switch tasks, too. Constant clock-watching breaks focus, while a fixed stopping point gives you a check-in without interruptions.

Does Dayflow block distracting websites?

No. Dayflow has no website blocking, and here another tool beats it. RescueTime lists distraction blocking and focus sessions on its Focus plan. Apple Screen Time is free and offers downtime schedules, time allowances for app categories and blocking of content and features. If the problem is drifting into specific sites, pick one of those. Dayflow tells you where the time went afterward. It does not stop you mid-drift.

Which tracker is best if I bill clients by the hour on a Mac?

Timing is the stronger choice. Its documentation lists billing status tracking, customizable reports with rounding, and GrandTotal invoicing integration depending on plan. It also stores tracked time locally unless you opt into sync. Professional costs $9 per month billed annually or $11 per month billed monthly, with a 30-day trial and no credit card required. Dayflow does not create invoices.

Do automatic time trackers send my data to the cloud?

It depends on the tool. Rize says data is hosted on Amazon Web Services, encrypted at rest and in transit. RescueTime sends activity data to its servers to generate reports. Timing keeps tracked time on your Mac unless you turn on sync. Dayflow stores recordings on your Mac. Its local AI mode keeps analysis on-device, while your own provider or Dayflow Pro processes selected screenshots off-device.

Can I use these tools on Windows as well as a Mac?

Some of them. Rize supports Mac and Windows, and RescueTime lists desktop apps plus iOS, Android and web. Timing is Mac only. Apple Screen Time covers only Apple devices. Dayflow runs only on macOS 14 or later. If you split your working day between a Mac and a Windows PC and want one record, Rize is the closest fit of these.

How long does it take to get better at estimating my time?

There is no fixed timeline, and it varies from person to person. A good approach is to write an estimate before each task, compare it with what your record shows, and review the gaps once a week. You are not aiming for perfect estimates. You want to learn your usual error, such as finishing late on writing tasks, so you can plan around it.