Live
Powered by

2026-07-20 weekly self-assessment

Metadata

  • Athlete: Sidney McGill
  • Assessment type: Weekly self-assessment
  • Assessment date: 2026-07-20
  • Athlete-local timezone: America/Toronto
  • Week under review: 2026-07-13 to 2026-07-19
  • Planned trigger day: Monday
  • Plan horizon: July build into Vermont camp
  • Status: Preparation only

Coach preparation

Weekly positives

  • The July block now has a coherent structure again, with recovery, intensity, strength, run work, skills, and long endurance all appearing in the calendar in a deliberate sequence.
  • The athlete has already shown good decision-making by flagging air-quality constraints instead of forcing a meaningless benchmark day.
  • The travel context is stable right now in Orillia, which gives a clean window for training and recovery before the Vermont camp.
  • The plan is respecting the earlier re-entry work by keeping support load and skill work progressive rather than jumping straight into a race-heavy pattern.
  • Fueling targets are now being written into the work, which gives us a better chance of getting real feedback on long-ride tolerance before camp.

Weekly concerns

  • Several key outcomes are still unconfirmed in the logs, especially how the FTP test, the substitute indoor ride, and the long endurance work actually landed in the body.
  • Recovery detail is still thin. Sleep, heaviness, appetite, and overall freshness have not been documented well enough to judge how absorbable the current build is.
  • The week ahead stacks VO2, gym, run, CX skills, and a long ride with late pressure, so hidden fatigue would matter quickly.
  • Back, SI, hamstring, ankle, and cramp precursors still need active watchfulness as the short efforts and run work progress.
  • Heat and air quality have already affected execution once, so the plan needs a clear fallback mindset if conditions turn poor again.

Ranked talking points

  1. What actually happened with the FTP test and the surrounding rides, and whether the body check felt normal enough to trust the numbers.
  2. How the athlete is absorbing the current build overall, especially sleep, heaviness, soreness, appetite, and general freshness.
  3. Whether any back, SI, hamstring, ankle, or cramp warning signs showed up with the gym, run, starts, or short-power work.
  4. Whether fueling, hydration, and sodium targets felt sustainable on the longer ride and during warmer or harder sessions.
  5. Whether the coming week should stay on the current progression or be trimmed before the camp block starts.

Open questions

  • Did the FTP test actually happen, and if not, what kept it from being a valid day?
  • How did the indoor substitute ride feel once the air quality forced the change?
  • Did the easy run, stair intro, and CX starts stay quiet for ankle, calf, SI, and hamstring?
  • Did the posterior-chain gym sessions stay clean, or did any back or SI guarding show up?
  • Was 75 to 100 g/hr on the longer rides realistic, and did the gut stay calm?
  • Is there any travel, work, or scheduling friction coming before the Vermont camp on August 3?

Forward-looking planning checkpoints

  • Confirm the athlete is fresh enough to absorb the Monday VO2 session without turning the rest of the week into survival mode.
  • Confirm gym load on Tuesday and Thursday stays supportive rather than provocative.
  • Confirm the run and CX skill work remain symptom-stable as the off-bike load steps up.
  • Confirm the Friday long ride can hit the late-pressure blocks and fueling targets without cramp or fade.
  • Confirm camp travel prep, especially GF/DF food packing, bike logistics, and recovery expectations before August 3.

Specialist-sensitive prompts

  • Endurance: Is the athlete ready for another quality week, or does the body still need a quieter progression before camp?
  • Nutrition: Did the longer ride fueling and hydration feel repeatable, and is the gut happy with the current intake range?
  • Recovery: How are sleep, heaviness, soreness, appetite, and general freshness right now?
  • Strength: Did the posterior-chain work stay clean through the back, SI, and hamstrings, or did any guarding show up?

Conversation goals

  • Reconstruct what actually happened last week instead of relying only on the written plan.
  • Check whether the body is absorbing the current build well enough to keep progressing.
  • Catch any symptom, recovery, or fueling issue early enough to protect the next block.
  • Leave the athlete with a clear and realistic direction for the coming week.

Raw conversation log

Coach Luca

Timestamp: 2026-07-20 11:00 America/Toronto

Hey Sidney — quick weekly check-in before I tighten the next block.

1) How did the week feel overall, including the FTP-test day, the substitute ride, the long endurance work, the gym re-entry, and the run/walk?
2) Any leftovers I need to account for today — sleep, soreness, heaviness, appetite, back/SI, hamstring, ankle, cramping, or anything else that felt off?
3) Are you good with the current direction for next week, or do you want me to keep anything conservative before camp?

Short reply is fine.

/luca

Key extracted findings

  • Awaiting athlete reply before closing the week with coaching consequences.

Planning implications

  • Training: pending athlete response.
  • Nutrition: pending athlete response.
  • Recovery: pending athlete response.
  • Strength: pending athlete response.
  • Follow-up later this week: if no reply comes in, close the assessment as unresolved and keep the next block conservative.

Specialist routing notes

  • Endurance: no new routing yet.
  • Nutrition: no new routing yet.
  • Recovery: no new routing yet.
  • Strength: no new routing yet.

Unresolved items

  • Athlete reply to the weekly self-assessment prompt.

System

  • Assessment file updated: draft athlete-facing weekly self-assessment body saved in the canonical daily log.
  • Preparation completed: yes
  • Athlete thread started: no
  • Last same-day follow-up sent: none
  • Assessment closed: no