Skip to content
Coach Sheet

The 5-to-10-hour Sunday admin pain (and how to systemise it down to 90 minutes)

Most online coaches lose their Sunday afternoon to program updates and client check-ins. The fix isn't working faster. It's removing the work entirely.

By Coach Sheet team Published

Talk to any online coach with 15+ clients and the same conversation happens. They’re tired on Mondays. Sunday was admin day. Sunday is always admin day.

This is the math we kept hearing in the Reddit threads we read:

  • 22 clients × 12 minutes per program update = 4 hours 24 minutes
  • Plus 22 weekly check-ins × 5 minutes = 1 hour 50 minutes
  • Plus replying to messages that came in over the weekend = 1 to 2 hours
  • Plus updating the master tracking sheet = 30 to 45 minutes

That’s 8 to 9 hours every Sunday. For most coaches, that’s also their day off.

This post is about why that workload exists and how to cut it by 75% without buying anything new (Coach Sheet helps; the workflow concepts apply even if you don’t use it).

Why Sunday is always admin day

The pattern arises from how online coaching has evolved. Five-day-a-week clients log workouts through the week. The coach reviews them, sees what worked, adjusts next week’s prescription, sends the updated plan. The cadence locks the work into a weekly rhythm. The natural day to batch the rhythm is Sunday.

This is fine when you have 5 clients. It breaks when you have 25.

The reason it breaks isn’t time per client. It’s context switching. Every time you open a new client’s plan, you’re rebuilding the mental model of where they are in their training, what their last week looked like, what their goals are. Two minutes of context-switch overhead times 22 clients is 44 minutes of pure overhead, before you do any actual work.

Where the time goes

Coaches who’ve kept careful time logs report this distribution:

  • 25%: rewriting the same program with weight progressions (mechanical, not creative)
  • 20%: reviewing logs and seeing what happened
  • 15%: writing personalized comments on the week
  • 15%: replying to client messages
  • 10%: updating master tracking spreadsheets
  • 8%: hunting for client info that’s scattered across messages, sheets, notes
  • 7%: dealing with edge cases (client traveling, illness, deload week)

Three-quarters of the time goes to mechanical work that a system can do or a checklist can shorten. Only the personalized comments and message replies require the coach’s actual judgment.

What removes work versus what makes work faster

A common trap: coaches buy a faster tool and the Sunday becomes 4 hours instead of 6. Then they take on more clients and Sunday becomes 6 hours again. The tool didn’t save them; it just shifted the equilibrium.

Real time savings come from removing categories of work. Not from doing the same work faster.

Three systems that move the needle

1. Automated load progression

The 25% of time spent rewriting weight progressions is the biggest single category. The work is mechanical: read last week’s RPE, decide if the load goes up, by how much, write the new load into the new template.

A simple progression rule (RPE ≤ target → +2.5%; RPE = target+1 → hold; RPE = target+2 → -5%) covers 80% of cases. The remaining 20% need coach judgment (deload weeks, return from injury, client traveling).

A tool that runs the progression rule automatically saves the bulk 80% time without removing the 20% judgment cases. That’s the Save Week automation we built.

A 22-client coach saves 1.5 to 2 hours every Sunday on this single change.

2. Templated weekly check-ins

The 15% spent writing weekly comments often follows a pattern: “Good week, X went up, see if you can do Y next week.” 60-70% of weekly comments are variations of this template.

A coach with 22 clients writing “good week” 22 times is a coach who could have written it once and copy-pasted into the rest. Or used a template fill-in.

Save 30-45 minutes per Sunday with three or four templated comments and customize only when something noteworthy happened.

3. Async-only communication windows

The 15% spent replying to messages is partly real coaching, partly false urgency. Clients message on Saturday night because they assume the coach is on. Coach replies Sunday morning because they’re now in admin mode.

Set a clear async communication window: messages get replied to once on Sunday and once on Wednesday. No real-time messaging unless it’s an actual injury.

This sounds simple. It’s hard to enforce. Most coaches who try it discover they’d been training clients to message at all hours by being available at all hours.

The 1-2 hours of weekend message reply time becomes 20-30 minutes of focused reply on Sunday morning.

What good Sunday looks like

After the systems are in place:

  • 30-45 minutes: review the week’s logs (Save Week presents the trends, you don’t dig)
  • 20-30 minutes: reply to messages from the async window
  • 30-40 minutes: write personalized comments on the 5-8 clients who had something noteworthy happen
  • 15-20 minutes: sketch next week for any client whose plan needs structural change

Total: 90-130 minutes. Down from 5-10 hours.

What the systems don’t fix

Three categories of work the systems can’t reduce:

  • Acquiring new clients: this is its own job, not Sunday admin work
  • Quarterly program restructures: every 8-12 weeks, every client needs a real planning session. Block 2-3 hours for this, separate from Sunday admin
  • Genuinely complex weeks: the client got injured, the client got pregnant, the client just competed. These need real coaching attention; the systems just buy you the time to give it

The goal isn’t to eliminate the coach from coaching. It’s to remove the mechanical work so the coach has time to coach.

Where to start if you have the pain

If your Sunday is currently 6+ hours of admin, the order of operations:

  1. Track time for two Sundays in detail. You’ll find your actual breakdown is different from the averages above. Address the biggest category first.
  2. Implement automated load progression for clients on autoregulation. This is usually the biggest single win.
  3. Set up 2-3 templated weekly comments. Use them for routine weeks; write custom comments only when the week was noteworthy.
  4. Define your async communication windows and stick to them for two weeks straight.
  5. Re-measure. The Sunday should be shorter. If it isn’t, you’ve found a different bottleneck.

The goal is to spend less of Sunday on mechanical work, not to spend less time coaching. The better systems give you more attention per client, not less.

That’s the whole pitch.