How to time your team's work in one week

Ask most owners where their team's time goes and you will get a confident answer. Ask them to put hours next to it and the answer gets quieter.

That is normal. Very few small businesses have ever timed their own work. But you cannot decide what is worth fixing, with AI or anything else, until you know what each task costs in hours. The good news is that you do not need software, a consultant or a month of tracking to find out. One ordinary week is enough to get a useful picture.

Here is how to do it with as little disruption as possible.

Why one week is enough

You are not trying to produce a perfect time study. You are trying to find the two or three tasks that take far more time than anyone realized. Those tend to show up quickly.

A week catches anything that happens daily and most things that happen weekly. It will miss work that only happens at month end or once a quarter, so you will add those separately. More on that below.

The goal is rough numbers you trust, not precise numbers nobody will collect.

Before the week starts

Pick the people. Choose the people who do the repetitive work: the ones handling the inbox, entering data, building reports, answering the same questions. You do not need everyone. Three to six people usually covers the work that matters.

Pick a normal week. Avoid holidays, your busiest season and weeks when key people are out. You want the work as it usually runs.

Explain why. This step matters more than any other. If your team thinks they are being watched or graded, the numbers will be wrong. Tell them plainly: you are looking for tasks that eat time so you can fix them, and nobody is being measured on output. The person who spends six hours a week on a miserable task is the person most likely to get relief from this.

Keep the format simple. A shared spreadsheet, a paper sheet on the desk, or a note on their phone. Whatever they will actually use.

What to write down

Ask each person to log blocks of work, not every minute. A block is any stretch of fifteen minutes or more spent on one kind of task. For each block, four things:

• The task, in their own words. "Entering supplier invoices." "Answering scheduling emails." "Building the weekly sales report."
• About how long it took. Rounded to the nearest fifteen minutes is fine.
• Where the information came from. An email, a PDF, a phone call, another system.
• Where it went. Which system, document or person it ended up in.

The last two are the ones people skip, and they are the most useful later. A task that means copying information from one place to another is often a good candidate for a fix. You can only see that if you know both ends.

Ask people to log as they go, or at least twice a day. Trying to reconstruct a whole day at five o'clock produces guesses.

During the week

Check in once, around day two. Look at what is coming in and fix any confusion early. Common problems: tasks described too vaguely ("admin"), blocks that are far too long ("emails, 4 hours"), or someone who has stopped logging because the week got busy.

If someone writes "emails, 4 hours," ask what the emails were about. Usually that block breaks into two or three distinct tasks, and one of them is the real cost.

Do not comment on how long things take. The moment someone feels judged for a slow task, they stop writing it down honestly.

Add the tasks the week missed

At the end of the week, ask each person one question: "What do you do every month or every quarter that did not happen this week?" Month-end close, quarterly reports, renewals, compliance paperwork, inventory counts.

For each one, ask how long it usually takes and how often it comes around. Then turn it into a weekly figure so it sits alongside everything else. For example, if a task takes eight hours once a month, that is roughly two hours a week.

Turn the logs into a list

Now combine everything. Group similar tasks under one name, add up the hours across all the people who do them, and sort from largest to smallest.

You will end up with a short table: task, total hours per week, who does it, where the information comes from and where it goes. That table is the most useful document most small businesses do not have.

A few things to look for as you read it:

• Big numbers nobody mentioned. The task everyone complains about is often not the largest. The one at the top is often something people consider "just part of the job."
• The same task done by several people. Small amounts of time spread across a team add up fast.
• Copying between systems. Any task where the "from" and "to" columns are both software is worth a close look.
• Work that waits on one person. If a task can only be done by one person, it may cost more than its hours suggest when that person is busy or away.

What to do with the numbers

The table does not tell you what to fix. It tells you where to look. The next questions are whether a task can be fixed, what fixing it would cost, and what the saved hours are worth. We cover the last one in a separate post on putting a dollar value on hours saved.

This is also exactly the work our audit does, done for you and taken further. We time three to five workflows with the people who do them, price every fix, and rank them by what they are worth. It takes 5 business days at $2,500 fixed. If you have already done the timing yourself, you will get more out of it, because we can start from your table instead of a blank page.

Start this week

Pick your people, explain why, and hand out the sheet on Monday. By Friday you will know more about where your hours go than most businesses ever find out. If you want a quick sense of your readiness first, take the free AI readiness quiz. Or book thirty minutes and we will help you plan the week.