How to Share Your Workout Data With Your Coach (And What to Actually Send)

Most athletes who work with online coaches send some version of the same weekly check-in: a screenshot of their best lift, a one-line note that says “felt strong” or “had a tough week,” and maybe their body weight. The coach reads it, writes a response, adjusts the program.

The problem is not the effort. It is the signal quality. “Felt strong” tells a coach almost nothing. It does not tell them which sessions were strong, whether RPE crept up across the week, whether volume targets were hit, or whether the estimated 1RM on the primary lift moved at all. A coach who programs based on vague subjective reports is working with a significant information deficit, and the athlete pays for that deficit in suboptimal programming.

The growing adoption of remote coaching makes this problem more acute. Coaches working with athletes they never see in person are almost entirely dependent on athlete-reported data. The quality of that data determines the quality of the coaching.

What data is actually useful to share

Not all training data is worth sending. A coach who receives a raw data dump has the same problem as a coach who receives nothing: too much noise and not enough signal. The goal is structured, interpretable information.

Four categories of data matter for weekly coach communication:

Weekly volume by category. Total sets completed per muscle group or movement pattern for the week. This tells your coach whether the program was executed as designed. If the plan called for 18 sets of pulling work and you completed 12, that is information the coach needs: your numbers are being built on a different volume base than they intended.

RPE trends across the week. Not the RPE of a single set, but the pattern across sessions. Did effort levels stay consistent, rise across the week, or spike on specific days? Rising RPE at constant loads is the primary early signal of accumulated fatigue that a coach would act on by either extending the current phase, inserting a deload, or adjusting the load prescription.

Estimated 1RM trajectory on primary lifts. One week of estimated 1RM data tells you little. Three to four weeks of it shows the coach whether strength is trending in the right direction. A flat or declining estimated 1RM over multiple weeks while volume and effort are adequate is the signal that something in the program needs adjustment. This is covered in more detail in how to know if your workout program is working.

Session completion rate. How many planned sessions were completed? If an athlete consistently completes four out of five planned sessions, a coach programming for a five-day week is building on a faulty assumption. This is not about effort or commitment. It is information needed to prescribe a program that actually fits the athlete’s real week.

What is not worth including in detail: individual set-by-set logs for every exercise, minor form observations about accessory movements, and emotional or motivational narratives unless they directly relate to training execution (illness, injury, life stress affecting training).

Why structured data changes the coaching relationship

A 2025 qualitative study on technology adoption in collegiate coaching (Brewer et al., Frontiers in Sports and Active Living) found that coaches use data to initiate more structured conversations with athletes rather than relying on subjective reports alone. The dynamic applies equally in remote coaching contexts: the data does not replace the conversation; it improves it by grounding it in specifics.

When a coach can see that an athlete’s RPE on their squat climbed from 7.5 to 9.0 over three weeks at the same load, they have a concrete basis for the conversation about adding a deload. When an athlete reports “I’m feeling a bit tired,” the coach has to infer, and may infer incorrectly. Structured data eliminates that ambiguity.

The same dynamic applies to self-coached athletes, or athletes who use a coach periodically rather than weekly. The discipline of preparing data you would share with a coach is itself a useful analytical practice. The automated weekly workout report in Workout Lab makes this natural: the report aggregates exactly the information a coach would want to see, which means the review you do for yourself is simultaneously coach-ready.

A weekly data briefing template

The goal is to give your coach interpretable information in a format that minimizes the time they need to spend parsing it. Here is a structure that works:

Primary lifts summary. For each main movement (squat, deadlift, bench, overhead press, or your equivalents): the weight, sets, and reps you hit this week, plus the RPE of your top sets. If your tracking app shows an estimated 1RM, include that number and whether it moved up, down, or held flat from last week.

Volume summary. Total sets per muscle group or movement category for the week. One line per category is enough: “Pulling: 16 sets, Pushing: 14 sets, Legs: 20 sets.”

RPE note. A single sentence on the RPE pattern across the week. “RPE stayed consistent Monday through Thursday, spiked on Friday’s deadlift session.” That single sentence tells the coach more than “Friday was tough.”

Session completion. “Completed 4/5 sessions. Skipped Saturday due to work travel.”

Anything anomalous. Illness, injury, significant life stress, schedule disruptions. Keep it brief and factual.

That briefing takes about five minutes to write and gives your coach everything they need to make an informed programming decision. It is a significant upgrade over a screenshot and “felt good.”

How the data changes over a training block

Single-week data is a snapshot. Multi-week data is a narrative. This distinction matters for how coaches use the information you send them.

In week one of a new training block, your estimated 1RM and RPE give the coach a current baseline. In week three, those same metrics show whether the program load was calibrated correctly. By week six, the trend across the block tells the coach whether you are on track for the planned peaking week or whether an adjustment is needed before the block ends.

This is why consistent tracking compounds in value. A coach who has one week of your data can make an educated guess about your next training week. A coach who has six weeks can identify patterns you would not notice yourself: a specific day where your RPE consistently runs high (which may indicate inadequate recovery between sessions), an exercise where your estimated 1RM has been stubbornly flat for four weeks despite rising on all related movements (which may indicate a technique limitation rather than a strength ceiling), or a progressive RPE climb that indicates accumulated fatigue the athlete has stopped consciously noticing.

Athletes who train without a coach can use the same analysis framework on their own. The question to ask each week is: does the data from this week fit the expected pattern for this stage of the training block, or does something look anomalous? If you expected to be building load and your estimated 1RM dropped, identify why before the next session, not after three more weeks of the same pattern.

Using Workout Lab to generate coach-ready data

Workout Lab’s weekly report format was designed around exactly this type of structured review. After each training week, the report surfaces your volume by muscle group, your estimated 1RM trend on tracked exercises, your session completion rate, and RPE patterns across the week.

This means the data you need for a coach briefing is already assembled. You are not reconstructing it from individual session logs. The weekly report is, in effect, the briefing with some additional context. Share it with your coach as a starting point, then add your brief written note on anything anomalous.

For athletes working with coaches who structure programming in multi-week blocks, the data becomes more valuable over time. A coach who has four weeks of RPE and estimated 1RM data from your training can make programming decisions with far more confidence than one who has four weeks of “felt good / tough / okay” messages.

This is part of the broader case for consistent tracking laid out in why tracking your workouts matters: the data compounds. Each week of accurate logs makes the next coaching decision more informed.

The full range of Workout Lab’s capabilities for different athlete types, including how the tracking system adapts to different training disciplines, is covered in Workout Lab for every athlete. For athletes who use a plan-track-adjust framework with their coach, applying the plan-track-adjust cycle to your training explains how weekly data review fits into that process.

The athlete-coach relationship is a data partnership. Better data going in means better programming coming back. And the athletes who send structured, interpretable data week after week are the ones whose coaches can actually make the adjustments that matter.