Fillmore Outdoors
Fillmore Outdoors

Running

Block 1 Report: Eight Weeks of Re-Entry, Scored Against the Plan I Froze in July

A 46-year-old re-enters running with a pre-registered 8-week plan: 31/32 sessions, all five criteria scored, negative results included.

September 24, 2026

Start here: In July, I froze an 8-week training plan and then logged what actually happened. The training program's success criteria were stated in advance, with no edits allowed once it started. Result: I completed 31 of 32 sessions, and all five of the pre-registered criteria were passed — from a run-walk start to 37 minutes of continuous running at a conversational effort. This report scores the block against the plan exactly as written, including the parts that went sideways: an equipment failure that broke three programming rules in one session, a heat "adaptation" that turned out to be a measurement outlier, and two knees' worth of open register items that carry into the next block. One case, honestly documented — not medical advice.

What this is

This is a block report, the scoring document the whole method builds toward. The plan was registered and frozen on July 13 (you can read it as written); nothing in it was edited after signature. Every session was logged within hours in a standardized six-line format. Every deviation was recorded as a modification with its reason. The five success criteria below were written before week one, which means the block gets graded against what I said would count, and not against whatever story eight weeks of hindsight would prefer to tell.

The subject: Me. Mid-forties male, re-entering training after years away. I was active into my twenties — running and gym work, self-directed, no coaching or formal programming — but nothing has consistently stuck since. My weight has fluctuated considerably in both directions over that span — at one point, recently, up to 245 lbs. At registration I was effectively not running: zero to one short runs per week across the preceding eight weeks. My first ruck in twenty years was July 17, 2026. Training is whenever I can fit it in — from early mornings to evenings to weekends — around a demanding schedule; work forced sessions to slide a day in five of the eight weeks, each one logged. Note: this is not a comeback story or a beginner's diary, but rather it is an out-of-shape adult re-entering a sport on a deliberately conservative ladder and reporting what the ladder actually did.

The registered plan, in brief

Eight weeks, two 4-week cycles, four sessions per week: strength led (done first, fresh), running re-entered conservatively as a run-walk ladder, one genuinely light weekly ruck (backpack + 10 lb), and weeks 4 and 8 as recovery weeks at roughly a one-third cut. Strength leads in a Texas summer because quality running in 100°F is a challenge, and because when strength and endurance are trained concurrently, running is the modality that costs strength the most. The interference literature traces to Hickson's concurrent-training study, and a meta-analysis found running produces larger strength decrements than cycling because of its stabilization demands and eccentric stress (ISSA, Tactical Conditioning 316–317). All easy running at 70–75% of max heart rate, where "the exact pace of easy runs is the least important" variable (ISSA, Running Technique and Programming 172), with a chest strap policing the ceiling.

The five criteria, frozen at signature:

  1. Adherence ≥ 80% of planned sessions (26+ of 32)
  2. Continuous easy 40 minutes at RPE ≤ 5 by week 7 (from a run-walk start)
  3. Ruck at 50–60 minutes brisk at the ~10 lb starting load, no flags
  4. Strength progression logged on ≥ 3 movement patterns
  5. Zero unresolved adverse-event flags with 3+ appearances entering Block 2

The scoreboard

#Criterion (as registered)ResultVerdict
1Adherence ≥ 80% (26+/32)31/32 (97%) — one skip, week 5, personal travel, loggedPASS
2Continuous 40 min @ RPE ≤ 5 by wk 737:00 @ RPE 3, week 7 (35–40 window)PASS
3Ruck 50–60 min @ ~10 lb, no flags50:00 clean, banked week 3, repeated week 7PASS
4Strength progression, ≥ 3 patternsPull-ups 2→3 strict · A-session 3→4 rounds at lower RPE · push-up decay 64%→25%PASS
5Zero register items at 3+ appearancesTwo items closed the block at 2 of 3; both carry forward openPASS

Five for five — but the passes are less interesting than how they happened, and two of them nearly didn't.

What eight weeks actually looked like

Weeks 1–3: the appetite. Every discretionary ceiling in the plan got used in week one — the ladder at ×10, the ruck at 44 of 45 minutes, every optional finisher taken. I flagged it in the week 1 rollup as an item to watch — appetite exceeds ramp. Week 2 confirmed the direction and added the block's most instructive failure. My 20 lb dumbbells and pull-up bar went missing on the same day the planned fourth circuit round went in, so I substituted 25s — and three rules broke in one session: load and volume moved together, the run block accidentally ran before the lift (sequencing matters because "fatigue inhibits motor learning" — Tactical 317), and push-ups decayed 20/20/12/10, which is going to failure, not finishing with one rep in the tank (Running 266). The session landed at RPE 8 on a plan designed for 6. The fix, written mid-workout: when the kit forces load up, take the reps down — never stack the newest progression on top. That conversion rule stood for the rest of the block. The finding underneath it: equipment is a programming variable whether or not you chose to change it.

Week 4: the first test that mattered. A recovery week is where an appetite like weeks 1–3 goes to cheat. The textbook is blunt about recovery weeks being just as important as the hard ones — do not try to run more or faster during them (Running 265) — so the cut was pre-committed to specific numbers before the week ran. It executed at RPE 2/3/2/2, reps deliberately left in the tank, the optional finisher cut without negotiation. The watch item closed against my own hypothesis: the appetite is real, but it did not override a registered cut. That's a negative result, and it stays in the report.

Weeks 5–7: the risk inverts. The ladder ended and continuous running began — and immediately overshot. Week 5's prescribed 20 minutes became an accidental 30 (I'd lost my session sheet and guessed at the number). Week 6 held the correct duration, but ran it a minute per mile faster "because it felt good," which put perceived effort exactly on the scoring line. By mid-block the question was no longer whether fitness would come back. It was whether easy would stay easy, which the text calls the single biggest mistake runners make (Running 72). The criterion attempt in week 7 answered it structurally rather than through willpower: treadmill speed set at 13:00/mi before the session, one pre-authorized adjustment, no other decisions permitted mid-run. Thirty-seven minutes, RPE 3, two full points of margin under the line. The lesson of the week: slower feels worse but scores better.

Week 8: recovery, pre-committed again, executed again. 31/32.

The finding the block was secretly about

Look at where discipline held and where it drifted, and one pattern explains it all. The turn-timer (alarm at the halfway point) fixed the ruck overruns instantly and permanently. The pre-committed denominator made week 4's cut non-negotiable. Set-and-forget pace delivered the criterion at RPE 3. A reformatted session card with the numbers in caps ended a run of misread workouts. Meanwhile, every failure in the block — the 55-minute ruck, the accidental 30, the pace creep, a misread session that added a round and load at once — happened where a decision was left to in-the-moment judgment. And the drift was never random: it always went up.

Discipline held wherever there was a mechanism and drifted wherever there was discretion. For a detrained returner whose aerobic system remembers more than his tendons do, that's not a personality note — it's the design principle. The engine accepts more than the tissue will, and every ceiling reads as a floor. If that describes you, don't plan to be disciplined. Build the mechanism: decide the number before the session, and let a timer, a treadmill belt, or a pre-committed schedule hold it.

The negative result: no, I did not heat-adapt (that I can prove)

Every ruck was outdoors, same 10 lb load, and once temperatures were tagged the heart-rate story looked like this: ~120 bpm in the mild early weeks, 135–140 bpm at ~100°F — 15–19 beats of thermoregulatory drift at constant load, confirmed by the cleanest control the block produced: an unloaded easy walk at 100°F that ran HR 125, above what a loaded 44-minute ruck cost in week 1. Then week 6 produced a single spectacular reading — the block's fastest ruck pace at 98°F, at week-1 heart rate — and for a week it looked like the heat-adaptation objective showing up in data. Week 7 failed to confirm it: slower pace, same temperature, HR back to 140. Four rucks at ~100°F read 135–140; one read 120; the outlier stands unexplained (possibly a strap artifact) and the honest score is: heat drift documented, heat adaptation not demonstrated on this evidence. The practical consequence was real either way — heart rate was uninterpretable as a fitness signal all summer, so RPE and pace carried the block's load-carriage data, which is precisely why effort, not pace, governs hot-weather work.

Adverse events register

Kept clinician-style: an item "appears" when it produces symptoms, and three appearances make it a finding that reprograms the plan.

  • Left posterior knee — mild tenderness. Appearance #1: July 24, at the end of a ruck that overran its window. Appearance #2: August 4, after a treadmill session. My own surface hypothesis (blame the treadmill) was not supported by the log — the first appearance was outdoors, and three quiet treadmill sessions sat between the two. Closed the block at 2 of 3, 33 days quiet. Response: a standing mobility protocol adopted August 5 — post-session calf and hamstring work, a daily foot/ankle block, and twice-weekly eccentric calf raises at low volume with 3–4 days between sessions, dosed per NCCPT guidance on eccentric training.
  • Bilateral first-round knee stiffness — appeared week 1 after a skipped warm-up, then again week 6 despite a full warm-up, which weakened my original attribution. Resolves within one circuit round every time. 2 of 3, 20 days quiet.
  • Right knee, acute — a trip during single-leg work in week 7, mild anterior soreness for the rest of that session only. A 72-hour watch closed clean: 37 continuous minutes the next day and a 50-minute ruck on day four, no residual. Logged as an event, not a register item.

Both open items enter Block 2 at 2 of 3. A third appearance of either is a finding and reprograms the block. The standing line: if soreness becomes pain, changes character, or persists between sessions, that's a physician question, not a programming question.

Limitations

This is one case (n = 1), self-reported, self-scored — the pre-registration constrains the scoring but not the subject. RPE is subjective and demonstrably drifted twice before mid-course correction. Heart-rate data carries three documented confounds: the device's zone display was mis-set and then auto-adjusted underneath the study, summer heat added 15–19 bpm to outdoor work, and one unexplained outlier reading survives. Nearly all running was on a treadmill at 1% incline; outdoor running will move every number. One session is missing entirely (week 5 ruck). The strength "loads" are 20 lb dumbbells and bodyweight — progression at this level says little about loaded barbell work. And the subject's prior athletic history, while long expired, is not nothing: a genuinely never-trained reader should expect the same ladder to feel harder and the same caution to be more necessary, not less.

Citation-accuracy note. Every textbook citation in this report was verified against the source texts before publication, and the check caught errors in my own planning documents that are corrected here: the "single biggest mistake" line is on p. 72 of the Running text, not p. 266 as my plan file cited; the concurrent-training material spans pp. 316–317 of Tactical, not 316 alone. Two rules I had attributed to Tactical p. 219 are actually my operationalizations of it: the text prescribes load-carriage work two to four times per month (weekly was my scheduling choice), and "never progress load and duration in the same step" is my rule derived from the text's progressive-increase language and example program, not a sentence in it. Both remain the rules I trained by — but they're mine, and now labeled as such.

What Block 2 inherits

Block 2 (registered September 6, frozen, running-led) starts from: a banked 37-minute continuous run, two register items open at 2 of 3, a conversion rule for kit failures, an environment tag on every outdoor session, a mobility protocol with a citable dose, and the meta-finding above — which is why its recovery week is already pre-committed to numbers, its long run has a turn-timer, and its easy-pace discipline is a scored criterion this time rather than a watch item. The aerobic system passed its test. The next eight weeks find out whether the tendons agree.

Overall, it has been an interesting and informative experience to have signed off on the plan in July, tracked the execution performance data for eight weeks, and graded my adherence in September.


FAQ

Why freeze the plan before starting? Because hindsight edits are invisible. If the plan can be quietly rewritten to match what happened, adherence is always 100% and the report is fiction. Freezing it means the misses stay visible — and a 31/32 means something a retrofitted 32/32 never could. In my view, it is the most transparent way to hold myself accountable.

Is run-walk really necessary for someone who used to run? For me it was the point. Aerobic fitness returns faster than connective tissue does, which makes a returner's engine the least trustworthy judge of what the ladder should be. The walk breaks are the conservative way to scale up in a sport as demanding as running — and the register above, two knee items from even this careful a ramp, suggests the caution was warranted.

What heart rate should easy runs be? The prescription I trained by was 70–75% of max heart rate, effort conversational, and the exact pace treated as the least important variable (Running 172). In practice the RPE and the conversation test governed, because summer heat made the raw heart rate unreadable for weeks at a time.

Further reading: ISSA, Running Technique and Programming (easy-run prescription and long-run cap, p. 172; recovery weeks, p. 265; effort management, pp. 72, 266; Appendix A on shoe selection, pp. 320–323) · ISSA, Tactical Conditioning (concurrent training, pp. 316–317; load-carriage programming, p. 219) · Weir, J., Understanding and Implementing Eccentric Training, NCCPT CE.

ISSA-certified Running Coach; strength and conditioning work draws on ISSA's Tactical Conditioning curriculum (studied, not examined). This is one documented case plus the certifying doctrine, not medical advice. If you've been inactive for a long time or have a health condition, check with a physician before starting.

Keep reading

Newsletter

Gear notes, trail picks, no fluff.

Occasional emails when we publish something worth your time. Unsubscribe anytime.

More about what you'll get on the newsletter page.