Direct answers to the questions that come up most often about 15-minute time tracking. Longer where length is needed. Shorter where it isn’t.
Do I Really Need a Timer, or Can I Log at Natural Breaks?
Both approaches work, but they produce different results.
Timer-based logging tends to produce more complete data in the first few weeks because it forces entries even when you haven’t noticed a transition. The cost is interruption: a timer fires during deep work, you make a quick entry, you return to the work. Most people find this disruptive for the first few days and then adapt.
Transition-based logging produces cleaner, more contextually accurate entries because you’re logging at the moment you actually change activities. The cost is compliance: you can go 45 or 60 minutes without logging if you’re deeply focused and don’t notice transitions.
The practical recommendation: use a timer for the first two weeks while the habit forms. Once you’re logging consistently and automatically, switch to transition-based logging if that feels more natural. Many experienced trackers use a hybrid—transition-based during focused work, timer as a backstop for longer administrative periods.
How Do I Handle Meetings That Span Multiple 15-Minute Blocks?
Log a new entry at each 15-minute boundary with the same label. A 60-minute meeting from 10:00 to 11:00 becomes four identical entries:
10:00 — Client call, Smith project (P/Meeting)
10:15 — Client call, Smith project (P/Meeting)
10:30 — Client call, Smith project (P/Meeting)
10:45 — Client call, Smith project (P/Meeting)Some people object that this creates “duplicates” in the log. It’s not duplication—each entry represents one 15-minute quantum of time spent in that meeting. When you analyze the week’s data, the AI will correctly total them as 60 minutes of meeting time.
What Category Should I Use When I’m Doing Multiple Things at Once?
The category that best describes the primary task—the one requiring the most active cognitive engagement.
If you’re listening to a meeting while also writing a Slack message, the meeting is the primary task (you’re attending it actively) and the Slack message is a secondary interrupt. Log the meeting.
If you’re in a “working meeting” where you’re simultaneously building a deliverable (common in certain consulting contexts), use your deliverable category. The meeting framing is incidental to the work.
When in doubt, use your best judgment and be consistent. What matters for analysis isn’t that every edge case is perfectly categorized—it’s that similar situations are categorized the same way, so comparisons over time are valid.
How Many Weeks of Data Do I Need Before the Insights Are Useful?
One week of data answers: “What did I actually do last week?” Four weeks of data answers: “What patterns characterize how I typically work?” Three months of data answers: “How does my time use change across different types of weeks and projects?”
Most people find the first genuinely surprising insight at the one-week mark, when they see the category breakdown for the first time. The truly useful insights—the ones that drive structural changes to how you work—tend to come from the four-week patterns, when individual week anomalies average out.
Start the weekly review immediately. Don’t wait for “enough” data before analyzing. One week of imperfect data is better than waiting for perfect data that you don’t yet have.
Should I Track Personal Time as Well as Work Time?
Only if you want data about personal time.
Most people who start 15-minute tracking have a specific professional problem they’re trying to understand—where the workday goes, how much deep work they’re actually doing, whether business development is getting enough attention. Personal time tracking adds logging overhead without serving those goals.
That said, if your work and personal time are genuinely interleaved (remote work, freelancing, caregiving responsibilities during the day), tracking both can reveal patterns that work-only tracking misses—specifically, how personal obligations are affecting professional capacity.
If you do track both, use a clear, simple personal category (just “Personal”) rather than sub-categorizing personal activities. The goal is to capture the time cost, not to audit your personal life.
What Do I Do With Gaps in My Log?
Acknowledge them honestly and move on.
If the gap is under 30 minutes and you can reconstruct it reasonably well, write the reconstruction and mark it with a ? to indicate it’s approximate. If the gap is longer or you genuinely don’t know what you were doing, write [gap — unknown] or just leave the entries blank for that period.
In analysis, gaps marked as unknown can be excluded from category totals. A log with acknowledged gaps is more honest and more useful than one where gaps are filled with plausible-but-wrong entries.
The right response to a day with several large gaps is not to abandon the log—it’s to note that this was a fragmented or unusual day and continue. Incomplete data is still data. Two days of complete logs and three days of partial ones is better than no logs at all.
Can I Use 15-Minute Tracking for Billing Clients?
Yes. This is actually the original context for 15-minute increments in professional work.
A few billing-specific practices worth noting:
Log billable entries contemporaneously, not at day-end. The accuracy advantage of live logging is most financially important in billing contexts. Day-end reconstruction of billable hours systematically underestimates cognitively demanding work—which means you’re undercharging.
Mark billable vs. non-billable clearly in your category structure. Some practitioners use a simple B/NB marker on every entry. Others put billable categories in one group and non-billable in another.
Clients and projects as tags, not categories. Categories should describe activity types (Client Delivery, Admin, etc.). Client names and project codes are better handled as a separate tag column rather than separate categories—otherwise your category set explodes as you add clients.
Keep a copy before sending. Before invoicing from your log, export or screenshot the relevant entries. This is your documentation if a client ever disputes a time entry.
What Happens When I Have an Unusual Week?
Log it and label it unusual.
Travel, conference weeks, family events, illness, product launches—these are real parts of your working life and they belong in your data. What you don’t want is for a week that doesn’t match your typical pattern to skew your analysis of your typical pattern.
Two practices help:
Add a week-level note before running your weekly analysis. “This was a conference week — Tuesday and Wednesday I was at [event], minimal regular work.” When the AI analysis compares this week to prior weeks, that context prevents it from treating the anomaly as a pattern.
After an unusual week, add a note in your AI analysis prompt: “This week was atypical because [reason]. Please flag where this week differs from typical weeks but don’t let it drive structural recommendations.”
How Do I Know If My Category System Needs Updating?
Three signals that your taxonomy has drifted out of alignment with how you actually work:
You’re regularly uncertain which category an entry belongs to. Ambiguity on occasional edge cases is normal. If you’re uncertain about more than 10–15% of entries, the categories aren’t distinct enough or don’t cover your actual work types.
One category contains very few entries. If a category you added (say, “Learning”) consistently represents less than 2% of your week, it may not be a meaningful distinction for your current work. Either the work type is genuinely rare, or it’s being absorbed into another category incorrectly.
The analysis keeps telling you obvious things. If the weekly AI review produces observations that feel completely unsurprising, the categories may be too coarse to reveal the distinctions that would actually be informative. Splitting a large “Admin” category into “Internal Admin” and “Client Admin,” for instance, might reveal that one of those is much larger than expected.
Review your taxonomy at the end of each month, not more often. Frequent taxonomy changes break the comparability of your data.
How Does 15-Minute Tracking Fit With Time Blocking?
They’re complementary: time blocking is a planning method, 15-minute tracking is a measurement method.
The combination closes the planning loop that most systems leave open. You plan your blocks on Sunday or Monday. You track in 15-minute increments throughout the week. On Friday, you compare the plan to the reality.
The comparison question:
Here's my time block plan for this week:
[planned blocks]
Here's my actual 15-minute log:
[actual entries]
Where did my plan match reality? Where did it diverge most significantly?
What does the divergence tell me about how I should plan differently next week?Over four to eight weeks of running this comparison, patterns emerge that fundamentally change how you build your plans. You stop planning for the ideal week and start planning for the realistic one—accounting for the unplanned work that always appears, the meetings that always run long, and the energy patterns that make certain times of day better for certain work.
Can I Use AI to Log Entries for Me?
Not reliably, yet.
Some tools can observe your application usage and infer what you were working on (which app was in focus, what documents were open). For certain types of work, this produces useful logs automatically. The limitations: it doesn’t capture thinking that happens away from a screen, it doesn’t capture conversations or calls, and it doesn’t work for people whose “work” isn’t well-represented by their app usage.
The most useful partial automation right now is AI-assisted tagging—you write the entries, AI applies the categories. This is genuinely available and works well. Full automatic logging that doesn’t require your input is still more promise than reality for most knowledge workers.
What Should I Do in the First 10 Minutes After Reading This?
Open a notes app. Write today’s date as the title. Write the current time and what you’ve been doing for the past 15 minutes. Set a timer for 15 minutes.
You now have one data point. When the timer fires, write the second.
The system doesn’t require setup, apps, categories, or plans to start. It requires entries. Start with entries, and build the rest around what you observe.
The complete guide has the full implementation path once you’ve decided the method is worth investing in.
Frequently Asked Questions
-
Is this FAQ regularly updated?
Yes. We update this as new questions come up and as AI tools change what's possible in the analysis layer. The complete guide to the 15-Minute Time Tracking Method covers the full system in depth if you want more than answers to specific questions.