How to find which repetitive tasks to automate with AI
Most teams know they lose time to repetitive work, but not which tasks are worth automating first. This is the method we use in our AI automation audits, simplified so you can run it yourself in an afternoon.
Harnad AI · · 7 min read
Start with time, not technology
The question is not “where can we use AI?” but “where does our team’s time go on work that repeats?”. Start from the work, and only then ask whether AI is the right tool. Sometimes a simple form, a template, or a rule in an existing system is enough, and that is a good result too.
Step 1: List the work as it really happens
Sit with the people who do the work for a few hours, or ask each person to note what they do in a normal day. Managers often describe the process as it should run; the people doing it know the workarounds, the copying, and the chasing. Write down every task, however small.
Step 2: Spot the repetitive pattern
A task is a good candidate when several of these are true:
- It happens many times a day or week, in roughly the same way
- It starts from the same kind of input: a call, a message, a form, a document
- It involves copying information from one place to another
- It means answering the same questions again and again
- It involves waiting for, chasing, or checking something
- Mistakes come from tiredness or volume, not from lack of judgement
Step 3: Score each task
For each candidate, estimate the minutes it takes and how often it happens, and multiply to get hours a week. Then score it on four questions: Is the information it needs available digitally, or could it be? Does it follow rules, or need judgement each time? What happens if the system gets it wrong? How hard would it be to connect to the systems involved? The worksheet below puts this in one table.
Step 4: Pick the first one
Choose the task with the most hours a week, low risk if something goes wrong, and information that is already digital or easy to capture. Do not start with the most complex process in the business. A first system that ships in weeks and saves real time builds trust, and teaches you what to automate next.
What not to automate
Even in the tasks you do automate, keep a checkpoint where a person approves or takes over. Your team keeps the work that needs judgement; the system handles the repetitive part.
- Tasks that happen rarely: the saving will not cover the cost
- High-stakes decisions where a person must own the outcome
- Work that is mostly about relationships and trust
- Processes that change every time, with no stable pattern
Next step
If you want a second opinion, our AI automation audit does this with your team and adds a cost and savings estimate for each opportunity, so you know what to build first and what to leave alone.
Worksheet: score each repetitive task
Copy this table into a spreadsheet, or print this page, and fill in one row per task.
| Task | Minutes each | Times a week | Hours a week | Digital input? (Y/N) | Rules or judgement | Risk if wrong (L/M/H) | Systems involved |
|---|---|---|---|---|---|---|---|
| Answer “where is my order / appointment?” | |||||||
| Collect and check onboarding documents | |||||||
| Compile the weekly report | |||||||
| Your task here |
Want us to look at your process? It starts with one call.


