The 168-hour audit has a reputation for being more demanding than it turns out to be. The perception is that tracking every hour of a week requires constant vigilance. The reality is that most people need about 30 seconds per transition — roughly ten to fifteen short entries per day.
Here is the exact process, following Laura Vanderkam’s methodology as described in 168 Hours and her subsequent work.
Step 1: Write Your Pre-Audit Estimates
Before you track a single hour, write down your best guess for the upcoming week.
Estimate the following:
- Total hours you expect to work (including evenings and weekend work)
- Total hours of sleep
- Hours of exercise
- Hours with family or close friends
- Hours on entertainment, screens, or leisure
- Hours on household logistics and chores
Do not spend more than five minutes on this. The estimates do not need to be precise — they need to be honest. Their purpose is to surface what you currently believe about your time, so you can compare it against what you actually observe.
Keep this list somewhere you can find it after the week ends.
Step 2: Choose Your Logging Format
You have three practical options.
Paper or notebook. Draw a grid: days across the top, time blocks down the side. Use 30-minute rows. This is analog-friendly and does not require any battery.
Spreadsheet. Build a 336-row sheet (168 hours × 2 rows per hour, one for each 30-minute block). Column A for the time, Column B for the activity, Column C for the category, Column D for brief notes. This format makes analysis faster at the end of the week.
Notes app or voice memo. If a grid feels like too much friction, a running log in your notes app works. Write the time, what you just finished or started, and a one-word category label. You can structure it later.
The right format is the one you will actually sustain for seven days. The most elaborate system you abandon on Wednesday is less useful than a rough notebook you complete.
Step 3: Track in Real Time at Transitions
The single most important rule: log at the moment of transition, not at the end of the day.
When you switch from one activity to another — finish a meeting, sit down for lunch, start your commute, pick up your phone — write down what you just stopped and what you are starting. Thirty seconds, no more.
John Robinson’s time-diary research established why this matters: end-of-day reconstruction systematically distorts the record. You compress time spent on low-status activities (browsing, informal chat, waiting) and expand time spent on activities that feel important (focused work, productive conversation). Real-time logging removes most of this distortion.
You do not need to log every micro-transition. If you are deep in work for three hours with a few brief interruptions, a single “focused work, 9–12pm” entry is fine. The granularity that matters is between major activity categories, not within a sustained block of the same activity.
Step 4: Use Vanderkam’s Four Categories
Assign each logged block to one of four domains:
Work — paid professional activity, including job-related email, commuting, and job-adjacent administration.
Personal care — sleep, eating (as a standalone activity), exercise, hygiene, medical appointments.
Relationships and family — time where a relationship is the primary activity. Watching television with a partner on the couch counts; being in the same room while both of you are on separate screens probably does not.
Discretionary — everything else: entertainment, hobbies, social media, reading for pleasure, religious practice, volunteering, uncategorized transition time.
You can add sub-categories if your situation requires more precision. Freelancers often split “work” into client work and business development. Parents often split “relationships” into time with children versus time with a partner. These refinements are useful as long as they do not create so many categories that logging becomes burdensome.
Step 5: Add One Context Note Per Block
Beyond the category label, add a brief annotation for each block. “Work” does not tell you much. “Work — quarterly board prep” and “Work — inbox triage” are two very different activities even though they share a category.
Context notes do not need to be long. One to five words is enough. Their value appears in the analysis phase, when you are trying to understand not just how many hours went to work, but what kind of work filled those hours.
Step 6: Complete the Full Seven Days
This step sounds obvious and is the one most people fail.
The audit requires all 168 hours — including both days of the weekend. Weekend data is where most of the “found time” lives. It is also where many people’s self-narratives about how they spend their non-work hours are most wrong.
If Wednesday feels tedious, that is normal. The friction peaks around the midpoint. Keep going. The Saturday-Sunday data is often the most revealing portion of the entire audit.
Step 7: Total Each Category and Compare to Estimates
Once the week ends, total the hours in each category. Then pull out your pre-audit estimates.
Run the comparison directly:
| Category | Estimated Hours | Actual Hours | Difference |
|---|---|---|---|
| Work | ? | ? | ? |
| Sleep | ? | ? | ? |
| Exercise | ? | ? | ? |
| Relationships | ? | ? | ? |
| Discretionary | ? | ? | ? |
| Logistics/chores | ? | ? | ? |
The gaps are your data. You are looking for two things: the direction of the gap (did you overestimate or underestimate?), and the magnitude (a two-hour gap is different from a twelve-hour gap).
Vanderkam’s research with readers typically finds the largest gaps in discretionary time (usually higher than estimated) and work hours (often lower than claimed for those who feel very busy, but sometimes higher for those who feel productive).
Step 8: Run the Alignment Check
With your totals in hand, ask three questions explicitly.
Are my hours reflecting my stated priorities? Write down your top two or three priorities — the things you say matter most to you. Is there evidence of those priorities in the numbers?
Where is time going that I did not consciously choose? Look for the categories that surprised you. These are the allocation decisions you are making by default rather than by design.
What is one reallocation I could make? Vanderkam’s approach is not to overhaul the whole week — it is to identify one intentional shift. Move one hour from a lower-priority use to a higher-priority one, and notice whether that shift is sustainable.
Step 9: Repeat at the Right Interval
One audit is useful. A pattern across multiple audits is actionable.
Run the audit quarterly for the first year. Each repetition takes less setup time than the first, and the comparison across quarters surfaces seasonal patterns and structural changes that a single audit cannot show. After the first year, an annual audit is sufficient for most people unless a major life or work transition warrants an off-cycle run.
What “Properly” Actually Means
Running the audit “properly” does not mean achieving perfect granularity or zero reconstruction. It means:
- Tracking all 168 hours, including sleep and weekends
- Logging in real time rather than at the end of each day
- Writing your pre-audit estimates before the week begins
- Using the data for the alignment check, not just as a log
The rest is implementation detail. The format, the app, the exact category structure — these are adjustable. The four steps above are the methodology.
Set your audit start date now — pick the next Monday that is likely to be a reasonably normal week — and write your pre-audit estimates before that date arrives.
Related:
- The Complete Guide to the 168-Hour Audit
- The Deep Framework Behind the 168-Hour Audit
- Five 168-Hour Audit Variants Compared
- 168-Hour Audit Framework
Tags: 168-hour audit, time tracking, Laura Vanderkam, how to track time, weekly time audit
Frequently Asked Questions
-
When should I start the 168-hour audit?
Start on a Monday that is likely to be reasonably representative — not a vacation week, major conference, or public holiday. Run through the following Sunday night to capture the full 168-hour cycle. -
Do I need special software to do the 168-hour audit?
No. Vanderkam herself used a simple spreadsheet and paper log. Any system you will actually maintain for a full week works — a notebook, a notes app, or a spreadsheet. -
How do I handle days that are very atypical?
Log them accurately and note the anomaly. If the whole week is unusual, consider it a practice run and run the audit again the following week. A single atypical day does not invalidate the week's data. -
What if I forget to log for several hours?
Reconstruct as best you can using calendar events, messages sent, or memory — and note those hours as 'reconstructed' so you know to treat them as less reliable during analysis.