How to Write Effective Weekly Athlete Summaries (Without Spending Hours)
It's Sunday night. You've been at an event part of the day, your laptop open, and 26 athlete summaries to write before Monday morning. You start strong — the first five get specific feedback, genuine observations, a personal note about race prep or a niggle they mentioned. By athlete twelve, you're copying sentence structures. By athlete twenty, you're writing "solid week, keep it up" and hoping nobody notices the difference between their summary and the one you sent to the person above them in the spreadsheet.
You know the summaries matter. You also know you can't keep doing them like this.
Why weekly summaries are the highest-value thing you write
Of everything a coach does in a week — programming, session review, data screening, admin — the weekly summary is the one thing the athlete actually sees and reads. It's your coaching made visible.
A well-written summary does three things at once. It shows the athlete you've looked at their data. It connects what they did this week to where they're heading. And it gives them something specific to focus on next week. That's not just communication — it's the mechanism that makes an athlete feel coached rather than plan-delivered.
Matt Dixon of Purple Patch Fitness has talked about the patterns he sees when athletes leave coaches. Three of the four most common complaints are rooted in communication: athletes not understanding the reasoning behind their training, coaches not appearing to listen, and a failure to adjust when life gets in the way. A weekly summary that addresses even one of those concerns — "I noticed you missed Thursday, so I've adjusted next week's volume" — can be the difference between an athlete who stays and one who quietly starts shopping for a new coach.
And yet, summaries are reliably the first casualty when a squad grows. Because unlike programming (which has templates and structures and tools), summaries require you to synthesise a week of data into something personal. That takes time — and time is exactly what a growing squad takes away from you.
What a good weekly summary actually contains
Before talking about speed, it's worth being clear about what "good" looks like. Not every summary needs to be a letter. But every summary should contain five things:
1. An acknowledgement of what actually happened
Not what was prescribed — what was done. Athletes know when you're commenting on the plan rather than the execution. Reference a specific session, a specific metric, a specific day. "Your Tuesday threshold set was bang on target — 3:42/km average across four reps" tells the athlete you actually looked. "Good work this week on the threshold sessions" doesn't.
2. A load or trend observation
This is where your coaching eye earns its keep. You're not just reading one week's data — you're reading it in context. Is their chronic load building the way you planned? Has their heart rate been creeping up on easy runs? Did their CSS pace improve for the third straight test? Even a single sentence here — "Your run volume is up 12% over the last three weeks, which is where we want it heading into the base phase" — adds enormous value.
3. A flag for anything that needs attention
If something looked off, say it plainly. "Your resting heart rate has been 6-8 beats above your usual range since Wednesday — worth keeping an eye on. If it hasn't settled by Tuesday, let me know and we'll adjust the back half of the week." This is the summary doing its job as a two-way communication tool. You're opening the door for the athlete to respond with context you might not have — stress at work, a bad night's sleep, the start of a cold.
4. A connection to the bigger picture
Athletes live in weekly cycles, but they're motivated by goals that are weeks or months away. Tie the week to the arc. "This is week three of the build phase — you're exactly where we want to be heading into the race-specific block in April" costs you one sentence and gives the athlete a reason to trust the process.
5. One clear focus for next week
Not a list of ten things. One thing. "Next week, the priority is nailing the Saturday long ride — everything else supports that." A single focus point is more useful than a paragraph of general encouragement, and it's far easier for the athlete to act on.
The time problem — and why templates aren't the answer
If you're coaching 25 athletes and each summary takes 8-10 minutes, that's over three hours every week — just on summaries. For coaches with 40+ athletes, it's closer to six hours. And that's before you factor in the time spent reviewing the data that informs what you write.
The obvious response is templates. And templates help — to a point. A structural template (acknowledgement, load observation, flag, connection, focus) gives you a framework. But the content still has to be personal. The moment an athlete reads a sentence that could have been sent to anyone, the summary loses its power.
Some coaches try a tiered approach: detailed summaries for their top-tier or most-engaged athletes, shorter check-ins for the rest. That works logistically but creates a two-tier service that athletes can sense. The athlete paying the same monthly fee as everyone else doesn't want to be the one getting the abridged version.
The real problem isn't that coaches don't know what to write. It's that the process of going from raw session data to a written, personalised summary involves too many manual steps: open the athlete's calendar, scan sessions, check load trends, compare to the plan, recall what they said last week, and then write something that sounds like you and not a form letter. That sequence, repeated thirty times, is what creates the Sunday night dread.
What actually makes summaries faster (without making them worse)
The coaches who maintain quality summaries at scale tend to share a few habits:
Screen first, write second
Don't open every athlete's data with a blank page in front of you. Screen your entire squad first — identify who needs detailed attention, who had a straightforward week, and who has a flag worth raising. That triage step means you're not spending equal time on every athlete. You're spending time where it matters. A coach with 30 athletes might find that 6-8 need a detailed, nuanced summary in any given week. The rest had a solid, unremarkable week — and the summary can reflect that honestly without being lazy.
If you want to go deeper on the screening side of this, we've written about how many athletes a coach can realistically manage and why screening is the bottleneck.
Write to the data, not from memory
The fastest way to write a personal summary is to have the relevant data in front of you — not in a separate app, not in a spreadsheet you built yourself, but immediately visible. When you can see load trends, compliance, and flagged sessions at a glance, the summary almost writes itself. You're describing what you see, not trying to recall what you saw three days ago when you glanced at their Garmin file.
Use your voice, not a formula
This might sound contradictory to "be faster," but it isn't. Coaches who write in their natural voice — the way they'd talk to the athlete poolside or at the track — write faster than coaches who try to compose something polished. If you'd say "Tuesday's session was mint, your pacing was way more controlled than last month" out loud, write that. Athletes want to hear from their coach, not from a report generator.
Batch by exception, not by alphabet
Instead of going athlete by athlete, batch your summaries by what the data tells you. Write the flagged athletes first (while the detail is fresh). Then the athletes who had a standout session or hit a milestone. Then the athletes who had a clean, on-plan week. This exception-based flow means your most important summaries get your best energy, and the routine ones still get done — just without the diminishing returns that come from writing your thirtieth summary at 11pm.
The gap between knowing and doing
Most coaches reading this will nod along. You already know what a good summary looks like. You already know communication drives retention. You already know that the Sunday night email grind is where your time disappears.
The gap isn't knowledge — it's capacity. You can write five excellent summaries in an hour. You can't write thirty. And the gap between five and thirty is where the coaching quality drops, athletes start to disengage, and the slow churn begins. If you want to understand why that churn happens and what it costs, this piece on why athletes really leave their coach is worth a read.
The coaches who solve this aren't the ones who learn to type faster. They're the ones who find a way to get the screening done before they sit down to write — so the summary step becomes synthesis, not research.
The summary is the relationship made visible
Here's the thing about weekly summaries that's easy to forget when you're on your twenty-fifth one: to the athlete, this is the most tangible proof that they have a coach. Not the programme (which they could get from an app). Not the monthly call (which happens once). The weekly summary — personal, specific, grounded in what they actually did — is what makes them feel like someone is paying attention.
That's worth protecting. And if the process of writing them is what's breaking your coaching model, the answer isn't to stop writing them. It's to fix the process.
If you're spending your Sunday nights turning session data into athlete summaries by hand, you're not alone — and it doesn't have to stay that way. Simma reads your squad's sessions, screens for who needs attention, and drafts weekly summaries in your voice. You review, adjust, and send. Join the early access waitlist.