Monday morning. 0530. The platoon runs 4 miles at whatever pace the formation leader sets. It wasn’t on your plan. It wasn’t at the right effort. But it happened, and your body doesn’t care that it wasn’t scheduled.
Unit PT is the controlled chaos of military and first responder training. You can’t skip it, you can’t control it, and you can’t pretend it didn’t happen. What you can control is how you train around it.
The Problem
Unit PT creates two challenges for individual training:
Pace mismatch. The group runs at a pace dictated by the formation, not by your training plan. If you’re faster than the group, you’re running too slow for a quality session and too fast for a recovery run. If you’re slower, you’re getting pushed harder than planned.
Load uncertainty. A “light PT” day and a full-body smoke session produce very different training loads. But both show up on the same calendar block. Your individual plan needs to absorb whatever happened and adjust.
How Pacewright Handles It
Group run tagging. When you log a unit PT run, you mark it as a group run — “I didn’t control the pace.” This tells the algorithm to exclude the pace data from fitness trend analysis. Your unit’s formation pace doesn’t reflect your fitness; using it would corrupt your aerobic trend and race predictions.
The training load still counts. Duration × RPE captures how hard the session actually was, regardless of who chose the pace.
Calendar pre-flagging. You set your recurring unit PT days — Monday/Wednesday/Friday mornings, or whatever your schedule dictates. The algorithm knows not to schedule hard individual workouts on those days. Your tempo runs and interval sessions go on days when you control the effort.
Post-unit-PT adjustment. The type of unit PT determines what’s appropriate for the rest of the day:
| Unit PT Type | Evening Run Adjustment |
|---|---|
| Upper body heavy | Run as planned — minimal leg conflict |
| Lower body / legs | Reduce intensity or convert to easy |
| Full-body smoke session | Easy run or rest |
| Light PT / stretching | Run as planned |
The algorithm treats unit PT days as input, not interference. Your job is to report what happened. The algorithm’s job is to adjust everything else around it.
The Key Principle
Your personal training plan focuses on the days you control. Unit PT days are logged, accounted for, and absorbed — but they don’t drive the training decisions. The tempo run that matters is the one you do on Tuesday evening, not the formation run you did Monday morning.
This means your total weekly volume is lower than a pure individual plan would prescribe, because unit PT is filling some of that volume with training you didn’t choose. That’s fine. The quality of your individual sessions compensates for the quantity you’re giving up to unit PT.
Making Unit PT Work For You
Some unit PT sessions align with your plan better than others:
Formation runs at easy pace are essentially free easy mileage. If your unit runs at a pace that’s genuinely easy for you, treat it as a recovery run. Don’t fight the pace; accept the gift of easy aerobic volume.
Hard PT sessions (timed runs, sprints, competitive events) count as quality sessions. If unit PT included a timed 2-mile run, that’s your quality workout for the day — don’t add a tempo run on top of it.
Smoke sessions are unpredictable and often intense. Log the RPE honestly. If it was a 7-8, the algorithm will recognize that you need recovery time before your next quality individual session.
The worst thing you can do is pretend unit PT didn’t happen and follow your individual plan on top of it. That’s how you exceed safe training load limits. The algorithm catches this through your volume caps and session-load limits, but the first line of defense is honest logging.