Questions we answer Capacity and workload

Repetitive admin is eating the week

Work out how much of it should exist at all before automating any of it. Some repetitive admin is a process nobody has simplified, some is a good candidate for software, and a little of it genuinely needs a person.

Start from this question

Free · a few minutes · starts from “I think AI could help”

The short answer

Repetitive administration is the strongest case for automation in most teams, and the weakest case for hiring. The sequence that works is to write down what the steps actually are, remove the ones that exist only because of how something else is set up, and then automate what is left — starting with whatever the systems you already pay for can do. A person hired to absorb this work absorbs it permanently, and the underlying waste is still there next year.

Repetitive admin is the most automatable work in most teams and also the most over-automated. The order that works is: stop the steps that do not need to happen, simplify what is left, then automate whatever survives.

It is worth being specific about where the week actually goes. Re-keying information between systems, chasing people for answers, formatting documents and arranging meetings are four different problems with four different fixes, and only some of them need AI at all.

Is it really this?

Worth checking before you spend anything. These are the signals that tend to tell the two apart.

Signs it is

You can name the tasks, and they arrive on the same rhythm with the same steps each time.
The same information is typed into more than one place.
The people doing it can describe it start to finish without pausing.
The volume has grown while the method has not changed.

Signs it's something else

Each case looks similar but the decisions inside it differ, which is judgement wearing an admin costume.
The admin exists because something upstream is unreliable, and the chasing is a symptom of that.
Nobody has written the steps down, so what looks like one process may be several.
Most of the time goes on exceptions rather than on the standard path.

What's usually behind it

Two systems that do not talk to each other, with a person in the middle.
Reporting that was asked for once and has been produced ever since.
Approval steps added after something went wrong, which nobody has revisited.
Skilled people doing work that was never meant to be theirs, because it arrived without an owner.

What people usually get wrong

Automating a process before simplifying it, which makes the wrong thing happen faster and harder to change.
Buying a tool for each symptom, and ending up with more systems to keep in step.
Assuming the work is uniform when the exceptions are where the hours actually go.
Automating without deciding who owns it when it breaks, which it will.

The options, and when each one fits

In no particular order. Which of these fits depends on your situation, not on the question you typed.

Stop some of it
Steps exist out of habit and nobody would miss the output.
Connect the systems you already have
The work is moving the same information between tools that could exchange it.
Switch on what you already pay for
Your existing software covers this and nobody has configured it.
Give people AI assistance
A person's judgement is needed, but the drafting, summarising and checking around it is not.
Automate the workflow
The steps are stable, frequent, documented and low-judgement, and somebody will own it when it breaks.

When doing nothing is the right call

If the admin is irritating but small, and a busier quarter is coming, leaving it alone is a legitimate choice. Automating badly costs more than a few more weeks of a task everybody already knows how to do.

What the diagnostic asks

Where the time goes: drafting, a repetitive process, analysis or customer contact.
How repeatable the work is, how much judgement it needs, and how often it comes round.
How sensitive the information is, what happens when it goes wrong, and whether software is already in place.

“I don't know” is always an answer. Nothing is assumed on your behalf.

The routes it weighs

Every diagnostic weighs all ten routes. These are the ones that tend to matter for this question — a description of the rules, not a promise about your answer.

Process improvement
Change how the work flows — remove steps, name an owner, fix the hand-offs.
AI Assist
Keep a person in charge and give them AI for drafting, summarising, checking or analysis.
AI Agent
Delegate a defined, repeatable workflow to software inside boundaries you set, with human oversight.
Redistribute
Move ownership of the work to where it fits, and make that explicit.
Outsource
Hand a defined, ongoing scope of work to an external provider.

What changes the answer

Work that exists in nobody's written-down process has to be described before it can be automated.
Exceptions that take most of the time mean the standard path is not where the saving is.
Sensitive information limits what can run without a person, whatever else is true.

Get your own read

A handful of short questions, then the strongest route for your situation, what's also credible, what we still don't know and what would change our view. No account, no setup.