Admin That Grew
The category that starts small, absorbs everything that does not fit elsewhere, and turns out to be a fifth of the week.
Every category scheme has one bucket for the things that are not the work. It grows, and by the time anybody looks it contains several different problems. Teams investigating the same pattern can use the healthcare guide to see where working time is being absorbed, then discuss the surrounding process; the record should reveal friction without turning ordinary pauses into a performance verdict.
What ends up in it
Genuine administration: invoices, expenses, forms, scheduling.
Communication overhead: the email about the meeting about the work.
Tool maintenance, including the time tracking itself.
Work that belongs to somebody else and arrived anyway.
And the residue of poor systems: looking for files, re-entering data, fixing what did not save.
Five different things with five different remedies, counted as one.
Why it grows unnoticed
Each item is small, so none justifies attention.
It arrives distributed across the week rather than in blocks.
And it feels like the cost of doing business, which some of it is and most of it is not.
In tracked weeks it routinely reaches fifteen to twenty-five percent, and almost nobody predicts that in advance.
Splitting it
The single most useful analysis here: break the bucket into the five kinds above and total them separately.
One pass over the raw entries, twenty minutes.
The result usually shows that one kind dominates, and that kind has a specific remedy rather than a general resolution to be more efficient.
What each kind responds to
Genuine administration: batching, and a fixed slot. It is the one category where batching works well, since the switching cost within it is low.
Communication overhead: fewer channels and shorter replies, plus the meeting substitutions in the previous note.
Tool maintenance: fewer tools. This includes the tracking system, which is a real cost and covered in its own note.
Other people's work: a conversation, not a technique.
System residue: a one-off fix. An hour spent making the file findable returns weekly.
The one-off fixes
The residue category is the one where a fixed investment pays repeatedly, and people consistently fail to make it.
A template, a saved search, a proper folder, a script, a checklist.
Each takes twenty to sixty minutes and removes a recurring few minutes forever.
List them as they occur during a tracking fortnight; the list is usually short and the return obvious.
The slot approach
One fixed period for administration, and nothing else in it.
Which works because admin's switching cost is low and its interruption cost to other work is high — it is the ideal candidate for batching, and almost the only one.
Protect it like any other block, or it becomes the thing that gets displaced and then accumulates.
What not to conclude
That admin should be zero. It should not; some of it is the job.
That the total is the problem. Twenty percent spread evenly is manageable; twenty percent arriving in interruptions is not.
And that efficiency is the answer, when for at least two of the five kinds the answer is that the work should not be yours.
What to check
What is in your admin bucket, split five ways?
Which kind is largest?
What one-off fixes did you notice yourself needing during tracking, and have you made any?
And is there a slot, or does it happen in the gaps?
Worth keeping in mind
Administration is the one category where batching genuinely works, because its internal switching cost is low and its interruption cost to other work is high. A fixed slot, protected like any other block, is the arrangement.
The short version
Split the admin bucket five ways once, over the raw entries, in twenty minutes. The result usually shows one kind dominating, and that kind has a specific remedy rather than a general resolution to be more efficient.
In short
One fixed slot for administration, protected like any other block, or it becomes the thing that gets displaced and then accumulates.
It is almost the only category where batching works cleanly.
The point
An hour spent making the file findable returns weekly.
The residue category is where fixed investments pay repeatedly and where people consistently fail to make them. For a complementary perspective on work, measurement or planning, consult GOV.UK.