There's a question most training plans never actually answer. They tell you what to do — the workouts, the intervals, the long ride, the key run. Some of them tell you why. But almost none of them answer the question that matters most week to week:

How much is the right amount right now?

Not how much is theoretically possible. Not how much the plan says. How much can this athlete — with the sleep they've been getting, the work stress they've been carrying, the soreness they have or haven't been experiencing, the motivation they've been feeling — actually absorb and adapt to right now?

That question doesn't have a fixed answer. It changes week to week, sometimes day to day, and it's different for every athlete. The StressLogic Framework is how QT2 coaches answer it.

What's Wrong With Following the Plan

Nothing is wrong with having a plan. The problem is treating the plan as fixed — as if the weeks are interchangeable, the athlete's response is predictable, and the right amount of training stress is whatever the calendar says it is on any given Monday.

Real athletes don't work that way. Some weeks the body is absorbing training well and the plan is leaving fitness on the table by holding back. Other weeks the athlete is carrying more fatigue than the numbers show — the workouts look fine on paper but execution is slipping, motivation is down, something's off — and pushing the plan forward means digging a hole that takes two weeks to climb out of.

The traditional response to this is the 3:1 model — three weeks of building load, one week of recovery, repeat. It's a reasonable default. For some athletes in some periods, it works fine. But it's a calendar answer to a physiological question. The athlete who is responding well at the end of week two doesn't need to stop building because the schedule says so. The athlete who is already showing signs of strain at the end of week one can't afford to push through two more weeks because the plan hasn't reached its recovery week yet.

Fixed calendars produce fixed decisions. Fixed decisions, applied to athletes who are anything but fixed, produce inconsistent results.

One Question, Every Week

StressLogic answers one question: What is the maximal amount of  appropriate training stress this athlete can absorb right now?

Not the most training possible. Not the least necessary. The most appropriate — the amount that will produce adaptation without pushing the athlete into the kind of strain that leads to missed sessions, deteriorating execution, injury, illness, or burnout.

The output of that question is simple. Three possible directions:

That's the decision. Three options*. Applied weekly, for this athlete, based on what's actually happening in their training and their life. The simplicity of the output is intentional — the complexity lives in the inputs, not the answer.

*Really, it's five options because we break 'Push' into two categories - 'Big Push' and 'Small Push' and we similarly break 'Pull Back' into 'Small Pull Back' and 'Big Pull Back'.

What Goes Into the Decision

StressLogic is only as good as the information it draws on. The inputs fall into two categories: what the data shows, and what the athlete reports.

Both columns matter. Neither one tells the full story alone.

An athlete can have acceptable training numbers — TSB in a reasonable range, ATL:CTL ratio holding stable, workouts completing on schedule — and still be poorly positioned to absorb more stress. A difficult week at work, two nights of bad sleep, a nagging tightness in the Achilles that's been building quietly for ten days. The data looks fine. The athlete isn't fine. Push the training forward anyway and you're likely to end up with a missed week or worse in the near future.

The reverse is also true. An athlete can feel tired while still carrying productive, controlled fatigue. Training is supposed to be hard. Fatigue is part of the process. The job of StressLogic isn't to eliminate fatigue — it's to distinguish between fatigue that's appropriate and fatigue that's excessive. Those are very different situations that look similar from the outside and feel similar to the athlete.

The Throttle Analogy

This distinction matters because it defines what StressLogic is not. It's not a training plan. It doesn't choose the athlete's block, design their workouts, or tell them what intervals to run. It doesn't replace the coaching judgment that comes from knowing an athlete's history, goals, and context. It organizes the information that informs that judgment and helps the coach answer one specific question with more precision than a calendar can provide.

Why This Matters Mid-Season

The middle of a race season is where load management gets complicated. The fitness is built. The goal races are on the calendar. The athlete is training harder than they were in January and racing more frequently than they were in April. And the temptation — especially for competitive athletes who can see the work paying off — is to keep pressing forward regardless of the signals.

This is exactly when fixed-calendar thinking breaks down. The athlete who just raced a 70.3 two weeks ago and has a full IRONMAN in eight weeks is not the same athlete they were in January when the plan was written. Their CTL is higher. Their accumulated fatigue from racing is real. Their life stress may have changed. The plan might say it's week nine of the build. StressLogic asks a different question: given where this athlete actually is right now, what does the coming week need to look like?

Sometimes the answer is push — the race went well, the recovery has been clean, the athlete is absorbing training and has the capacity to keep building. Sometimes it's hold — the fitness is where it needs to be, and consistency without additional overload is the right play. Sometimes it's pull back — the athlete is carrying more fatigue than they realize, and the next two months of training are better served by a week of deliberate reduction now than by forcing the issue and losing ten days to illness or breakdown in week twelve.

The Thing About Missed Workouts

This deserves its own attention because it's one of the most counterintuitive parts of the framework — and one of the most practically useful.

When an athlete misses a workout, the instinct — in most plans and for most athletes — is to make it up. Squeeze it in later in the week. Double up somewhere. Get the TSS back on the books.

QT2 doesn't do that. Missed training becomes part of the athlete's actual training history. The CTL, ATL, and TSB adjust to reflect what was actually completed. StressLogic then makes the next weekly recommendation based on where the athlete actually is — not where they would have been if the workout had happened.

Chasing missed stress adds load on top of whatever caused the miss in the first place — fatigue, life demands, a body that needed the rest it got. It's the training equivalent of borrowing money to pay off debt. The account doesn't get healthier. It just gets more complicated.

What StressLogic Is Not

Worth being clear about this, because the term "framework" can make it sound more mechanical than it is.

StressLogic is not an algorithm that spits out a weekly training file. It's not an AI-generated plan. It's not a system that runs autonomously in the background and adjusts training without a coach involved. It is a decision-support structure — a set of inputs organized in a way that helps a coach make a better judgment call. The human interpretation is required. The coaching context is required. The knowledge of the athlete built over months of working together is required.

The framework makes that judgment more consistent and more defensible. It ensures the right questions are being asked every week. It reduces the likelihood that important signals get missed because the coach was focused on a different variable. But it doesn't replace the coach. It makes the coach better at the decision they're already trying to make. It gives the coach a basis upon which to make his or her own training decision. It is informative, not prescriptive.

The Bigger Picture

Long-course triathlon is a multi-month, multi-year endeavor. The athletes who show up to their A races in July or September performing at their best are almost never the ones who trained the hardest in May. They're the ones who trained consistently — who avoided the two-week illness in week fourteen, the overuse injury that cost them six weeks of run training in the spring, the motivational crater that comes from pushing too hard for too long without adequate recovery.

That kind of consistency doesn't happen by accident. It happens when training load is managed week by week, athlete by athlete, based on what's actually happening rather than what the calendar anticipated four months ago when the plan was written.

StressLogic is the mechanism for that management. Not glamorous. Not something most athletes ever see or think about. But it's one of the things that separates a training plan from actual coaching — and one of the primary reasons QT2 athletes tend to arrive at their goal races in better shape, more rested, and more motivated than athletes who followed a plan alone.