The AI time audit: how to find the work you should automate first

When a business decides to “do something with AI”, the first project is usually whatever someone saw in a demo. Sometimes that works. More often the team spends a month automating a task that happens twice a quarter, while the thing eating ten hours a week goes untouched.

The fix is boring and it works: measure first. I call it the AI time audit.

Step 1: Log a normal week

For five working days, everyone involved logs what they do in 15-minute blocks. It doesn’t need to be precise. A shared spreadsheet with four columns is enough:

• Task: what you did, in plain words (“replied to quote requests”).
• Minutes: roughly how long it took.
• Trigger: what started it (an email, a form, a date, a request).
• Tool: where you did it (inbox, CRM, spreadsheet, phone).

Pick a normal week, not the week of a launch or a holiday. You want the everyday reality.

Step 2: Tag every task

Group identical tasks, then tag each one with five questions:

1. How often does it happen? Daily, weekly, monthly or rarely.
2. How long does it take per week in total?
3. Is it rules or judgment? Could you write the steps down for a new hire, or does it rely on experience and taste?
4. What do the inputs look like? Structured (form fields, spreadsheets) or messy (emails, PDFs, calls)?
5. What happens if it’s done wrong? Annoying, costly, or seriously damaging?

The input question decides the tool. Structured inputs usually need ordinary automation. Messy inputs are where AI steps earn their place.

Step 3: Score and rank

Give each task a score from 1 to 5 on four factors, then multiply the first three and divide by risk.

Score = hours × frequency × rules ÷ risk. It’s not science, but it forces the right conversation. A task that happens constantly, follows clear steps and can be safely checked will float to the top. A rare, high-stakes task will sink, which is exactly right for a first project.

What usually comes out on top

After running this with a lot of small teams, the same tasks keep winning:

• Lead intake and first response. Reading new enquiries, qualifying them and replying fast.
• Meeting notes to CRM. Turning call transcripts into updated records and next steps.
• Document chasing. Reminding clients about missing paperwork on a schedule.
• Support triage. Sorting tickets by urgency and drafting replies to common questions.
• Report drafting. Pulling numbers together and drafting the commentary for a person to finish.

If one of these showed up in your audit, you’re in good company.

Step 4: Write the process down

Before building anything, write the steps for your top three tasks as if you were training a new hire. Include the exceptions: what happens when information is missing, when a customer is upset or when something doesn’t match.

This document becomes the agent’s instructions. It’s also where you’ll find problems in the process itself.

The traps to avoid

• Automating a broken process. If the manual version is confusing, the automated version will be confusing faster. Fix it first.
• Chasing rare tasks. A clever automation for something that happens monthly rarely pays back the build and maintenance time.
• Ignoring exceptions. The routine 80% is easy. Decide up front who handles the other 20%.
• Skipping the measurement. Log the time a task takes before automating it, so you can prove the result afterwards.

Put a number on it

Once you’ve chosen your top three, estimate what they’re worth. Multiply the weekly hours by the share you could realistically automate and by what that time costs you. The automation ROI calculator does the arithmetic and is deliberately conservative.

The bottom line

The audit takes a week and saves months of building the wrong thing. Log honestly, score everything, start with frequent and low-risk tasks, write the process down, and only then pick tools.