Run a Two-Week Admin Audit on Your Coaching Business

Coaches are told constantly that too much of the week goes to admin. The articles repeat and the percentages get quoted, and none of them describe your week, your roster or your price point. A borrowed statistic cannot tell you where your own hours go. The claim layer of this topic is taken. The measurement layer is empty.

This page is the measurement layer. It is a coaching business admin audit: a two-week instrument in five categories that records where your own week actually goes, then turns the total into a single number. That number, minutes per client per week, is what decides what to fix first. The five categories are the only places admin can hide in a coaching business, and each maps to a different remedy.

Part of the method is the counter-position. Two of the five categories should not be automated, and knowing which ones is half of why the audit is worth doing at all. Some of what you find should stay exactly where it is, as slow and as human as it already is.

Why you cannot fix an admin problem you have not measured

Every coach who has too much admin can say the admin is too much. They cannot say what it is, in which category, for their own roster. That gap is the whole problem. A felt overload cannot be acted on. A line on a table can.

There is a second reason measurement beats anecdotes. A solo coach with twenty clients and an owner with a team of five spend their non-coaching hours in different places. The first is buried in programming and messages. The second is buried in the coordination that running a team creates. Advice that treats those two as the same problem is advice that is not for either of them, and the audit is what tells you which one you are.

The narrative version of this question, one coach's actual week written out day by day, is worth reading, and it is a different thing entirely. This page is the instrument half. It does not show you somebody else's week, because that is the one thing it cannot do.

FitFocus's own claim, on the homepage, is that the platform saves eight hours of admin a week. That claim is only testable once you know what your own week costs, and this audit exists to produce exactly that number.

How do you audit admin time in a coaching business?

How do you audit admin time in a coaching business? Log every non-coaching task for two weeks in five categories: programming, client communication, scheduling and rescheduling, billing and payments, and progress review. Add the totals, divide by your active client count, and the result in minutes per client per week is the number that decides what to fix first.

The two weeks are deliberate. A single week is distorted by one busy day or one quiet one. Two weeks overlap that noise and still fit inside a fortnight, which is the longest an audit survives before it becomes another admin task. You are measuring a habit, and a habit needs enough days to show itself.

The five categories, and why they are these five

These five are the only places admin can hide in a coaching business. The test for a category: if a task is not coaching delivery, it fits one of these five, or it is one of them in disguise, or it is not yours to do at all. That last one is a finding too.

Category	What counts in this category	Week 1 (minutes)	Week 2 (minutes)
Programming	Building programs, adjusting them, reviewing exercises, set-up time
Client communication	Every message you reply to, check-ins, calls, follow-ups
Scheduling and rescheduling	Booking, rescheduling, confirming, reminders, chasing no-shows
Billing and payments	Invoices, chasing payment, payment questions, plan changes
Progress review	Reading logs, preparing for a review, writing the review

This is the worksheet. Copy the table, keep it somewhere you already look, and fill it in. The categories are these five because each one has a different remedy, which means the split is a decision structure rather than a taxonomy. The worst possible audit is one that tells you "admin" as a single number. The whole point is the split.

How to run the audit in two weeks without it becoming another admin task

The audit fails when it turns into a project. Four rules keep it light enough to finish.

• Capture as you go. Tally at the moment the task ends, not at the end of the day. Retro-tracking from memory is a fiction and you know it.
• Use the one-minute rule. If a task took more than a minute, it counts. Everything else is rounding. This stops the audit from becoming its own bookkeeping.
• Count the doubling. When one client moment spawns a second task, the follow-up message that becomes a program change, count both. The doubling is where the week actually goes and it is the exact thing your recollection cannot see.
• Do not fix anything while you are measuring. The whole point is the honest shape of the current week. Change the week first and you measure the change, not the problem.

Two weeks, five categories, one table. It is not a diary, it is a tally, and a tally is the one admin task that removes more time than it costs.

Reading the result: minutes per client, and what that number means

Add each column, average the two weeks, and divide the total by your active client count. That is minutes per client per week. It is the number that makes different coaches comparable and makes the week legible against the price being charged.

Here is how to read it against your own price. If a client pays $300 a month and takes forty minutes of the audit's total, the time cost is around $10 an hour of that client's money. If they take ninety minutes, it is half that. The per-client figure is not a grade and there is no target to hit. It is the input that tells you which clients the admin is actually attached to, and it is the same input that the cost-to-serve model for a client uses, so the audit feeds straight into it.

Read the categories before the total. A business where programming is the biggest line has a different problem from one where scheduling is, and the remedy differs with the diagnosis. The category that owns the most minutes is the category to attack first, and the total decides whether the problem is a single leak or the whole pipe.

The three categories that usually collapse with better support

Not all five collapse with better tooling, and the order matters. Tool the three below and leave the other two alone, and you have changed the shape of the week. Tool the wrong two and you have built a faster way to do work that should not be done faster. The boundary is drawn before any product is mentioned, and it is worth respecting.

Programming. The program block collapses first because most of it is re-creation, not thinking. A roster of twenty clients runs most of the year on the same scaffold, and a library of reusable program templates turns the Monday build from a blank page into an adjustment. The audit will show you what your programming really is: if the block is mostly layout and set-up, the platform is the fix.

Client communication. The message that gets typed out from scratch, every week, is the most common theft in the audit. A structured inbox with saved replies and scheduled check-ins removes the re-typing without touching the relationship. The check-in that is a template, not a person's read of the week, is the one that fails, and the tooling only helps the typing. The judgement stays yours.

Scheduling and rescheduling. The back-and-forth of confirming and re-confirming is the category with the least judgement in it and the most minutes attached. Self-booking and automated reminders remove the coordination from the coach's hands, and the coach gets the time back without the client noticing any drop in care, because the care was never in the calendar choreography.

The two categories that should not be automated

Billing and payments. The money is where the care has to stay concrete. A payment follow-up that runs on a schedule reads as a machine, and a client who owes money already knows it. The judgement in this category, when to ask, how hard, what to say, is the judgement that decides whether the business feels like a person's. Tooling it makes it worse, and the audit that finds billing in the top two is telling you something about the client's experience, not about the tooling.

Progress review. The review is the part of the week the client actually feels, and a review that was assembled by a machine is a review that tells a client they are a row in a table. The reading of the week, what changed, what it means, why the plan moves, is the coach's. It is the slowest category and it should be. This is the work the client pays for.

These two are why the counter-position is honest. A coaching business that automates programming and communication and scheduling has removed the re-created part of the admin while keeping the judgement. A business that automates the review or the billing has removed the care. The audit tells you which you have been doing.

What to do with the hours you get back

The audit does not generate hours, it moves them. The hours that leave the admin categories have one destination that matters, which is the delivery: the programming, the check-in, the review that the client can feel. If the hours disappear into a new admin project, the audit has failed and you can run it again to watch the same category refill.

Where the diagnosis lands decides the next step. If the biggest category is one of the three that respond to tooling, the remedy is inside the platform, and the hours are the dividend. If the biggest is the two that should not be automated, the hours are not a leak at all: they are the cost of the depth the business sells, and the question moves to the structure, not the calendar. If the week's audit shows the business is at capacity and the admin is the overflow, the fix is not faster, it is a second person, and that is the measurement half of the argument in our guide to why a full coaching business stops growing.

Once the audit has named the categories, the systemisation can follow the evidence. The six documents in the systemisation guide each exist to hand a category to a second person, and knowing the category is the prerequisite. The separate question of what to automate, which categories earn the automation and which do not, is its own decision and it belongs on its own page, because automating the wrong part of a measured week is exactly how a coach burns the hours back.

Frequently asked questions

How much admin is normal?

There is no honest number to give you, and the ones that get quoted are repeated without a measurement behind them. The figure that matters is your own, and you will have it after two weeks. What to compare is the split, not the total: a business that shows programming as the giant block and a business that shows billing as the giant block have different problems, and "normal" does not exist for either of them.

Should I count messaging as admin?

Yes, and expect it to be the biggest surprise of the audit. A reply that takes three minutes and a check-in that takes fifteen both count, because both are the communication category. Most coaches underestimate the tail of short messages because no single one feels like a block. The weekly total is the block.

What about programming?

Programming counts, and it is a real category, not a hiding place. The audit will show you whether the programming block is delivery or re-creation. The re-creation, layout, set-up, adjusting the same scaffold for the same kind of client, is the part the platform can absorb. The creative part stays, and that is exactly the split you want from a measurement.

Is this worth doing twice a year?

Yes, and the second run is cheap. The first audit takes two weeks because the habits are being established. Once the table exists, a re-run is a weekend of the same tally, and it is worth one after anything structural: a new service tier, a new team member, a migration to a new platform, a roster that has grown by a third. The audit is the instrument, and an instrument only works when it is re-calibrated.

The worksheet is this page. Copy the table, run the two weeks, and the number will be the most honest figure your business has produced all year. The hours are yours, the categories are the diagnosis, and what happens next is a decision about the structure, not a reason to keep going the way the audit found you.

The worksheet on this page is a measurement instrument, not a benchmark. FitFocus does not publish admin-load benchmarks, and the figures here are the reader's to generate from their own records. The eight-hour figure mentioned above is FitFocus's own claim about the platform, included so you can test it against your own week rather than as an independent finding. This article is a guide for your own decisions, not professional advice.