Skip to content
ruam.ai

How to do a time audit (free template)

A time audit shows where your work hours really go. Log one week in 30-minute blocks, sort them, compare with your guess. Free template and CSV included.

Indrayudh Sen

, 8 min read

A time audit is a record of where your working hours actually go, kept for long enough to see a pattern. To do one, log one work week in 30-minute blocks as you go, sort each block into four or five categories, and compare the totals with what you expected. The gap between the two is the finding. This guide has a step-by-step method, a template you can copy below, and notes on what to do with the results.

Why memory is the wrong tool

Most people already have a feel for where their week goes. The trouble is that the feel is built from memory, and memory is a poor timekeeper.

Researchers have argued about this for years in the case of work hours. A 2011 paper in the BLS Monthly Labor Review, “The overestimated workweek revisited,” compared what people said they worked with time diaries and concluded that self-reported hours run above diary hours. The pattern it pointed to was that people who report long hours overstate them the most.

That claim was challenged. A 2014 article in the same journal, “Is the workweek really overestimated?,” reran the comparison. It found that average respondents in the Current Population Survey, who were asked about the previous week, reported their actual hours with very little bias. It also found that the earlier pattern is what you would expect from reporting error alone, so it does not show that people who really work long hours are the ones who overstate. The answer, it says, depends on the question you ask and how work is defined.

So the honest summary is mixed. How many hours you worked last week may be something you can state fairly well. How those hours were split between tasks, and how long each task took, is a different question, and that is what a time audit measures.

On that second question the evidence is clearer. In a classic set of studies on the planning fallacy, people predicting how long their own tasks would take were too optimistic. They leaned on a plan in their head and gave too little weight to how long similar tasks had taken them before (Buehler, Griffin and Ross, 1994). An audit replaces the plan in your head with a record.

How to do a time audit, step by step

You need a week, a place to write, and about two minutes at each break. Don’t change how you work during the week. The point is to see your normal.

1. Write your expected split first

Before you log anything, write down how you think a normal work week divides. Pick four or five categories that suit your job. A common set:

  • Focused work (the main thing you are paid for)
  • Meetings and calls
  • Email and messages
  • Admin (invoices, scheduling, expenses, tools)
  • Other or unplanned

Next to each, write the hours you expect in a 40-hour week, or whatever your week is. Do this before the log starts. If you peek at data first, you will quietly adjust your guess.

2. Log five working days in 30-minute blocks, as you go

Set a repeating reminder every 30 minutes. When it goes off, write down what you did in that block and pick a category. If a block had two things in it, write the one that took most of the time.

Do it as it happens, not at the end of the day. Peter Drucker recommended recording time as it happens, in The Effective Executive, rather than rebuilding it from memory later. Reconstructing a day at 6 p.m. gives you the day you remember, which is usually the day you meant to have.

A 30-minute block is coarse on purpose. It is quick enough to keep up and fine enough to show a pattern. Stanford’s Center for Teaching and Learning suggests a similar rhythm of logging every 30 to 60 minutes, and writing what you actually did rather than what you think you should have done (Stanford CTL, time auditing).

3. Sort and total

At the end of the week, count the blocks in each category. Each block is half an hour, so divide the count by two to get hours.

4. Ask three questions

Stanford’s guide lists reflection questions for the record. Here are three, adapted:

  1. Where did my time go? Which categories were bigger than expected? Did anything eat time you did not plan to give it, such as the minutes between tasks?
  2. How long do tasks really take? Which kinds of work ran longer than your guess, and which ran shorter?
  3. When did I do my best work, and when did I drift? Look at which times of day your focused blocks cluster in, and where the interruptions sit. Were your breaks chosen or accidental?

Write one or two plain sentences for each. Those sentences are your audit result.

A time audit template you can copy

Use the tables below on paper, in a doc, or in a spreadsheet. The first is one day. Copy it for each day of the week.

Daily log (one day, 30-minute rows)

TimeWhat I didCategory
9:00
9:30
10:00
10:30
11:00
11:30
12:00
12:30
1:00
1:30
2:00
2:30
3:00
3:30
4:00
4:30

Weekly summary

CategoryExpected hoursActual hoursDifference
Focused work
Meetings and calls
Email and messages
Admin
Other or unplanned
Total

Difference is actual minus expected. A positive number means the category took more than you thought.

Paste into Google Sheets

Copy the block below, open a blank Google Sheet, click cell A1 and paste. If everything lands in one column, use Data, then “Split text to columns” and choose comma. Log your blocks in the first table, then count each category’s half-hour blocks and divide by 2 to fill in the actual hours. For example, in the Actual hours cell for Focused work, enter =COUNTIF(D:D,"Focused work")/2. Add Tuesday to Friday by copying the Monday rows above the summary table.

Day,Time,What I did,Category
Mon,9:00,,
Mon,9:30,,
Mon,10:00,,
Mon,10:30,,
Mon,11:00,,
Mon,11:30,,
Mon,12:00,,
Mon,12:30,,
Mon,1:00,,
Mon,1:30,,
Mon,2:00,,
Mon,2:30,,
Mon,3:00,,
Mon,3:30,,
Mon,4:00,,
Mon,4:30,,

Category,Expected hours,Actual hours,Difference
Focused work,,,
Meetings and calls,,,
Email and messages,,,
Admin,,,
Other or unplanned,,,
Total,,,

The first block is Monday. Copy and paste the rows four more times for Tuesday to Friday, changing the day.

Reading the results

Look at the Difference column first. Most audits turn up a few of the same surprises.

  • Switching. Many short blocks of email, chat and quick checks between longer tasks. Each is small, but together they can crowd out the work you call your real job. Count how many separate things you touched in a day.
  • Meetings. They are often a bigger share than anyone remembered, especially the ones that are not on the calendar, like a “quick call” that ran an hour.
  • Admin. Invoices, scheduling, expenses and tool upkeep tend to spread thinly across the week, which is why they feel small and total large.
  • Focused work. Often the smallest of the five relative to what you expected. This is the number to protect.

Then decide what to do about each large gap. Three moves cover most cases:

  • Cut. Drop the meeting with no decision, the report nobody reads, the recurring task that no longer has a purpose. If you can’t say what would break, stop doing it for two weeks and see.
  • Delegate. Anything that does not need you in particular. If it takes you 30 minutes a week and costs someone else 10, hand it over.
  • Batch. Group the small things into fixed windows. Check email at set times instead of all day, do all invoicing in one block, and put your meetings back to back so a free stretch stays free.

Then fix your estimates. If a task you planned for one hour took 90 minutes, plan it that way next time. Our free time estimation check compares your guesses with the clock and gives you a multiplier. If you find days hard to plan, the ADHD day planner uses that same idea and works for anyone.

Repeat the audit in a few months, or after a big change in your work. One week shows you a pattern. Two weeks apart shows whether your changes held.

The automatic version

Writing a note every 30 minutes works, and it is how you learn the method. It is also tiring, and you will miss blocks. An automatic tracker logs the day for you, so you review a record instead of making one. Here is how several tools handle it.

ToolHow it recordsWorth knowing
RescueTimeRuns in the background and tracks app and website use automaticallyOffers a two-week free trial, then a paid plan. Also has goals, alerts and a timesheets tool. Checked November 2026.
TimingAutomatic tracker for MacA strong choice for a detailed record of every app on a Mac. Checked November 2026.
Toggl TrackA timer, plus a desktop timeline of apps and sites that you turn into entriesFree plan for up to 3 users. See Ruam vs Toggl Track. Checked October 2026.
TimelyA private automatic timeline you turn into your own timesheet entriesRecords page titles, file paths and timestamps of apps in use. See Ruam vs Timely. Checked October 2026.
RuamCounts work time automatically on paid plans; Free starts the day with one tapFree for one person; Solo is $6 a month.

Toggl Track and Timely details come from our comparison pages, checked in October 2026. The others were checked in November 2026. Ruam is our product, which is a bias to keep in mind. If you want the broadest record of what happens on a computer, one of the app-level trackers above may suit you better. If you want a simple record of hours by project, read on.

Where Ruam fits

Ruam’s Logbook shows each person’s own day, sorted by project and client, so you can read it the way you would read a finished audit. It records hours during work time, plus the site name and page title, which you see first. It never takes screenshots or logs keystrokes. Projects, one for each client, are on Solo and up. Free starts your day with one tap and keeps your last 30 days. See the Ruam pricing for what each plan includes.

A day in the Ruam Logbook, with time blocks by task and hours by category
The Logbook shows where a day went, like a finished time audit. Sample data.

Ruam can also answer from Claude or ChatGPT, for example “how many hours did I work this week?” That is in closed beta. See /mcp.

What to do next

Print or copy the template and write your expected split today, before you log anything. Then log five days and fill in the weekly summary. Pick the single biggest gap and make one change to it for two weeks. If you would rather not log by hand, try an automatic tracker. Ruam is free for one person.

Questions

What is a time audit?

A time audit is a record of how you spend your working time, kept for long enough to show a pattern. Most last a week. You log what you do, sort it into categories, and compare the totals with what you thought.

How long should a time audit last?

One working week is the usual minimum, since it covers your regular meetings and admin. If your work changes a lot from week to week, such as freelance or project work, two weeks gives a fairer picture.

How often should I log?

Every 30 minutes is a good balance. Every hour is easier to keep up but hides short interruptions. If 30 minutes feels like too much, start with 60 and move to 30 once the habit sticks.

Do I need software for a time audit?

No. Paper or a spreadsheet works, and the template above is built for that. Software helps when you keep forgetting to log, because it records for you.

What categories should I use?

Four or five. Too many makes sorting slow and hides the pattern. Pick the groups that match how your job is split, and add an "other" so nothing is left uncategorized.

Is a time audit the same as time tracking?

They overlap. Tracking is usually ongoing, often for billing. An audit is a short, deliberate study with a question in mind: where does my time go, and what should change?

Hours that count themselves.

By project, client and shift. No screenshots. Free forever for one person.

Try Ruam for free
Indrayudh Sen

Founder, Ruam

Indrayudh Sen, the founder of Ruam, has managed remote teams since 2020 and has run a cold email agency.

Newsletter

New articles by email.

One email when there's a new article. No spam, unsubscribe any time.

See our Privacy Policy.

More articles