Live
Powered by

2026-09-14 weekly self-assessment

Metadata

  • Athlete: Sidney McGill
  • Assessment type: Weekly self-assessment
  • Assessment date: 2026-09-14
  • Athlete-local timezone: America/Edmonton
  • Week under review: 2026-09-07 to 2026-09-13
  • Current 7-day plan: 2026-09-14 to 2026-09-20
  • Current 3-week plan: 2026-09-14 to 2026-10-04
  • Planned trigger day: Monday
  • Plan horizon: post-Canmore recovery, then Rochester race lead-in and early east-coast race block
  • Status: In progress

Coach preparation

Weekly positives

  • The week held a clear taper-and-race shape, with recovery, opener, travel, recon, and race-day focus all staged in the right order.
  • The daily plan stayed conservative rather than trying to force extra load into a race week, which is the right choice around a key CX opener.
  • The travel and race lead-in were organized around execution first, not training heroics, which should help absorb the race cost.
  • No acute illness, injury, or major red flag is visible in the recent weekly log trail.
  • The athlete made it through the lead-in and into race day without the plan needing a visible rescue.

Weekly concerns

  • Actual training absorption is still not fully verified, so the real cost of the week may differ from the written taper.
  • There is still no fresh direct athlete check-in in the visible record, so readiness remains partly inferred rather than confirmed.
  • Race-day effort, travel load, and any residual soreness from starts, run-ups, barriers, and repeated accelerations could be hiding under a good-looking taper.
  • The next block comes quickly, so any lingering fatigue, appetite drift, sleep disruption, or tissue irritation matters more than usual.
  • Travel and logistics for the next race sequence need a clean confirmation before the week hardens.

Ranked talking points

  1. What actually landed across Sep 7 to Sep 13, especially the recovery day, opener, recon, and Canmore race day?
  2. How does the body feel this morning after the race weekend and travel shift?
  3. Which sessions were completed as written, which were shortened, and which were skipped or modified?
  4. Any ankle, calf, back, SI, hamstring, or general lower-leg warning from starts, run-ups, barriers, or race efforts?
  5. Are sleep, appetite, hydration, and general freshness still steady after the race lead-in?
  6. Is Rochester travel, equipment, and logistics already settled, or does the coming week need more restraint?

Open questions

  • Whether the taper produced real freshness or mostly just reduced volume on paper.
  • Whether Canmore left any residual heaviness, soreness, or tissue irritation that should change the next few days.
  • Whether the athlete needs a softer restart before the Rochester lead-in.
  • Whether sleep, appetite, hydration, or GI comfort shifted during race prep or travel.
  • Whether any race-week logistics still need clarification before the next block.

Forward-looking planning checkpoints

  • Keep Sep 14 as a true recovery day and do not let it turn into hidden volume.
  • Reassess freshness on the next training day before restoring meaningful load.
  • If fatigue is higher than expected, trim density before cutting the few sessions that matter most for Rochester.
  • Protect carbohydrate availability, sleep, and hydration through the early part of the race block.
  • Confirm travel, equipment, and race-week timing before the week gets busy.

Specialist-sensitive prompts

  • Endurance: did the taper and opener leave the legs sharp, or are they still flat or stale?
  • Nutrition: any appetite change, GI drift, or under-fueling around race prep, race morning, or travel?
  • Recovery: how are sleep, heaviness, soreness, and overall freshness after Canmore?
  • Strength: any ankle, calf, back, SI, or hamstring warning from starts, run-ups, barriers, or repeated accelerations?

Conversation goals

  • Confirm how the Canmore week actually absorbed, not just how it looked on paper.
  • Surface any recovery, fueling, travel, or tissue issue before the Rochester lead-in starts.
  • Decide whether the coming week can stay as planned or needs a small reset.

Raw conversation log

Coach Luca

Timestamp: 2026-09-14 09:00 America/Edmonton

Morning Sidney — quick weekly reset before the Rochester lead-in.

Give me the straight story on the Canmore week:
- what felt sharp
- what felt flat, sticky, or harder than it should have
- any ankle, calf, back, SI, or lower-leg warning from starts, run-ups, barriers, or repeated accelerations
- how sleep, appetite, hydration, and general freshness actually held up

Then tell me what I should protect this week as we move into Rochester: keep pressing as planned, or trim the load a bit to protect freshness?

If there’s one session or one issue that matters most, lead with that.

Key extracted findings

  • Weekly self-assessment prompt opened; no athlete response yet.
  • The visible week centered on Canmore race execution, so the main planning question remains how the body absorbed travel, race stress, and repeated accelerations.
  • Freshness, soreness, and recovery status remain unconfirmed until the athlete answers.

Planning implications

  • Training: keep the Rochester lead-in direction conservative until the athlete response clarifies freshness and any tissue issues.
  • Nutrition: watch for any appetite, hydration, or recovery-fueling drift around the race weekend.
  • Recovery: protect today as a recovery/assessment day unless a new issue is reported.
  • Strength: keep the ankle, calf, back, SI, and lower-leg watch items in view.
  • Follow-up later this week: only if the athlete does not respond today or if a key issue remains unclear.

Specialist routing notes

  • Endurance: wait for the athlete summary before deciding whether the Rochester lead-in stays unchanged.
  • Nutrition: no extra action yet.
  • Recovery: no extra action yet.
  • Strength: no extra action yet.

Unresolved items

  • Athlete's summary of the Canmore week.
  • Any lingering soreness, tissue warning, or fatigue signal after the opener and race.
  • Whether the coming week should stay as written or be trimmed back.

System

  • Assessment file created: yes
  • Preparation completed: yes
  • Athlete thread started: yes
  • Last same-day follow-up sent: none yet
  • Assessment closed: no