Workshop playbook

The Time Audit Playbook

How to find what your team should automate first, from your own time data.

This playbook gets you a ranked list of what your team should automate first, built from your own time data, in about an hour. It follows the four steps from the Rize workshop How to Identify Automation Opportunities With a Time Audit (Nov 17, 2026).

Last updated:

Workshop recording coming soon

← Back to the workshopAll Rize workshops and playbooks

Why most AI efforts stall

  • No idea where to start. Everyone says “use AI more”, but nobody knows which work to point it at.
  • The gains stay local. In a study of 515 startups, firms taught to map AI to their workflows found 44% more AI use cases and made 1.9x the revenue of firms with the same tools and training.
  • No way to tell if it's working. Without a baseline, you're guessing whether AI saved time or just moved it around.

Source for the study: INSEAD working paper, Kim, Kim and Koning, 2026 →

A time audit fixes all three. You map the real week (where to start), score and pick (what to automate), then measure before and after (is it working).

The four steps

  1. See the real week. Real data, not memory.
  2. Spot the repeats. Find the work that happens every week.
  3. Score them. Not everything repetitive should be automated.
  4. Pick 3 and measure. Decide, then check it worked.

Throughout, we follow Sam, the ops lead at a 20-person agency (a made-up example).

See the real week

Start with one normal week of real data. Timesheets filled in from memory miss the small, repeated work, and that's exactly the work you're looking for.

Sam's example

Client workMeetingsAdmin and repetitive
Friday timesheet, from memory30h6h4h
Tracked automatically18h11h13h

Memory missed 9 hours of admin and repetitive work in a single week.

How to get one real week

  • With Rize: install the desktop app and let it run for one normal week. It tracks automatically, with no timers, and tags time to clients and projects.
  • Without a tracker: use your calendar plus the activity history in the tools your team works in (email, Slack, your project manager).

Prompt (ask the Rize agent, or Claude or ChatGPT with the Rize connector):

Prompt
Summarize my team's tracked time last week by client work, internal work and admin.

Spot the repeats

Sort the week into client delivery, internal work, and admin and repetitive work. Then list the tasks that come back every week. Look across days, people and clients: the same task spread thinly over five people is easy to miss.

Sam's example

780 tracked hours. 55% client delivery, 25% internal, 20% admin and repetitive (156 hours). The repetitive tasks:

TaskTeam hours a week
Weekly status reports14
Meeting notes and follow-ups11
Slack and email triage10
Reporting data pulls9
Chasing timesheets8
Resizing and exporting assets7
Invoice prep6
Scheduling5
Total70

Prompts:

Prompt
Which repetitive tasks took the most time last week? Show team hours for each, who did them, and for which clients.
Prompt
Look at my last two weeks and list the tasks I do every week, with hours spent on each.

Score them

Not everything repetitive should be automated. Score each task on three things, then rank by the score.

Score = Hours a week × Repeatable (1 to 5) × Safe to hand off (1 to 5)

Higher score means automate first.

RatingRepeatable: how rule-based is it?Safe to hand off: what if AI gets it wrong?
5Same steps every time, clear inputs and outputsInternal only, easy to check, no harm if wrong
4Mostly the same, a few judgment callsA person reviews it before it goes anywhere
3A template with real variationClient-facing but low stakes
2Different every time, needs contextClient-facing and visible mistakes
1Pure judgment or creative workSensitive data, money, legal or relationships

Sam's ranked list

TaskHrs a weekRepeatableSafeScore
Reporting data pulls955225
Weekly status reports1444224
Chasing timesheets855200
Meeting notes and follow-ups1144176
Resizing and exporting assets754140
Scheduling54480
Invoice prep64372
Slack and email triage102360

Slack triage is one of the biggest time sinks but scores last, because it's hard to hand off safely. Optimise for quality first, and the time savings follow.

Prompt
For each repetitive task, rate Repeatable (1 to 5, how rule-based it is) and Safe to hand off (1 to 5, 5 = low risk if AI gets it wrong). Score = hours per week x Repeatable x Safe. Show a table ranked highest first, with one line on each rating.

Pick 3 and measure

Pick your top three, make one decision for each, and set a date to check that it worked.

  • Look at the chain, not just the task. Tasks often feed each other. Sam's top two are one chain: pull the data, build the deck, send the status update. Automate the chain end to end, or the time you save on one step gets stuck at the next.

Make one decision per task

DecisionWhen to use itSam's tasks
AutomateHigh score, rule-based, safe to hand offThe reporting chain (data pulls and status reports), meeting notes
DeleteThe work only exists because of a broken processChasing timesheets (automatic tracking ends it)
DelegateRepetitive but needs a person, or a better tool already existsInvoice prep, scheduling
Keep humanNeeds judgment, context or relationshipsSlack and email triage
  • Set a baseline and check in 30 days. This week's numbers are your baseline. In 30 days, track the same tasks again and compare. If the hours didn't go down, find out where the time moved. The hardest part of AI is usually getting people to change how they work, not the tech.

The one-slide plan for leadership

  • Automate the reporting chain and meeting notes: 34 hours a week, about 136 hours a month
  • Delete timesheet chasing: 8 hours a week
  • Check again on Dec 17
Prompt
Turn my ranked list into a one-slide plan: the top 3 decisions (automate, delete, delegate or keep human), hours at stake per month (hours per week x 4), and a check date 30 days out.

The Time Audit report

This one prompt runs the whole audit: totals, repetitive tasks, scores, chains, decisions and the one-slide plan. Run it once for your baseline, then schedule it monthly so the 30-day check happens on its own.

Prompt: the Time Audit report
Run a time audit of the team's last full week to find automation opportunities.

1. Totals: tracked hours, split into client delivery, internal work, and admin and repetitive work (hours and %).
2. Repetitive tasks: find work that recurs every week (the same kind of task across days, people or clients), using labels, time entries and window titles. For each: task, team hours per week, people involved, main clients.
3. Score each task:
   - Repeatable, 1 to 5: how rule-based and consistent it is.
   - Safe to hand off, 1 to 5: 5 means low risk if AI gets it wrong. Client-facing judgment and sensitive data score lower.
   - Score = hours per week x Repeatable x Safe. Show a table ranked highest first.
4. Chains: flag tasks that feed each other (for example data pulls that feed status reports) and recommend automating them together.
5. Decision for each task: Automate, Delete, Delegate or Keep human, with one line on why.
6. One-slide plan: the top 3 decisions, hours at stake per month (hours per week x 4), and a check date 30 days out.

Keep it plain. Use only numbers from the data.

Run it in Rize

  1. Go to Reports and create a new report from scratch.
  2. Name it “Time Audit: Automation Opportunities”, set it to your team, and choose the last 7 days.
  3. Paste the prompt into the AI analysis and run it.
  4. Turn on a monthly schedule so it re-runs and you can compare against your baseline.
  • Run it in Claude or ChatGPT: connect the Rize connector, paste the prompt into a new chat, and ask it to use last week's data. To repeat it monthly, use a scheduled task in Claude or ChatGPT.

Time audit template

Copy these columns into a spreadsheet, one row per repetitive task. Fill in hours from your tracked week, rate the two 1 to 5 columns with the rubric in Step 3, and sort by score.

TaskHours a weekRepeatable (1 to 5)Safe to hand off (1 to 5)ScoreFeeds intoDecisionOwnerCheck date
Reporting data pulls955225Weekly status reportsAutomateSamDec 17

Score = Hours a week × Repeatable × Safe to hand off. Hours at stake per month = hours a week × 4.

Want it filled in for you? Build your time audit template →

Prompt cheat sheet

StepPrompt
See the real weekSummarize my team's tracked time last week by client work, internal work and admin.
Spot the repeatsWhich repetitive tasks took the most time last week? Show team hours for each, who did them, and for which clients.
Spot the repeatsLook at my last two weeks and list the tasks I do every week, with hours spent on each.
Score themFor each repetitive task, rate Repeatable and Safe to hand off from 1 to 5, multiply by hours per week, and rank them.
Pick 3Which of these tasks feed each other? Group them into chains.
MeasureCompare this week to my baseline week for the same tasks. Where did the time go down, and where did it move?

Next steps

If you want toGo here
Watch the workshop recordingThe Rize workshops page
Try it yourselfStart a free Rize trial
Roll it out to a teamBook a demo
Automate project time trackingThe AI Time Tracking Playbook
See which clients make moneyThe Client Profitability Playbook

Run your own time audit

Start a free Rize trial, track one normal week, and find what to automate first.

Team? Book a demo →

Next workshop: December, date coming soon. Subscribe on Luma.

Back to the workshop page