The Admin Tax: How Coaches Are Losing 15 Hours a Week (And How to Get Them Back)

The Admin Tax Is Real

You became a coach to change lives. Instead, you're spending Sunday nights writing session summaries, generating reflection questions, and answering the same client questions you answered last week. This is the admin tax — and it's stealing the best parts of your work.

Let's actually count it up. Session summaries: 15 minutes per session. Pre-session prep: 20 minutes per client. Answering repeated student questions: easily an hour a day at scale. Scheduling, rescheduling, follow-up emails: another 30 minutes. That's 15 hours a week — conservatively — going to tasks that don't require your unique coaching expertise. At scale, it gets worse.

The Specific Tasks Eating Coaches' Weeks

• Post-session documentation: summaries, action items, progress notes written manually after every session
• Pre-session prep: reviewing where the client was last time, what they committed to
• Repeated student support: the same 10 questions answered 40 different times across a cohort
• Content creation: translating expertise into posts, emails, and course materials
• Scheduling and logistics: the invisible administrative overhead of a service business

The painful irony: these tasks feel productive because they're clearly 'work.' But none of them are why clients pay you. They pay you for the thinking, the pattern recognition, the ability to see what they can't see about themselves.

Post-Session Summary: Copy-Paste AI Prompt

'You are summarising a coaching session. Client: [name]. Session focus: [main topic]. Key insights surfaced: [3–5 bullet points from your notes]. Commitments made: [what the client agreed to do]. Emotional tone of the session: [engaged/frustrated/breakthrough/stuck]. Output: A 200-word summary the client would find useful to read before our next session, written in a warm, direct tone. Also generate 3 reflection questions for the client to sit with this week.'

That prompt, consistently applied, turns a 15-minute post-session task into a 3-minute one. Multiply by 20 clients, and you've recovered almost an hour of weekly admin.

Pre-Session Prep: Another 10 Minutes Back

'Based on these session notes from our last three conversations: [paste notes]. Brief me on: (1) where this client started, (2) where they are now, (3) the pattern I should watch for in today's session, (4) the one question most likely to move them forward today. Output: A 150-word brief I can read in 5 minutes before the session.'

Personal Touch and Automation Are Not Opposites

Here's the pushback I hear most often: 'But if I automate the admin, won't it feel less personal?' This is exactly backwards. Think about it: the most personal thing you can offer a client is your full attention during the time you're with them. A coach who arrives to every session having spent 20 minutes reviewing notes is present and prepared. A coach who arrives having spent those 20 minutes on admin is distracted and slightly behind.

Automation doesn't replace the personal touch. It creates the conditions for more of it.

The 1:1 vs 1:Many Distinction

For coaches transitioning from 1:1 work into 1:many programmes, the admin picture changes dramatically. In 1:1 coaching, the admin is proportional to your client load. In 1:many, the support burden doesn't scale linearly with revenue. A cohort of 50 students can generate 5x the support questions of your 10 individual clients, at a fraction of the per-student revenue. Without a system, this is how coaches build successful courses and then burn out delivering them.

Skolasti's AI Teaching Assistant is trained on your specific course content and handles student Q&A 24/7. The admin tax on predictable questions drops to near zero — and the hours go back into actual coaching.

The admin tax isn't inevitable. It's a design problem. And like most design problems, it's solvable — if you build the right systems before the work overwhelms you.

What's the single admin task eating the most of your week? Drop it in the comments — there's probably a system for it.