When a reader we'll call "Runner M" first wrote to us, she wasn't asking about shipping. She was asking whether a structured training log could survive the 9-hour time difference between Karachi and her coach in Toronto. She'd signed up for a spring half marathon, bombed the build, and wanted to know if the problem was her legs or her record-keeping. We followed her next 24 weeks closely. The short version: the legs were fine. The log was the leak.
Her fix came from an unlikely corner — a running community journal called Woodstockharriers, which she'd stumbled onto while looking for 5K plans that didn't assume a flat, cool, sea-level morning. What follows is a timeline of what she did, where it broke, and what the numbers looked like at the end.
The starting position: 24 weeks, one blown build
Runner M's baseline was honest but modest: a 26:40 5K from the previous winter, roughly 28 km per week across four runs, and a stubborn habit of treating every easy day like a tempo day. Her first half marathon attempt in October ended at 2:14 — not a disaster, but 11 minutes slower than her own projection. She had the fitness. She didn't have the evidence trail.
That's the gap training logs are supposed to close. Hers lived in three places: a phone app she forgot to sync, a paper diary with two missing weeks, and voice notes she never transcribed. When her coach asked why the long runs kept falling apart, neither of them could point to a single data point. They were guessing.
The decision point: a journal, not another app
In early January she committed to a 24-week plan built around three pillars: a Tuesday interval session, a Thursday easy-zone run, and a Saturday long run that would climb from 14 km to 30 km. Everything else — the warm-ups, the cooldowns, the days she felt awful — went into a single written log she updated within an hour of finishing, no exceptions.
She chose Woodstockharriers as her reference point partly for the plan structure and partly for the race recaps, which she said read like someone who had actually suffered on the same courses. The journal's training logs gave her a format: date, distance, average pace, perceived effort out of 10, and one sentence on how it felt. Five fields. Nothing fancy. The discipline was in the fifth field.
Obstacles: heat, Ramadan, and a calf strain
Three things went wrong, and all three are worth naming because they're the reason the log mattered.
- April heat. Karachi mornings hit 34°C by week 9. Her Tuesday intervals had to move to 5:15 a.m. or get cut. The log showed her that interval pace dropped about 8 seconds per kilometre in heat — useful, because it stopped her from panicking.
- Ramadan scheduling. Four weeks of training shifted to post-Iftar runs. Volume fell 22%, but the log kept the streak alive at four sessions a week, and the easy-zone runs actually improved because she was forced to slow down.
- A calf strain in week 17. This was the real test. Her instinct was to push through. The log said otherwise: three consecutive sessions with effort ratings of 8/10 on runs that should have been 4/10. She took nine days off, cross-trained on a stationary bike, and returned without losing more than a week of fitness.
That nine-day break is the kind of decision that's almost impossible to make without a written record. Memory flatters us. Logs don't.
What the numbers showed
By week 24, the picture was clear. Weekly volume had stabilised at 42 km, up from 28 km. Her 5K time trial in week 20 came in at 24:12 — a 2:28 improvement on her baseline. The half marathon, run on a flat coastal course in slightly cooler conditions, finished at 1:58:47. She broke two hours for the first time.
More interesting than the race result was the consistency data. Across 24 weeks she completed 91 of 96 planned sessions — a 94.8% adherence rate. In the previous build, by her own estimate, she'd finished maybe 70%. The difference wasn't motivation. It was visibility.
We asked her what she'd tell another runner starting the same process. Her answer was blunt: pick one place to write things down, and write them down the same day. Everything else follows from that.
What this means for cross-border runners
There's a lesson here that goes beyond one runner's season. If you're buying gear, books, or recovery tools from abroad — a heart-rate strap, a pair of trail shoes, a foam roller that isn't stocked locally — the friction isn't the product. It's the logistics: the U.S. or U.K. address you don't have, the consolidation, the customs paperwork, the last-mile delivery that turns a two-week wait into a two-month saga. That's the part a concierge service handles, so the training log stays the only thing you have to think about.
Runner M's gear arrived in 11 business days, fully insured, with no customs surprises. She logged the unboxing like everything else. Old habits.
The takeaway
Woodstockharriers reports 24 weeks of structured plans and race recaps for harriers at every pace, and that framing is the point: the journal doesn't promise speed, it promises a record. Runner M didn't get faster because she read more. She got faster because she could finally see what she was doing — and stop doing the parts that weren't working.
If you're rebuilding a season, start with the log. The rest is arithmetic.