What Is a Time Audit? The Complete Guide (2026)

A time audit is a one or two week record of how you actually spend your working hours, sorted into five to eight categories and compared with how you meant to spend them. For a quick, free pass on a Mac, Apple Screen Time is enough. Timing suits audits that end in billable hours, RescueTime suits cross-platform use with blocking, and Dayflow suits a free, readable Mac timeline.

A time audit is a short, deliberate stretch, usually one or two weeks, where you record how you actually spend your working hours and sort those hours into a few categories. You then compare that record with how you meant to spend your time and change something based on the gap.

People get it wrong in two ways. Some treat it as a scorecard: they glance at a “productive vs. unproductive” percentage, feel guilty and move on. Others run it for a single day, which mostly measures whatever that day happened to throw at them. A useful audit runs longer than a day, uses categories you chose on purpose and ends with a decision.

Disclosure: we make Dayflow, which appears in the tools section near the end. Everything before that is about the method, and it works with a notebook.

The short version

• A time audit is a diagnosis, not a habit. You run it for one or two normal weeks, then stop.
• Pick five to eight categories before you start, based on the question you want answered.
• Record without trying to behave better. A flattering week is a useless week.
• Total the hours per category and compare them with what you intended. The gap is the result.
• Make one or two specific changes, then audit again later to see whether they held.

What is a time audit, exactly?

A time audit has three parts.

A record. A continuous account of your working hours for a fixed window. It can come from a manual log, from your calendar or from software that records activity automatically. What matters is that it covers whole days, not just the parts you remember.

A categorization. Each block of time goes into one bucket: deep work, meetings, messages, admin and so on. Without categories you just have a long list of things you did.

A comparison. You set the totals beside what you wanted, or what your role assumes. A designer who expects to design most of the week and finds design time is the third-largest bucket has learned something no single day would show.

The output is not a number to improve forever. It is a short list of things to cut, move, batch or protect. Once you have that list, the audit has done its job.

This is also why a time audit differs from tracking time for clients or payroll. Billing needs accuracy to the minute and never ends. An audit needs honesty at the level of half hours and ends after two weeks.

Time audit vs. time tracking, time blocking and a Screen Time report

These four get used interchangeably, and mixing them up is the most common reason an audit produces nothing.

	Time audit	Time tracking	Time blocking	Device usage report
Purpose	Find where hours go and decide what to change	Record hours for billing, payroll or project costs	Plan the day in advance	Show time per app and website
Duration	One or two weeks, then stop	Ongoing	Ongoing, day by day	Ongoing, in the background
Unit	Categories you define	Projects, clients, tasks	Calendar blocks	Apps and sites
Output	A gap and a decision	Timesheets, invoices, reports	A schedule	Daily or weekly totals

Time tracking can feed an audit, and a device usage report can be one input. Time blocking is often what you do after an audit, once you know which hours need protecting. None of them is an audit on its own, because none of them includes the comparison and the decision.

How does a time audit work?

The hard part is the record. There are three ways to get one, each with a trade-off.

Manual log. Every 30 minutes, write down what you did. A paper sheet or a spreadsheet is enough, and our daily work log template gives you a ready layout. Manual logging is free and makes you notice your day as it happens. It also changes your day a little, and entries written late get smoothed over. The ten-minute detour into an inbox tends to vanish.

Calendar reconstruction. At the end of each day, read back through your calendar and fill in the gaps. This is fast but weak, because a calendar shows what was planned. It is accurate for meetings and vague for everything between them.

Automatic record. Software runs in the background and records which apps, sites or screens you used. You categorize afterward. This catches interruptions and context switches that manual logs miss, and it does not require discipline during the week. It does require you to be comfortable with what gets recorded and where it is stored. What is an automatic time tracker? covers how these tools differ.

Whichever source you use, aim for roughly 15 to 30 minute resolution. Finer than that turns categorization into a chore. Coarser than an hour hides the fragmentation that most audits exist to find.

Keep a second, simpler tally if you can: how many times a day you switched from one kind of work to another. Two people with identical category totals can have very different days if one worked in long stretches and the other switched constantly.

How do you do a time audit? The Record, Sort, Compare, Decide method

This is a plain four-phase method spread over about two weeks. The steps are numbered so you can follow them in order.

1. Write down the question. “Why do I never finish design work?” leads to different categories than “Am I spending too much time on internal meetings?” One sentence is enough.
2. Pick the window. Choose one or two normal working weeks. Skip weeks with travel, holidays or a launch unless those are what you want to understand.
3. Define five to eight categories before day one. Write a one-line rule for each, such as “Messages: email, Slack, any reply under 15 minutes.” Add one catch-all bucket for time you cannot place.
4. Record every working hour. Use whichever method from the previous section you will actually keep up. Do not try to improve during the window.
5. Sort at the end of each day. Spend ten minutes putting the day’s blocks into categories while you still remember them. Leaving it to the weekend makes everything blur into “work.”
6. Total each week. Add up hours per category. Note the context switches and the longest uninterrupted stretch each day.
7. Compare against your intent. Next to each total, write what you would want that category to be. Circle the two biggest gaps.
8. Decide one or two changes. Pick specific changes for the circled gaps that you can check later, put them on the calendar and schedule a short repeat audit after a few weeks.

Steps 1 and 3 are the ones people skip, and skipping them is why so many audits end with “huh, interesting” and no change.

What categories should a time audit use?

Categories should answer your question from step 1, not describe your job title. A good default set for knowledge work:

• Deep work: focused work on your main output, such as writing, designing, coding or analysis.
• Meetings: scheduled calls and in-person meetings, including prep that happens right before.
• Messages: email, chat and replies that do not need focus.
• Admin: expenses, scheduling, tool upkeep, forms.
• Reviews and support: reviewing others’ work, answering questions, unblocking people.
• Learning: reading, courses and research not tied to a current task.
• Unclear: anything you cannot place.

Two other ways to cut the same hours, depending on the question:

• By project or client. Useful when you suspect one project is quietly eating the week.
• By energy. Tasks that drained you versus tasks that gave you energy. Helpful when the problem is exhaustion rather than output.

A few rules keep categories useful. Keep meetings and messages separate, since they need different fixes. Keep the Unclear bucket small. If it grows past a few hours a week, your categories do not fit your work, and it is better to change them on day two than to discover it on day ten. Finally, do not create a “wasted time” category. Breaks, chats and wandering are part of a normal day, and labeling them waste makes the audit dishonest.

A worked example (made-up)

This is a made-up illustration, not a real person or real data.

Maya is a product designer. Her question: “Why do I feel like I never get to design?” She runs a one-week audit using a manual log in 30-minute blocks, sorted each evening into six categories.

Her week, totaled:

Category	Hours	What she wanted
Deep work (design)	12	20
Meetings	11	8
Messages	9	5
Reviews and support	4	4
Admin	3	2
Unclear	1	1
Total	40	40

The two biggest gaps are design (8 hours short) and messages (4 hours over). The log also shows something the totals do not. Most of her design time came in blocks under an hour, squeezed between a 10:00 standup and an 11:30 sync.

Her decisions:

1. Ask to move the 11:30 sync to the afternoon, which opens a 10:15 to 12:30 block four days a week.
2. Check chat at three set times a day instead of keeping it open in the corner of the screen.

She repeats a one-week audit three weeks later to see whether the design block survived. The point of the example is the shape: a narrow question, a small table, two gaps and two concrete changes.

What do you do with time audit results?

Every useful change after an audit falls into one of five types:

• Cut. Drop a recurring meeting, a report nobody reads or a channel you only skim.
• Move. Shift work to a better time of day, like Maya moving a sync out of her best focus window.
• Batch. Group small, similar tasks such as messages, admin and approvals into set slots.
• Protect. Put deep work on the calendar as a real block and defend it like a meeting.
• Hand off. Give a recurring task to someone better placed to do it, or automate it.

Pick one or two. A list of seven changes after a single audit usually means none of them stick.

Keep the raw record, not just the totals. Three weeks later, the detail of what happened on a bad Tuesday is often more useful than the weekly sum. If you write a regular retrospective, the audit gives it real material, and our guide to a deep work review shows one way to structure that.

Then run a shorter repeat audit. One week is usually enough to see whether a change held. If it did not, the repeat audit tells you what pushed back, which is often a meeting someone else controls.

Common mistakes

Auditing a fake week. People clean up their behavior once they know they are being recorded. Choose an ordinary week and resist the urge to perform for your own log.

Categories that describe everything and explain nothing. “Work” and “not work” is not a category system. Start from the question.

Sorting at the end of the week. By Friday, Tuesday is gone. Ten minutes each evening beats an hour on Saturday.

Treating app totals as categories. Six hours in a browser could be research, email, a design tool or a long video. App-level data is a starting point, not a category.

Judging instead of describing. The audit records what happened. If every block gets a moral label, you will start fudging the record.

No decision at the end. An audit that ends with a chart and no calendar change is just a chart.

Never repeating it. Without a follow-up, you cannot tell whether a change worked or merely felt like it worked.

Tools that help with a time audit

Software only helps with the recording step. Categories, comparison and decision are still yours. Most Mac time trackers can handle recording, and that guide covers the wider field. The details below are a comparison of each vendor’s own documentation as checked on October 4, 2026.

The four tools besides ours that come up most for audits are RescueTime (how it compares with Dayflow), Toggl (formerly Toggl Track) (Toggl on the Mac), Timing (Timing alternative) and Apple Screen Time (Screen Time vs. Dayflow).

Tool	What it does for this	Price
RescueTime	Runs in the background and tracks time on apps and websites automatically. Adds goals, alerts, focus sessions and distraction blocking. Desktop apps, iOS, Android and web; activity data is processed in the cloud.	Free Lite plan (limits: see the vendor’s pricing page). Focus (Solo) $7/month billed annually ($84 USD), or $9/month billed monthly. 14-day trial on paid plans.
Toggl (formerly Toggl Track)	Manual and real-time timers, timesheets and calendar integrations. The vendor also lists automated background tracking and a timeline in the desktop app. Web, Mac, Windows, iOS, Android and browser extensions.	Free plan for up to 3 users. Starter $9 per user per month billed annually, or $12 per user per month billed monthly. 30-day trial on paid plans.
Timing	Records time automatically across apps, websites and documents on the Mac, down to specific URLs and Mail threads. Data is stored locally unless you opt into sync. AI activity summaries on all plans.	No free tier. Professional $9 per month billed annually, or $11 per month billed monthly. 30-day trial, no credit card required.
Apple Screen Time	Built into macOS. Once App & Website Activity is on, shows which apps and websites you used and for how long, notifications and how often you use your devices, in daily or weekly views. App and website level only.	Free, built in.
Dayflow	Records the screen at one frame every 10 seconds and has AI write the day into a readable timeline. Recordings and the timeline are stored on your Mac. Export a date range as Markdown.	$0, MIT licensed. Optional Pro plan at $20 a month. Mac only, macOS 14 or later.

Dayflow is our product. It fits the recording step when you want a free, readable account of each day on one Mac, with screenshot analysis kept on-device through Local AI (Ollama or LM Studio). How the local and cloud processing modes differ is documented separately. It does not fit an audit that has to end in invoices, payroll approvals or team reports, and like any AI summary, its timeline can miss or misread work, so check it before you share anything built from it.

When Dayflow is the wrong choice

• The audit has to turn into billable hours. Timing wins on a Mac, with billing status tracking and invoicing integrations depending on plan. Toggl wins for teams that need billable rates, team reports and timesheet approvals.
• You want blocking once the audit is over. Dayflow has no website blocking. RescueTime has distraction blocking and focus sessions, and Apple Screen Time has downtime schedules and app category limits for free.
• You do not work on a Mac running macOS 14 or later. RescueTime and Toggl both run beyond the Mac.
• You only want a five-minute look at app totals. Apple Screen Time is already on your Mac and costs nothing.

The bottom line

A time audit is a short, honest record of one or two normal weeks, sorted into categories you chose for a specific question, then compared with what you intended. The record is the tedious part, and software can take it off your hands. The value comes from the last step: one or two concrete changes on the calendar and a repeat audit to see whether they held.

If you want to start today, pick your question, write down six categories and open a daily work log or turn on a tracker before tomorrow morning. If the week has already slipped away, where did my day go is a good place to begin reconstructing it.

Frequently asked questions

How long should a time audit last?

One to two normal working weeks. One day is too short, because a single day is mostly shaped by whatever happened to land on it. Two weeks usually covers your recurring meetings, a full cycle of weekly tasks and at least one unusual day. Avoid weeks with travel, holidays or a launch unless that kind of week is exactly what you want to understand.

Can I do a time audit with Apple Screen Time alone?

Yes, for a rough pass. Once App & Website Activity is turned on, Screen Time shows which apps and websites you used and for how long, in daily or weekly views. It does not know about projects or tasks, so a day spent in a browser shows up as browser time. It also records nothing until you turn it on, so enable it before the audit starts.

How many categories should a time audit have?

Five to eight is a workable range. Fewer than five and everything lands in one or two buckets, which tells you little. More than eight and you spend the audit arguing with yourself about where a half hour belongs. Keep one small catch-all bucket for time you cannot place, and split communication from meetings, since they usually need different fixes.

Should I change my habits during a time audit?

Try not to. The audit is a diagnosis, and changing behavior while you measure it gives you a record of a week you do not normally have. Knowing you are being recorded will nudge you a little anyway, which is one reason automatic recording helps. Save every change for after you have totaled the results and picked what to do about them.

How often should I repeat a time audit?

Repeat it after you make a change, to check whether the change held, and again whenever your role or workload shifts noticeably. A new job, a new manager, a reorg or a new big project are all good triggers. Between audits there is no need to keep scoring yourself; the point of an audit is a clear snapshot, not permanent self-monitoring.

What is the best tool for a time audit that has to end in client billing?

Not Dayflow. If the audit needs to turn into billable hours, Timing is the stronger pick on a Mac, with billing status tracking, report rounding and invoicing integrations depending on plan. For teams or anyone off the Mac, Toggl (formerly Toggl Track) offers billable rates, team reports and timesheet approvals on its paid plans. Dayflow has no invoicing, payroll approvals or team reports.

Is a manual time log good enough for a time audit?

It can be, if you keep it up. A paper or spreadsheet log every 30 minutes costs nothing and forces you to notice your day. The weak point is memory: entries written hours later tend to round off interruptions and short switches. If you go manual, write entries as you go and keep a tally of context switches alongside the time blocks.

Can a time audit help with time blindness?

It can make time visible after the fact, which is often the hard part with time blindness. An automatic record shows how long tasks really took instead of how long they felt. It is not a treatment and will not replace advice from a clinician, but a plain record of a normal week gives you something concrete to plan around rather than a guess.

Is it private to record my screen for a time audit?

It depends on where the data goes. With Dayflow, full screen recordings and the timeline are stored on your Mac, and Local AI keeps screenshot analysis on-device. If you choose your own cloud provider or Dayflow Pro instead, selected screenshots are processed off-device under those terms. Tools that send activity data to the cloud, such as RescueTime, are a different trade-off.

Is Dayflow free to use for a time audit?

Yes. Dayflow is $0 and MIT licensed, and runs on macOS 14 or later. There is an optional Pro plan at $20 a month that manages cloud analysis for you. If you connect your own AI provider instead, that provider's charges apply, since the free app does not include paid API usage. Local AI through Ollama or LM Studio uses your own hardware.