How do I do a time audit with AI?

Arjita Sethi · Updated November 13, 2026 · 4 min read

AI for Ops

You do a time audit with AI by letting it read the record of what you actually did, your calendar and your sent email from the last four weeks, and asking it to tag that time into repeat, judgment and relationship work. It then flags repeat jobs you forgot to list and suggests which ones to hand off first, and you approve every change. Build with AI Club teaches this as a read-only job: the AI looks at what happened and touches nothing.

Why your memory makes a poor time audit

Most time audits come from memory, and memory is a terrible accountant. It forgets the eleven little emails, the three reschedules and the thing you do every Thursday without noticing. Your calendar and your sent folder don't forget, so they make a far more honest starting point.

What you need before you start

  • A first list of your tasks, sorted into three piles and ranked by hours saved, saved as a file in one folder. If you haven't made one, write a quick 15-minute version from memory first, so the AI can check your guess against the record.
  • An AI tool that can connect to your calendar and email. In Claude, that means connecting Google Calendar and Gmail, or Outlook mail and calendar if you work in Microsoft.
  • About thirty minutes.

Step 1: Connect with read-only intent

Connect your calendar and email, and be precise about what the AI may look at. Point it at four weeks of calendar and your sent mail only. Leave your inbox and your drafts out, because the audit is about what you did with your time. Before you connect any tool, run it through a safety check: how it signs in, what it can see, what it can do, and whether you can disconnect it.

Step 2: Write the job in four parts

Give the AI a clear brief with four parts:

  1. What to read: my calendar and sent email from the last four weeks, plus the task list and ranking in this folder.
  2. What to do: tag my time into repeat, judgment and relationship work, and find repeat jobs that are missing from my list.
  3. What to hand back: a short report with the hours in each pile, the repeat jobs I missed and a suggested new ranking.
  4. What it may never do: send, delete, reply, accept or change anything.

Step 3: Review the report and approve changes

Read the report the way you would read a new assistant's first week of notes. Look for the repeat job you never wrote down, because there is often one. Approve the ranking changes you agree with and ignore the rest, because nothing changes until you say so.

Step 4: Pick your next Job Card

Take the top task from the updated ranking and write a Job Card for it: the trigger, the task, the outcome, the check moment and the line it must never cross. That card becomes your next skill.

FAQ

Is it safe to let AI read my email? Keep it narrow: give it sent mail only, make it read only, write a clear never list, and connect it only after the tool passes your safety check. You can disconnect it when the audit is done.

How often should I redo the audit? Once a month works well, because your work shifts and new repeat jobs creep in.

Can I run it automatically? You can set it as a recurring task in some tools, and it still leaves a draft for you to approve. Check when your tool runs scheduled tasks, because some only run while your computer is awake and the app is open.

Learn it with me

My next free AI 101 class at SHACK15 in San Francisco is Wednesday, Nov 18, 6 to 7 PM PT: The One-Person AI Media Setup. Every seat is taken, and the waitlist is open at luma.com/build-kgkg.

In the meantime, this week's Build with AI Club YouTube lesson, 4 Claude skills I would set up before anything else, shows how to save a job like this audit as a skill. Watch it on the Build with AI Club YouTube channel