Schedule recovery proportional to intensity immediately after high-demand periods — a calendar commitment, not a vague intention

Why This Is a Rule

High-demand periods deplete cognitive, emotional, and physical reserves. Without deliberate recovery, this depletion carries into the next period as a capacity deficit — you start the next cycle already behind, with reduced resilience and impaired judgment. Over multiple cycles without recovery, the deficit accumulates into chronic burnout: not a single catastrophic failure but a gradual erosion of capacity that eventually makes baseline functioning feel overwhelming.

The "proportional" calibration is critical: a one-week high-demand sprint requires a day or two of lighter scheduling afterward. A month-long crisis period requires a week of reduced commitments. The recovery must match the withdrawal — bigger expenditures require bigger deposits. Under-recovering from intense periods is like consistently spending more than you earn: the debt compounds.

The "structural calendar commitment" clause addresses the implementation failure that kills most recovery intentions. "I'll take it easy after the launch" is a vague intention that dissolves the moment something urgent appears. "January 15-17 is blocked for recovery: no meetings, no deadlines, reduced workload" is a structural commitment that survives scheduling pressure because it occupies real calendar space.

When This Fires

• When mapping the seasonal calendar (Audit the past 12 months of calendar data — rate each month as low/baseline/high-demand/crisis to reveal recurring seasonal patterns) and placing recovery windows
• Immediately after surviving a high-demand period without having pre-scheduled recovery
• When chronic fatigue persists despite adequate sleep — likely accumulated recovery debt
• Complements Make at least one structural adjustment before each high-demand period — push deadlines, reduce projects, or front-load preparation (pre-adjustments) with the post-period recovery that completes the cycle

Common Failure Mode

Immediately jumping into the next project after a high-demand period: "Great, the launch is done! Let's start planning the next one." The relief of completing the high-demand period feels like recovery, but it's not — it's the absence of acute stress, not the presence of recovery. Actual recovery requires reduced demand, not just the end of elevated demand.

The Protocol

(1) For each high-demand period in your seasonal map, schedule a recovery window immediately following it. Block it on the calendar now, before the high-demand period starts. (2) Calibrate duration: After a high-demand week → 1-2 days of reduced load. After a high-demand month → 3-5 days of reduced load. After a crisis period → 1-2 weeks of deliberately light scheduling. (3) "Reduced load" means: fewer commitments (not zero), lower intensity, no new projects starting, permission to operate at 50-60% capacity. (4) Protect recovery windows as fiercely as you protect maker-time blocks (Move meeting requests that land on maker blocks to manager-mode blocks — treat internal deep work with equal calendar commitment as client meetings). They're not optional "nice to haves" — they're the mechanism that prevents accumulated depletion. (5) If you find yourself consistently skipping recovery windows, you're prioritizing short-term throughput over long-term sustainability. The math doesn't work: the capacity lost to burnout exceeds the capacity gained by skipping recovery.