How to Use a “Time Audit” to See Where Your Day is Really Going

You finish most days tired, with the important work untouched, and you can’t say exactly where the hours went. Memory is a poor witness here. It shrinks meetings, forgets the ten-minute detours, and remembers the day as busier or emptier than it really was.

A time audit replaces that memory with a record. Log what you actually do for five working days in 15- or 30-minute slots, tag each block, then question the totals with four diagnostic questions. The output should be one or two schedule changes, not a new system.

First, decide how big an audit you need

A full week is worth it when the problem is persistent: deep work keeps sliding, your estimates are routinely wrong, or you work long hours without ever feeling caught up. If you only suspect one part of the day, start with a two-hour snapshot.

For the snapshot, pick your usual worst two hours. Every 15 minutes, write one line describing what you just did, then count the task switches and the minutes spent on what you meant to do. If the answer surprises you, run the full audit.

Set the rules before day one

• Length. Five consecutive working days catches the difference between a meeting-heavy Tuesday and a quiet Friday. Laura Vanderkam, who popularised whole-week logging in 168 Hours, tracks every hour of the week; do that if evenings and weekends are part of the question.
• Granularity. Vanderkam’s own guidance is to log in 15- or 30-minute intervals and check in a few times a day rather than constantly. Choose 15 if your day is fragmented, 30 if it runs in long blocks.
• Tags. Fix them now so you don’t invent categories halfway through. Four is enough: Deep Work, Shallow Admin, Unplanned Interruption and Time Leak. Tag meetings by what they demand: a design working session is Deep Work, a status update is Shallow Admin.
• Energy. Add a 1-5 score to each block. It costs two seconds and answers a question the time totals can’t.
• Behaviour. Don’t improve anything during the audit week. A log of your best behaviour tells you nothing.

Choose one of two logging methods

Both methods rely on short, frequent check-ins instead of end-of-day recall. The Day Reconstruction Method developed by Daniel Kahneman and colleagues showed that rebuilding a day systematically, episode by episode, produces far more usable data than a general impression of how it went. Logging every few hours means there is less to reconstruct.

Method 1: the retrospective calendar log

This keeps your planned day and your actual day side by side, in a tool you already open constantly.

1. In Google Calendar on a computer, click the plus next to “Other calendars”, choose “Create new calendar”, name it “Actual” and save. Google’s help page on creating a new calendar covers the same steps, and Outlook lets you add a blank calendar in a similar way.
2. Set three check-in reminders: 11:00, 14:00 and 17:00.
3. At each check-in, add events to “Actual” covering the previous hours, titled with what really happened: “Module 4 storyboard”, “Email and news sites”, “Broken quiz question from LMS admin”.
4. Put the tag and energy score in the event title and colour by tag: green for Deep Work, blue for Shallow Admin, orange for Unplanned Interruption, red for Time Leak.
5. Toggle “Actual” on and off over your normal calendar. The gaps between plan and reality show up at a glance.

This method suits people whose days are already calendar-driven, such as managers, consultants and account leads.

Method 2: the phone shortcut log

If you spend much of the day away from a desk, log from your phone and make each entry take a few keystrokes.

1. On iPhone, open Settings > General > Keyboard > Text Replacement, tap +, then enter a phrase and its shortcut, as described in Apple’s guide to setting up shorthand for frequently used text. On Android, Gboard’s personal dictionary offers similar shortcuts.
2. Create one shortcut per tag: “tdw” expands to “Deep Work |”, “tsa” to “Shallow Admin |”, “tui” to “Unplanned Interruption |” and “ttl” to “Time Leak |”.
3. Create “tlog” to expand to your entry template: “Planned: / Actual: / Energy:”.
4. Send each entry as a message to yourself in a note-to-self chat in WhatsApp, Signal or Slack. Every message is timestamped automatically.

One correction to a version of this trick that circulates online: text replacement inserts fixed text only, so “tlog” cannot produce the current date and time on its own. The timestamped chat handles that, and at the end of the day you copy the thread into a spreadsheet.

What one logged day looks like

Here is a single day from an e-learning course designer working from home, logged in slots of varying length.

Planned deep work: 4 hours 15 minutes. Actual: 2 hours. Two of the three biggest losses were self-started (news at 08:30, forums at 16:30), and the best-energy hour after 10:30 went to someone else’s problem.

Total the week, then ask four questions

Add up minutes per tag for each day and for the week; a SUMIF on the tag column takes five minutes. Then compare the logged total with the hours you believe you work. Picture a remote customer-success manager whose log totals 60 hours against an assumed 45, with 17 of them on email, ticket updates and team chat and 5 on unplanned browsing: that gap is the starting point, not a verdict.

For question 1, time blocking turns the gap into a plan you can defend. For question 2, the log effectively maps your biological prime time, so protect those hours first.

For question 3, batching is the standard remedy. Rubinstein, Meyer and Evans found that each switch carries its own cost for shifting goals and activating new rules; small per switch, it compounds across the dozens of tag changes a fragmented log reveals.

For question 4, if the leaks come from colleagues, the useful conversation is with your team about synchronous versus asynchronous communication norms.

Two audits, two different fixes

A university admissions director with back-to-back meetings

Three days of retrospective calendar logging showed committee, recruitment and file-review meetings booked at 30 and 60 minutes, with 5 to 10 minutes of prep and follow-up attached to each. The 15-minute gaps between them went to applicant and faculty email, which ran into the next call and made every meeting start late.

The changes: default meetings to 25 and 50 minutes, two 45-minute no-meeting blocks a day, and email in two 30-minute batches. The new buffers became breaks rather than inbox checks, and the meetings themselves got shorter agendas.

A freelance writer with an empty calendar

A week of notebook logging in 30-minute slots showed the highest energy scores between 8:00 and 11:00. Those hours went to industry news, website tweaks and file tidying, while “one-minute” admin tasks were scattered across the whole afternoon.

The changes: a fixed writing block from 8:30 to 11:00 with the phone in another room, 50-minute sprints with 10-minute breaks, and all invoicing and email in a single hour after lunch. Same method, opposite problems: one person needed to defend time from other people, the other needed structure against their own drift.

After the audit: keep it light and repeat it

Change one or two things, not ten. Pick the remedy for the question with the worst warning sign and run it for two weeks before judging it.

Keep a minimal form of tracking going in a free tracking or calendar app, tagging deep work blocks and totalling them on Friday, so drift shows up within a week instead of a quarter.

Rerun the full audit for two or three days each quarter, or whenever your role, team or schedule changes. When the log stops surprising you, the audit has done its job.