What Is Deep Work Tracking? The Complete Guide (2026)

Deep work tracking is counting the hours you spend in unbroken, demanding focus, then checking that count against reality. A paper tally works to start. For automatic records on a Mac, Timing suits people who also bill hours, RescueTime wins if you want distraction blocking, ActivityWatch is free and local, and Dayflow turns screen captures into an AI-written timeline you can audit.

Deep work tracking is the practice of recording how many hours you spend in sustained, distraction-free focus on demanding work, then comparing that number with what you planned. It is the measurement side of deep work, the idea Cal Newport popularized in his book Deep Work.

People usually get it wrong by counting presence instead of focus. If the editor was open for an hour, they log an hour of deep work, even when chat, email and a news tab took turns pulling their attention away every few minutes. A timer that ran for 50 minutes says nothing about whether those 50 minutes were unbroken. Honest deep work tracking mostly comes down to not giving yourself credit for time that only looked focused.

Disclosure up front: Dayflow publishes this guide, and Dayflow is one of the tools listed near the end.

The short version

• Deep work means focused, uninterrupted effort on work that is hard to do and hard to replicate. Shallow work is everything logistical around it.
• Tracking it means deciding what counts, setting a minimum block length and counting only the blocks that meet the bar.
• Memory is a poor witness for a whole day, so check your tally against some record of what actually happened on screen.
• The weekly review matters more than the daily number. The useful output is the patterns: when blocks break and what breaks them.
• Tools range from a paper tally to automatic trackers. None of them can tell focus from presence on its own, so you still have to judge.

What is deep work tracking, exactly?

Newport splits work into two kinds. Deep work is professional activity done in distraction-free concentration. It stretches your abilities and produces something valuable and hard to copy, such as a difficult piece of writing, a system design, a subtle bug fix or a proof. Shallow work is the logistical, low-concentration work that keeps things running: replying to messages, scheduling, status updates and most admin.

Deep work tracking is the habit of measuring the first kind. In practice it has three parts:

1. A definition. You decide in advance which activities count as deep work for your job. For a developer, that might be writing or reviewing code with chat closed. For a writer, it might be drafting but not researching.
2. A measurement. You capture when deep work started, when it stopped and whether it was interrupted. You can use a pen-and-paper tally, a timer or an activity record from software.
3. A review. You look at the totals regularly and ask why they came out the way they did.

Newport’s book borrows the idea of a scoreboard, a visible tally of deep work hours that you update as you go. The number itself matters less than the feedback it gives you. When the tally stays flat for three days, you notice, and you start asking what is eating the time.

Deep work tracking is not a productivity score, a judgment of your worth or a way for a manager to watch you. It is a personal measuring stick. If it starts to feel like surveillance, it has drifted from its purpose. There is more on that in time tracking without surveillance.

Deep work tracking vs time tracking, focus timers and screen time

These four practices get lumped together because they all involve a clock. Each one answers a different question.

Practice	What it measures	Question it answers	Blind spot
Deep work tracking	Unbroken blocks of demanding work that met your definition	How much real focus did I get, and what broke it?	Depends on an honest definition and an honest review
Time tracking	Hours per project, client or task	Where did my hours go, and what can I bill?	An hour on a project can be deep or shallow
Focus timers (Pomodoro and similar)	How long a timer ran	Did I start and finish a session?	A running timer does not prove focus
Screen time and app usage	Minutes per app or website	Which apps took my attention?	Being in the right app is not the same as focusing

Time tracking is the closest cousin. If you already track time by project, you have half the data. You only need to mark which blocks were deep and which were not.

A focus timer is a useful trigger for starting a block, but treat its total as an upper bound, not a measurement. Screen time reports are good for spotting leaks, such as dozens of short visits to a chat app. They cannot tell you whether your time in the editor was spent thinking or staring.

For more on the software side, see what an automatic time tracker is.

How does deep work tracking actually work?

Every approach combines three choices.

Where the data comes from

• Memory. You write down your deep work hours at the end of the day. This costs nothing, but memory is a poor witness. A day with one great hour often gets remembered as a focused day.
• A timer. You start a timer when a block begins and stop it when the block ends. This is better, but it records your intentions. It does not notice the moment you switched to email “for a second.”
• An activity record. Software logs which apps, windows or screens were active over the day, so it catches the switches you forget about. It cannot read your mind, so you still decide which stretches were deep.

The most honest setups combine a plan (what you meant to do) with a record (what actually happened).

What counts as a block

A block is a stretch of deep work long enough to matter. Pick a minimum length, for example 45 minutes, and keep it fixed. The exact threshold is your choice. Keeping it the same from week to week is what makes your weeks comparable.

What breaks a block

Decide in advance what counts as an interruption. One reasonable rule: any switch to messaging, email, social media or unrelated browsing ends the block, even a brief one. Looking up documentation for the task in front of you does not end it. Without a rule, you will negotiate with yourself after the fact, and you will usually win.

The tally-and-audit method, step by step

There is no official way to track deep work. “Tally-and-audit” is our name for a simple routine that combines Newport’s scoreboard idea with an honest audit. It takes a few minutes a day.

1. Write your definition. Keep it to one or two sentences, for example: “Deep work for me is drafting, restructuring and outlining. Research and email are not.”
2. Set a minimum block length. Pick one, such as 45 minutes, and keep it for at least a month.
3. Plan blocks the night before. Put two or three blocks on your calendar, each with a specific task. A block without a task tends to dissolve into shallow work.
4. Keep a visible tally. Use a sticky note, a notebook page or a daily work log. Add a mark for each block that met the bar.
5. Audit against a record. At the end of the day, compare your tally with whatever record you have, such as browser history, an app usage report or a timeline. Cross out any block that was actually broken.
6. Note the breaker. For each broken block, write one word: chat, email, meeting, tired or unclear task.
7. Review weekly. Total the honest blocks, look at the breakers and change one thing for next week. You might move a meeting, close chat during blocks or shrink the planned task.

If you suspect your sense of elapsed time is off, a short exercise like the time estimation test shows how your guesses compare with a clock. It is a reflection exercise, not a diagnosis.

A worked example (made up)

This is an invented illustration, not a real person or real data.

Priya is a backend developer. Her definition of deep work is writing or reviewing code, or designing a system, with chat closed. Her minimum block is 45 minutes. On Tuesday she plans three blocks:

• 9:00 to 10:30 a.m. for a migration script
• 1:00 to 2:00 p.m. for a code review
• 3:30 to 5:00 p.m. for a design doc

At 5:30 p.m. her gut says she got about four hours of deep work. Her timer agrees, with 4 hours 10 minutes logged.

Then she audits the day. Her activity record shows:

• 9:00 to 10:30 a.m.: Editor and terminal throughout, except for two switches to chat, at 9:40 and 10:05, to answer questions. Neither was urgent. The longest unbroken stretch was 40 minutes, so under her rule the block does not count.
• 1:00 to 2:00 p.m.: A clean 60 minutes in the code review tool. This block counts.
• 3:30 to 5:00 p.m.: 25 minutes on the design doc, then a long email thread, then 40 more minutes on the doc starting at 4:20. Neither stretch reaches 45 minutes, so the block does not count.

Her honest tally is one block of 60 minutes. The breakers were chat (twice) and email.

Priya does not treat this as a failure. Next week she turns on do-not-disturb for chat during the morning block and moves her email check to 3:00 p.m., just before the afternoon block. Over the following weeks she watches whether the honest tally rises.

The useful output was never the number. It was spotting that chat broke the morning block and email broke the afternoon one.

What are the common mistakes when tracking deep work?

Counting presence as focus. Time in the editor, the doc or the design tool is not deep work by default. Audit it before you count it.

Trusting the timer total. A timer measures how long you intended to focus. Use it to start blocks, not to score them.

Changing the rules mid-week. If the minimum block drops from 45 to 25 minutes on a bad day, the numbers stop meaning anything. Change rules only at the weekly review.

Setting a target you cannot hit. Newport argues that deep work has a daily ceiling well short of a full workday. A target of eight deep hours guarantees a discouraging tally. Start from what you actually achieve and grow it slowly.

Counting meetings. A working session where you and a colleague crack a hard problem together can be deep. A status meeting is not. Decide which kind a meeting is before it starts.

Chasing a productivity score. Some tools assign scores to apps or categories. A score can be a useful nudge, but it bakes in someone else’s definition of productive. Your definition is the one that counts.

Letting it become surveillance. Deep work tracking is for the person doing the work. Once the data lands in a team dashboard, people start optimizing for the dashboard. Keep it personal unless you choose to share a summary.

Skipping the review. A tally nobody reads is just bookkeeping, and the weekly look at breakers is where the habit pays off. A fixed review also makes it much easier to remember what you worked on.

Tools that help with deep work tracking

A paper tally is enough to start. Software helps with the audit step, because it records the switches you forget. The tools below are all automatic trackers. This is a comparison of vendor documentation as checked on October 4, 2026, not hands-on use. Dayflow details reflect version 2.2.0.

Tool	What it does for this	Price
Rize (compare)	Automatic app and website tracking with AI auto-categorization and AI focus insights. Mac and Windows. Data hosted in the cloud	Basic $9.99/mo billed annually or $12.99/month billed monthly; no free tier; 7-day trial
RescueTime (compare)	Background app and website tracking plus distraction blocking, focus sessions, goals and alerts	Focus $7/month billed annually or $9/month billed monthly; free Lite plan (see the vendor’s pricing page for its limits); 14-day trial
Timing (compare)	Mac-only automatic tracking down to URLs and documents, AI activity summaries, data stored locally unless you opt into sync	Professional $9 per month billed annually or $11 per month billed monthly; no free tier; 30-day trial
ActivityWatch (compare)	Records the active app, window title and away-from-keyboard time, with browser and editor plugins. Data stays on your device	Free, open source (MPL-2.0)
Dayflow	Records the screen at one frame every 10 seconds and has AI write the day into a readable timeline	$0, MIT licensed; optional Pro at $20 a month

A few notes on fit for deep work:

• Rize puts AI focus insights front and center, but it has no permanently free tier and stores data in the cloud.
• RescueTime is the only tool in this table that lists distraction blocking. That helps if protecting the block is your main problem.
• Timing keeps data on your Mac by default. Its billing reports matter only if you also bill clients.
• ActivityWatch is free and local, but it lists no AI summaries, so you sort the record into deep and shallow work yourself.

For a broader comparison, see our roundup of the best time tracker for Mac options.

Dayflow is our product. It fits the audit step: instead of app minutes, you get a written timeline of what was on screen, which makes it easier to see where a block broke. Analysis can run on your Mac with local AI through Ollama or LM Studio, through your own cloud provider or through Dayflow Pro, and AI summaries can miss or misread work, so check them before you rely on them. It does not fit if you need blocking, invoices, payroll approvals or team reports, and it only runs on macOS 14 or later.

Where Dayflow is the wrong choice

• You want distractions blocked during a block. Pick RescueTime, which lists distraction blocking and focus sessions. Dayflow has no website blocking.
• You work on Windows, or on both Mac and Windows. Rize covers both, and ActivityWatch also runs on Windows, Linux and Android. Dayflow is Mac only.
• You want a local record without screen captures or AI. ActivityWatch records app and window titles rather than the screen, is free and keeps data on your device.
• You also need to bill clients for the same hours. Timing offers billing status tracking and, depending on plan, GrandTotal invoicing integration. Dayflow does not do invoices.

The bottom line

Deep work tracking is a simple idea that is easy to fudge. Define what counts, set a minimum block length, keep a visible tally and audit it against a record of what actually happened.

The honest number will probably be lower than your gut says, and that is the point. A small, honest number you can grow beats a flattering one that teaches you nothing.

Start on paper this week. If the audit is the step you keep skipping, add an automatic tracker to handle the recording. To see what a weekly look-back can involve, read our deep work review guide, or rough out your week with the where does my week go calculator.

Frequently asked questions

What counts as deep work?

Deep work is focused, uninterrupted effort on demanding work that produces something valuable and hard to replicate. Cal Newport popularized the term. Writing a hard section, designing a system or debugging a subtle problem usually count. Email, scheduling, status updates and most admin are shallow work. The exact line depends on your job, so write your own one-sentence definition before you start tracking.

How many hours of deep work a day is realistic?

There is no universal number. Newport argues that deep work has a daily ceiling well short of a full workday, and that the capacity grows with practice. Picking a target in advance is less useful than tracking honestly for two weeks, seeing what you actually achieve, then raising that number slowly. A tally you can hit is more useful than one that always disappoints.

Is a Pomodoro timer the same as tracking deep work?

No. A Pomodoro or focus timer records how long a session was scheduled to run, not whether you stayed on task. It is a good way to start a block and protect it. For tracking, treat the timer total as an upper bound. Check it against what actually happened, such as browser history or an activity record, before you count the time as deep work.

Can software track deep work automatically?

Partly. Automatic trackers record which apps, windows, websites or screens were active, which catches the quick switches people forget. No tool can tell from that record alone whether you were thinking hard or just had the right window open. Use the software for the record. Then apply your own definition and minimum block length to decide which stretches count.

What is the best deep work tracker if I want distracting sites blocked?

RescueTime is the better pick here. Its vendor pages list distraction blocking, focus sessions, goals and alerts alongside automatic app and website tracking. The Focus plan is $7/month billed annually or $9/month billed monthly, with a 14-day trial. Dayflow, our product, has no website blocking, so it cannot stop you from opening a distracting tab during a block.

Is there a free deep work tracker for Mac?

Yes. ActivityWatch is free and open source under MPL-2.0. It keeps data on your device and records the active app, the window title and away-from-keyboard time. Dayflow, our product, is $0 and MIT licensed, with an optional Pro plan at $20 a month, and it needs macOS 14 or later. A paper tally also works and costs nothing.

Does deep work tracking work on Windows?

The method does, because a written definition and a tally work anywhere. For software, Rize runs on Mac and Windows, and ActivityWatch runs on Windows, Mac, Linux and Android. RescueTime lists desktop apps along with iOS, Android and web, so check the vendor's site for the exact desktop systems. Dayflow is Mac only, so Windows users should pick one of the others.

Should meetings count as deep work?

Usually not. Status meetings, check-ins and most calls are shallow work, even when they matter. A working session where two people solve a hard problem together, with no other distractions, can count. Decide which kind a meeting is before it starts rather than after. That way you are not tempted to upgrade a scattered hour into deep work when you tally the day.

How do I track deep work without feeling watched?

Keep the data personal. Track for your own review, not for a manager's dashboard, and share summaries only when you choose to. If local storage matters to you, pick tools that offer it. ActivityWatch keeps everything on your device, and Timing stores tracked times locally unless you opt into sync. Review trends weekly instead of checking numbers all day.