For Athletes Training & analysis

Planned breaks: logging "I am taking 2 weeks off"

How to communicate planned downtime to the Hub so the system does not treat it as missed training.

What planned breaks are

Sometimes you take time off intentionally: post-race recovery, family vacation, off-season block, planned injury rehab. The Hub does not auto-distinguish "planned break" from "missed training": both look like a gap in the data.

Communicating the planned break helps the coach interpret the gap correctly and stops false-positive concerning patterns from firing later.

What the Hub does NOT have

These are coaching-side decisions, not system features today.

What to do as the athlete

Tell your coach in advance

The simplest path: a message to the coach saying:

Taking 2 weeks off June 12 to 26. Family vacation. I will log wellness if I can; no structured training.

This sets expectation, lets the coach plan around the break, and avoids alarm if your activity feed goes quiet.

Log wellness if you can

Mark races appropriately

If a race falls in the break window:

What the coach should do

Update the macrocycle config

Edit the config_json for the affected weeks to reflect zero volume / "planned break". Even though the Hub does not read this field for any automatic action, the record is clear when you look back.

Write a CoachNote

A CoachNote on the athlete documenting the break and the return plan keeps the timeline coherent.

Pause new race planning

Do not deploy fresh race plans into the break window.

After the break

Multiple short breaks

Travel weeks, holidays, and work crunches add up. A coach with 2 or 3 athletes who each take 4 weeks of unplanned breaks per year writes very different macrocycles from one who pretends every week is structured. Be honest about the real-life calendar; the plan can absorb it if it is known.

See also: After 4+ weeks off, DNF / DNS handling, Logging daily wellness.

Last updated May 12, 2026

Still stuck? Ask us a question and we'll write up an answer.

Ask a question