How to do a personal time audit

Pick one question you want answered, write down where you think your week goes, then log what you actually do in 30-minute blocks for five working days. A paper log and a kitchen timer cover most people and catch off-screen time. If most of your work is on a Mac and you keep forgetting to log, Dayflow records the screen and drafts the timeline for you. Then compare your guess with the log and change one thing.

It is 5:40 on a Thursday. You were at your desk by nine, you never really stopped, and yet the thing you meant to finish this week is still open in a tab. You try to replay the day and get a blur: a call that ran over, a thread you had to answer, something about a spreadsheet, lunch at some point.

This happens to almost everyone, and it is not a character flaw. Memory is good at storing events and bad at storing durations. A personal time audit is a simple way to swap the blur for an actual record, for one week, so you can see where the hours went and change one thing on purpose.

This guide walks through a one-week audit you can do with paper and a timer, how to read what you find, and where an automatic record can help if you work on a Mac. Dayflow, which publishes this blog, is one of those automatic options, and we say plainly below where it is the wrong choice.

The short version

• Write one question you want the audit to answer before you start, such as “Why do I never get to deep work before lunch?”
• Guess where your week goes, in hours per category, and write the guess down before you log anything.
• Log what you actually do in 30-minute blocks for five working days, on paper, with a timer to prompt you.
• Use five to seven categories in your own words, and give “switching” and “messages” their own lines.
• At the end of the week, compare your guess with the log, find the biggest surprise, and change only that.
• Run a shorter check the following week to see if the change held.

Why don’t I know where my time goes?

Most of us run on a mental summary of our day, and that summary is built from the moments that stood out. A tense meeting, a breakthrough, a long lunch with a friend all get stored. The fifteen minutes of checking messages after each of those does not, because nothing happened that felt worth remembering.

The result is a story about your day that is mostly true but skewed. Big, memorable blocks feel longer than they were. Small, repeated ones feel like nothing, even when they add up to a large part of the afternoon.

Switching between tasks makes this worse. Each time you leave something and come back, there is a stretch where you are rereading, reorienting and finding your place. Many people find those stretches feel like “working” in the moment and vanish completely from memory afterward.

Then there is the end-of-day reconstruction. When you try to answer “what did I do today?” at six o’clock, you are tired, and the easiest answer is a tidy one. That is why a written record made during the day almost always looks different from the story told at the end of it. If this is the question that brought you here, our page on where did my day go covers the same gap from a slightly different angle.

Step 1: What question should a time audit answer?

Before you log anything, write one sentence at the top of a page: the thing you actually want to know. An audit without a question tends to produce a pile of numbers that nobody reads.

Good questions are specific and a little uncomfortable. “Where does my week go?” is a start. “Why do I keep working evenings when my days feel full?” is better, because it tells you what to look for in the log.

Illustration: Someone who freelances might write, “Am I spending more time on client email than on client work?” Someone on a team might write, “How much of my day is meetings plus the time around them?” Each question points at two or three categories that matter most.

After a week, how to tell it is working: When you sit down to review, you know which rows of your log to look at first. If you find yourself staring at the totals with no idea what they mean, the question was too vague. Sharpen it for next time.

Step 2: Guess first, then measure

Take five minutes and estimate how many hours a typical week goes to each category you care about. Write the numbers down and do not change them later. This guess is half the value of the whole exercise.

The comparison between what you believed and what you logged is where the useful surprises live. Without the guess, the log just looks like your week. With it, you see exactly where your sense of time and the clock disagree.

If you want a structured way to make that guess, the where does my week go calculator walks you through it. If you are curious how your sense of short durations compares with a clock in general, the time estimation test is a short exercise for that. It is not a diagnostic, just a quick comparison.

Illustration: You estimate ten hours of meetings, eight hours of email and messages, and twenty hours of focused work. You fold the paper and put it in a drawer until Friday.

After a week, how to tell it is working: You can put your guess and your actual totals side by side and point to at least one category where they differ in a way that matters to you. If they match closely across the board, that is useful too. It means your problem is probably not where the time goes, but what the time is spent on.

Step 3: Log in 30-minute blocks for one working week

This is the core of the audit and it needs no software. Divide a page into rows, one per half hour of your working day. Set a kitchen timer or a repeating alarm for every 30 minutes. When it goes off, write one short line about the block that just ended, then reset it.

Write what you were mostly doing, not what you meant to do. If the block was split, write both and roughly how it split. Keep it fast. A line like “report draft, then Slack” is plenty.

Thirty minutes is a deliberate choice. Shorter intervals break your concentration too often. Longer ones push you back into reconstructing from memory, which is the habit you are trying to get around. If you prefer a ready-made page, the daily work log template is laid out for this.

Do it for five working days. One day is too easy to explain away as unusual. A month is long enough that most people quietly stop.

Illustration: Tuesday, 10:00 to 10:30: “Started budget, stopped for two messages, back to budget.” 10:30 to 11:00: “Meeting prep, then meeting started late.” 11:00 to 11:30: “Meeting.” You do not need more detail than that.

After a week, how to tell it is working: You have at least four mostly complete days. A few missing blocks are normal. If whole afternoons are blank, the timer is too easy to ignore. Move it somewhere you have to physically get up for, or tape a note to your screen.

Step 4: What categories should you use?

Pick five to seven categories in your own words, the ones you would naturally use if a friend asked about your day. Your categories should map to your question from Step 1, so you can actually answer it.

Two categories are worth giving their own lines even if they feel minor. The first is messages: email, chat, and quick replies. The second is switching: the time spent finding your place again after an interruption. Both tend to disappear into other categories unless you name them.

You can assign categories as you log or all at once on Friday with a highlighter. Many people find the Friday approach easier because it keeps the logging itself quick.

Illustration: A designer might use: design work, feedback and review, meetings, messages, admin, switching, breaks. A writer might use: drafting, research, editing, messages, admin, switching, breaks.

After a week, how to tell it is working: Almost every logged block fits one category without much debate. If you keep writing “other,” split that category. If you are agonizing over two categories that never differ, merge them.

Step 5: Count the time around meetings, not just the meetings

Meetings are easy to count because they are on the calendar. The time around them is not. The ten minutes before, when you stop what you are doing to get ready, and the fifteen after, when you write notes or answer what came up, rarely get logged as “meeting.”

During your audit week, add a small mark to the blocks before and after each meeting when they were mostly about that meeting. On Friday, total them separately. This is often where a “light” meeting week turns out to be heavier than it looked.

If you want to put a number on a recurring meeting for a conversation with your team or a client, the meeting cost calculator does the arithmetic.

Illustration: Your calendar shows six hours of meetings. Your log shows those six hours plus about two more of prep and follow-up spread across the week in small pieces. The meeting load is really closer to eight.

After a week, how to tell it is working: You can say how much of your week goes to meetings including the time around them, and the number feels right when you say it out loud. If it still feels wrong, check whether some “messages” time is really meeting follow-up.

Step 6: Compare, then change one thing

On Friday, total each category and put the totals next to your guess from Step 2. Read the two columns slowly. Look for the single biggest gap, or the one that most directly answers your question from Step 1.

Then pick one change aimed at that gap. Not a new system. One change, small enough to do on Monday. Write it at the bottom of the page.

Good changes are concrete: “Messages at 11 and 4, closed otherwise.” “No meetings before noon on Tuesdays and Thursdays.” “First 90 minutes of the day on the main project before opening email.” Vague changes like “be more focused” give you nothing to check.

The following week, do a lighter version of the audit. You do not need to log every half hour again. A quick end-of-day note on whether you kept the one change, and roughly how the target category looked, is enough. If you want to keep a lighter ongoing record after that, a running work journal works well. Our guide to work journals covers simple formats.

Illustration: You guessed eight hours of messages and logged closer to thirteen, mostly in short bursts. You choose to batch messages twice a day. Next Friday, your note says you kept it on three of five days and the bursts dropped noticeably on those days.

After a week, how to tell it is working: You can say yes or no to “did I make the change?” for each day. If the answer was mostly no, the change was too big or fought against something real, like a manager who expects quick replies. Shrink it rather than abandoning it.

Where seeing your actual day helps

The hardest part of a paper audit is the logging itself. A timer goes off during a call, you skip it, and by the afternoon the page has gaps you fill in from memory, which is the thing you were trying to avoid.

If most of your work happens on a Mac, an automatic record removes that step. Dayflow records your screen at one frame every 10 seconds and has AI write the day into a readable timeline. You do not start a timer or reconstruct anything. At the end of the week you read what was actually on your screen and compare it with your Step 2 guess.

The full recordings and the local timeline are stored on your Mac. You choose how screenshots are analyzed: a local model on your Mac keeps analysis on-device, your own cloud provider receives selected screenshots under its own terms, or Dayflow Pro manages cloud analysis and deletes screenshots after processing under the privacy policy. You can export a date range as Markdown from Settings → Export. AI summaries can miss or misread work, so treat the timeline as a draft to check.

Dayflow is free and MIT licensed, with an optional Pro plan at $20 a month, and needs macOS 14 or later. The details here come from Dayflow 2.2.0’s own documentation, reviewed 2026-09-06. For a Mac-specific walkthrough, see how to do a time audit on a Mac, or browse other Mac time trackers.

Dayflow publishes this article.

Where Dayflow is the wrong pick

Be honest about the shape of your week before reaching for any app.

• Much of your work happens off a Mac. If you work on Windows, on a phone, on paper, in person or out on site, Dayflow sees none of it. A paper log with a timer is the better tool, because it records everything you write down, wherever you are.
• It sees only the screen. A long phone call, a whiteboard session or twenty minutes of thinking on a walk show up as a gap, not as work. For a lot of people those are some of their most important hours.
• It is a record, not a coach or a blocker. Dayflow shows you what happened. It does not tell you what to change, nudge you during the day, or block websites. The thinking in Step 6 is still yours to do.
• It does not do billing or team reporting. There are no invoices, payroll approvals or team reports. If your audit is really about billing clients accurately, a tracker built for invoicing fits better.
• Screen recording is not for everyone. If the idea of your screen being recorded, even locally, would make you uncomfortable or change how you work, the paper method gives you the same insight without it.

For a first audit with a lot of offline time, the plain answer is a pen, a sheet of paper and a kitchen timer.

The bottom line

A personal time audit is one ordinary week of paying attention on purpose. Write the question, write your guess, log in half-hour blocks, name the small categories that usually hide, and count the time around your meetings. On Friday, find the biggest gap and change one thing.

Most people can do all of this with paper. If you work mostly on a Mac and keep forgetting to log, an automatic record can take over the writing-down part. Either way, the useful moment is the same one: seeing your guess next to what actually happened, and deciding what to do about it.

Frequently asked questions

What is a personal time audit?

A personal time audit is a short, deliberate period, usually one working week, where you record what you actually do and compare it with where you believed your time went. It is not a productivity score or a judgment. The point is to find the one or two gaps between your picture of your day and the real one, then make a single change you can check the following week.

How long should a time audit last?

One full working week is enough for most people. A single day is easy to dismiss as unusual, and a month is long enough that most people stop logging halfway through. Five working days shows you the repeating patterns, like a slow Monday morning or a meeting-heavy Wednesday, without turning the audit into a second job.

How often should I log my time during an audit?

Every 30 minutes works for most people. A kitchen timer or phone alarm prompts you, and you write one line about the block that just ended. Shorter intervals interrupt your work too often, and longer ones push you back into reconstructing from memory, which is exactly the habit the audit is trying to get around.

What categories should I use for a time audit?

Use five to seven categories in your own words, the ones you would say out loud if a friend asked about your day. Examples might be focused work, meetings, messages, admin, breaks and switching between tasks. Too many categories make logging slow. Too few hide the thing you are trying to see. You can always split a category next week.

Can I do a time audit without an app?

Yes, and many people should start that way. A sheet of paper divided into 30-minute rows, a pen and a timer cover everything a first audit needs. Paper also captures time away from screens, like phone calls, errands and thinking on a walk, which screen-based apps cannot see. Software helps mainly when you keep forgetting to write things down.

Is a paper log better than Dayflow for a time audit?

If a lot of your working day happens off the computer, in person, on calls away from your desk, on a phone or on paper, then yes, a paper log will give you a more complete picture. Dayflow only sees what is on your Mac's screen and runs only on macOS 14 or later. For mixed or mostly offline work, a paper log is the better tool.

What should I do with the results of a time audit?

Put your original guess next to the actual totals and look for the single biggest surprise. Then choose one small change aimed at that gap, such as moving messages to two set times or protecting one morning block. Run the change for a week and check again. Trying to fix everything at once usually means none of it sticks.

Why do I feel busy all day but get little done?

Many people find that the day fills up with short pieces of work, replies, quick questions and the minutes it takes to get back into a task after each one. None of these feel large, so they do not make it into memory, but together they can take a lot of the day. A time audit makes those pieces visible so you can decide what to do about them.

Does Dayflow cost money for a time audit?

The Dayflow app is free and MIT licensed. You can run analysis with a local model on your Mac or with your own cloud provider, whose charges and terms apply. There is an optional Dayflow Pro plan at $20 a month where Dayflow manages the cloud analysis. A one-week audit does not require Pro.